Operating System - OpenVMS
cancel
Showing results for 
Search instead for 
Did you mean: 

FTP fails although telnet works

 
shri Kanekal
Occasional Visitor

Re: FTP fails although telnet works

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
Honored Contributor

Re: FTP fails although telnet works

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.
Highlighted
shri Kanekal
Occasional Visitor

Re: FTP fails although telnet works


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
Honored Contributor

Re: FTP fails although telnet works

> 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
Occasional Visitor

Re: FTP fails although telnet works

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
Honored Contributor

Re: FTP fails although telnet works

> >>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.