Tom's Guide | Tom's Hardware | Tom's Games
![]() |
![]() |
![]() |
We have been experiencing a problem for several months. We are running a DNS server on a Windows 2000 machine. Our network consist of several hindred clients, the bulk of which are wireless laptops either running Windows XP Pro or Windows 98 SE.
The problem is seen first on our XP clients. When it is occuring, they will take around 4 or 5 minutes to logon to our domain. When working normally, this process is less than 30 seconds. Anyone launching Outlook during this time can expect a time out when logging onto Exchange. Our 98 clients experience it as a general slowdown in network activity although I don't as much about the symptoms on those machines.
To solve this, I stop the DNS Server service. The bar that tracks the time of the shutdown will get to about 50%. Then we get an error that the service took too long to shut down. After about 10 minutes, the service is showed as stopped. We can restart the service and everything works great until the next time this happens.
Can someone tell me where to start tackling this problem. No errors are jumping out at me in the event log but I might not know what to look for.
Any help appreciated.
chip

This machine is also a file and print server. There probably is always something going on. I should look more carefully at what is running when it happens.
When our kids leave for Christmas, I will try a reinstall.

![]() |
explorer.exe failure
|
Problem with Win2000 shut...
|

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |