Linked by Adam S on Tue 28th Sep 2004 22:29 UTC
I've been using Windows as a network administrator for just over 6 years now. I've used NT4 servers, 2000 servers, and Windows 2003, and there has been a tremendous improvement with each version. There are still some things that drive me nuts in my job, though, and this is a chronicle of the top five.
Permalink for comment
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Recent Original Stories
Recent Comments
Headlines
Random Comments
Random Stories
Random OS Link
I've run into this problem on XP machines... basically what is happening is that if the DNS client service's connection to a DNS server in your DNS server list times out then it drops the DNS server from the list. This is particularly frustrating if you have a local DNS server listing hosts for your local network as your primary DNS and an external DNS as your secondary. If your primary doesn't respond in time (I haven't figured out what the default timeout is) it gets dropped and then your machine can't resolve local hostnames.
The only way I've found to resolve this is to disable the DNS Client service. I haven't found any detrimental effect of this as it's just a chaching DNS server anyway. This resolves the issue and I wish it would come as disabled from the get-go.