Skip to content
Search found 8 matches
Search found 8 matches
Page 1 of 1
- by ElGrowZone
- Tue Jul 12, 2011 7:03 pm
- Forum: Viscosity Support (Mac Version)
- Topic: no connection after upgrading to 1.3.1 / 1.3.0
- Replies: 23
- Views: 25624
Hi James,
the "script-security 2" (without the quotes ) did the trick. Now I'm back on my clients network.
I didn't change anything in my settings. Is this a new behavior from the openvpn software?
Thank you very much!
Volker
the "script-security 2" (without the quotes ) did the trick. Now I'm back on my clients network.
I didn't change anything in my settings. Is this a new behavior from the openvpn software?
Thank you very much!
Volker
- by ElGrowZone
- Mon Jul 11, 2011 7:14 pm
- Forum: Viscosity Support (Mac Version)
- Topic: no connection after upgrading to 1.3.1 / 1.3.0
- Replies: 23
- Views: 25624
Hi James, tun and tap seem to be loaded: 131 0 0x81af5000 0x6000 0x5000 com.viscosityvpn.Viscosity.tap (1.0) <7 5 4 1> 132 0 0x81bbc000 0x6000 0x5000 com.viscosityvpn.Viscosity.tun (1.0) <7 5 4 1> following is the console log of a connection try: 11.07.11 11:07:08 openvpn[29245] OpenVPN 2.2.0 x86_64...
- by ElGrowZone
- Thu Jul 07, 2011 6:39 am
- Forum: Viscosity Support (Mac Version)
- Topic: no connection after upgrading to 1.3.1 / 1.3.0
- Replies: 23
- Views: 25624
Hi James, here you go: Jul 06 22:34:21: Viscosity 1.3.3 (1024) Jul 06 22:34:21: Checking reachability status of connection... Jul 06 22:34:23: Connection is reachable. Starting connection attempt. Jul 06 22:34:30: OpenVPN 2.2.0 x86_64-apple-darwin10.7.0 [SSL] [LZO2] [PKCS11] [eurephia] built on Jun ...
- by ElGrowZone
- Tue Jul 05, 2011 5:21 am
- Forum: Viscosity Support (Mac Version)
- Topic: no connection after upgrading to 1.3.1 / 1.3.0
- Replies: 23
- Views: 25624
Hi, 1. No. 2. No. 3. No - (btw. openvpn isn't 64 Bit? Not that I really care, but ... ;) ) 4. No. Here is the log: (no, I'm NOT working for Microsoft, maybe admins are having fun or something ...) Jul 1 16:28:17 ovpn_srv openvpn[12561]: MULTI: multi_create_instance called Jul 1 16:28:17 ovpn_srv ope...
- by ElGrowZone
- Mon Jul 04, 2011 5:55 pm
- Forum: Viscosity Support (Mac Version)
- Topic: no connection after upgrading to 1.3.1 / 1.3.0
- Replies: 23
- Views: 25624
I'm getting the same server log entries as printed above. Any ideas on this?
- by ElGrowZone
- Fri Jul 01, 2011 4:24 pm
- Forum: Viscosity Support (Mac Version)
- Topic: no connection after upgrading to 1.3.1 / 1.3.0
- Replies: 23
- Views: 25624
Reboot didn't help :/
- by ElGrowZone
- Fri Jul 01, 2011 3:00 am
- Forum: Viscosity Support (Mac Version)
- Topic: no connection after upgrading to 1.3.1 / 1.3.0
- Replies: 23
- Views: 25624
I have an (almost) exact same log as in the post above. According to the admin, a second session is started WHILE the first try isn't even fully connected!?!
- by ElGrowZone
- Thu Jun 30, 2011 10:34 pm
- Forum: Viscosity Support (Mac Version)
- Topic: no connection after upgrading to 1.3.1 / 1.3.0
- Replies: 23
- Views: 25624
I'm having the same problem. According to my VPN administrator, my Mac tries to open a second connection, which is not allowed. Is this any help?
I'm using 1.3.3 and tried changing almost all settings mentioned in posts about connection settings
I'm using 1.3.3 and tried changing almost all settings mentioned in posts about connection settings
Search found 8 matches
Page 1 of 1