Skip to content
Win10 client can't reach internal network after connected.
Got a problem with Viscosity or need help? Ask here!
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.
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.
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
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
Eric Thorpe
Viscosity Developer
Web: http://www.sparklabs.com
Support: http://www.sparklabs.com/support
Twitter: http://twitter.com/sparklabs
Viscosity Developer
Web: http://www.sparklabs.com
Support: http://www.sparklabs.com/support
Twitter: http://twitter.com/sparklabs
2 posts
Page 1 of 1