1
1
I have a windows domain with DNS that forwards to my ISP and DHCP that passes out addresses in the 10.0.0.X range.
Things were fine until recently, now when I reboot I get a 192.168.40.X address with an invalid DNS server so I can't access any network resources or the internet.
When I manually change the ip to a 10.0.0.X adress and then back to obtain an address and dns server it can talk to the DHCP server and pulls a good address along with a DNS server and default gateway and everything works for a while.
Also, it randomly reverts back to the private range, but i can do an ipconfig /renew to fix it when this happens. I'm assuming because the 10.0.0.x address is cached.
What would cause it to not pull a address from my DHCP server when I boot, and why does it keep reverting to the 192.168.x range?
1I agree with @heavyd you probably have a rogue DHCP server on that same VLAN in your network. I would set up DHCP snooping, if you have Cisco, and try to find him or her. If not ping the default gateway that was assigned when you got the 192.168 network and look at the ARP cache then go around to your switches looking for the MAC address that you saw in your ARP cache. Most likely the default gateway is the person that has set up the DHCP server, not a sure thing though. – matak – 2012-11-15T00:26:31.800