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...
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.
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,
Roland
Let'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 forgot to mention this yesterday - changing the address on the adpro will not work - you will just lose all communication with it.
Using two different network address ranges, even on a single physical network, creates two logically separate networks and you'll actually need to configure a router to link the two, and even if you do that, because the two ends of the VPN are the same logical network, but on two physically different networks, those will no longer be able to communicate.
Fordem,
Thanks for your informative reply. I have digested your comments over the weekend, and absolutely agree.
I am now suspsicious about the setup of the software on the PC end. As you say the comms channel exists between the PC and Adpro exists, and that just that this particular application is not working. Its windows XP era software, and I am running it on Windows 8.
I will look at this as my next move, and will update as I progress!
Regards,
Roland
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
