This error makes it appear that you are having a DNS name resolution problem. When in a broken state, open a command prompt and type "ipconfig
/flushdns". Try accessing the page again. Does this work? If so, it appears that something is return negative responses to your DNS queries. The DNS client
on Windows 2000 caches this information for up to 15 minutes. Disabling the caching of negative responses may help. To do this on a Windows 2000 pro box,
open Regedit and go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Dnscache\Parameters. Set the value for NegativeCacheTime to
"0". Also set the value NegativeSOACacheTime to "0" as well. If either of these values does not exist, you will need to create them. To do this, right click on
the right pane and choose New>DWORD Value.
If this helps, it's really only masking another problem. You may need to investigate the DNS servers your client is pointing to. These DNS servers may be
either returning incorrect information or not able to resolve the names themselves. If these servers are under your control, then install Network Monitor on them
and start some traces. When a DNS failure occurs, the traces may shed some light as to the real cultprit.
Microsoft Network Support
This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at
Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from which they originated.