• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

New router with 192.168.1.X IPs, but computers still using 192.168.2.X from before

T

tracerit

Senior member
Our old router assigned IPs within the 192.168.2.X range. We ended up replacing it due to wifi dropping issues and we're now set up with 192.168.1.X IPs. Yet two computers are still connected with the old 192.168.2.X IPs and I can't see them on the network. They're connected by ethernet whereas everyone else is connected via wifi if that helps.
 
And you don't say how long ago the router was replaced, how long the leases were set or if the PCs were rebooted or not. They could still be holding onto a lease from the old router.
 
I've seen routers that will continue to renew DHCP leases for IP addresses outside their DHCP pool. You need to shut down ALL of the PCs, and then the router, then power up the router, then power up the PCs.

That is, assuming that all the PCs are already set to DHCP/Obtain IP address automatically.

If those PCs are set to static IPs, then they have to be manually changed.
 
VirtualLarry said:
I've seen routers that will continue to renew DHCP leases for IP addresses outside their DHCP pool. You need to shut down ALL of the PCs, and then the router, then power up the router, then power up the PCs.

That is, assuming that all the PCs are already set to DHCP/Obtain IP address automatically.

If those PCs are set to static IPs, then they have to be manually changed.
Click to expand...

Really? What POS broken router would do that?
 
blotto said:
/release first though. Sometimes the PCs can get so puzzled on new ip range that they won't see the DHCP server without clearing it first.
Click to expand...

They're not puzzled, the issue is that the DHCPREQUEST packet used to renew a lease is sent directly to the DHCP server that granted the lease. The new DHCP server won't be "seen" until the lease runs out and the client fails to renew it and reverts back to sending a broadcast DHCPDISCOVER to elicit a new address.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top