Reachability check fails:Address could not be resolved
Posted: Sat Jan 04, 2020 12:22 pm
Hi,
I am using a connection profile that was originally created a while back on a different machine, but has worked on several other machines, both work and home, until now. I now have a different home PC with Windows 10 and I am unable to get Viscosity to connect.
Now, when I attempt to connect from home, the reachability check fails and the messages in the log show:
Checking reachability status of "<host>.<domain>.com"... (redacted for privacy)
Resolving address: "<host>.<domain>.com"
Address could not be resolved: "<host>.<domain>.com".
Endpoint is not reachable, skipping.
…
No usable connection profiles are present
No valid endpoints available.
State changed to Disconnected
However, from Windows Command prompt, tracert shows the <host>.<domain>.com should be reachable:
>tracert <host>.<domain>.com
Tracing route to <host>.<domain>.com [<IP addr>]
over a maximum of 30 hops:
1 1 ms 1 ms <1 ms homeportal [192.168.236.1]
…
18 201 ms 201 ms 201 ms <host>.<domain>.com [<IP addr>]
Trace complete.
So, I don't understand what is causing Viscosity to fail.
I know my ISP provides a gateway which prevents me from modifying the DNS used, but tracert works, so that seems to be okay. The firewall also is set to allow Viscosity to work. What else on this new PC might be the culprit?
I am using a connection profile that was originally created a while back on a different machine, but has worked on several other machines, both work and home, until now. I now have a different home PC with Windows 10 and I am unable to get Viscosity to connect.
Now, when I attempt to connect from home, the reachability check fails and the messages in the log show:
Checking reachability status of "<host>.<domain>.com"... (redacted for privacy)
Resolving address: "<host>.<domain>.com"
Address could not be resolved: "<host>.<domain>.com".
Endpoint is not reachable, skipping.
…
No usable connection profiles are present
No valid endpoints available.
State changed to Disconnected
However, from Windows Command prompt, tracert shows the <host>.<domain>.com should be reachable:
>tracert <host>.<domain>.com
Tracing route to <host>.<domain>.com [<IP addr>]
over a maximum of 30 hops:
1 1 ms 1 ms <1 ms homeportal [192.168.236.1]
…
18 201 ms 201 ms 201 ms <host>.<domain>.com [<IP addr>]
Trace complete.
So, I don't understand what is causing Viscosity to fail.
I know my ISP provides a gateway which prevents me from modifying the DNS used, but tracert works, so that seems to be okay. The firewall also is set to allow Viscosity to work. What else on this new PC might be the culprit?