Page 1 of 1

Win10 client can't reach internal network after connected.

Posted: Thu Sep 13, 2018 12:51 pm
by zo718
Hello,

I have open VPN Set up on my PFsense Firewall and used client export to download the Viscosity inline config.
Everything works great in all the Mac clients running Viscosity VPN. authentication against the LDAP, ping, DNS resolution etc. They can access the internal network, work on our SMB shares with no issues.

Our Windows 10 clients using Viscosity VPN are able to authenticate. But when connected, they can't access our SMB shares and ping (to an internal IP address) or DNS resolution doesn't work as well.

Any help is much appreciated.

Re: Win10 client can't reach internal network after connected.

Posted: Fri Sep 14, 2018 11:03 am
by Eric
Hi zo718,

Please start here an also check the log for any errors or warnings - https://sparklabs.com/support/kb/articl ... connection

You are welcome to post complete copies of your logs as well as test results if you are still stuck.

Regards,
Eric