Connects, but doesn't work (FIXED)

Got a problem with Viscosity or need help? Ask here!

DonnEdwards

Posts: 10
Joined: Fri Jun 28, 2013 7:00 pm

Post by DonnEdwards » Fri Jun 28, 2013 7:43 pm
Hi everyone
Yesterday I installed Viscosity on my Windows Vista laptop, loaded the SwissVPN.visz config file for SwissVPN.net, and it all works perfectly. I supplied the user login and password for my account, and tested my new IP address on Shields Up. Sure enough it reported that I was connecting to the internet in Switzerland, and my google searches sharted asking me if I wanted to use google.ch in German or French. All good so far.

Today I am trying the exact same thing on my Windows 7 Home Premium PC (office machine), and it simply will not work. I have included two log files, one running viscosity as a "normal" user, and the other as an "administrator" using the "Run as administrator" option and then clicking "yes" when the UAC dialog box pops up.

I have taken great care to make sure I'm not trying to connect from both computers at the same time.

The connection icon goes green, but when I run Shields Up it tells me that I am still connected to the internet from my South African ISP, not SwissVPN.

One other thing: I run "Peerblock 1.1" from my PC, not from my laptop. I quit from this program, but it didn't make any difference. Apart from that, the machines have largely the same software installed.

Any suggestions on what to try next will be greatly appreciated.
Donn
Code: Select all
Not run as administrator:
Jun 28 10:53:07: State changed to Connecting
Jun 28 10:53:07: Viscosity 1.4.4 (1191)
Jun 28 10:53:07: Running on Microsoft Windows 7 Home Premium 
Jun 28 10:53:08: Bringing up interface...
Jun 28 10:53:08: Checking reachability status of connection...
Jun 28 10:53:08: Connection is reachable. Starting connection attempt.
Jun 28 10:53:09: OpenVPN 2.2.2 Win32-MSVC++ [SSL] [LZO2] [PKCS11] built on Jan  4 2012
Jun 28 10:53:10: WARNING: No server certificate verification method has been enabled.  See http://openvpn.net/howto.html#mitm for more info.
Jun 28 10:53:10: NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Jun 28 10:53:10: RESOLVE: NOTE: connect-openvpn.swissvpn.net resolves to 3 addresses
Jun 28 10:53:10: Attempting to establish TCP connection with 80.254.79.101:443
Jun 28 10:53:10: TCP connection established with 80.254.79.101:443
Jun 28 10:53:10: TCPv4_CLIENT link local: [undef]
Jun 28 10:53:10: TCPv4_CLIENT link remote: 80.254.79.101:443
Jun 28 10:53:11: WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
Jun 28 10:53:19: [server] Peer Connection Initiated with 80.254.79.101:443
Jun 28 10:53:22: TAP-WIN32 device [SwissVPN] opened: \\.\Global\{B9555F38-5C3A-4A24-804C-11058E6190D1}.tap
Jun 28 10:53:22: Set TAP-Win32 TUN subnet mode network/local/netmask = 93.94.245.0/93.94.245.16/255.255.255.128 [SUCCEEDED]
Jun 28 10:53:22: Notified TAP-Win32 driver to set a DHCP IP/netmask of 93.94.245.16/255.255.255.128 on interface {B9555F38-5C3A-4A24-804C-11058E6190D1} [DHCP-serv: 93.94.245.126, lease-time: 31536000]
Jun 28 10:53:22: Successful ARP Flush on interface [16] {B9555F38-5C3A-4A24-804C-11058E6190D1}
Jun 28 10:53:57: Warning: route gateway is not reachable on any active network adapters: 93.94.245.1
Jun 28 10:53:57: Warning: route gateway is not reachable on any active network adapters: 93.94.245.1
Jun 28 10:53:57: SYSTEM ROUTING TABLE
Jun 28 10:53:57: 0.0.0.0 0.0.0.0 192.10.200.250 p=0 i=10 t=4 pr=3 a=260377 h=0 m=276/0/0/0/0
Jun 28 10:53:57: 0.0.0.0 128.0.0.0 93.94.245.1 p=0 i=10 t=4 pr=3 a=0 h=0 m=21/0/0/0/0
Jun 28 10:53:57: 80.254.79.101 255.255.255.255 192.10.200.250 p=0 i=10 t=4 pr=3 a=0 h=0 m=20/0/0/0/0
Jun 28 10:53:57: 127.0.0.0 255.0.0.0 127.0.0.1 p=0 i=1 t=3 pr=3 a=260385 h=0 m=306/0/0/0/0
Jun 28 10:53:57: 127.0.0.1 255.255.255.255 127.0.0.1 p=0 i=1 t=3 pr=3 a=260385 h=0 m=306/0/0/0/0
Jun 28 10:53:57: 127.255.255.255 255.255.255.255 127.0.0.1 p=0 i=1 t=3 pr=3 a=260385 h=0 m=306/0/0/0/0
Jun 28 10:53:57: 128.0.0.0 128.0.0.0 93.94.245.1 p=0 i=10 t=4 pr=3 a=0 h=0 m=21/0/0/0/0
Jun 28 10:53:57: 169.254.0.0 255.255.0.0 169.254.186.230 p=0 i=16 t=3 pr=3 a=32 h=0 m=286/0/0/0/0
Jun 28 10:53:57: 169.254.186.230 255.255.255.255 169.254.186.230 p=0 i=16 t=3 pr=3 a=32 h=0 m=286/0/0/0/0
Jun 28 10:53:57: 169.254.255.255 255.255.255.255 169.254.186.230 p=0 i=16 t=3 pr=3 a=32 h=0 m=286/0/0/0/0
Jun 28 10:53:57: 192.10.200.0 255.255.255.0 192.10.200.102 p=0 i=10 t=3 pr=3 a=260371 h=0 m=276/0/0/0/0
Jun 28 10:53:57: 192.10.200.102 255.255.255.255 192.10.200.102 p=0 i=10 t=3 pr=3 a=260371 h=0 m=276/0/0/0/0
Jun 28 10:53:57: 192.10.200.255 255.255.255.255 192.10.200.102 p=0 i=10 t=3 pr=3 a=260371 h=0 m=276/0/0/0/0
Jun 28 10:53:57: 224.0.0.0 240.0.0.0 127.0.0.1 p=0 i=1 t=3 pr=3 a=260385 h=0 m=306/0/0/0/0
Jun 28 10:53:57: 224.0.0.0 240.0.0.0 192.10.200.102 p=0 i=10 t=3 pr=3 a=260377 h=0 m=276/0/0/0/0
Jun 28 10:53:57: 224.0.0.0 240.0.0.0 169.254.186.230 p=0 i=16 t=3 pr=3 a=50 h=0 m=286/0/0/0/0
Jun 28 10:53:57: 255.255.255.255 255.255.255.255 127.0.0.1 p=0 i=1 t=3 pr=3 a=260385 h=0 m=306/0/0/0/0
Jun 28 10:53:57: 255.255.255.255 255.255.255.255 192.10.200.102 p=0 i=10 t=3 pr=3 a=260377 h=0 m=276/0/0/0/0
Jun 28 10:53:57: 255.255.255.255 255.255.255.255 169.254.186.230 p=0 i=16 t=3 pr=3 a=50 h=0 m=286/0/0/0/0
Jun 28 10:53:57: SYSTEM ADAPTER LIST
Jun 28 10:53:57: Viscosity Virtual Adapter V9.1
Jun 28 10:53:57:   Index = 16
Jun 28 10:53:57:   GUID = {B9555F38-5C3A-4A24-804C-11058E6190D1}
Jun 28 10:53:57:   IP = 169.254.186.230/255.255.0.0 
Jun 28 10:53:57:   MAC = 00:ff:b9:55:5f:38
Jun 28 10:53:57:   GATEWAY = 0.0.0.0/255.255.255.255 
Jun 28 10:53:57:   DHCP SERV =  
Jun 28 10:53:57:   DHCP LEASE OBTAINED = Fri Jun 28 10:53:58 2013
Jun 28 10:53:57:   DHCP LEASE EXPIRES  = Thu Jan 01 02:00:00 1970
Jun 28 10:53:57:   DNS SERV =  
Jun 28 10:53:57: Realtek RTL8102E/RTL8103E Family PCI-E Fast Ethernet NIC (NDIS 6.20)
Jun 28 10:53:57:   Index = 10
Jun 28 10:53:57:   GUID = {64C19529-8789-4639-A5DB-CF2C456F88CE}
Jun 28 10:53:57:   IP = 192.10.200.102/255.255.255.0 
Jun 28 10:53:57:   MAC = 00:19:66:a1:47:d2
Jun 28 10:53:57:   GATEWAY = 192.10.200.250/255.255.255.255 
Jun 28 10:53:57:   DNS SERV = 196.22.160.12/255.255.255.255 8.8.8.8/255.255.255.255 208.67.222.222/255.255.255.255 168.210.2.2/255.255.255.255 196.207.35.29/255.255.255.255 196.28.182.12/255.255.255.255 196.14.239.2/255.255.255.255 80.254.79.157/255.255.255.255 
Jun 28 10:53:57: Initialization Sequence Completed With Errors ( see http://openvpn.net/faq.html#dhcpclientserv )
Jun 28 10:53:58: State changed to Connected
and
Code: Select all
Run as Admin
Jun 28 10:47:56: State changed to Connecting
Jun 28 10:47:56: Viscosity 1.4.4 (1191)
Jun 28 10:47:56: Running on Microsoft Windows 7 Home Premium 
Jun 28 10:47:56: Bringing up interface...
Jun 28 10:47:56: Checking reachability status of connection...
Jun 28 10:47:57: Connection is reachable. Starting connection attempt.
Jun 28 10:47:57: OpenVPN 2.2.2 Win32-MSVC++ [SSL] [LZO2] [PKCS11] built on Jan  4 2012
Jun 28 10:47:58: WARNING: No server certificate verification method has been enabled.  See http://openvpn.net/howto.html#mitm for more info.
Jun 28 10:47:58: NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Jun 28 10:47:58: RESOLVE: NOTE: connect-openvpn.swissvpn.net resolves to 3 addresses
Jun 28 10:47:58: Attempting to establish TCP connection with 80.254.79.87:443
Jun 28 10:47:58: TCP connection established with 80.254.79.87:443
Jun 28 10:47:58: TCPv4_CLIENT link local: [undef]
Jun 28 10:47:58: TCPv4_CLIENT link remote: 80.254.79.87:443
Jun 28 10:47:59: WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
Jun 28 10:48:05: [server] Peer Connection Initiated with 80.254.79.87:443
Jun 28 10:48:08: TAP-WIN32 device [SwissVPN] opened: \\.\Global\{B9555F38-5C3A-4A24-804C-11058E6190D1}.tap
Jun 28 10:48:08: Set TAP-Win32 TUN subnet mode network/local/netmask = 80.254.76.128/80.254.76.242/255.255.255.128 [SUCCEEDED]
Jun 28 10:48:08: Notified TAP-Win32 driver to set a DHCP IP/netmask of 80.254.76.242/255.255.255.128 on interface {B9555F38-5C3A-4A24-804C-11058E6190D1} [DHCP-serv: 80.254.76.254, lease-time: 31536000]
Jun 28 10:48:08: Successful ARP Flush on interface [16] {B9555F38-5C3A-4A24-804C-11058E6190D1}
Jun 28 10:48:44: Warning: route gateway is not reachable on any active network adapters: 80.254.76.129
Jun 28 10:48:44: Warning: route gateway is not reachable on any active network adapters: 80.254.76.129
Jun 28 10:48:44: SYSTEM ROUTING TABLE
Jun 28 10:48:44: 0.0.0.0 0.0.0.0 192.10.200.250 p=0 i=10 t=4 pr=3 a=260060 h=0 m=276/0/0/0/0
Jun 28 10:48:44: 0.0.0.0 128.0.0.0 80.254.76.129 p=0 i=10 t=4 pr=3 a=0 h=0 m=21/0/0/0/0
Jun 28 10:48:44: 80.254.79.87 255.255.255.255 192.10.200.250 p=0 i=10 t=4 pr=3 a=0 h=0 m=20/0/0/0/0
Jun 28 10:48:44: 127.0.0.0 255.0.0.0 127.0.0.1 p=0 i=1 t=3 pr=3 a=260068 h=0 m=306/0/0/0/0
Jun 28 10:48:44: 127.0.0.1 255.255.255.255 127.0.0.1 p=0 i=1 t=3 pr=3 a=260068 h=0 m=306/0/0/0/0
Jun 28 10:48:44: 127.255.255.255 255.255.255.255 127.0.0.1 p=0 i=1 t=3 pr=3 a=260068 h=0 m=306/0/0/0/0
Jun 28 10:48:44: 128.0.0.0 128.0.0.0 80.254.76.129 p=0 i=10 t=4 pr=3 a=0 h=0 m=21/0/0/0/0
Jun 28 10:48:44: 169.254.0.0 255.255.0.0 169.254.186.230 p=0 i=16 t=3 pr=3 a=32 h=0 m=286/0/0/0/0
Jun 28 10:48:44: 169.254.186.230 255.255.255.255 169.254.186.230 p=0 i=16 t=3 pr=3 a=32 h=0 m=286/0/0/0/0
Jun 28 10:48:44: 169.254.255.255 255.255.255.255 169.254.186.230 p=0 i=16 t=3 pr=3 a=32 h=0 m=286/0/0/0/0
Jun 28 10:48:44: 192.10.200.0 255.255.255.0 192.10.200.102 p=0 i=10 t=3 pr=3 a=260055 h=0 m=276/0/0/0/0
Jun 28 10:48:44: 192.10.200.102 255.255.255.255 192.10.200.102 p=0 i=10 t=3 pr=3 a=260055 h=0 m=276/0/0/0/0
Jun 28 10:48:44: 192.10.200.255 255.255.255.255 192.10.200.102 p=0 i=10 t=3 pr=3 a=260055 h=0 m=276/0/0/0/0
Jun 28 10:48:44: 224.0.0.0 240.0.0.0 127.0.0.1 p=0 i=1 t=3 pr=3 a=260068 h=0 m=306/0/0/0/0
Jun 28 10:48:44: 224.0.0.0 240.0.0.0 192.10.200.102 p=0 i=10 t=3 pr=3 a=260060 h=0 m=276/0/0/0/0
Jun 28 10:48:44: 224.0.0.0 240.0.0.0 169.254.186.230 p=0 i=16 t=3 pr=3 a=47 h=0 m=286/0/0/0/0
Jun 28 10:48:44: 255.255.255.255 255.255.255.255 127.0.0.1 p=0 i=1 t=3 pr=3 a=260068 h=0 m=306/0/0/0/0
Jun 28 10:48:44: 255.255.255.255 255.255.255.255 192.10.200.102 p=0 i=10 t=3 pr=3 a=260060 h=0 m=276/0/0/0/0
Jun 28 10:48:44: 255.255.255.255 255.255.255.255 169.254.186.230 p=0 i=16 t=3 pr=3 a=47 h=0 m=286/0/0/0/0
Jun 28 10:48:44: SYSTEM ADAPTER LIST
Jun 28 10:48:44: Viscosity Virtual Adapter V9.1
Jun 28 10:48:44:   Index = 16
Jun 28 10:48:44:   GUID = {B9555F38-5C3A-4A24-804C-11058E6190D1}
Jun 28 10:48:44:   IP = 169.254.186.230/255.255.0.0 
Jun 28 10:48:44:   MAC = 00:ff:b9:55:5f:38
Jun 28 10:48:44:   GATEWAY = 0.0.0.0/255.255.255.255 
Jun 28 10:48:44:   DHCP SERV =  
Jun 28 10:48:44:   DHCP LEASE OBTAINED = Fri Jun 28 10:48:44 2013
Jun 28 10:48:44:   DHCP LEASE EXPIRES  = Thu Jan 01 02:00:00 1970
Jun 28 10:48:44:   DNS SERV =  
Jun 28 10:48:44: Realtek RTL8102E/RTL8103E Family PCI-E Fast Ethernet NIC (NDIS 6.20)
Jun 28 10:48:44:   Index = 10
Jun 28 10:48:44:   GUID = {64C19529-8789-4639-A5DB-CF2C456F88CE}
Jun 28 10:48:44:   IP = 192.10.200.102/255.255.255.0 
Jun 28 10:48:44:   MAC = 00:19:66:a1:47:d2
Jun 28 10:48:44:   GATEWAY = 192.10.200.250/255.255.255.255 
Jun 28 10:48:44:   DNS SERV = 196.22.160.12/255.255.255.255 8.8.8.8/255.255.255.255 208.67.222.222/255.255.255.255 168.210.2.2/255.255.255.255 196.207.35.29/255.255.255.255 196.28.182.12/255.255.255.255 196.14.239.2/255.255.255.255 80.254.79.157/255.255.255.255 
Jun 28 10:48:44: Initialization Sequence Completed With Errors ( see http://openvpn.net/faq.html#dhcpclientserv )
Jun 28 10:48:44: State changed to Connected
From my laptop:
Code: Select all
Jun 28 11:40:06: State changed to Connecting
Jun 28 11:40:06: Viscosity 1.4.4 (1191)
Jun 28 11:40:06: Running on Microsoft® Windows Vista™ Business 
Jun 28 11:40:06: Bringing up interface...
Jun 28 11:40:12: Checking reachability status of connection...
Jun 28 11:40:14: Connection is reachable. Starting connection attempt.
Jun 28 11:40:15: OpenVPN 2.2.2 Win32-MSVC++ [SSL] [LZO2] [PKCS11] built on Jan  4 2012
Jun 28 11:40:18: WARNING: No server certificate verification method has been enabled.  See http://openvpn.net/howto.html#mitm for more info.
Jun 28 11:40:18: NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Jun 28 11:40:18: RESOLVE: NOTE: connect-openvpn.swissvpn.net resolves to 3 addresses
Jun 28 11:40:18: Attempting to establish TCP connection with 80.254.79.115:443
Jun 28 11:40:18: TCP connection established with 80.254.79.115:443
Jun 28 11:40:18: TCPv4_CLIENT link local: [undef]
Jun 28 11:40:18: TCPv4_CLIENT link remote: 80.254.79.115:443
Jun 28 11:40:19: WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
Jun 28 11:40:29: [server] Peer Connection Initiated with 80.254.79.115:443
Jun 28 11:40:32: TAP-WIN32 device [SwissVPN] opened: \\.\Global\{EE0E7317-F7AB-44D2-AF53-5C25F1C4C368}.tap
Jun 28 11:40:32: Set TAP-Win32 TUN subnet mode network/local/netmask = 109.205.170.0/109.205.170.35/255.255.255.128 [SUCCEEDED]
Jun 28 11:40:32: Notified TAP-Win32 driver to set a DHCP IP/netmask of 109.205.170.35/255.255.255.128 on interface {EE0E7317-F7AB-44D2-AF53-5C25F1C4C368} [DHCP-serv: 109.205.170.126, lease-time: 31536000]
Jun 28 11:40:32: Successful ARP Flush on interface [99] {EE0E7317-F7AB-44D2-AF53-5C25F1C4C368}
Jun 28 11:40:37: Initialization Sequence Completed
Jun 28 11:40:38: State changed to Connected
Last edited by DonnEdwards on Sun Jun 30, 2013 1:14 am, edited 1 time in total.
Donn Edwards
Johannesburg, South Africa

Eric

User avatar
Posts: 969
Joined: Sun Jan 03, 2010 3:27 am

Post by Eric » Sat Jun 29, 2013 3:33 pm
Hi Donn,

It would appear your work computer has some firewall or AV software that is interfering with the Network Interface Viscosity uses to maintain your connection, this is apparent from the line showing that dhcp is failing:

Initialization Sequence Completed With Errors ( see http://openvpn.net/faq.html#dhcpclientserv )

This is unfortunately not an uncommon problem that we are working on finding an automatic solution for ourselves. In the mean time, you can make a slight alteration to your configuration to hopefully relieve the problem.

Edit your connection the computer having problems and go to the Advanced tab. On a new line in Advanced commands, add the following:

ip-win32 netsh

Then save the connection and try to connect again.

Let us know if this helps.

Regards,

Erc
Eric Thorpe
Viscosity Developer

Web: http://www.sparklabs.com
Support: http://www.sparklabs.com/support
Twitter: http://twitter.com/sparklabs

DonnEdwards

Posts: 10
Joined: Fri Jun 28, 2013 7:00 pm

Post by DonnEdwards » Sat Jun 29, 2013 10:29 pm
Thanks for such a prompt response. Before trying the remedy you suggested, I had uninstalled Viscosity completely, and used CCleaner's registry checker to ensure there were not traces of the install.

Next, after a full shutdown, I reinstalled Viscosity, and shut the PC down again. Finally, I ran Viscosity ad an administrator and set up the network for SwissVPN. Here is the result:
Code: Select all
Jun 29 02:15:35: State changed to Connecting
Jun 29 02:15:35: Viscosity 1.4.4 (1191)
Jun 29 02:15:35: Running on Microsoft Windows 7 Home Premium 
Jun 29 02:15:35: Bringing up interface...
Jun 29 02:15:35: Checking reachability status of connection...
Jun 29 02:15:36: Connection is reachable. Starting connection attempt.
Jun 29 02:15:36: OpenVPN 2.2.2 Win32-MSVC++ [SSL] [LZO2] [PKCS11] built on Jan  4 2012
Jun 29 02:15:38: WARNING: No server certificate verification method has been enabled.  See http://openvpn.net/howto.html#mitm for more info.
Jun 29 02:15:38: NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Jun 29 02:15:38: RESOLVE: NOTE: connect-openvpn.swissvpn.net resolves to 3 addresses
Jun 29 02:15:38: Attempting to establish TCP connection with 80.254.79.115:443
Jun 29 02:15:38: TCP connection established with 80.254.79.115:443
Jun 29 02:15:38: TCPv4_CLIENT link local: [undef]
Jun 29 02:15:38: TCPv4_CLIENT link remote: 80.254.79.115:443
Jun 29 02:15:38: WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent thisJun 29 02:15:45: [server] Peer Connection Initiated with 80.254.79.115:443
Jun 29 02:15:49: NETSH: C:\WINDOWS\system32\netsh.exe interface ip set address SwissVPN static 109.205.170.57 255.255.255.128
Jun 29 02:15:49: ERROR: netsh command failed: returned error code 1
Jun 29 02:15:54: NETSH: C:\WINDOWS\system32\netsh.exe interface ip set address SwissVPN static 109.205.170.57 255.255.255.128
Jun 29 02:15:54: ERROR: netsh command failed: returned error code 1
Jun 29 02:15:59: NETSH: C:\WINDOWS\system32\netsh.exe interface ip set address SwissVPN static 109.205.170.57 255.255.255.128
Jun 29 02:16:00: ERROR: netsh command failed: returned error code 1
Jun 29 02:16:05: NETSH: C:\WINDOWS\system32\netsh.exe interface ip set address SwissVPN static 109.205.170.57 255.255.255.128
Jun 29 02:16:05: ERROR: netsh command failed: returned error code 1
Jun 29 02:16:09: WARNING: No server certificate verification method has been enabled.  See http://openvpn.net/howto.html#mitm for more info.
Jun 29 02:16:09: NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Jun 29 02:16:09: RESOLVE: NOTE: connect-openvpn.swissvpn.net resolves to 3 addresses
Jun 29 02:16:09: Attempting to establish TCP connection with 80.254.79.115:443
Jun 29 02:16:09: TCP connection established with 80.254.79.115:443
Jun 29 02:16:09: TCPv4_CLIENT link local: [undef]
Jun 29 02:16:09: TCPv4_CLIENT link remote: 80.254.79.115:443
Jun 29 02:16:09: WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
Jun 29 02:16:09: [server] Peer Connection Initiated with 80.254.79.115:443
Jun 29 02:16:09: NETSH: C:\WINDOWS\system32\netsh.exe interface ip set address SwissVPN static 109.205.170.57 255.255.255.128
Jun 29 02:16:09: The RPC server is unavailable.
Jun 29 02:16:10: State changed to Disconnected
Next, I disabled the Windows Firewall and NOD32 Antivirus, and tried again:
Code: Select all
Jun 29 02:23:08: State changed to Connecting
Jun 29 02:23:08: Viscosity 1.4.4 (1191)
Jun 29 02:23:08: Running on Microsoft Windows 7 Home Premium 
Jun 29 02:23:08: Bringing up interface...
Jun 29 02:23:08: Checking reachability status of connection...
Jun 29 02:23:09: Connection is reachable. Starting connection attempt.
Jun 29 02:23:09: OpenVPN 2.2.2 Win32-MSVC++ [SSL] [LZO2] [PKCS11] built on Jan  4 2012
Jun 29 02:23:12: WARNING: No server certificate verification method has been enabled.  See http://openvpn.net/howto.html#mitm for more info.
Jun 29 02:23:12: NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Jun 29 02:23:12: RESOLVE: NOTE: connect-openvpn.swissvpn.net resolves to 3 addresses
Jun 29 02:23:12: Attempting to establish TCP connection with 80.254.79.101:443
Jun 29 02:23:12: TCP connection established with 80.254.79.101:443
Jun 29 02:23:12: TCPv4_CLIENT link local: [undef]
Jun 29 02:23:12: TCPv4_CLIENT link remote: 80.254.79.101:443
Jun 29 02:23:12: WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
Jun 29 02:23:21: [server] Peer Connection Initiated with 80.254.79.101:443
Jun 29 02:23:26: NETSH: C:\WINDOWS\system32\netsh.exe interface ip set address SwissVPN static 93.94.245.80 255.255.255.128
Jun 29 02:23:26: ERROR: netsh command failed: returned error code 1
Jun 29 02:23:31: NETSH: C:\WINDOWS\system32\netsh.exe interface ip set address SwissVPN static 93.94.245.80 255.255.255.128
Jun 29 02:23:31: ERROR: netsh command failed: returned error code 1
Jun 29 02:23:36: NETSH: C:\WINDOWS\system32\netsh.exe interface ip set address SwissVPN static 93.94.245.80 255.255.255.128
Jun 29 02:23:36: ERROR: netsh command failed: returned error code 1
Jun 29 02:23:41: NETSH: C:\WINDOWS\system32\netsh.exe interface ip set address SwissVPN static 93.94.245.80 255.255.255.128
Jun 29 02:23:41: ERROR: netsh command failed: returned error code 1
Jun 29 02:23:45: WARNING: No server certificate verification method has been enabled.  See http://openvpn.net/howto.html#mitm for more info.
Jun 29 02:23:45: NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Jun 29 02:23:45: RESOLVE: NOTE: connect-openvpn.swissvpn.net resolves to 3 addresses
Jun 29 02:23:45: Attempting to establish TCP connection with 80.254.79.101:443
Jun 29 02:23:45: TCP connection established with 80.254.79.101:443
Jun 29 02:23:45: TCPv4_CLIENT link local: [undef]
Jun 29 02:23:45: TCPv4_CLIENT link remote: 80.254.79.101:443
Jun 29 02:23:45: WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
Jun 29 02:23:45: [server] Peer Connection Initiated with 80.254.79.101:443
Jun 29 02:23:45: NETSH: C:\WINDOWS\system32\netsh.exe interface ip set address SwissVPN static 93.94.245.80 255.255.255.128
Jun 29 02:23:45: The RPC server is unavailable.
Jun 29 02:23:46: State changed to Disconnected
I'm beginning to wonder if my network card itself isn't faulty.
Both the office PC and the laptop connect through the same router/firewall to the internet, so I doubt it would be treating each PC differently.

Any other suggestions I could try?
Donn Edwards
Johannesburg, South Africa

Eric

User avatar
Posts: 969
Joined: Sun Jan 03, 2010 3:27 am

Post by Eric » Sun Jun 30, 2013 12:33 am
Hi Donn,

I've actually never seen that one before. Viscosity itself doesn't need to be run with Administrator rights, it's ViscosityService.exe (which runs as SYSTEM) that needs elevated permissions to make sure everything is run correctly. It might be worth quickly checking with your organisations Information Technology guys to make sure the user SYSTEM has not been blocked from running elevated processes, though I doubt this is the case.

There should be no impact from a problamatic main network adapter as well as the Viscosity Adapter installs as a standalone network interface and does not piggy back off the main adapter (except to pass through encrypted packets to the VPN Servier).

"The RPC server is unavailable." is interesting. The problem could be that the DHCP service in Windows is not running, you can check it's status by going to Start, searching for services.msc and running it as Administrator and then locating the "DHCP Client" service. If it is running, stop then start it again. If it's not running, try starting it.

It would be worth doing a test with netsh to see why it is throwing a failed attempt at setting information on the adapter. Go to the Network and Sharing Center->Manage network adapters and enable the SwissVPN adapter, then try running the following command from an elevated command prompt and post up the output:

C:\WINDOWS\system32\netsh.exe interface ip set address SwissVPN static 93.94.245.80 255.255.255.128

It may also be worth contacting SwissVPN, as the failure to set the IP address could be because Windows is detecting a duplicate IP address on their server and not allowing the copy to be set.

Hopefully some of the above helps.

Regards,

Eric
Eric Thorpe
Viscosity Developer

Web: http://www.sparklabs.com
Support: http://www.sparklabs.com/support
Twitter: http://twitter.com/sparklabs

DonnEdwards

Posts: 10
Joined: Fri Jun 28, 2013 7:00 pm

Post by DonnEdwards » Sun Jun 30, 2013 12:59 am
Bingo!

You were right about the DHCP service being disabled. I also found a few other services I must have disabled some time ago, such as the DNS client and the "Routing and Remote Access" service.
I turned them on, removed the "ip-win32 netsh" line, and tried Viscosity again.

It all works fine now. I guess I was too aggressive in turning off "unneeded" services some time ago.

Thanks for the reply and support! I have just registered my first copy in appreciation.
Donn Edwards
Johannesburg, South Africa

Eric

User avatar
Posts: 969
Joined: Sun Jan 03, 2010 3:27 am

Post by Eric » Sun Jun 30, 2013 1:06 am
Good to hear we got it fixed, hope you enjoy using Viscosity.

Cheers,

Eric
Eric Thorpe
Viscosity Developer

Web: http://www.sparklabs.com
Support: http://www.sparklabs.com/support
Twitter: http://twitter.com/sparklabs
6 posts Page 1 of 1