Skip to content
Doesn't complete connection
Got a problem with Viscosity or need help? Ask here!
Hi, I'm trying to set up a connection using Viscosity and get stuck before it completes. I have a MBP 2,1 with OSx 10.5.6. I'm a home user connecting to the VPN server through ADL with no NAT.
My logfile looks like this (actual ip's are replaced w xxx but i know i have the right figures):
Sun Apr 5 09:32:20 2009: LZO compression initialized
Sun Apr 5 09:32:20 2009: gw xxx.xxx.xxx.xxx
Sun Apr 5 09:32:20 2009: TUN/TAP device /dev/tap0 opened
Sun Apr 5 09:32:20 2009: /sbin/ifconfig tap0 delete
Sun Apr 5 09:32:20 2009: NOTE: Tried to delete pre-existing tun/tap instance -- No Problem if failure
Sun Apr 5 09:32:20 2009: /sbin/ifconfig tap0 xxx.xxx.xxx.xxx netmask 255.255.255.0 mtu 1500 up
Sun Apr 5 09:32:20 2009: /Applications/Viscosity.app/Contents/Resources/dnsupalt.py tap0 1500 1593 XXX.XXX.XXX.XXX 255.255.255.0 init
Sun Apr 5 09:32:21 2009: UDPv4 link local (bound): [undef]:xxxx
Sun Apr 5 09:32:21 2009: UDPv4 link remote: xxx.xxx.xxx.xxx:xxxx
Here are my settings in Viscosity (minus the real values ofc, i have double checked so i use the right numbers for my account)
So, for some reason my connection halts after I get a Client IP, any ideas? Thank you.
My logfile looks like this (actual ip's are replaced w xxx but i know i have the right figures):
Sun Apr 5 09:32:20 2009: LZO compression initialized
Sun Apr 5 09:32:20 2009: gw xxx.xxx.xxx.xxx
Sun Apr 5 09:32:20 2009: TUN/TAP device /dev/tap0 opened
Sun Apr 5 09:32:20 2009: /sbin/ifconfig tap0 delete
Sun Apr 5 09:32:20 2009: NOTE: Tried to delete pre-existing tun/tap instance -- No Problem if failure
Sun Apr 5 09:32:20 2009: /sbin/ifconfig tap0 xxx.xxx.xxx.xxx netmask 255.255.255.0 mtu 1500 up
Sun Apr 5 09:32:20 2009: /Applications/Viscosity.app/Contents/Resources/dnsupalt.py tap0 1500 1593 XXX.XXX.XXX.XXX 255.255.255.0 init
Sun Apr 5 09:32:21 2009: UDPv4 link local (bound): [undef]:xxxx
Sun Apr 5 09:32:21 2009: UDPv4 link remote: xxx.xxx.xxx.xxx:xxxx
Here are my settings in Viscosity (minus the real values ofc, i have double checked so i use the right numbers for my account)
So, for some reason my connection halts after I get a Client IP, any ideas? Thank you.
Hi nuthead,
A few points:
- You shouldn't need to have the port listed twice. Try removing the "port xxx" command from the Advanced tab, and just make sure the port number is correct under the General tab
- Remove the "route-delay 40" command under the Advanced tab as well. Viscosity automatically adds a route delay of 20 seconds for TAP connections
- Try manually specifying the local routes for the remote network under the Networking tab. For example, if the remote network uses an IP range of 192.168.0.x, specify a route of 192.168.0.0/255.255.2550.0 under the Networking tab.
- During testing you may like to try unticking the "Send all traffic over VPN connection" option until you can get a stable connection and can ping other local machines
- If you are in control of the VPN server, try using a TCP connection instead of UDP. Troubleshooting connection issues with TCP is generally easier (you can switch back to UDP one the connection is working).
- Check to see if you can ping any machines on the remote network (even if Viscosity thinks the connection still hasn't connected)
Cheers,
James
A few points:
- You shouldn't need to have the port listed twice. Try removing the "port xxx" command from the Advanced tab, and just make sure the port number is correct under the General tab
- Remove the "route-delay 40" command under the Advanced tab as well. Viscosity automatically adds a route delay of 20 seconds for TAP connections
- Try manually specifying the local routes for the remote network under the Networking tab. For example, if the remote network uses an IP range of 192.168.0.x, specify a route of 192.168.0.0/255.255.2550.0 under the Networking tab.
- During testing you may like to try unticking the "Send all traffic over VPN connection" option until you can get a stable connection and can ping other local machines
- If you are in control of the VPN server, try using a TCP connection instead of UDP. Troubleshooting connection issues with TCP is generally easier (you can switch back to UDP one the connection is working).
- Check to see if you can ping any machines on the remote network (even if Viscosity thinks the connection still hasn't connected)
Cheers,
James
Web: https://www.sparklabs.com
Support: https://www.sparklabs.com/support
Twitter: https://twitter.com/sparklabs
Support: https://www.sparklabs.com/support
Twitter: https://twitter.com/sparklabs
4 posts
Page 1 of 1