F5F Stay Refreshed Power Users Networks The second router in the LAN isn't connected to the internet.

The second router in the LAN isn't connected to the internet.

The second router in the LAN isn't connected to the internet.

Pages (2): 1 2 Next
_
_NORO
Member
59
05-03-2016, 01:07 PM
#1
Hello everyone, I’m facing a problem with my home network setup. The fiber connection is routed through an ISP ONT from ZTE, and three Gigabit Ethernet cables are connected directly to the PC, NAS, and the second router (TPLink TL-WDR3600 N600). The second router’s LAN port is linked to the Smart TV, which works perfectly—streaming 4K is smooth. However, when I connect my phone via Wi-Fi to that port, the internet drops completely. The main router has DHCP disabled and a different IP assigned, so it’s reachable and responsive. The TV connected through Ethernet still functions normally. It seems the Wi-Fi side isn’t getting the connection, but the switch appears to be operational. I’m wondering if there’s an issue with the second router itself or if something is aging and causing this behavior. Please advise. Also, thank you for your help—I didn’t find a matching discussion in the forum earlier.
_
_NORO
05-03-2016, 01:07 PM #1

Hello everyone, I’m facing a problem with my home network setup. The fiber connection is routed through an ISP ONT from ZTE, and three Gigabit Ethernet cables are connected directly to the PC, NAS, and the second router (TPLink TL-WDR3600 N600). The second router’s LAN port is linked to the Smart TV, which works perfectly—streaming 4K is smooth. However, when I connect my phone via Wi-Fi to that port, the internet drops completely. The main router has DHCP disabled and a different IP assigned, so it’s reachable and responsive. The TV connected through Ethernet still functions normally. It seems the Wi-Fi side isn’t getting the connection, but the switch appears to be operational. I’m wondering if there’s an issue with the second router itself or if something is aging and causing this behavior. Please advise. Also, thank you for your help—I didn’t find a matching discussion in the forum earlier.

S
SrGeed
Junior Member
13
05-03-2016, 02:39 PM
#2
The operation mode needs to be configured as 'Access Point'.
S
SrGeed
05-03-2016, 02:39 PM #2

The operation mode needs to be configured as 'Access Point'.

Z
Zver510
Junior Member
8
05-03-2016, 09:35 PM
#3
There isn’t an "operation mode" menu available. Even guidance from TPLink suggests adjusting settings manually. It seems I might be overlooking a detail.
Z
Zver510
05-03-2016, 09:35 PM #3

There isn’t an "operation mode" menu available. Even guidance from TPLink suggests adjusting settings manually. It seems I might be overlooking a detail.

P
Poke_King
Junior Member
23
05-17-2016, 10:28 PM
#4
These instructions should assist you.
P
Poke_King
05-17-2016, 10:28 PM #4

These instructions should assist you.

K
KlayDog1
Senior Member
685
05-24-2016, 10:16 AM
#5
Here’s a revised version:
The current setup includes the first router with IP 192.168.1.1 and DHCP range up to 192.168.1.254, while the second router is at 192.168.1.2 with DHCP disabled. The cable connection uses LAN-LAN mode. When connecting via WiFi, I experience issues—Pokemon Go won’t sign in from the second router, but works fine on the main router. My TV functions with Netflix, YouTube, and apps like Plex, though it sometimes fails to connect to my NAS server. The TV is linked through cable to the second router. It seems the problem might stem from a conflict rather than just misconfiguration.
K
KlayDog1
05-24-2016, 10:16 AM #5

Here’s a revised version:
The current setup includes the first router with IP 192.168.1.1 and DHCP range up to 192.168.1.254, while the second router is at 192.168.1.2 with DHCP disabled. The cable connection uses LAN-LAN mode. When connecting via WiFi, I experience issues—Pokemon Go won’t sign in from the second router, but works fine on the main router. My TV functions with Netflix, YouTube, and apps like Plex, though it sometimes fails to connect to my NAS server. The TV is linked through cable to the second router. It seems the problem might stem from a conflict rather than just misconfiguration.

T
tuxedocorey
Junior Member
41
05-24-2016, 10:34 AM
#6
Second wireless router connects to DNS server 192.168.1.1 and gateway 192.168.1.1. The current wireless configurations remain unchanged across all devices.
T
tuxedocorey
05-24-2016, 10:34 AM #6

Second wireless router connects to DNS server 192.168.1.1 and gateway 192.168.1.1. The current wireless configurations remain unchanged across all devices.

S
Shimorinkakito
Junior Member
15
05-29-2016, 08:52 PM
#7
Gateway was already configured, DNS added on router 2. The issue appears consistent for Pokemon Go login from router 2 using the Wifi connection—connection shows connected again, though no internet is available. Regarding wireless settings, they are labeled as "Room 1" (2.4 Ghz only) and "Room 2" (2.4 Ghz and 5 Ghz) on router 2, with custom passwords applied while other options remain auto.
S
Shimorinkakito
05-29-2016, 08:52 PM #7

Gateway was already configured, DNS added on router 2. The issue appears consistent for Pokemon Go login from router 2 using the Wifi connection—connection shows connected again, though no internet is available. Regarding wireless settings, they are labeled as "Room 1" (2.4 Ghz only) and "Room 2" (2.4 Ghz and 5 Ghz) on router 2, with custom passwords applied while other options remain auto.

O
OobFiche
Junior Member
18
06-04-2016, 10:58 PM
#8
The main DHCP range is being utilized. Static IP reservations by MAC addresses can be made at the primary router. A wireless survey should be performed using WiFi Analyzer, with screenshots of the Networks and Analysis pages. Both routers must have WPA/WPA2-PSK with AES encryption enabled.
O
OobFiche
06-04-2016, 10:58 PM #8

The main DHCP range is being utilized. Static IP reservations by MAC addresses can be made at the primary router. A wireless survey should be performed using WiFi Analyzer, with screenshots of the Networks and Analysis pages. Both routers must have WPA/WPA2-PSK with AES encryption enabled.

A
asmuund
Member
125
06-04-2016, 11:27 PM
#9
Main router is configured for IPs from 192.168.1.10 to 192.168.1.254. It supports static IP assignments via MAC address, but only applies them when the addresses fall within its DHCP range. TPLink advised using addresses outside that range, which isn't possible here. I attempted this per their suggestion but saw no improvement. The local Wi-Fi environment is quite busy due to poor apartment layout, and usually a single router isn't sufficient. Both networks use WPA2 AES encryption. In the screenshots labeled "my networks," I see Sufragerie (router 1) and Dormitor (router 2).
A
asmuund
06-04-2016, 11:27 PM #9

Main router is configured for IPs from 192.168.1.10 to 192.168.1.254. It supports static IP assignments via MAC address, but only applies them when the addresses fall within its DHCP range. TPLink advised using addresses outside that range, which isn't possible here. I attempted this per their suggestion but saw no improvement. The local Wi-Fi environment is quite busy due to poor apartment layout, and usually a single router isn't sufficient. Both networks use WPA2 AES encryption. In the screenshots labeled "my networks," I see Sufragerie (router 1) and Dormitor (router 2).

E
EmmaForLife
Member
201
06-22-2016, 01:48 PM
#10
This 2.4GHz analysis isn’t ideal, especially in a shared building. Where’s the 5GHz option? Your TP-Link router can handle 802.11n on the 5GHz band. You might be able to use it if channels are open instead of the 2.4GHz range. Also, are wired connections through the second router reliable? Have you recently restarted both devices? Other considerations: In a busy 2.4GHz area, stick to narrower 20MHz channels. Anything wider will clash with nearby networks and reduce speed. If you stick with 2.4GHz, performance will be limited. Move low-priority devices to the 2.4GHz network. Your devices may not switch to the new signal when you move because the old one is still strong enough. The fix involves lowering the transmission power on each access point so the new signal fades just enough for your client devices to connect and switch. This requires some trial and error in a crowded environment, but it should improve results on 5GHz. If you plan to deploy multiple access points competing with neighbors, expect challenges. It’s like a stadium full of voices—speaking louder doesn’t always help; you need quieter signals to be heard clearly. The same applies to WiFi: lower the output power, and everyone must do the same for better performance.
E
EmmaForLife
06-22-2016, 01:48 PM #10

This 2.4GHz analysis isn’t ideal, especially in a shared building. Where’s the 5GHz option? Your TP-Link router can handle 802.11n on the 5GHz band. You might be able to use it if channels are open instead of the 2.4GHz range. Also, are wired connections through the second router reliable? Have you recently restarted both devices? Other considerations: In a busy 2.4GHz area, stick to narrower 20MHz channels. Anything wider will clash with nearby networks and reduce speed. If you stick with 2.4GHz, performance will be limited. Move low-priority devices to the 2.4GHz network. Your devices may not switch to the new signal when you move because the old one is still strong enough. The fix involves lowering the transmission power on each access point so the new signal fades just enough for your client devices to connect and switch. This requires some trial and error in a crowded environment, but it should improve results on 5GHz. If you plan to deploy multiple access points competing with neighbors, expect challenges. It’s like a stadium full of voices—speaking louder doesn’t always help; you need quieter signals to be heard clearly. The same applies to WiFi: lower the output power, and everyone must do the same for better performance.

Pages (2): 1 2 Next