|
|
At 09:41 PM 4/30/2002 +0100, you wrote:
On Tuesday 30 April 2002 9:26 pm, Andrew Greenburg wrote:
> ftpd[1394]: getpeername (in.ftpd): Transport endpoint is not connected
Never seen that before - does anyone else know what this means ?
> I've checked this, and I'm not seeing any packets destined for TCP port
> 113. I'm fairly positive that in the past I used to see these packets.
Okay, if you've seen ident packets in the past, but you're not now, two
things come to mind:
1. Are the servers trying to use some other form of authentication (but you
say their configuration hasn't changed either, and you're obviously the admin
of at least one of them...) ?
2. Is some other packet filter in between blocking the ident packets, and
thus causing the delay in authenticating the client ?
Well, scratch that. I _am_ seeing ident packets; it just threw me off
because I was getting delays on pop3 and just assumed that it must be an
ident problem.
Can you try running nmap from the server end, at the same time as a packet
sniffer at the client end, and see if some ports (eg 113) seem to be getting
blocked along the way ?
It's the only thing I can think of that could cause this, and is outside your
control if you look after both client and server machines.
I ran a port scan, and it doesn't look like ports are being blocked, so I'm
going to assume it's a DNS issue until I can determine otherwise.
--
Andrew M. Greenburg | agreenbu @ in-span . net
Systems Engineer | (317)234-1001 (317)234-1328
Indiana Web Academy | Phone Fax
|
|