30 second delay before ping command will succeed


In a site-specific networking environment (other sites do not
experience this problem), we consistently observe a 30 second delay
from the time the networking cable is plugged into the system and the
time that the ICMP ping command will succeed.

Requests to ping the server within this 30 second period from initial
network connection will timeout.

It is an important feature of our application to dynamically
connect/disconnect from various networks.

Does anyone have any ideas on how to troubeshoot/eliminate this 30
second delay?

Thanks in advance for your thoughts on this issue.

A. Irish

.

Relevant Pages

  • Re: The specified network name is nolonger available
    ... Look in properties -> networking for your network connection ... Where exactly shall I find this "networking" property? ... > (you must have been logged on as administrator on notebookaa) ... > Desktop1 was not listening at all. ...
    (microsoft.public.win2000.networking)
  • RE: Network Connection from recovery console
    ... There is no networking built into Recovery Console. ... <X-Newsreader: Microsoft Outlook Express 6.00.2900.2670 ... <How can I established a Network Connection from the Recovery Console from ...
    (microsoft.public.windows.server.general)
  • Re: Network Connection from recovery console
    ... There is no networking built into Recovery Console. ... > a very limited enviroment while in Recovery Console and networking is not ... > <How can I established a Network Connection from the Recovery Console from ...
    (microsoft.public.windows.server.general)
  • Re: The specified network name is nolonger available
    ... Look in properties -> networking for your network connection ... Where exactly shall I find this "networking" property? ... he means networking properties but we still need to see ipconfig /all ... for both computers. ...
    (microsoft.public.win2000.networking)