Windows DHCP Client only limited to 192.168.0.1?

[BetaDroid™]

Whenever i change my router's IP to use something like 192.168.1.1 or 10.0.0.1, Windows clients are unable to obtain an IP from the router. But when its on 192.168.0.1 they're able to obtain without any problems at all.

Adding IPs like 192.168.1.1 or 10.0.0.1 to the Default Gateway in the Advanced properties of TCP/IP doesn't appear to help either. Nor does adding the IPs to the primary DNS,

This leads me to think that the Windows DHCP client only scans for a DHCP server limited to the 192.168.0.x area. Is this true?

For now, I have to statically assign IPs, which works, but that's defeating the whole point of a DHCP server in the router. What should I do?

[gamehead200]

Try and see if 10.10.10.1 will work instead!

[BetaDroid™]

sorry, forget this post. I'm an id***. I forgot to restart the DHCP server when I changed the router's IP away from 192.168.0.1 cos it still thinked the router was on 192.168.0.1.