TP-Link SG1024DE setup over VPN

[colecaz]

I have the TP-Link switch in my home network and use the Easy Smart Configuration Utility to set it up. It's installed and working fine with VLAN's, etc.

I want to be able to access it for changes over VPN while I'm not home for extended periods. I'm using PPTP for VPN, and RT-AC68P running the latest Merlin for the VPN server at home. Win 10 on the remote computer.

Connecting to the VPN and bringing up the config utility, it scans both local and VPN IP's and correctly finds the switch and identifies its IP address. The "Located On" IP address is the IP assigned to the VPN interface on the remote computer. Everything looks like normal until I try to log in. Then it says the switch is not on the same subnet as the utility, even though in the utility's initial screen it shows the switch IP address and "Located On" as being the same subnet.

Any suggestions to make it work?

 

[System Error Message]

the switch does not send back to the router, this is the disadvantage of layer 2 switching and where layer 3 switches help. Because it sees you on the same subnet it assumes it does not need to go through the gateway so sends the packet to the router's switch which cannot find you.

 

[colecaz]

AhHa! I just tried addressing the switch GUI by it's IP address over the VPN instead of using the configuration utility and it works correctly. I guess it's a deficiency in the TP-Link Easy Smart utility, not in the routing. And the Netgear Prosafe Plus Utility isn't smart enough to scan the VPN network adapter in addition to the local adapter so it doesn't find any of the Netgear switches on the home network. But again, using the IP address of a Netgear switch over the VPN allows configuration via GUI for those later models that have it.

Or could it be in the DNS of the router? It's beyond my capabilities to troubleshoot further.

The lesson I get is, if you want to remotely manage switches, buy ones with a GUI. And use IP addresses.

Thanks for the reply, SysErrMsg.

 

[System Error Message]

AhHa! I just tried addressing the switch GUI by it's IP address over the VPN instead of using the configuration utility and it works correctly. I guess it's a deficiency in the TP-Link Easy Smart utility, not in the routing. And the Netgear Prosafe Plus Utility isn't smart enough to scan the VPN network adapter in addition to the local adapter so it doesn't find any of the Netgear switches on the home network. But again, using the IP address of a Netgear switch over the VPN allows configuration via GUI for those later models that have it.

Or could it be in the DNS of the router? It's beyond my capabilities to troubleshoot further.

The lesson I get is, if you want to remotely manage switches, buy ones with a GUI. And use IP addresses.

Thanks for the reply, SysErrMsg.

All the utilities scan on layer 2, not layer 3 which is why they did not find your switch. You could always get mikrotik switches and use dude instead which works over any network interface.