When a secondary router fails to connect while other servers work, the issue usually stems from IP address conflicts, incorrect WAN port configuration, or ISP restrictions on DHCP clients. Verify that the secondary router’s WAN interface is obtaining an IP from the primary network and that its LAN subnet does not overlap with the upstream provider’s range.
Diagnosing the Network Topology
Before attempting complex fixes, you must establish exactly how the two routers are linked. The summary indicates that two servers connecting to Router B work well, but Router B itself fails to connect. This phrasing is slightly ambiguous. It likely means that devices connected *to* Router B (via Wi-Fi or LAN) cannot reach the internet, while the servers mentioned might be directly connected to Router A (the ISP/load balancing unit) or are virtual machines hosted elsewhere. Alternatively, it could mean that the physical link between Router A and Router B is failing. Assume the standard home/small office topology: Router A is the main gateway provided by the ISP, handling load balancing. Router B is a secondary device intended to extend the network or provide additional ports. If Router B cannot get an IP address from Router A, no downstream device will have internet access. Check the physical cabling first. Ensure you are using an Ethernet cable rated for Cat5e or higher. Connect one end to a LAN port on Router A and the other to the WAN (Internet) port on Router B. Do not use a LAN port on Router B for this connection unless you are configuring it as an Access Point, which requires different settings.Verifying IP Address Assignment
Log into the management interface of Router B. Navigate to the Status or Network Map page. Look at the WAN connection status. If it shows "Disconnected" or "Obtaining IP Address..." indefinitely, the physical link is broken or Router A is not responding. If Router B receives an IP address, check if it is in the same subnet as Router A. For example, if Router A is 192.168.1.1, Router B’s WAN interface should receive something like 192.168.1.x. If Router B’s default LAN IP is also 192.168.1.1, a conflict occurs. You must change Router B’s LAN IP to a different subnet, such as 192.168.2.1, before connecting it to Router A.Common Configuration Errors
Many users encounter issues because they apply settings meant for standalone routers to a bridged environment.- DHCP Server Conflict: On Router B, disable the DHCP server if you want Router A to handle all addressing. However, most modern routers allow Router B to act as a DHCP server for its own LAN segment while receiving a WAN IP from Router A. This is called NAT routing. Ensure Router B’s NAT is enabled.
- Subnet Overlap: As mentioned, if both routers use 192.168.0.x or 192.168.1.x, traffic gets confused. Change Router B’s LAN IP to 192.168.10.1 or similar.
- MAC Address Cloning: Some ISPs lock their service to the MAC address of the first device connected. If Router A is acting as a bridge or modem only, Router B might need its MAC cloned to match the original PC or server that was registered. This is less common with load balancers but worth checking if the WAN IP never changes.
Testing Connectivity Steps
Follow these steps to isolate the failure point.- Direct Connection Test: Disconnect Router B. Connect a laptop directly to Router A via Ethernet. Confirm internet works. Ping the router’s gateway IP (e.g., ping 192.168.1.1). If this fails, the issue is with Router A or the ISP.
- Router B Isolation: Power on Router B without connecting it to Router A. Reset it to factory defaults. Configure its WAN settings to obtain IP automatically (DHCP). Save and note the new LAN IP.
- Link Establishment: Connect Router A LAN to Router B WAN. Wait two minutes. Check Router B’s WAN status again. It should show a valid IP, Subnet Mask, Gateway, and DNS servers.
- Downstream Test: Connect a client device to Router B’s LAN or Wi-Fi. Try to ping an external IP like 8.8.8.8. If you can ping 8.8.8.8 but not websites, your DNS settings on Router B are incorrect. Enter 8.8.8.8 and 1.1.1.1 manually.
Advanced Troubleshooting
If the basic steps fail, consider more specific constraints. ISP Restrictions: Some ISP-provided load balancers restrict the number of active DHCP leases or block certain types of traffic from unauthorized devices. Contact your ISP to see if there are limits on the number of devices behind the gateway. VLAN Tagging: In some enterprise setups, the ISP requires VLAN tagging on the WAN interface. If Router B supports VLANs, check if Router A is sending tagged frames. You may need to configure Router B’s WAN port to accept or strip specific VLAN IDs. Firmware Updates: Outdated firmware on either router can cause compatibility issues with newer encryption standards or routing protocols. Update both devices to the latest stable versions. For more information on managing connections behind restrictive ISP gateways, see How to Open Ports (TCP/UDP) Behind CGNAT 5G Router. This guide explains how to handle scenarios where the upstream device limits direct connectivity. Another related scenario involves securing specific connections through complex routing. If you are trying to route specific traffic securely, refer to Using PC VPN client behind VPN router with ASUS AX5400 router and NordVPN on Windows devices for insights on layered network configurations.Frequently Asked Questions
Why can I ping the router but not the internet?
This indicates a DNS resolution failure rather than a connectivity problem. Your device has successfully reached the router, but the router cannot translate domain names into IP addresses. Log into the router’s admin panel and manually set the DNS servers to public resolvers like Google (8.8.8.8) or Cloudflare (1.1.1.1).
Should I use a LAN port or WAN port to connect the second router?
Use the WAN port if you want Router B to create a separate network segment (Double NAT). Use a LAN port if you want Router B to act purely as a switch or access point, extending the existing network. Using a LAN port requires disabling the DHCP server on Router B to prevent conflicts.
What causes IP address conflicts between two routers?
Conflicts occur when both routers use the same LAN subnet, such as 192.168.1.1. When Router B tries to route traffic, it gets confused about whether the destination is local or remote. Change Router B’s LAN IP to a different subnet, like 192.168.2.1, to resolve this.
Does MAC cloning help with ISP restrictions?
Yes, if your ISP binds your internet service to the MAC address of your first device. By cloning the MAC address of a working PC onto Router B’s WAN interface, you can trick the ISP into thinking the router is the authorized device.
How do I reset a router to factory defaults?
Locate the small reset button on the back of the router. While the device is powered on, press and hold the button for 10-15 seconds using a paperclip. The lights will flash, indicating a reset. You will need to reconfigure all settings afterward.