Device providing addresses beyond its DHCP scope
Device providing addresses beyond its DHCP scope
Hi Everyone, I recently noticed some odd behavior with my new TP-Link router. It seems to be assigning IP addresses like 192.168.230.XX when it shouldn’t be doing that. Normally, my desktop connects fine by plugging in the Ethernet cable a few times. On my phone and girlfriend’s phone, it works after a delay but never actually gets online. My phone reports it’s connected, yet it can’t reach the internet. I’m trying to figure out why the router is behaving this way—especially since it claims to be on the 192.168.0.x subnet.
This seems to be a DHCP configuration problem. I attempted to reset my phone, restart the router, clear the network info, and even used a static IP, but nothing resolved the issue. Now I’m using a fixed IP and it works fine. How can I fix this without the router detecting any errors?
Access the command prompt and input IPCONFIG /ALL to retrieve details about the DHCP server IP. This may indicate a connected device on your network.
It seems there might be an unauthorized DHCP server present in your network.
This FiOS gateway likely supports DHCP as well. Since most fiber gateways combine routing and switching functions, they often include a built-in router. If not configured for bridge or passthrough, it may attempt to handle LAN IP assignments from another subnet. Visit 192.168.230.1 in your browser to check its available services.
Although this should only be a problem if the WiFi is still active on the gateway and the phone is switching to it. Plus the Internet should still work when that happens unless its some sort of broken bridge mode where its no longer performing NAT but still giving out DHCP, so its a bit odd all around.
Sure, that's what you're saying. It looks like the ONT is in your basement or garage, and you're not using any Verizon equipment. It might be a rogue DHCP server, but it could also mean you'd get double NAT if that device was present.