Page 1 of 1

Unable to connect to hosts on network

Posted: Thu Sep 03, 2020 6:39 am
by Maiadog
Hi,

I am trying to figure out why I can't reach any hosts through viscosity. All other computer have no problems with a similar configuration. The VPN connection connects fine, and I am routing all traffic for the 192.168.0.0 network through the VPN gateway, and I cannot connect to or ping any of the available hosts by name or IP. Other remote computers using the same configuration work fine. Here is a connection log, any help is appreciated:

Sep 02 4:36:16 PM: State changed to Connecting
Sep 02 4:36:16 PM: Viscosity Windows 1.8.6 (1682)
Sep 02 4:36:16 PM: Running on Microsoft Windows 7 Home Premium 64 bit
Sep 02 4:36:16 PM: Running on .NET Framework Version 4.6.01590.394806
Sep 02 4:36:16 PM: Checking reachability status of connection...
Sep 02 4:36:16 PM: Connection is reachable. Starting connection attempt.
Sep 02 4:36:17 PM: Bringing up interface...
Sep 02 4:36:17 PM: OpenVPN 2.4.9 Windows-MSVC [SSL (OpenSSL)] [LZO] [LZ4] [AEAD] built on Jul 8 2020
Sep 02 4:36:17 PM: library versions: OpenSSL 1.1.1g 21 Apr 2020, LZO 2.10
Sep 02 4:36:17 PM: Valid endpoint found: 108.58.159.250:1194:udp
Sep 02 4:36:17 PM: TCP/UDP: Preserving recently used remote address: [AF_INET]108.58.159.250:1194
Sep 02 4:36:17 PM: UDP link local: (not bound)
Sep 02 4:36:17 PM: UDP link remote: [AF_INET]108.58.159.250:1194
Sep 02 4:36:17 PM: State changed to Authenticating
Sep 02 4:36:17 PM: [server] Peer Connection Initiated with [AF_INET]108.58.159.250:1194
Sep 02 4:36:17 PM: State changed to Connecting
Sep 02 4:36:17 PM: Awaiting adapter to come up...
Sep 02 4:36:17 PM: TAP-WIN32 device [openvpn-EricKrapohl-inline] opened: \\.\Global\{57107BED-22CA-4496-9C4A-B6ED4E4C176B}.tap, index: 19
Sep 02 4:36:17 PM: Waiting for DNS Setup to complete...
Sep 02 4:36:31 PM: Successful ARP Flush on interface [19] {57107BED-22CA-4496-9C4A-B6ED4E4C176B}
Sep 02 4:36:31 PM: [server] Inactivity timeout (--ping-restart), restarting
Sep 02 4:36:31 PM: SIGUSR1[soft,ping-restart] received, process restarting
Sep 02 4:36:31 PM: State changed to Connecting
Sep 02 4:36:31 PM: Valid endpoint found: 108.58.159.250:1194:udp
Sep 02 4:36:31 PM: TCP/UDP: Preserving recently used remote address: [AF_INET]108.58.159.250:1194
Sep 02 4:36:31 PM: UDP link local: (not bound)
Sep 02 4:36:31 PM: UDP link remote: [AF_INET]108.58.159.250:1194
Sep 02 4:36:31 PM: State changed to Authenticating
Sep 02 4:36:31 PM: [server] Peer Connection Initiated with [AF_INET]108.58.159.250:1194
Sep 02 4:36:31 PM: State changed to Connecting
Sep 02 4:36:31 PM: Preserving previous TUN/TAP instance: openvpn-EricKrapohl-inline
Sep 02 4:36:31 PM: WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
Sep 02 4:36:31 PM: Initialization Sequence Completed
Sep 02 4:36:31 PM: DNS set to Split, report follows:
Server - 172.16.130.1:53; Lookup Type - Split; Domains - barone.internal.
Server - 192.168.0.10:53; Lookup Type - Split; Domains - barone.internal.
Server - 192.168.1.1:53; Lookup Type - Any; Domains - ptd.net.

Sep 02 4:36:31 PM: State changed to Connected

Re: Unable to connect to hosts on network

Posted: Thu Sep 03, 2020 9:01 am
by Eric
Hi Maiadog,

At a glance from your log, my first guess would be a firewall is blocking traffic on your local PC. This could be AV software as well blocking OpenVPN traffic. Please try rebooting, disabling any AV or firewall software you have installed and trying again.

Are you able to ping the VPN server directly through the tunnel?

Regards,
Eric

Re: Unable to connect to hosts on network

Posted: Fri Sep 04, 2020 5:31 am
by Maiadog
Thanks for the response. No, I am unable to ping. The user had Norton 360 (which I removed completely), Malwarebytes (which I disabled completely) and Windows firewall (which I had also disabled) and the problem still persisted. Is there anything else I might look at?

Re: Unable to connect to hosts on network

Posted: Fri Sep 04, 2020 9:20 am
by Eric
Hi Maiadog,

If you are unable to ping the VPN Server, it means that either something is blocking the traffic at either the local or remote end, or the server or client is misconfigured, for example non-matching or too aggressive ping-restart values.

You may wish to try dropping the users MTU and fragment values to see if this helps as well, if it does it would indicate the users internet or local network is unstable or misconfigured.

There could also be a route clash if the VPN connection is pushing IP addresses or routes similar to the users local network.

Regards,
Eric