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.
LVL 27
Fred MarshallPrincipalAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Sushil SonawaneCommented:
0
Fred MarshallPrincipalAuthor Commented:
I can likely do that.
The real question is "which port(s)?"
0
Fred MarshallPrincipalAuthor 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

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Fred MarshallPrincipalAuthor 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
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows 8

From novice to tech pro — start learning today.