Unable to Access Local Network: Router and Two PCs Acting as DHCP Servers

Local network access failures caused by multiple DHCP servers are resolved by disabling the router’s DHCP service or assigning static IP addresses to the client PCs. This eliminates IP address conflicts and ensures that all devices receive consistent configuration from a single authoritative source, restoring stable connectivity across the LAN.

Understanding the Dual DHCP Conflict

The root cause of this issue lies in the fundamental role of the Dynamic Host Configuration Protocol (DHCP). In a standard home or small office network, there should be exactly one device responsible for handing out IP addresses to connected clients. When both your main router and two separate PCs are acting as DHCP servers, they create a chaotic environment where devices may receive conflicting subnet masks, gateway addresses, or DNS settings. This often results in intermittent connectivity, inability to ping other devices, or complete loss of local network access.

For example, if PC A requests an IP address, it might receive a response from the router with a gateway of 192.168.1.1, while PC B receives a response from another PC with a different gateway or no gateway at all. Devices configured this way cannot communicate effectively because they do not share a common understanding of how to route traffic within the local segment. This scenario is particularly problematic when the rogue DHCP server on the PC is misconfigured or running software that inadvertently enables a DHCP relay or server function.

Identifying the Rogue Servers

To confirm which devices are providing DHCP services, you can use diagnostic tools available in both Windows and Debian-based Linux systems. On Windows, open the Command Prompt and run ipconfig /all. Look for the line labeled "DHCP Server". If it does not list your router’s IP address, another device is interfering. Similarly, on Linux, you can use cat /var/log/syslog | grep DHCP or check the configuration files for services like dnsmasq or isc-dhcp-server.

Another method is to disconnect one PC at a time and observe if network stability returns. If the network stabilizes after disconnecting a specific PC, that machine is likely running an unauthorized DHCP service. It is also worth checking if any network adapters are set to bridge mode or if virtualization software (like VMware or VirtualBox) has created virtual network interfaces that include DHCP capabilities.

Solution One: Disable Router DHCP

In many cases, the router itself is the primary source of confusion if it is set up incorrectly alongside existing infrastructure. However, the prompt suggests the router and PCs are *both* acting as servers, which implies the router is actively handing out IPs. The most robust solution is to ensure only one device handles this task. If you intend for the router to remain the central management point, you must disable its DHCP server function if it is somehow conflicting with a dedicated server elsewhere, but typically, you want the router to handle it for simplicity.

If you decide to let the router be the sole DHCP server, log into its administrative interface via a web browser using its default gateway IP. Navigate to the LAN or Network Settings section. Look for an option labeled "DHCP Server" or "DHCP Service." Change the status from "Enabled" to "Disabled." Save the settings and reboot the router. Afterward, ensure your PCs are set to obtain IP addresses automatically (Dynamic IP).

This approach simplifies the network topology significantly. All devices will receive their IP configuration from the same source, ensuring consistency in subnet masks and default gateways. This is generally the preferred method for home networks unless you have a specific enterprise requirement for a dedicated DHCP appliance.

Solution Two: Assign Static IP Addresses to PCs

If you prefer to keep the router’s DHCP server enabled for other devices (such as smartphones or IoT gadgets) but want to remove the PCs from the pool of potential DHCP providers, you can assign them static IP addresses. This prevents the PCs from needing to request an IP via DHCP, thereby removing the need for them to act as servers if they were doing so due to misconfiguration.

On Windows:

1. Open Control Panel > Network and Sharing Center.
2. Click on Change adapter settings.
3. Right-click your active network adapter and select Properties.
4. Select Internet Protocol Version 4 (TCP/IPv4) and click Properties.
5. Select Use the following IP address and enter a static IP outside the router’s DHCP range (e.g., if the router hands out 192.168.1.100-200, use 192.168.1.50).
6. Enter the correct Subnet Mask (usually 255.255.255.0) and Default Gateway (your router’s IP).

On Debian-based Linux:

Edit the network configuration file, typically located at /etc/network/interfaces or managed by Netplan in newer versions. Define the interface with a static address, netmask, and gateway. For example, in Netplan, you would edit the YAML file to specify addresses and gateway4. Restart the networking service using systemctl restart networking or netplan apply.

By assigning static IPs, you eliminate the dependency on DHCP for these machines. If the PCs were previously running DHCP server software, they may stop serving IPs once they are statically configured, depending on the software’s behavior. You should also audit the PC for any installed DHCP server applications and uninstall or disable them to prevent future conflicts.

Verifying Network Stability

After implementing either solution, verify the fix by pinging other devices on the network. Use ping 192.168.1.1 to test connectivity to the router and ping [other_PC_IP] to test peer-to-peer communication. Additionally, check that internet access remains functional. If issues persist, flush the DNS cache by running ipconfig /flushdns on Windows or sudo systemd-resolve --flush-caches on Linux.

It is also advisable to review your network diagram to ensure no physical loops exist, which can exacerbate DHCP issues. For more insights on resolving complex loop scenarios, see Resolving a Loop Scenario Network Issue Due to a Physical Short Circuit. Ensuring a clean, single-source DHCP environment is critical for maintaining a reliable local network.

Frequently Asked Questions

Can two routers provide DHCP on the same network?

No, having two routers provide DHCP on the same broadcast domain causes IP conflicts and network instability. You must disable DHCP on the secondary router and connect it via a LAN port to act as a switch or access point instead.

How do I find my router's DHCP range?

Log into your router’s admin page and look for the DHCP Server settings under LAN or Local Network options. The range is usually displayed as a starting and ending IP address, such as 192.168.1.100 to 192.168.1.200.

Why did my PC start acting as a DHCP server?

This often happens due to misconfigured virtualization software, bridged network adapters, or third-party utilities that enable sharing of internet connections. Check your network adapter properties for "Allow other network users to connect through this computer" settings.

Is it safe to disable DHCP on the router?

Disabling DHCP on the router is safe only if you have another DHCP server on the network or if all devices are manually configured with static IPs. Without a DHCP server, new devices will not be able to join the network automatically.

What happens if I don't fix this DHCP conflict?

Devices may receive invalid IP configurations, leading to intermittent connectivity, inability to access shared resources, or complete loss of internet access. It can also cause ARP table corruption and increased network latency.