10-01-2010 06:31 AM
On the client side I switched from DSL to use FIOS Internet/Phones/TV. Everything works fine except I cannot connect to the remote office via VPN.
Prior to the FIOS switch we used to VPN to the remote office and worked fine using laptop and other workstations. If I go to any Starbucks with the same laptop I can VPN to the remote office instantly.
What is weird, I can VPN backwards from the remote office to the client office. This issue occurs with both using Windows and Macs. My VPN setup is just a plain PPTP protocol.
I also noticed tons of people who complain about the same thing. This is a big problem. as I cannot recommend FIOS to customers.
Any solutions are appreciated.
Solved! Go to Solution.
10-01-2010 06:45 AM
The issues describe with regards to VPN connectivity on other threads relate to IPsec tunnels. IPsec uses a different tunneling technique which the routers seem to occasionally have trouble dealing with if you have more than one users behind the router at the same time.
PPTP (besides the fact that this is a very poor VPN protocol -- but that's a different issue) doesn't require this and thus is really router agnostic. You don't say what the remote office's IP address range is. Is it possible that prior to the switch, you're clients were on a different IP range and now that you've switched to FiOS, you've moved to 192.168.1.x network and that network conflicts with the same address range at the remote office? You can't have a local and remote location both using the 192.168.1.x range and try to connect them together with a VPN -- the VPN client can't differentiate which traffic should remain local and which needst to go remote.
You can change the local subnet that you're running on for FiOS in the router -- Verizon has said this "won't work" because they need you to be on the 192.168.1.x network for their STB's to work properly (if you have TV), but I've done it and it works just fine. What happens however is if you ever have a service issue and reset the router, it will all default back to the 192.168.1.x network and typically Verizon won't begin troubleshooting anything until they see your network on the 192.168.1.x network. So keep that in mind.
10-01-2010 11:02 AM - edited 10-01-2010 11:34 AM
The remote is on 192.168.10.xxx
The FIOS side is on 192.168.1.xxx
I also have the latest Actiontec firmware installed.
It is interesting that I can actually do this in reverse. In other words I also have a VPN server on the FIOS side. So the remote side actually connects to the FIOS router VPN without a hassle. (Of course I have the FIOS side router port forwarding 1723.) I thought maybe this is the problem and disabled port forwarding 1723 but to no avail.
Verizon needs to provide a solution. Too many people have issues with this.
10-01-2010 01:07 PM - edited 10-01-2010 01:09 PM
are you manually configuring these vpn ports or are you using the pre-installed protocol thing from the drop down?
there is a GRE protocol that needs to get installed for it to work properly, and i've noticed when you manually build it doesn't build that GRE properly
would this have anything to do with your problem? I think this is for more when you are acting as the VPN?
If you use the preconfigured L2TP and PPTP it will automatically build in GRE and it will work.
10-03-2010 07:34 PM
The router works when it is port forwarding to my VPN server. It is only when trying to connect to an outside VPN from a workstation that has an issue whether it;s L2TP or PPTP.
10-06-2014 07:00 AM
As this thread is now over two years old, it will be locked in order to keep discussions current. If you have the same or a similar question/issue we invite you to start a new thread on the topic.