FTP fails although telnet works

[shri Kanekal]

Hi,
I have recently become "system manager" on an old VAX
Alpha and have been trying to set up FTP on it. The machine
already had FTP setup but in its new location (on a new network) has stopped working. Telnet works and FTP fails with
SAMPEX$ ftp localhost
421 Service not available, Remote server has closed the connection

From reading previous posts in this forum I have tried to fiddle around but to no avail. If anybody can help it would be greatly appreciated. (I am appending some details from
UCX)
Thanks
Shri

UCX> sh ver

DIGITAL TCP/IP Services for OpenVMS Alpha Version V4.2 - ECO 1
on a Digital Personal WorkStation running OpenVMS V7.1-2

UCX> sh serv ftp /ful

Service: FTP
State: Enabled
Port: 21 Protocol: TCP Address: 0.0.0.0
Inactivity: 5 User_name: UCX$FTP Process: UCX$FTPD
Limit: 10 Active: 0 Peak: 1

File: SYS$SYSDEVICE:[UCX$FTP]UCX$FTPD_STARTUP.COM
Flags: Listen

Socket Opts: Keepalive Rcheck Scheck
Receive: 0 Send: 0

Log Opts: None
File: not defined

Security
Reject msg: not defined
Accept host: 0.0.0.0
Accept netw: 0.0.0.0

UCX> sh dev bg104 /ful
Device_socket: bg104 Type: STREAM LOCAL REMOTE
Port: 21 0
Host: 0.0.0.0 0.0.0.0
Service: FTP

RECEIVE SEND
Queued I/O 0 0

Q0LEN 0 Socket buffer bytes 0 0

QLEN 0 Socket buffer quota 8600 9700

QLIMIT 5 Total buffer alloc 0 0

TIMEO 0 Total buffer limit 34400 38800

ERROR 0 Buffer or I/O waits 0 0

OOBMARK 0 Buffer or I/O drops 0 0

I/O completed 11 0

Bytes transferred 0 0


Options: ACCEPT REUSEADR KEEP
State: PRIV
RCV Buff: None
SND Buff: None

[Andy Bustamante]

Please show the results from

$ UCX SHOW HOST
$ UCX SHOW CONFIG INTERFACE

Does the the address assigned to the network interface have a listed host name? Since you say "new network" Was the address properly changed and host entry created? Properly changed means with either sys$manager:ucx$config.com or appropraite UCX commands, you should not edit UCX configuration files manually.

Correct with:
$ @sys$manager:ucx$config

Please try to connect to yourself with both

$ ftp a.b.c.d ! your address here
$ ftp 0

[Steven Schweda]

> SAMPEX$ ftp localhost
> 421 Service not available, Remote server has closed the connection

The FTP service seems to be available, but
having trouble. If were completely dead,
then I'd expect something more like this:

alp $ ftp localhost
%TCPIP-E-FTP_NETERR, I/O error on network device
-SYSTEM-F-REJECT, connect to network object rejected


You might look at the FTP server log file.
Nowadays it's:
SYS$SYSDEVICE:[TCPIP$FTP]TCPIP$FTP_RUN.LOG

I'd guess that if you change "TCPIP" to "UCX"
everywhere, then you might find yours.

> Log Opts: None
> File: not defined

Well, you might need to define the log file
first. I see nothing in TCPIP HELP, but the
config procedure suggests something like:

$TCPIP set serv ftp -
/log=(file:sys$sysdevice:[TCPIP$ftp]TCPIP$ftp_run.log, all)

Again, "TCPIP" -> "UCX" for an old version.


> $ @sys$manager:ucx$config

Going through that whole thing again might be
the easy way.

[John Gillings]

Could be SYLOGIN.COM is doing something which only works for an interactive login.

Simplest test is to change the first line to:

$ EXIT

and retry your FTP connecting.

[P Muralidhar Kini]

Hi Shri,

Welcome to the ITRC forum.

>> Telnet works and FTP fails

You need to check whether the FTP server is enabled.
Also need to check if SYLOGIN.COM file to check if it encountered any error
as it could lead to FTP getting disabled.

The following link talks more about this -
http://forums13.itrc.hp.com/service/forums/questionanswer.do?threadId=1434742

Hope this helps.

Regards,
Murali

[Shriniketan Bhagwat]

Hi Shri,

Can you try restarting the FTP service on your machine? There was a discussion on similar topic in the below thread.

http://forums11.itrc.hp.com/service/forums/questionanswer.do?admit=109447626+1274178128562+28353475&threadId=698290

May be helpful.

Regards,
Ketan

[Steven Schweda]

> You need to check whether the FTP server is
> enabled.

You mean like this?:

> UCX> sh serv ftp /ful
>
> Service: FTP
> State: Enabled
> [...]

I think that that's been done already.

[P Muralidhar Kini]

Steven,

>> I think that that's been done already.
Ahhh. How can i miss the data in the very first post!

>> UCX> sh serv ftp /ful
>>
>>Service: FTP
>> State: Enabled
Yes, FTP server is started as per the output provided.

Regards,
Murali

[Bhadresh]

Hi,

Please have a look at following thread:

http://forums11.itrc.hp.com/service/forums/questionanswer.do?&threadId=1219348

Regards,
Bhadresh

[Steven Schweda]

> Please have a look at following thread:
> [...]

I'll bite. How is that (name resolution)
problem relevant to this FTP server problem?

[shri Kanekal]

Thanks for all the suggestions. Sidestepping SYLOGIN.COM
with a $EXIT as John suggested, did not solve the problem. Here is the output for Andy's suggestions. Something seems off here but I dont know how to correct it.

UCX> sh host

LOCAL database

Host address Host name

127.0.0.1 LOCALHOST, localhost
128.8.5.2 NOC.UMD.EDU
128.244.181.106 ULEIS.JHUAPL.EDU, ULEIS
129.2.162.17 UMTOF3.UMD.EDU, IMP8.UMD.EDU
128.8.162.1 csc1hub-gw.umd.edu
128.8.74.2 cville-srv.umd.edu
128.138.131.1 lasp
128.138.131.2 lasp.colorado.edu
128.138.131.55 sampex, SAMPEX
128.8.76.2 wor-srv.umd.edu
%UCX-W-BIND_NOSERVNAM, Server with address 128.138.131.55 is not responding
%UCX-E-BIND_NOSERVERS, Default servers are not available
%UCX-W-NORECORD, Information not found
-UCX-E-BIND_NOSERVERS, Default servers are not available
UCX> sh config interface

Interface: WE0
IP_Addr: 128.138.131.55 NETWRK: 255.255.255.192 BRDCST: 128.138.131.63

Interface: LO0
IP_Addr: 127.0.0.1 NETWRK: 255.0.0.0 BRDCST:
UCX> sh route

DYNAMIC database

Type Destination Gateway

AH 127.0.0.1 127.0.0.1
AH 128.138.131.55 128.138.131.1
AN 0.0.0.0 128.138.131.1
AN 128.138.131.0 128.138.131.55

[Steven Schweda]

Apparently, 128.138.131.55 is not the best
choice for a name server. It seems not even
to have a name:

ALP $ nslookup 128.138.131.55
Server: alp-l.antinode.info
Address: 10.0.0.9

*** alp-l.antinode.info can't find 128.138.131.55: Non-existent host/domain

Why did you choose it?

Better candidates:

ALP $ nslookup -type=ns COLORADO.EDU
Server: alp-l.antinode.info
Address: 10.0.0.9

Non-authoritative answer:
colorado.edu nameserver = oldduke.colorado.edu
colorado.edu nameserver = otis.colorado.edu
colorado.edu nameserver = boulder.colorado.edu

Authoritative answers can be found from:
otis.colorado.edu internet address = 128.138.129.76
boulder.colorado.edu internet address = 128.138.240.1
boulder.colorado.edu internet address = 128.138.238.18
oldduke.colorado.edu internet address = 128.138.130.30

Or perhaps these:

ALP $ nslookup -type=ns umd.edu
Server: alp-l.antinode.info
Address: 10.0.0.9

Non-authoritative answer:
umd.edu nameserver = ns2.umd.edu
umd.edu nameserver = noc.umd.edu
umd.edu nameserver = ns1.umd.edu

Authoritative answers can be found from:
noc.umd.edu internet address = 128.8.5.2
ns1.umd.edu internet address = 128.8.74.2
ns2.umd.edu internet address = 128.8.76.2

depending on where you actually are.

But I doubt that that's the FTP server
problem.


> Something seems off here but I dont know
> how to correct it.

At least something.

> $ @sys$manager:ucx$config

That seemed to me to be a good place to
start.

[shri Kanekal]

I found a temporary workaround to FTP going -
$@UCX$FTPD_STARTUP

gets FTP up and running - however it locks out a terminal
and a user. The startup procedure when run using loginout
however does not result in getting FTP going.

Shouldnt the UCX$FTPD_STARTUP start on its own whenever
a client tries to access the server ?

[Steven Schweda]

> Shouldnt the UCX$FTPD_STARTUP start on its
> own whenever
> a client tries to access the server ?

More or less. It seems pretty likely that
you should _not_ be trying to run it
interactively.


> > $ @sys$manager:ucx$config
>
> Going through that whole thing again might be
> the easy way.

Did you ever try that?


Did you ever define the log file for the FTP
service (and its options)?


Do you ever answer any questions, or do you
only ask more?

[shri Kanekal]

Jul 6, 2010 22:22:02 GMT points for answer:
> Shouldnt the UCX$FTPD_STARTUP start on its
> own whenever
> a client tries to access the server ?

>>More or less. It seems pretty likely that
>>you should _not_ be trying to run it
>>interactively.

That is the only way I have been able to
get the FTP going

> > $ @sys$manager:ucx$config
>
> Going through that whole thing again might be
> the easy way.

>>Did you ever try that?

Yes multiple times


>>Did you ever define the log file for the >>FTP service (and its options)?

Yes

>>Do you ever answer any questions, or do you
>>only ask more?
"ever" ? so far I have asked only two questions

[Steven Schweda]

> >>Did you ever try that?
>
> Yes multiple times

Ok. What does "UCX SHOW SERVI /FULL FTP"
say now?

> >>Did you ever define the log file for the
> >>FTP service (and its options)?
>
> Yes

Swell. Did you ever get a log file? Was
there anything in it? Or should I know these
things already?

> so far I have asked only two questions

> [...] If anybody can help [..]

> Something seems off here but I dont know
> how to correct it.

> Shouldnt the UCX$FTPD_STARTUP start on its
> own whenever
> a client tries to access the server ?

Perhaps we're not counting the same things.