Networking Forums

Networking Forums > Computer Networking > Linux Networking > cannot access ftp server -- getpeername (in.ftpd): Transport endpoint is not connected

Reply
Thread Tools Display Modes

cannot access ftp server -- getpeername (in.ftpd): Transport endpoint is not connected

 
 
Matthias Hupp
Guest
Posts: n/a

 
      05-17-2004, 03:58 PM
Hello,

maybe one of you can help me with this problem:

The ftp server on a web/mail/inet-gateway machine I am taking care of can
no longer be accessed, ever since one of the secretaries decided to
switch it off and on again because she could not access her files on a
Windows server. I have made some changes on the ipchains rules since
then, but ftp is open on the external interface.

Anyway, access is possible neither from the LAN, nor from the machine
itself when I am logged on via ssh.

I get this message on the shell:
***
# ftp localhost
Trying ::1...
ftp: connect to address ::1: Connection refused
Trying 127.0.0.1...
Connected to localhost.
421 Service not available, remote server has closed connection.
***

and this turns up both in /var/log/warn and /var/log/messages:
***
May 17 13:01:01 server in.ftpd[12726]: warning: can't get client address:
Invalid argument
May 17 13:01:01 server ftpd[12726]: getpeername (in.ftpd): Transport
endpoint is not connected
May 17 13:01:01 server inetd[813]: /usr/sbin/tcpd: exit status 0x1
May 17 13:01:01 server in.ftpd[12727]: warning: can't get client address:
Invalid argument
May 17 13:01:01 server ftpd[12727]: getpeername (in.ftpd): Transport
endpoint is not connected
May 17 13:01:01 server inetd[813]: /usr/sbin/tcpd: exit status 0x1
May 17 13:01:01 server in.ftpd[12728]: warning: can't get client address:
Invalid argument
May 17 13:01:01 server ftpd[12728]: getpeername (in.ftpd): Transport
endpoint is not connected
May 17 13:01:01 server inetd[813]: /usr/sbin/tcpd: exit status 0x1
May 17 13:01:01 server inetd[813]: ftp/tcp server failing (looping),
service terminated
***

.... repeated over and over again, with rising pids.
Trying other ftp servers (by changing inetd.conf) resulted in the same,
with in.ftpd changed to proftpd etc.
BTW, the name of the machine is included in /etc/hosts.

Have any of you had that problem? Please help, running out of time...
Looking for old threads that included these error messages only turned up
tons of hacking-related questions.

Thank you!

Matthias
 
Reply With Quote
 
 
 
 
Matthias Hupp
Guest
Posts: n/a

 
      05-17-2004, 04:36 PM
Correction: ftp is not open on the external interface, jus on the internal
one, as it should be.
 
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
I can't access files in my VPN server when connected via VPN Allie Windows Networking 3 03-30-2007 10:13 PM
Squid error: Transport endpoint is not connected billbo Linux Networking 0 03-28-2006 07:42 PM
Newbie can't log into his own wu-ftpd server... ANTant@zimage.com Linux Networking 15 02-21-2005 12:39 AM
problem: Transport endpoint is not connected Spiral Linux Networking 0 07-11-2004 09:26 AM
using hardware vpn endpoint and server 2003 krag Windows Networking 0 01-04-2004 02:02 AM



1 2 3 4 5 6 7 8 9 10 11