2.2.2 question



  • Hi Guys.
    after i update to 2.2.2 something strange happens.
    one of my VPN site i can connect using Viscosity tunnel is up. but can't ping the firewall or connect to any RDP computers behind.
    i can connect using OPENVPN and its works.

    any suggestions why it doesnt work with VISCOSITY ?
    other connections are working fine.



  • What does your Mac's routing table look like after connecting? 'netstat -rn' from a terminal. What does the Viscosity log show?



  • @cmb:

    What does your Mac's routing table look like after connecting? 'netstat -rn' from a terminal. What does the Viscosity log show?

    sorry i didnt mention,
    i am using Viscocity on Windows
    i've notice the client IP "169.254.236.2 is not the ip i configured to build the tunnel.

    the log i can catch is "
    Apr 17 2:39:50 AM: Warning: route gateway is not reachable on any active network adapters: 10.0.8.5
    Apr 17 2:39:50 AM: env_block: add PATH=C:\Windows\System32;C:\WINDOWS;C:\WINDOWS\System32\Wbem
    Apr 17 2:39:50 AM: Warning: route gateway is not reachable on any active network adapters: 10.0.8.5
    Apr 17 2:39:50 AM: env_block: add PATH=C:\Windows\System32;C:\WINDOWS;C:\WINDOWS\System32\Wbem
    Apr 17 2:39:50 AM: Warning: route gateway is not reachable on any active network adapters: 10.0.8.5
    Apr 17 2:39:50 AM: env_block: add PATH=C:\Windows\System32;C:\WINDOWS;C:\WINDOWS\System32\Wbem
    Apr 17 2:39:50 AM: SYSTEM ROUTING TABLE
    Apr 17 2:39:50 AM: 0.0.0.0 0.0.0.0 192.168.4.1 p=0 i=17 t=4 pr=3 a=99032 h=0 m=261/0/0/0/0
    Apr 17 2:39:50 AM: 10.0.8.1 255.255.255.255 10.0.8.5

    Thank you



  • ah, I tend to assume Viscosity==Mac.

    That log describes the root issue, it's not able to assign an IP or route. It shouldn't end up with a 169.254.x.x IP though, that indicates you have DHCP enabled on Viscosity's interface.

    Nothing in that regard would change by upgrading, something else changed related to your Viscosity or Windows system if that worked previously. There should be a lengthier log from Viscosity somewhere (not familiar with the Windows client). Compare your Viscosity config with the working OpenVPN client config.  Check the interface and Viscosity config. If Viscosity's adapter was screwed up in Windows and that's the only root cause, uninstall and reinstall of Viscosity might fix tha.t



  • I wonder if this windows viscosity client was installed with and is running as admin?



  • @cmb:

    ah, I tend to assume Viscosity==Mac.

    That log describes the root issue, it's not able to assign an IP or route. It shouldn't end up with a 169.254.x.x IP though, that indicates you have DHCP enabled on Viscosity's interface.

    Nothing in that regard would change by upgrading, something else changed related to your Viscosity or Windows system if that worked previously. There should be a lengthier log from Viscosity somewhere (not familiar with the Windows client). Compare your Viscosity config with the working OpenVPN client config.  Check the interface and Viscosity config. If Viscosity's adapter was screwed up in Windows and that's the only root cause, uninstall and reinstall of Viscosity might fix tha.t

    strange behaivor.
    just did reinstall but the issue still exist.

    i've reinstalled the VMware tools on my VM i use to connect from.
    et voila everything starts working.
    thank you for your help


Log in to reply