1847084 Members
5416 Online
110262 Solutions
New Discussion

Re: FTP problems

 
JOHN TURNER_2
Frequent Advisor

FTP problems

We have three servers called athos, aramis and porthos. when we try and ftp to these servers from any other server we get the error message

421 Service not available, remote server has closed connection

however if we FTP out of these machines it will let us do it provided it's not to any of the three machines listed above.

can anyone shed any light on this subject
john
GUI's are for wimps!
4 REPLIES 4
A. Clay Stephenson
Acclaimed Contributor

Re: FTP problems

I suspect that the ftp daemon is not running. That would in no way impact the same box's ability to launch the ftp client.

Examine /etc/inetd.conf and see if the ftp entry is enabled. If it has been commented out, then uncomment the line and issuer an "inetd -c" to force a reread of the file by the inetd daemon.
If it ain't broke, I can fix that.
Brian Bergstrand
Honored Contributor

Re: FTP problems

Are you sure ftpd is configured in /etc/inetd.conf and the ftp ports are listed in /etc/services (or your NIS master)?

Is there an open socket listenting for FTP connections on the servers in question?

netstat -a | grep ftp | grep LISTEN

HTH.
Steven E. Protter
Exalted Contributor

Re: FTP problems

The only other possibility to Clay's answer(which I think is right) is that the /etc/services file is messed up or a firewall has port 21 blocked.

You might want to enable enhanced logging in /etc/inetd.conf inetd -c and watch the log files while testing.

tail -f /var/adm/syslog/syslog.log

then attempt the ftp command. The error message will help you a lot. If there is no message, then the connection is being blocked between the machines.

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Steven Gillard_2
Honored Contributor

Re: FTP problems

Also check the /var/adm/inetd.sec file on the three servers - you could be restricting access to certain IPs in there.

From the error it sounds like the connection is being accepted (indicating that inetd is listening) but torn down straight away.

Regards,
Steve