Installed 'new' Netgear N300 (DGN2200-100UKS model number)
Day 1: Install
Changed router IP to 192.168.1.1
Setup DHCP range to 192.168.1.50 - 100
All clients connected and working, 4 Pc's connected via LAN (separate switch). 1 laptop and 2 mobiles connected on Wifi, all on DHCP. 3 static devices - network laser & 2 print servers for dot matric printers. All static addresses out of DHCP range.
Day 2: Problems start
One of the LAN connected PC's (Windows 7) reports an IP address in the 192.168.0.x subnet (mask is 255.255.255.0) so would not connect. 'stop gap' measure (as I'm not on site), was to set it with a static IP (192.168.1.155 - out of the DHCP range, alongside the other static addresses). Everything else still working ok.
Day 3: Problems continue
Remaining LAN connected Windows Windows 7 PC reports an invalid IP address out of the subnet and won't connect. Set it as static (like the first Win 7 PC) and check the DHCP range is correct within router (it is). Reboot router. Wifi client devices also cannot connect, wrong IP's again. Change Win7 Laptop on Wifi to a static address as a work around.
Remaining DHCP Wifi clients (2 mobiles) cannot connect so need DHCP working. There will be more DHCP connected mobile devices in the near future as seasonal people return to work. Remaining DHCP LAN client PC's (2 Windows XP's) have been totally unaffected by this and continue to have correct IP's.
Running whatever base firmware the router came with - so will update this when next on site.
There is mention of the RIP version having an impact on clients connecting on DHCP so I will be changing that shortly. Probably another router reboot as part of the setting change.
I drew a complete blank running
netsh dhcp show server (command not found) to verify what DHCP server clients were connected - because the client needs to be connected on DHCP to run it? And I cannot do that as I can't then be connected to the client PC remotely...
Are there other DHCP commands I can run - I'm ideally looking for one which will list available DHCP servers as I'm convinced DHCP is running on something else (that I'm unaware of) and dishing out these 192.168.0.x addresses.