Tom's Guide | Tom's Hardware | Tom's Games
 |
 |
 |
Hi,
I've got a Windows 2003 DHCP server on the network which should assign DNS servers of 192.168.50.4 and 192.168.50.5.
When certain clients log on and I run ipconfig /all the DNS server is set to 192.168.0.1 - all the other DHCP settings are correct.
If I run ipconfig /renew it fixes the problem - BUT as the day goes on machines revert back to having DNS set to 192.168.0.1. The affected machines are all set to "obtain dns server addresses automatically"
Thanks
Sounds that there is another DHCP server running like a dsl router or something like that.
And so the first one wins and assigns ip and dns information to the clients.
So make sure, that only one DHCP server is running at your network.
0 
Hi,
Thanks, that was my first thought, but I cant find anything else that could be doing this.
On the affected clients when I run ipconfig /all the DHCP Server which is shown is correct.
Also i've had dhcploc.exe running and thats not found any rogue servers.
It is very confusing.
0
Ok, so if the clients gets the DNS server 192.168.0.1, what happens when you ping this IP address.
Did you get a response?Try ping -a 192.168.0.1
With a little luck, you also get the name of the machine with that IP.
This should give you an idea on where to start searching.
0 0 0
All the other DHCP settings are correct, ip address, mask, gateway, wins - its just the DNS entry that is wrong.
0
Have you already tried to clear the arp cache and the dns cache at those workstations?
arp -d
ipconfig /flushdns
0
On the problem PC try this from a command prompt:
ipconfig /flushdns
and then release and renew.
I'm thinking maybe that was the PC you used to configure the router originally, or was connected to the router prior to you changing the subnet to .50 and it's trying to use dns info that's cached locally. Doing a /flushdns will hopefully clean any cached dns info and the unit will start picking up the correct info from your DHCP server.
It's worth a try anyhow.
If that doesn't fix the issue, open up the property sheet for your NIC and check the properties on your TCP/IP stack. If you had statically assigned it TCP/IP info previously with that address configured as your DNS, that could be causing it too if you didn't actually delete the DNS address.
MS's TCP/IP stack has a bad habit of not getting rid of the DNS address when you change from static to DHCP.
0  |
 |
 |
This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |
