what's been consistent about the installs?Īnd each system has had Avast installled. So at this point I'm going through the non-variables. I even had the cable company come out, test my lines for connectivity and then swap out my router for a new one. The one temp fix that seems to work is manually changing the IPv4 DNS address, but as mentioned earlier, the settings never hold. I've tried troubleshooting with the TorGuard techs by toggling various DNS settings in Viscosity or the TorGuard app on or off, or disabling IPv6 in the Windows (non VPN ) network adapter. The solution is to add the redirect command in Extra OpenVPN configuration commands. plus the multiple scans show nothing, different OS installs, etc. It's not like virus behavior - that usually happens in the other direction - it would be going from Obtain Automatically routed to another DNS for the virus to intercept traffic. This works temporarily, but the adapter keeps resetting back to "Obtain IP Automatically". One of the troubleshooting things I've tried is to manually set the IPv4 DNS addresses. multiple scans, multiple times - on two platforms (Win 7 and Win 10), two different mobo's (the other one a Gigabyte board), updated drivers, etc. I can also do this manually, but either method is a temp fix it still doesn't resolve the internet kick outs and having to start over, by re-installing the network adapter again. Occasionally the problem can be resolved by turning off the VPN and rebooting, but usually I have to uninstall the Network adapter in Device Manager, and then reboot and let Windows ID then re-install the drivers. Basically, the VPN app would force all traffic that goes through the VPN Server instead of the Proxyman Local Server (127.0.0.1:9090). Error messages on web pages are generally just disconnect or DNS relate: I have set the Internal View to allow queries from both .x and the OpenVPN 172.22.x.x subnets. Logs and UI show connection to VPN successful. Hosts: OSX hosts (Mojave, Catalina) using Viscosity client. I get the yellow disconnected warning triangle in the taskbar network icon. Firewall config appears all good and DNS config - prior to VPN also appears all good). The JAMF applications log is unhelpful as it just says There was a problem installing Viscosity VPN. What happens is that the regualr Windows (non VPN) adapter stops working properly. I've had a an ongoing problem with my internet kicking out while running through the VPN. I'm using TorGuard VPN service with the Viscosity app provided by TorGuard, v1. I'm always connected via Ethernet LAN (no wifi) connection is high speed Turbo via co-ax cable 07:21:59: The OpenVPN subsystem could not be started.I'm running Win 10 pro v1511 buil 10586.420 07:21:59: Full command: block-outside-dns Please edit the connection, make sure the command is valid, and try again. 07:21:59: Options error: The command "block-outside-dns" or one of its parameters is invalid for this version of OpenVPN (2.4.11). To resolve this you should first check the OpenVPN log. 07:21:59: Checking reachability status of connection. If Viscosity's icon spins forever, or you receive an error message indicating a connection could not be established, it usually indicates that Viscosity is unable to start the connection or connect to the VPN server. 07:21:59: Viscosity OpenVPN Engine Started My Viscosity's icon isn't even spinning for a sec, and it's a direct connection failure. But it's not connected to my OpenVPN server, I tested the same config file with Tunnelblick, and it's working fine there. I am using the mac version of Viscosity (v1.9.4:1578).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |