SparkLabs Forum.

Community Help.


After Windows 10 anniversary update VPN won't work

Hi,
I was using my VPN no problems, then my computer updated with the Windows 10 Anniverary update (1607 release start of August) and after that I had problems. Viscosity could connect fine, it said connected, nothing in the logs, but I can't connect to any of the machines on my office network. I can't ping them etc.
Many hours of trying to fix this, I found that if I use the route-delay option, then within the time the VPN connects - and before the route-delay has expired - I seem to have access to the office machines!! So if I add an option like:
route-delay 100000000
Then although Viscosity says "Connecting" - I am actually connected, and I can use the VPN as normal - * although not all the routes that I configured in Viscosity took effect yet so I have to add them manually.
Hi cwasyl,

This indicates that the routes set in your configuration, or being pushed by the VPN Server are incorrect. Are you able to post (you may prefer to email this to us instead) a copy of your route table before and after you have connected and we can take a look, as well as an example IP address that you are trying to connect to that doesn't work with routes applied.

Regards,
Eric
Hello I'm getting the same exact issue, and hit route delay option works for me too. Smae version of windows same exact situation was working fine then updated and not working.

I've completely removed the client rebooted, reinstalled with admin, still doing the same exact thing.

Using Pfsense 2.2.6 on the server side, and the latest Viscosity client. What other info do you need? I could send my route tables but yes would rather email them, can you let me know an address you prefer? Thank you!
Hi Shadokin,

Please send us a complete copy of your OpenVPN log, routing table before and after connecting and your configuration as exported from Viscosity (we only need the config.conf file) to [email protected]

Regards,
Eric
Sent all details, looking forward to your help!
Hello,

I seem to be having the same problem with several Windows 10 machines, but not my mac. The Windows machines can connect, but can't access our LAN while connected. Looking at the routing table, the routes for the VPN subnet are there, but not the route for our LAN. On the mac, all the routes appear and everything works fine.

Has anyone found a solution?
Hi Elgin,

Is your LAN the local network the user is on, or the LAN they wish to access through the VPN? Is the VPN server pushing a route for this LAN or is one set in the client configuration?

Regards,
Eric
Eric wrote:
Hi Elgin,

Is your LAN the local network the user is on, or the LAN they wish to access through the VPN? Is the VPN server pushing a route for this LAN or is one set in the client configuration?

Regards,
Eric


How can you tell if the VPN server is pushing a route?
Hi Humbert,

You will need to check your routing table to see if the route is present, or increase the verb (edit your connection, go to Advanced, add verb 5) to see what options the server is pushing in the log.

Regards,
Eric
9 posts Page 1 of 1

Copyright © 2016 SparkLabs Pty Ltd. All Rights Reserved. Privacy Policy