![]() ![]() They didn't have an answer for me on how to fix it other than to use their web-based SSLVPN feature in the firewall. I told support it works fine using a Verizon supplied FIOS router, the Comcast routers, as well as with Cisco ASA 5505 firewalls that I have configured at numerous other customers that work with no problem with multipleĬoncurrent Microsoft RRAS VPN users using Windows 2003, Windows 2008, and SBS 2008. I called Netgear, and support told me that was a limitation in the product. It also works fine using the Comcast supplied SMC firewall/gateways on cable systems. The default Verizon supplied FIOS router, that was in place before the Netgear. As soon as you connected an additional client, the first one dropped out. After testing, I found only one VPN client can stay connected. ![]() Then I started getting phone calls saying the VPNs were staying connected. I set them up, allowed "VPN Passthrough" to the RRAS server, etc, and tested the VPN from a remote client. For example, I've seen this issue at oneĬustomer site that decided to go with two Netgear ProSecure firewalls for their two locations (they needed a tunnel). Not all firewalls will exhibit this behavior. From my experience, unless anyone else points out differently, it's due to limitations on the firewall in use, especially if the firewall has a built-in VPN capability. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |