Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Windows XP DNS issue

Status
Not open for further replies.

RunNetworkRun

IS-IT--Management
Sep 23, 2003
4
US
Last week our entire class C network was renumbered. I'm running Windows 2000 AD with DNS and everything came back up great. Now, after being logged in for a few minutes, my windows XP clients stop doing DNS lookups. This problem only affects XP clients, we have several 2Kpro boxes that stay running. When I run ipconfig /all, I get the one DNS server listed: 192.168.10.3 but when I run nslookup on the client, it defaults to 10.0.0.3 (an old server address). I can't figure out where it's getting this information from. The server is not listing that address anywhere and the cache has been cleared on the clients and the server numerous time. I have been in the network control panels and I can't figure out why nsloopkup is defaulting to this dead address. If I change the server in nslookup to 192.168.10.3 (what ipconfig says it is), I can do DNS queries in nslookup all day long. Like I said before, the weird thing is that this only affects our XP boxes (about 8 of 35 machines). Any ideas would be appreciated. Thanks!
 
Running fixed ip's or dhcp? Try searching the registry for the old server numbers. Good luck.

Glen A. Johnson
"Give the laziest man the hardest job and he'll find the easiest way to do it."

Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884
 
Weird!!! Maybe there's an entry it your hosts file. Remove any entry referring to 10.0.0.3 (but I guess no entry there:))

C:\winnt\system32\drivers\etc\hosts


Can you ping hostname and ip address?

Can you ipconfig/all for both PC and server.
 
The issue was with an old group policy our site administrator had put in to place and forgot about. Apparantly, one of the service packs removed the option to set DNS servers so he wasn't able to view the setting that was taking the machines offline. The fix was to make some registry changes on the client and then use 2003 tools to change the policy. I'd like to say we figured it out on our own, but we called Microsoft in.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top