Archer VR600V cannot detect device connected via ethernet port

Archer VR600V cannot detect device connected via ethernet port
Archer VR600V cannot detect device connected via ethernet port
2020-07-08 04:55:45 - last edited 2020-07-11 07:28:12
Hardware Version: V2
Firmware Version:

Dear all,

 

I have recently upgraded from a Netgear DGN2200v4 to a tp-link Archer VR600v. Everything went smoothly, except for how the new router cannot detect my home security system's control unit, which is connected to it via an ethernet cable (i.e. it does not show in the network map under wired clients). My old router has no problem recognizing it. Does anybody have any ideas what could be the issue?

 

Thank you in advance.

 

Nicola Zilio

0
0
#1
Options
1 Accepted Solution
Re:Archer VR600V cannot detect device connected via ethernet port-Solution
2020-07-11 07:27:44 - last edited 2020-07-11 07:28:12

@Sunshine 

 

I solved the issue. It turns out that the control unit was set with a static IP address (192.168.0.200), but the range of IPs given out by the router, by default, was 192.168.1.2-192.168.1.199. I changed this range to 192.168.0.2-192.168.0.200 and told the router to reserve 192.168.0.200 for the MAC address of the control unit. Although the router doesn't always seem to detect the control unit, I can nonetheless ping it all the time, and things are now working.

Recommended Solution
0
0
#3
Options
2 Reply
Re:Archer VR600V cannot detect device connected via ethernet port
2020-07-10 10:04:19

@nicolazilio 

Hello,

 

Did you change a different port to plug your home security system? Is it still not working?

 

Did you contact the security system's support before? Did it need any special settings on the router?

 

Please change an Ethernet cable to connect VR600v and your security system.

 

Thank you for your cooperation and have a nice day!

 

0
0
#2
Options
Re:Archer VR600V cannot detect device connected via ethernet port-Solution
2020-07-11 07:27:44 - last edited 2020-07-11 07:28:12

@Sunshine 

 

I solved the issue. It turns out that the control unit was set with a static IP address (192.168.0.200), but the range of IPs given out by the router, by default, was 192.168.1.2-192.168.1.199. I changed this range to 192.168.0.2-192.168.0.200 and told the router to reserve 192.168.0.200 for the MAC address of the control unit. Although the router doesn't always seem to detect the control unit, I can nonetheless ping it all the time, and things are now working.

Recommended Solution
0
0
#3
Options