NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
FVS336G VPN L2TP addressing
Hello Negear Forum,
We have a FVS336Gv2 which serves our small business well.
Recently I setup the L2TP VPN so I can access servers on our LAN, which is setup 192.168.1.X. The remote VPN L2TP client computer is assigned 192.168.100.2 etc by the Netgear, as the setup requires the VPN remote computer to be assigned a different subnet.
Now, once I allowed the server to respond to 192.168.X.X no problem with access, and the VPN connection works very well anywhere.
However, we have one bit of kit which we want to access. Its an Adpro Fasttrace security system, few years old now, and its designed to comunicate with a remote monitoring station. We have it on our local LAN and can get to it at the premises no problems from any computer with the software on the local LAN. Its not remote monitored by anyone.
I know that the Adpro is designed to be on a static route to the remote monitoring station, and router ports can be opened to allow this. The Adpro instructions are clear that its one static IP per each install. However, our home internet is not a fixed IP, nor of course would work from any other IP either. I was hoping to get at the Adpro from the VPN, but it does not like that we are coming from a 192.168.100.2 etc. Incidently, I can ping it through the VPN.
I like the idea at getting to the Adpro through the VPN, but as setup its not working for us. As a small business owner, you have to wear many hats, and its IT today! If any one has a comment or can suggest a tweak to the current setup, or perhaps is there a better approach I have not thought about!
Standby for any advice.
Roland.
9 Replies
If you can ping the Adpro through the VPN, then you have a functioning communication link with it - what exactly is the problem?
- Thanks for the reply, yes I have to agree with you with regards to the ping, as far as Netgears support can be expected to provide then yes, the route is technically functioning. Maybe this is more of a question of networking fundamentals, which I am failing to understand. I was looking to use the VPN to in effect join our office LAN, in our case 192.168.1.X etc which actually we are not quite doing, as we have assigned the remote client 192.168.100.2 etc.
The adpro software I think is looking at IP of the client computer and comparing that of the unit, and rejecting comms. Its designed to work on a fixed route to monitoring station, and so we are trying to do something else. Maybe if we assign the adpro unit a 192.168.100.X address we may have comms, but of course this will be at odds on our office 192.168.1.X network then. I have had a good long play with the setup of the software and Adpro box, but its defeated me.
Hope this makes some sort of sense, I do appreciate the any advice given.Regards,RolandLet's forget about Netgear support for the time being - regardless of whose equipment you have, as far as tcp/ip networking goes - ping is the definitive test for communications - if ping works, you have fully functional, bi-directional communications, the PC at the far end of the VPN can send a ping request across the VPN to the adpro, the adpro receives it & replies to it, and that reply makes it all the way back to the PC - the problem is not the network, setting static routes will have no impact, because a route already exists, opening ports will have no impact (unless you have specifically blocked them), etc - you need to address it with adpro.
I had a system similar to this that I needed to monitor. The easiest solution ended up being to just rdp into a system on the remote network and access it from there--then the unit works fine since the system accessing it is local.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
