J
Jim Garrison
System is a P3 600 MHz with 256MB connected to a 100Mb/s network,
running Win2K SP2 with all current security patches applied.
Any operation involving TCP/IP, such as connecting to a website,
running ping, netstat command, even "ipconfig /all", all start with
about a 20 second delay and then complete normally.
It makes no difference whether or not DNS is involved, as even ping to
a local IP address has the same delay. The delay seems to occur in the
opening of the socket, because all the ping packets show <10ms time,
with no packets lost. What's even more curious is that pinging my own
IP address, or even 127.0.0.1, gets the same 20-second delay in
initiating the connection. Once the connection has been initiated, the
network itself operates at normal speed until you need to open another
connection.
I've verified that the network card, cable hub and central ethernet
switch are operating correctly. I've also checked the Internet
options to ensure it's not looking for a proxy server (we don't use a
proxy).
The fact that "ping 127.0.0.1" experiences the same delay indicates to
me it's internal to that box's TCP/IP stack and does not involve the
network at all.
If I try a ping (any IP address) with the system otherwise quiescent,
I can hear some repetitive disk activity with a period of about 2
seconds during the long delay. The disk activity occurs during the
delay but not before or after.
Curiously, there is one operation that does NOT incur a 20-second
delay, and that's connecting to or accessing a network share.
I'm completely mystified. Anyone else see this?
running Win2K SP2 with all current security patches applied.
Any operation involving TCP/IP, such as connecting to a website,
running ping, netstat command, even "ipconfig /all", all start with
about a 20 second delay and then complete normally.
It makes no difference whether or not DNS is involved, as even ping to
a local IP address has the same delay. The delay seems to occur in the
opening of the socket, because all the ping packets show <10ms time,
with no packets lost. What's even more curious is that pinging my own
IP address, or even 127.0.0.1, gets the same 20-second delay in
initiating the connection. Once the connection has been initiated, the
network itself operates at normal speed until you need to open another
connection.
I've verified that the network card, cable hub and central ethernet
switch are operating correctly. I've also checked the Internet
options to ensure it's not looking for a proxy server (we don't use a
proxy).
The fact that "ping 127.0.0.1" experiences the same delay indicates to
me it's internal to that box's TCP/IP stack and does not involve the
network at all.
If I try a ping (any IP address) with the system otherwise quiescent,
I can hear some repetitive disk activity with a period of about 2
seconds during the long delay. The disk activity occurs during the
delay but not before or after.
Curiously, there is one operation that does NOT incur a 20-second
delay, and that's connecting to or accessing a network share.
I'm completely mystified. Anyone else see this?