Slave router doesn’t connect to internet
Hi,
I have two Vr600 v3 routers. The first (Master) is on the modem/router operation mode and connected to the landline adsl cable (ip: 192.168.1.1)
The second (slave) is on wireless router operation mode and connected to the master over an ethernet cat 6 cable (LAN-LAN connection), i assigned to it this ip: 192.168.1.2 and reserved it on the master router, i also disabled the DHCP on the slave router. Both master and slave have the same subnet mask.
I created a mesh by making the wifi name & password the same for both routers.
Disabled NAT on the slave router but this didn't help.
When troubleshooting if i disconnect the second router for few minutes and connect it again to the ethernet cable it allows devices connected to it to access the internet for a while (10 - 30 minutes) and then it disconnects again.
Now, Im not sure what's wrong, please help.
Many thanks.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Alright. Is there anything more we can do to solve this issue?
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
You can make one last attempt using this guide - it's explicitly for VR600 device.
Check this thread, this one and this one, you'll see a similar experiance when trying to put VR600 in AP mode.
If the retailer will allow you that, try replacing the slave VR600 for a different device like Archer C6 or C7, which has a dedicated AP mode.
- Copy Link
- Report Inappropriate Content
I will try the above methods
It's weird that the slave router give me access the first time i connect to it but if i connect to the master then the slave then i cannot access the internet. and that the issue is with computers (PC or MAC) and Android Mobiles only, there is no problem with iPhones.
- Copy Link
- Report Inappropriate Content
This is what google says exactly.
This site can’t be reached
www.google.com’s DNS address could not be found. Diagnosing the problem.
- Try running Windows Network Diagnostics.
DNS_PROBE_STARTED
- Copy Link
- Report Inappropriate Content
Hi, Thanks for the detailed information and also Thank you very much for your excellent suggestions @terziyski
I have got your email and send a beta firmware via email and please check whether it is working or not.
- Copy Link
- Report Inappropriate Content
@TP-Link
Yes, the beta firmware solved the problem. Thank you :)
@terziyski Thank you for the support
- Copy Link
- Report Inappropriate Content
Information
Helpful: 2
Views: 4335
Replies: 29