|
|
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 ?
> >If you don't want to change the firewall, put a packet sniffer on the
> > outside (ethereal would do nicely) and see if you're getting ident
> > requests back from the servers with the delays.
>
> I think this is the next step.
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.
Antony.
|
|