Cannot get a VR1600 to talk to VR900

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

Cannot get a VR1600 to talk to VR900

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Cannot get a VR1600 to talk to VR900
Cannot get a VR1600 to talk to VR900
2019-05-02 13:02:32 - last edited 2019-05-05 10:46:29
Model: Archer VR900v  
Hardware Version: V3
Firmware Version:

Having some issues figuring this out.

 

I had NBN HFC installed yesterday, unfortunately I cant use my TP Link VR900 for HFC due to being the V3 model and it not supporting VLAN ID tagging in "Wireless ROuter Mode".

 

More than happy to use the Internode supplied VR1600v (essentialy a VR600v) which is working fine. I have an Ethernet cable run under our house to my back room, where I have my old Billion 7800n, which talks with the VR1600 without any problems.

 

I'd like to replace the Billion with the VR900, but I'm having issues getting it talking with the VR1600.

 

When I plug the VR900 in, it has the same IP address gateway as the VR1600 – both default are 192.168.1.1

 

I've tried the following, but they still wont see each other:

 

  • changed the VR900 to different IP addresses - example 192.1.168.2 (the Billion default gateway is 192.168.1.254 which works fine)
  • have tried disabling DHCP on the VR900
  • have tried setting up bridge mode and changing operational mode to Wireless Bridge Mode
  • tried using normal LAN ports as well as port 4 which is WAN/LAN

 

I'd like to have both the TP Link routers working together, with the VR900 at the back of the house providing WiFi and being able to access it's interface, as well as the same for the front of the house using the VR1600.

 

I know this should be something simple, but it's got me scratching my head in trial and error, any help would be much appreciated.

 

Screenshot of the VR1600 when working fine with the Billion

 

Screenshot of the VR900 simply not picking anything up

  0      
  0      
#1
Options
2 Reply
Re:Cannot get a VR1600 to talk to VR900
2019-05-04 02:27:20 - last edited 2019-05-05 10:46:29

Fantastic support feedback, not.

 

FYI, have resolved the issue for anyone who stumbles across this.

 

As suspected, turns out it was something pretty simple, but easy to overlook.

 

The network cable from my wall port to the Billion was dodgy. Seemed to work fine with the Billion, but wouldn't work with the VR900. Was one of those yellow ethernet cables that usually come with a modem when you buy one. Swapped it out for a blue CAT6 spare cable I had, all working perfectly now, both routers started talking to each other immediately :)

 

Now the main VR1600 is the modem and DHCP server at 192.168.1.1, with the VR900 running essentially as a AP on 192.168.1.254. I can now access both routers interface's, and everything on the home network is running as expected.

  0  
  0  
#2
Options
Re:Cannot get a VR1600 to talk to VR900
2019-05-05 10:51:30

Hi,

 

Sorry to respond late cause we are off-duty during the international Labour Day.

 

You can setup VR1600v as the main router which is working fine for now.

 

While if you want to connect the VR900 to the VR1600v, there are 2 options. 

 

First, you can set it up VR900 as a wireless router. To avoid IP conflict, it is suggested to chaneg the Lan IP to 192.168.2.1 and reboot to apply it.

 

Then you can connect the LAN4/WAN port of VR900 to the VR1600v, theoretically, the VR900 will be plug and play.

 

Or you can configure VR900 as an access point to reduce the NAT. Below is the instruction: 

https://www.tp-link.com/en/support/download/archer-vr900/#video 

 

May it help and have a nice day. 

 

 

Nice to Meet You in Our TP-Link Community. Check Out the Latest Posts: Connect TP-Link Archer BE550 to Germany's DS-Lite (Dual Stack Lite) Internet via WAN Archer GE550 - BE9300 Tri-Band Wi-Fi 7 Gaming Router EasyMesh Is Available When Wi-Fi Routers Work in AP Mode as A Controller. Archer AX90 New Firmware Added Support for EasyMesh and Ethernet Backhaul If you found a post or response helpful, please click Helpful (arrow pointing upward icon). If you are the author of a topic, remember to mark a helpful reply as the "Recommended Solution" (star icon) so that others can benefit from it.
  0  
  0  
#3
Options