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?