Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1184
  • Last Modified:

Netgear Prosafe VPN Client not working with Windows 8 firewall

There are a number of computers that are accessing a main office using a Netgear336Gv2 router and the Netgear Prosafe VPN Client software on the clients.

It appears that the VPN won't work if the Windows firewall is turned on, on the client computer.  So, the users have turned off the firewall.  Since they need the VPN, I can't force them to turn the firewalls back on.  So I need a solution.

Normally, I would expect the firewall issues to be dealt with as part of the client softare installation - either automatically or, by instructions, manually.
Since I didn't install the client software, I can't say what was done.
I suppose that I could reinstall it just to see what it looks like and what choices there are and what happens then.....

I did try adding the Netgear VPN client software to the firewall application exceptions but it did no good.

So, I'm looking for ways to get these firewalls turned back on AND have the VPN work.
0
Fred Marshall
Asked:
Fred Marshall
  • 3
1 Solution
 
Sushil SonawaneCommented:
0
 
Fred MarshallAuthor Commented:
I can likely do that.
The real question is "which port(s)?"
0
 
Fred MarshallAuthor Commented:
I believe that I figured it out:

The Tunnel *would* be established but shared files could not be seen.

First, as background, one is well advised to select a LAN subnet for the main site which is a bit "odd".  That is, instead of 192.168.1.0/24, it might be much better to use 172.16.258.0/24.
.. the latter being in an established private range and NOT in a typical commodity range that comes as default "out of the box" of most products.
The reason for this is that the remote subnet can't match the main subnet without causing routing confusion and downright inability to communicate.

Second, with the release of Windows 7, the Windows firewall became less permissive than the Windows XP firewall.  Without adding specific scope to the File and Print Sharing for the main site, files can't be shared.  This is true whether there's a VPN connection or a private / unencrypted connection.  The rules already exist, its a matter of changing their allowed scope.

So, the solution here was to add the main site subnet to the scope of the File and Printer Sharing elements of the Windows firewall on the client.  And, we will be redoing those numbers as soon as the main site subnet is changed per the above.

Perhaps this wouldn't be a problem if the VPN weren't split at the client.
0
 
Fred MarshallAuthor Commented:
If anyone doesn't believe that there are firewall adjustments necessary for file sharing over VPN with Windows 7 and Windows 8, I'd like to hear about it and learn why!
0

Featured Post

New Tabletop Appliances Blow Competitors Away!

WatchGuard’s new T15, T35 and T55 tabletop UTMs provide the highest-performing security inspection in their class, allowing users at small offices, home offices and distributed enterprises to experience blazing-fast Internet speeds without sacrificing enterprise-grade security.

  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now