Telnet or TCP/IP timeout

[Mike Linger]

I have an isolated LAN with no gateway nor DNS. I have
one HP-UX server and one Win2000 PC on my network. Telnet
from the PC to the server takes exactly 75 seconds to
connect. Once connected, the traffic behaves normally.
What's wrong? Why does it take 75 seconds to connect?

Windows 2000 IP Configuration

Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R)
PRO/100 VE Network Connection #2
Physical Address. . . . . . . . . : 00-07-E9-AB-F6-
17
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 129.4.204.2
Subnet Mask . . . . . . . . . . . : 255.255.254.0
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . :

 

[Madhur Ahuja]

I have an isolated LAN with no gateway nor DNS. I have
one HP-UX server and one Win2000 PC on my network. Telnet
from the PC to the server takes exactly 75 seconds to
connect. Once connected, the traffic behaves normally.
What's wrong? Why does it take 75 seconds to connect?

Windows 2000 IP Configuration

Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R)
PRO/100 VE Network Connection #2
Physical Address. . . . . . . . . : 00-07-E9-AB-F6-
17
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 129.4.204.2
Subnet Mask . . . . . . . . . . . : 255.255.254.0
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . :

Hello
Address resolution might be taking the time. Try telnetting by directly
giving the IP addresses and post back the results.

--
Winners dont do different things, they do things differently.

Madhur Ahuja
India

Homepage : http://madhur.netfirms.com
Email : madhur<underscore>ahuja<at>yahoo<dot>com

 

[Guest]

I've always been using the dotted IP:

telnet 129.4.204.154

There shouldn't be any resolution. It takes exactly 75
seconds to connect every time.

I've been looking at parameters in the registry. I'm set
to a broadcast node. Many of the timeout values are small
such as 1.5 seconds. The retry attempts are all set to 3
for DNS and WINS, even though I shouldn't be making an
attempt on these services.

I've just re-installed the OS. It still takes exactly 75
seconds. When I connect the server to the building
network (with DNS and maybe some other services), I get an
immediate telnet connection.

The worst part is that I have another identical system (1
server, 1 hub, 1 PC) that doesn't have this problem. I
don't see a difference in the two configurations.

 

[Mike Linger]

I've tried three telnet clients (Bundled Win2K,
Hummingbird, PuTTY) using a dotted IP. All three clients
take exactly 75 seconds to connect.

I've tried two FTP clients (Bundled Win2K, Hummingbird).
Both of them timeout.

When I connect the server to the building network with a
DNS and some other services, other PCs connect via telnet
immediately.

 

[Jim Hughes]

Perhaps the HP-UX telnet daemon is configured to do a reverse DNS lookup of
clients.

As a quick fix, try adding the IP address and name of the Win 2000 PC to
/etc/hosts on the HP-UX box.