Very Computer

Hi,
I have just installed 2.0.30 (Redhat) on a couple of Linux boxes and am
having a strange problem when I try and connect from Win 95 box. E.g. if I
ftp to the Linux box, I observe the 'connected' message immediately, bu the
username prompt does not show up for a couple of minutes. same for telnet.
If however I connect from the other Linux box, it is fine.

I captured some traces and can't see any difference in the first 3 (SYN,
SYN/ACK, ACK) handshake other than the fact that the TTL on the win95 box
is 32 whereas on the Linux boxes it is 64. I am not sure if this is
significant. However, on the Linx connection the server responds
immediately with a packet whereas on the win95 client, the server packet is
sent after over 150 secs have elapsed.

Any help would be sincerely appreciated.

Paul

: Hi,
: I have just installed 2.0.30 (Redhat) on a couple of Linux boxes and am
: having a strange problem when I try and connect from Win 95 box. E.g. if I
: ftp to the Linux box, I observe the 'connected' message immediately, bu the
: username prompt does not show up for a couple of minutes. same for telnet.
: If however I connect from the other Linux box, it is fine.

: I captured some traces and can't see any difference in the first 3 (SYN,
: SYN/ACK, ACK) handshake other than the fact that the TTL on the win95 box
: is 32 whereas on the Linux boxes it is 64. I am not sure if this is
: significant. However, on the Linx connection the server responds
: immediately with a packet whereas on the win95 client, the server packet is
: sent after over 150 secs have elapsed.

: Any help would be sincerely appreciated.

Sounds like name lookup is bombing, or maybe identd.

-harold

Quote:> From your linux machine (the one you are telnetting to), what happens
> when you do "nslookup" for your various machines (or try to ping them
> by name)? What happens when you do a reverse lookup ("nslookup a.b.c.d"
> where a.b.c.d is the IP address)?

> Paul