Skip to content
Search found 5 matches
Search found 5 matches
Page 1 of 1
- by orcinusxhr
- Mon Jul 27, 2015 10:30 pm
- Forum: Viscosity Support (Windows Version)
- Topic: Windows 10 does not really connect
- Replies: 17
- Views: 14756
Thank you. I'll proceed to see if these things help.
- by orcinusxhr
- Mon Jul 27, 2015 8:07 pm
- Forum: Viscosity Support (Windows Version)
- Topic: Windows 10 does not really connect
- Replies: 17
- Views: 14756
Have you installed a clean 10240 build for the lab machine?
- by orcinusxhr
- Sat Jul 25, 2015 12:38 am
- Forum: Viscosity Support (Windows Version)
- Topic: Windows 10 does not really connect
- Replies: 17
- Views: 14756
Judging by the fact that on Ubuntu 15.04 I had to use resolvconf to fix DNS for VPN, I presume the same applies to Windows 10 now.
https://github.com/masterkorp/openvpn-u ... esolv-conf
However, I have no idea how to do it on Windows
https://github.com/masterkorp/openvpn-u ... esolv-conf
However, I have no idea how to do it on Windows
- by orcinusxhr
- Tue Jul 21, 2015 7:46 pm
- Forum: Viscosity Support (Windows Version)
- Topic: Windows 10 does not really connect
- Replies: 17
- Views: 14756
Can we please do this in a non-public email? Thank you.
- by orcinusxhr
- Mon Jul 20, 2015 5:40 pm
- Forum: Viscosity Support (Windows Version)
- Topic: Windows 10 does not really connect
- Replies: 17
- Views: 14756
I'm using Viscosity on Mac and it works fine. Wanted to use it here on Windows too, but I have a strange effect - Viscosity connects, but nothing is routed correctly, network reports to be in "no access" status.
On Windows 8 it all works just fine.
On Windows 8 it all works just fine.
Search found 5 matches
Page 1 of 1