"No internet access" for a while on a VDSL router that's used as access point

[Only_CORE]

Hey everyone,

I'm having some troubles with Tp-Link VR300 v1.2 my sister gave me since she wasn't using it anymore. So I put it in a place in our house with horrible coverage from my main router (Tp-Link Archer C6).

Wired connection works great but when I try it with a phone it connects but hangs with an exclamation mark and "no internet access" for a few minutes before it starts to work.

Fist thing I did was  reset it and update firmware to the latest version. The VR300 is a VDSL router so I switched to wireless router mode, set the 2.4 and 5 GHz ssid and password, turned off DHCP server and set the ip to 192.168.0.2 (Archer C6 is handling DHCP and is 192.168.0.1). 

 

I'm not sure what other setting to change because otherwise it works it's just stuck when I first connect to it. I event tried manually setting the IP on each device but without luck.

[Alex Atkin UK]

4 hours ago, Only_CORE said:

Hey everyone,

I'm having some troubles with Tp-Link VR300 v1.2 my sister gave me since she wasn't using it anymore. So I put it in a place in our house with horrible coverage from my main router (Tp-Link Archer C6).

Wired connection works great but when I try it with a phone it connects but hangs with an exclamation mark and "no internet access" for a few minutes before it starts to work.

Fist thing I did was  reset it and update firmware to the latest version. The VR300 is a VDSL router so I switched to wireless router mode, set the 2.4 and 5 GHz ssid and password, turned off DHCP server and set the ip to 192.168.0.2 (Archer C6 is handling DHCP and is 192.168.0.1). 

 

I'm not sure what other setting to change because otherwise it works it's just stuck when I first connect to it. I event tried manually setting the IP on each device but without luck.

How is this connected?  As with DHCP turned off it shouldn't work in Wireless Router Mode unless you are connecting it to the Archer via a LAN port rather than the WAN port in their official guide (which is intended for it to be an ethernet router not an Access Point as you are using it).

Also look for things like uPNP, that needs to be off so that clients don't accidentally try to open ports on the TP-Link rather than the Archer.

[Only_CORE]

20 hours ago, Alex Atkin UK said:

How is this connected?  As with DHCP turned off it shouldn't work in Wireless Router Mode unless you are connecting it to the Archer via a LAN port rather than the WAN port in their official guide (which is intended for it to be an ethernet router not an Access Point as you are using it).

Also look for things like uPNP, that needs to be off so that clients don't accidentally try to open ports on the TP-Link rather than the Archer.

The Vr300 and tplink are both connected via LAN ports. 

I tried turning upnp off but it hasn't made a difference

[Alex Atkin UK]

5 hours ago, Only_CORE said:

The Vr300 and tplink are both connected via LAN ports. 

I tried turning upnp off but it hasn't made a difference

Did you try it as a router first, just to see if this is an inherent problem with the WiFi on that device?

I mean its not unusual for Windows to take a while to detect Internet access (and it may work before that), but as you tried static IPs it seems this is very much it taking a while to get connectivity at all which is frustrating.

Its perhaps worth looking at the WiFi settings to see what options are enabled there.  Maybe something is upsetting the client causing a delay.  Have you tried other devices on it to see if the same problem occurs?

[Only_CORE]

19 hours ago, Alex Atkin UK said:

Did you try it as a router first, just to see if this is an inherent problem with the WiFi on that device?

I mean its not unusual for Windows to take a while to detect Internet access (and it may work before that), but as you tried static IPs it seems this is very much it taking a while to get connectivity at all which is frustrating.

Its perhaps worth looking at the WiFi settings to see what options are enabled there.  Maybe something is upsetting the client causing a delay.  Have you tried other devices on it to see if the same problem occurs?

My sister was using it as a main router for a year I think and without problems. 

It happen on all devices on Wi-Fi. 

Here are sceenshots of the wifi and some other settings. 

[Only_CORE]

Noone? 

[Alex Atkin UK]

39 minutes ago, Only_CORE said:

Noone? 

Problem is you seem to have everything set correctly so I can't think of what more to try.

[Falcon1986]

3 hours ago, Only_CORE said:

Noone? 

1. The proper operation mode is access point mode, which the VR300 does not seem to support. If you choose to do it your way, you have to use the WAN port as the ethernet uplink to the primary router's LAN port
2. Ensure that the static LAN IP assigned to the VR300 is not used elsewhere on the network or else there will be IP conflicts. Is there no area to input a gateway IP or DNS address? These would be the same IP address: that of the primary router.

Most older routers can't work in AP mode or by using the workaround you're attempting because of limitations inherent to the firmware.