Hey everyone! I have a home network set up with 5 devices—3 Windows PCs, a Xerox copier, and occasionally a MacBook Pro. We're using our ISP's router and modem. Here's the problem: my router is assigning all devices a 10.1.10.x IP address, but two of my Windows computers are stuck with a 192.168.165.x address. This is causing major issues since those two PCs cannot connect to the copier. I've tried restarting devices, forgetting/joining the network again, and even used the 'ipconfig release/renew' command. I also tried manually setting their IPs to 10.1.10.x, which allows internet access but printing still fails. The configs on the problematic computers seem normal. Any ideas on how to fix this? Any help is greatly appreciated!
4 Answers
Run 'ipconfig /all' on the problematic computers. Check what DHCP server is listed compared to one that works. You might find out something else is handing out the IPs on your network.
It sounds like there might be another DHCP server giving out IP addresses. Like, if you've had a cradlepoint or similar device installed, it might not have its DHCP server disabled. That could explain why some devices are getting a different IP range.
I’d check if your modem is set up for bridged networking, so it's not interfering with DHCP assignments.
Are your devices all connected wirelessly? Sometimes wired connections and wireless connections can end up on different IP ranges because of how the router distributes addresses.
Yes, all devices are wireless.
Have you tried printing from the computers? Can you reach the printer's web interface using its IP from any of the PCs? Also, is the router the only device on the network, or are there any other appliances between the router and your computers/printer? It's crucial to know if you have access to the router's admin page from these devices.
Only the computers on the 10.1.10.x range can print or access the router and printer admin pages. There's nothing else in between—they're all wireless.
There is indeed a USB wireless adapter on the copier—it could be causing the issue. Interestingly, my MacBook was close to it and ignored it, but the two problematic Windows PCs are right next to it.