F5F Stay Refreshed Power Users Networks No connection to the web for some time on a VDSL router functioning as an access point

No connection to the web for some time on a VDSL router functioning as an access point

No connection to the web for some time on a VDSL router functioning as an access point

B
BubbaNitro
Member
160
01-31-2016, 11:05 PM
#1
Hey everyone, I'm facing some issues with the Tp-Link VR300 v1.2. My sister gave it to me when she wasn't using it anymore. I placed it in a spot with poor coverage from my main router (Tp-Link Archer C6). The wired connection is fine, but when I try it with a phone it connects but then drops with an exclamation mark and says "no internet access" for a few minutes before working again. First thing I did was reset it and update the firmware to the latest version. Since it's a VDSL router, I switched it to wireless mode, set the 2.4 and 5 GHz networks and password, turned off DHCP, and changed the IP to 192.168.0.2 (the Archer C6 uses 192.168.0.1 for DHCP). I'm not sure what other settings to adjust because otherwise it just gets stuck when connecting initially. I also tried manually changing the IP on each device without success.
B
BubbaNitro
01-31-2016, 11:05 PM #1

Hey everyone, I'm facing some issues with the Tp-Link VR300 v1.2. My sister gave it to me when she wasn't using it anymore. I placed it in a spot with poor coverage from my main router (Tp-Link Archer C6). The wired connection is fine, but when I try it with a phone it connects but then drops with an exclamation mark and says "no internet access" for a few minutes before working again. First thing I did was reset it and update the firmware to the latest version. Since it's a VDSL router, I switched it to wireless mode, set the 2.4 and 5 GHz networks and password, turned off DHCP, and changed the IP to 192.168.0.2 (the Archer C6 uses 192.168.0.1 for DHCP). I'm not sure what other settings to adjust because otherwise it just gets stuck when connecting initially. I also tried manually changing the IP on each device without success.

F
Frosty345
Junior Member
7
02-02-2016, 04:18 AM
#2
This setup relies on specific configurations. It won't function properly in Wireless Router Mode unless connected through a LAN port to the Archer instead of the WAN port as described in their official documentation (which targets it as an Ethernet router, not an Access Point). Ensure features like uPNP are disabled so clients don’t mistakenly attempt to access ports on the TP-Link device rather than the Archer.
F
Frosty345
02-02-2016, 04:18 AM #2

This setup relies on specific configurations. It won't function properly in Wireless Router Mode unless connected through a LAN port to the Archer instead of the WAN port as described in their official documentation (which targets it as an Ethernet router, not an Access Point). Ensure features like uPNP are disabled so clients don’t mistakenly attempt to access ports on the TP-Link device rather than the Archer.

K
KRYSTABOH
Member
50
02-02-2016, 08:20 AM
#3
The Vr300 and tplink are linked through LAN ports. Adjusting UPnP didn't resolve the issue.
K
KRYSTABOH
02-02-2016, 08:20 AM #3

The Vr300 and tplink are linked through LAN ports. Adjusting UPnP didn't resolve the issue.

N
nickslices
Junior Member
4
02-02-2016, 09:38 AM
#4
You attempted it as a router initially just to check if the issue was with the device's WiFi functionality. It's normal for Windows to lag in detecting internet access, though it might work before then. Static IP settings seem to be causing delays in getting connected. Examining the WiFi configuration could reveal enabled options affecting performance. It might help to see if other devices on the network face the same delay.
N
nickslices
02-02-2016, 09:38 AM #4

You attempted it as a router initially just to check if the issue was with the device's WiFi functionality. It's normal for Windows to lag in detecting internet access, though it might work before then. Static IP settings seem to be causing delays in getting connected. Examining the WiFi configuration could reveal enabled options affecting performance. It might help to see if other devices on the network face the same delay.

P
PANDAANDHUMAN
Member
116
02-04-2016, 08:12 AM
#5
She used it as the primary router for about a year without any issues. The problem occurred across all devices connected to the Wi-Fi. I have some screenshots of the Wi-Fi and other settings.
P
PANDAANDHUMAN
02-04-2016, 08:12 AM #5

She used it as the primary router for about a year without any issues. The problem occurred across all devices connected to the Wi-Fi. I have some screenshots of the Wi-Fi and other settings.

B
badboylewisb
Junior Member
10
02-04-2016, 09:05 AM
#6
Noone?
B
badboylewisb
02-04-2016, 09:05 AM #6

Noone?

G
grisou47
Member
133
02-04-2016, 09:49 AM
#7
The issue appears to be that everything seems configured properly, leaving no clear direction for further adjustments.
G
grisou47
02-04-2016, 09:49 AM #7

The issue appears to be that everything seems configured properly, leaving no clear direction for further adjustments.

S
Silvinha10
Senior Member
694
02-04-2016, 10:46 AM
#8
The correct function is access point mode, but the VR300 doesn’t appear to support it. If you proceed manually, use the WAN port as your Ethernet uplink to the main router’s LAN. Make sure the static LAN IP assigned to the VR300 isn’t used elsewhere on the network to avoid conflicts. There’s no option to enter a gateway IP or DNS address—those would match the primary router’s IP. Most older routers can’t operate in AP mode or with this workaround due to firmware restrictions.
S
Silvinha10
02-04-2016, 10:46 AM #8

The correct function is access point mode, but the VR300 doesn’t appear to support it. If you proceed manually, use the WAN port as your Ethernet uplink to the main router’s LAN. Make sure the static LAN IP assigned to the VR300 isn’t used elsewhere on the network to avoid conflicts. There’s no option to enter a gateway IP or DNS address—those would match the primary router’s IP. Most older routers can’t operate in AP mode or with this workaround due to firmware restrictions.