Fórum Root.cz

Hlavní témata => Windows a jiné systémy => Téma založeno: Pupi1 29. 04. 2014, 21:41:23

Název: OpenVPN a Windows 8.1
Přispěvatel: Pupi1 29. 04. 2014, 21:41:23
Do pracovnej siete pouzivam OpenVPN konkretne Sophos SSL Client. Na svojom notebooku mam nainstalovany Windows 8.1. Zakazdym, ked sa pokusim prihlasit, tak mi vyhodi, ze sa pripojil s chybami. Skusal som resetovat tcp/ip stack, ale nic. Skusal som pustat klienta pod admin pravami. Potom sa to pripoji, po hodine nervov, ale neviem akym zazrakom. Niekde som cital, ze windows 8 ma nejake problemy s VPN. Neviete v com by bol problem?
Název: Re:OpenVPN a Windows 8.1
Přispěvatel: prcek 29. 04. 2014, 22:26:33
Nevim, hadam. Mozna by pomohl log z klienta. Mozna potrebuje admin prava k modifikaci routovaci tabulky. Rychlogoogle pise, ze potrebuje bezici sluzbu 'network connections' mozna to je duvod proc nekdy se pripoji a nekdy ne...
http://www.vpntutorials.com/tutorials/openvpn-client-setup-tutorial-for-windows-8/ (http://www.vpntutorials.com/tutorials/openvpn-client-setup-tutorial-for-windows-8/)
Název: Re:OpenVPN a Windows 8.1
Přispěvatel: jvb 29. 04. 2014, 22:48:50
Sophos SSL CLient neznám, ale OpenVPN musí běžet pod privilegovaným uživatelem.

http://openvpn.net/index.php/open-source/faq/79-client/275-why-cant-i-run-openvpn-on-windows-from-a-non-admin-user-account.html
Název: Re:OpenVPN a Windows 8.1
Přispěvatel: Pupi1 30. 04. 2014, 09:47:20
tu je vystup z log suboru:

Kód: [Vybrat]
Wed Apr 30 09:45:40 2014 OpenVPN 2.3.0 i686-w64-mingw32 [SSL (OpenSSL)] [LZO] [IPv6] built on Apr  9 2014
Wed Apr 30 09:45:40 2014 MANAGEMENT: TCP Socket listening on [AF_INET]127.0.0.1:25340
Wed Apr 30 09:45:40 2014 Need hold release from management interface, waiting...
Wed Apr 30 09:45:40 2014 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:25340
Wed Apr 30 09:45:40 2014 MANAGEMENT: CMD 'state on'
Wed Apr 30 09:45:40 2014 MANAGEMENT: CMD 'log all on'
Wed Apr 30 09:45:40 2014 MANAGEMENT: CMD 'hold off'
Wed Apr 30 09:45:40 2014 MANAGEMENT: CMD 'hold release'
Wed Apr 30 09:45:46 2014 MANAGEMENT: CMD 'username "Auth" "juraj.pupak"'
Wed Apr 30 09:45:46 2014 MANAGEMENT: CMD 'password [...]'
Wed Apr 30 09:45:46 2014 WARNING: Make sure you understand the semantics of --tls-remote before using it (see the man page).
Wed Apr 30 09:45:46 2014 NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Wed Apr 30 09:45:46 2014 Socket Buffers: R=[65536->65536] S=[65536->65536]
Wed Apr 30 09:45:46 2014 MANAGEMENT: >STATE:1398843946,RESOLVE,,,
Wed Apr 30 09:45:46 2014 Attempting to establish TCP connection with [AF_INET]62.209.196.181:443 [nonblock]
Wed Apr 30 09:45:46 2014 MANAGEMENT: >STATE:1398843946,TCP_CONNECT,,,
Wed Apr 30 09:45:47 2014 TCP connection established with [AF_INET]62.209.196.181:443
Wed Apr 30 09:45:47 2014 TCPv4_CLIENT link local: [undef]
Wed Apr 30 09:45:47 2014 TCPv4_CLIENT link remote: [AF_INET]62.209.196.181:443
Wed Apr 30 09:45:47 2014 MANAGEMENT: >STATE:1398843947,WAIT,,,
Wed Apr 30 09:45:47 2014 MANAGEMENT: >STATE:1398843947,AUTH,,,
Wed Apr 30 09:45:47 2014 TLS: Initial packet from [AF_INET]62.209.196.181:443, sid=f1ab2b84 99127fc6
Wed Apr 30 09:45:47 2014 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
Wed Apr 30 09:45:47 2014 VERIFY OK: depth=1, C=cz, L=Praha, O=TollNET, CN=TollNET VPN CA, emailAddress=administrator@tollnet.cz
Wed Apr 30 09:45:47 2014 VERIFY X509NAME OK: C=cz, L=Praha, O=TollNET, CN=mail.tollnet.cz, emailAddress=administrator@tollnet.cz
Wed Apr 30 09:45:47 2014 VERIFY OK: depth=0, C=cz, L=Praha, O=TollNET, CN=mail.tollnet.cz, emailAddress=administrator@tollnet.cz
Wed Apr 30 09:45:48 2014 Data Channel Encrypt: Cipher 'AES-256-CBC' initialized with 256 bit key
Wed Apr 30 09:45:48 2014 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Wed Apr 30 09:45:48 2014 Data Channel Decrypt: Cipher 'AES-256-CBC' initialized with 256 bit key
Wed Apr 30 09:45:48 2014 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Wed Apr 30 09:45:48 2014 Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 1024 bit RSA
Wed Apr 30 09:45:48 2014 [mail.tollnet.cz] Peer Connection Initiated with [AF_INET]62.209.196.181:443
Wed Apr 30 09:45:49 2014 MANAGEMENT: >STATE:1398843949,GET_CONFIG,,,
Wed Apr 30 09:45:50 2014 SENT CONTROL [mail.tollnet.cz]: 'PUSH_REQUEST' (status=1)
Wed Apr 30 09:45:50 2014 PUSH: Received control message: 'PUSH_REPLY,route 10.242.2.1,topology net30,ping 10,ping-restart 120,route 10.240.240.0 255.255.255.252,route 172.29.130.0 255.255.255.0,route 172.29.129.0 255.255.255.0,route 172.16.48.0 255.255.248.0,route 192.168.200.0 255.255.248.0,route 10.240.1.0 255.255.255.0,route 10.240.10.0 255.255.254.0,route 10.240.20.0 255.255.254.0,route 10.240.30.0 255.255.254.0,route 10.240.40.0 255.255.254.0,route 10.240.50.0 255.255.254.0,route 10.240.60.0 255.255.254.0,route 195.168.36.172 255.255.255.255,dhcp-option DNS 172.29.129.10,dhcp-option DNS 10.240.10.10,dhcp-option DOMAIN tollnet.local,ifconfig 10.242.2.106 10.242.2.105'
Wed Apr 30 09:45:50 2014 OPTIONS IMPORT: timers and/or timeouts modified
Wed Apr 30 09:45:50 2014 OPTIONS IMPORT: --ifconfig/up options modified
Wed Apr 30 09:45:50 2014 OPTIONS IMPORT: route options modified
Wed Apr 30 09:45:50 2014 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
Wed Apr 30 09:45:50 2014 ROUTE_GATEWAY 192.168.2.1/255.255.255.0 I=4 HWADDR=00:1e:65:8e:ad:82
Wed Apr 30 09:45:50 2014 do_ifconfig, tt->ipv6=0, tt->did_ifconfig_ipv6_setup=0
Wed Apr 30 09:45:50 2014 MANAGEMENT: >STATE:1398843950,ASSIGN_IP,,10.242.2.106,
Wed Apr 30 09:45:50 2014 open_tun, tt->ipv6=0
Wed Apr 30 09:45:50 2014 TAP-WIN32 device [Local Area Connection] opened: \\.\Global\{F5A2C21F-5E4A-43CD-8C91-3EFA924BEA80}.tap
Wed Apr 30 09:45:50 2014 TAP-Windows Driver Version 9.9
Wed Apr 30 09:45:50 2014 Notified TAP-Windows driver to set a DHCP IP/netmask of 10.242.2.106/255.255.255.252 on interface {F5A2C21F-5E4A-43CD-8C91-3EFA924BEA80} [DHCP-serv: 10.242.2.105, lease-time: 31536000]
Wed Apr 30 09:45:50 2014 NOTE: FlushIpNetTable failed on interface [12] {F5A2C21F-5E4A-43CD-8C91-3EFA924BEA80} (status=5) : Access is denied. 
Wed Apr 30 09:45:55 2014 TEST ROUTES: 0/0 succeeded len=15 ret=0 a=0 u/d=down
Wed Apr 30 09:45:55 2014 Route: Waiting for TUN/TAP interface to come up...
Wed Apr 30 09:45:59 2014 TEST ROUTES: 0/0 succeeded len=15 ret=0 a=0 u/d=down
Wed Apr 30 09:45:59 2014 Route: Waiting for TUN/TAP interface to come up...
Wed Apr 30 09:46:00 2014 TEST ROUTES: 0/0 succeeded len=15 ret=0 a=0 u/d=down
Wed Apr 30 09:46:00 2014 Route: Waiting for TUN/TAP interface to come up...
Wed Apr 30 09:46:01 2014 TEST ROUTES: 0/0 succeeded len=15 ret=0 a=0 u/d=down
Wed Apr 30 09:46:01 2014 Route: Waiting for TUN/TAP interface to come up...
Wed Apr 30 09:46:02 2014 TEST ROUTES: 0/0 succeeded len=15 ret=0 a=0 u/d=down
Wed Apr 30 09:46:02 2014 Route: Waiting for TUN/TAP interface to come up...
Wed Apr 30 09:46:03 2014 TEST ROUTES: 0/0 succeeded len=15 ret=0 a=0 u/d=down
Wed Apr 30 09:46:03 2014 Route: Waiting for TUN/TAP interface to come up...
Wed Apr 30 09:46:04 2014 TEST ROUTES: 0/0 succeeded len=15 ret=0 a=0 u/d=down
Wed Apr 30 09:46:04 2014 Route: Waiting for TUN/TAP interface to come up...
Wed Apr 30 09:46:05 2014 TEST ROUTES: 0/0 succeeded len=15 ret=0 a=0 u/d=down
Wed Apr 30 09:46:05 2014 Route: Waiting for TUN/TAP interface to come up...
Wed Apr 30 09:46:06 2014 TEST ROUTES: 0/0 succeeded len=15 ret=0 a=0 u/d=down
Wed Apr 30 09:46:06 2014 Route: Waiting for TUN/TAP interface to come up...
Wed Apr 30 09:46:08 2014 TEST ROUTES: 0/0 succeeded len=15 ret=0 a=0 u/d=down
Wed Apr 30 09:46:08 2014 Route: Waiting for TUN/TAP interface to come up...
Wed Apr 30 09:46:09 2014 TEST ROUTES: 0/0 succeeded len=15 ret=0 a=0 u/d=down
Wed Apr 30 09:46:09 2014 Route: Waiting for TUN/TAP interface to come up...
Wed Apr 30 09:46:10 2014 TEST ROUTES: 0/0 succeeded len=15 ret=0 a=0 u/d=down
Wed Apr 30 09:46:10 2014 Route: Waiting for TUN/TAP interface to come up...
Wed Apr 30 09:46:11 2014 TEST ROUTES: 0/0 succeeded len=15 ret=0 a=0 u/d=down
Wed Apr 30 09:46:11 2014 Route: Waiting for TUN/TAP interface to come up...
Wed Apr 30 09:46:12 2014 TEST ROUTES: 0/0 succeeded len=15 ret=0 a=0 u/d=down
Wed Apr 30 09:46:12 2014 Route: Waiting for TUN/TAP interface to come up...
Wed Apr 30 09:46:13 2014 TEST ROUTES: 0/0 succeeded len=15 ret=0 a=0 u/d=down
Wed Apr 30 09:46:13 2014 Route: Waiting for TUN/TAP interface to come up...
Wed Apr 30 09:46:14 2014 TEST ROUTES: 0/0 succeeded len=15 ret=0 a=0 u/d=down
Wed Apr 30 09:46:14 2014 Route: Waiting for TUN/TAP interface to come up...
Wed Apr 30 09:46:15 2014 TEST ROUTES: 0/0 succeeded len=15 ret=0 a=0 u/d=down
Wed Apr 30 09:46:15 2014 Route: Waiting for TUN/TAP interface to come up...
Wed Apr 30 09:46:17 2014 TEST ROUTES: 0/0 succeeded len=15 ret=0 a=0 u/d=down
Wed Apr 30 09:46:17 2014 Route: Waiting for TUN/TAP interface to come up...
Wed Apr 30 09:46:18 2014 TEST ROUTES: 0/0 succeeded len=15 ret=0 a=0 u/d=down
Wed Apr 30 09:46:18 2014 Route: Waiting for TUN/TAP interface to come up...
Wed Apr 30 09:46:19 2014 TEST ROUTES: 0/0 succeeded len=15 ret=0 a=0 u/d=down
Wed Apr 30 09:46:19 2014 Route: Waiting for TUN/TAP interface to come up...
Wed Apr 30 09:46:20 2014 TEST ROUTES: 0/0 succeeded len=15 ret=0 a=0 u/d=down
Wed Apr 30 09:46:20 2014 Route: Waiting for TUN/TAP interface to come up...
Wed Apr 30 09:46:21 2014 TEST ROUTES: 0/0 succeeded len=15 ret=0 a=0 u/d=down
Wed Apr 30 09:46:21 2014 Route: Waiting for TUN/TAP interface to come up...
Wed Apr 30 09:46:22 2014 TEST ROUTES: 0/0 succeeded len=15 ret=0 a=0 u/d=down
Wed Apr 30 09:46:22 2014 Route: Waiting for TUN/TAP interface to come up...
Wed Apr 30 09:46:23 2014 TEST ROUTES: 0/0 succeeded len=15 ret=0 a=0 u/d=down
Wed Apr 30 09:46:23 2014 Route: Waiting for TUN/TAP interface to come up...
Wed Apr 30 09:46:24 2014 TEST ROUTES: 0/0 succeeded len=15 ret=0 a=0 u/d=down
Wed Apr 30 09:46:24 2014 MANAGEMENT: >STATE:1398843984,ADD_ROUTES,,,
Wed Apr 30 09:46:24 2014 C:\Windows\system32\route.exe ADD 62.209.196.181 MASK 255.255.255.255 192.168.2.1
Wed Apr 30 09:46:24 2014 Route addition via service succeeded
Wed Apr 30 09:46:24 2014 C:\Windows\system32\route.exe ADD 10.242.2.1 MASK 255.255.255.255 10.242.2.105
Wed Apr 30 09:46:24 2014 Warning: route gateway is not reachable on any active network adapters: 10.242.2.105
Wed Apr 30 09:46:24 2014 Route addition via service failed
Wed Apr 30 09:46:24 2014 C:\Windows\system32\route.exe ADD 10.240.240.0 MASK 255.255.255.252 10.242.2.105
Wed Apr 30 09:46:24 2014 Warning: route gateway is not reachable on any active network adapters: 10.242.2.105
Wed Apr 30 09:46:24 2014 Route addition via service failed
Wed Apr 30 09:46:24 2014 C:\Windows\system32\route.exe ADD 172.29.130.0 MASK 255.255.255.0 10.242.2.105
Wed Apr 30 09:46:24 2014 Warning: route gateway is not reachable on any active network adapters: 10.242.2.105
Wed Apr 30 09:46:24 2014 Route addition via service failed
Wed Apr 30 09:46:24 2014 C:\Windows\system32\route.exe ADD 172.29.129.0 MASK 255.255.255.0 10.242.2.105
Wed Apr 30 09:46:24 2014 Warning: route gateway is not reachable on any active network adapters: 10.242.2.105
Wed Apr 30 09:46:24 2014 Route addition via service failed
Wed Apr 30 09:46:24 2014 C:\Windows\system32\route.exe ADD 172.16.48.0 MASK 255.255.248.0 10.242.2.105
Wed Apr 30 09:46:24 2014 Warning: route gateway is not reachable on any active network adapters: 10.242.2.105
Wed Apr 30 09:46:24 2014 Route addition via service failed
Wed Apr 30 09:46:24 2014 C:\Windows\system32\route.exe ADD 192.168.200.0 MASK 255.255.248.0 10.242.2.105
Wed Apr 30 09:46:24 2014 Warning: route gateway is not reachable on any active network adapters: 10.242.2.105
Wed Apr 30 09:46:24 2014 Route addition via service failed
Wed Apr 30 09:46:24 2014 C:\Windows\system32\route.exe ADD 10.240.1.0 MASK 255.255.255.0 10.242.2.105
Wed Apr 30 09:46:24 2014 Warning: route gateway is not reachable on any active network adapters: 10.242.2.105
Wed Apr 30 09:46:24 2014 Route addition via service failed
Wed Apr 30 09:46:24 2014 C:\Windows\system32\route.exe ADD 10.240.10.0 MASK 255.255.254.0 10.242.2.105
Wed Apr 30 09:46:24 2014 Warning: route gateway is not reachable on any active network adapters: 10.242.2.105
Wed Apr 30 09:46:24 2014 Route addition via service failed
Wed Apr 30 09:46:24 2014 C:\Windows\system32\route.exe ADD 10.240.20.0 MASK 255.255.254.0 10.242.2.105
Wed Apr 30 09:46:24 2014 Warning: route gateway is not reachable on any active network adapters: 10.242.2.105
Wed Apr 30 09:46:24 2014 Route addition via service failed
Wed Apr 30 09:46:24 2014 C:\Windows\system32\route.exe ADD 10.240.30.0 MASK 255.255.254.0 10.242.2.105
Wed Apr 30 09:46:24 2014 Warning: route gateway is not reachable on any active network adapters: 10.242.2.105
Wed Apr 30 09:46:24 2014 Route addition via service failed
Wed Apr 30 09:46:24 2014 C:\Windows\system32\route.exe ADD 10.240.40.0 MASK 255.255.254.0 10.242.2.105
Wed Apr 30 09:46:24 2014 Warning: route gateway is not reachable on any active network adapters: 10.242.2.105
Wed Apr 30 09:46:24 2014 Route addition via service failed
Wed Apr 30 09:46:24 2014 C:\Windows\system32\route.exe ADD 10.240.50.0 MASK 255.255.254.0 10.242.2.105
Wed Apr 30 09:46:24 2014 Warning: route gateway is not reachable on any active network adapters: 10.242.2.105
Wed Apr 30 09:46:24 2014 Route addition via service failed
Wed Apr 30 09:46:24 2014 C:\Windows\system32\route.exe ADD 10.240.60.0 MASK 255.255.254.0 10.242.2.105
Wed Apr 30 09:46:24 2014 Warning: route gateway is not reachable on any active network adapters: 10.242.2.105
Wed Apr 30 09:46:24 2014 Route addition via service failed
Wed Apr 30 09:46:24 2014 C:\Windows\system32\route.exe ADD 195.168.36.172 MASK 255.255.255.255 10.242.2.105
Wed Apr 30 09:46:24 2014 Warning: route gateway is not reachable on any active network adapters: 10.242.2.105
Wed Apr 30 09:46:24 2014 Route addition via service failed
Wed Apr 30 09:46:24 2014 SYSTEM ROUTING TABLE
Wed Apr 30 09:46:24 2014 0.0.0.0 0.0.0.0 192.168.2.1 p=0 i=4 t=4 pr=3 a=297 h=0 m=30/0/0/0/0
Wed Apr 30 09:46:24 2014 62.209.196.181 255.255.255.255 192.168.2.1 p=0 i=4 t=4 pr=3 a=0 h=0 m=31/0/0/0/0
Wed Apr 30 09:46:24 2014 127.0.0.0 255.0.0.0 127.0.0.1 p=0 i=1 t=3 pr=2 a=317 h=0 m=306/0/0/0/0
Wed Apr 30 09:46:24 2014 127.0.0.1 255.255.255.255 127.0.0.1 p=0 i=1 t=3 pr=2 a=317 h=0 m=306/0/0/0/0
Wed Apr 30 09:46:24 2014 127.255.255.255 255.255.255.255 127.0.0.1 p=0 i=1 t=3 pr=2 a=317 h=0 m=306/0/0/0/0
Wed Apr 30 09:46:24 2014 192.168.2.0 255.255.255.0 192.168.2.3 p=0 i=4 t=3 pr=2 a=297 h=0 m=286/0/0/0/0
Wed Apr 30 09:46:24 2014 192.168.2.3 255.255.255.255 192.168.2.3 p=0 i=4 t=3 pr=2 a=297 h=0 m=286/0/0/0/0
Wed Apr 30 09:46:24 2014 192.168.2.255 255.255.255.255 192.168.2.3 p=0 i=4 t=3 pr=2 a=297 h=0 m=286/0/0/0/0
Wed Apr 30 09:46:24 2014 224.0.0.0 240.0.0.0 127.0.0.1 p=0 i=1 t=3 pr=2 a=317 h=0 m=306/0/0/0/0
Wed Apr 30 09:46:24 2014 224.0.0.0 240.0.0.0 192.168.2.3 p=0 i=4 t=3 pr=2 a=309 h=0 m=286/0/0/0/0
Wed Apr 30 09:46:24 2014 255.255.255.255 255.255.255.255 127.0.0.1 p=0 i=1 t=3 pr=2 a=317 h=0 m=306/0/0/0/0
Wed Apr 30 09:46:24 2014 255.255.255.255 255.255.255.255 192.168.2.3 p=0 i=4 t=3 pr=2 a=309 h=0 m=286/0/0/0/0
Wed Apr 30 09:46:24 2014 SYSTEM ADAPTER LIST
Wed Apr 30 09:46:24 2014 Sophos SSL VPN Adapter
Wed Apr 30 09:46:24 2014   Index = 12
Wed Apr 30 09:46:24 2014   GUID = {F5A2C21F-5E4A-43CD-8C91-3EFA924BEA80}
Wed Apr 30 09:46:24 2014   IP = 0.0.0.0/0.0.0.0
Wed Apr 30 09:46:24 2014   MAC = 00:ff:f5:a2:c2:1f
Wed Apr 30 09:46:24 2014   GATEWAY = 0.0.0.0/255.255.255.255
Wed Apr 30 09:46:24 2014   DHCP SERV = 
Wed Apr 30 09:46:24 2014   DHCP LEASE OBTAINED = Wed Apr 30 09:46:24 2014
Wed Apr 30 09:46:24 2014   DHCP LEASE EXPIRES  = Wed Apr 30 09:46:24 2014
Wed Apr 30 09:46:24 2014   DNS SERV = 
Wed Apr 30 09:46:24 2014 Bluetooth Device (Personal Area Network)
Wed Apr 30 09:46:24 2014   Index = 5
Wed Apr 30 09:46:24 2014   GUID = {CFECDCB9-DA72-4006-A740-13BBD40B9664}
Wed Apr 30 09:46:24 2014   IP = 0.0.0.0/0.0.0.0
Wed Apr 30 09:46:24 2014   MAC = 00:26:5e:bb:63:f3
Wed Apr 30 09:46:24 2014   GATEWAY = 0.0.0.0/255.255.255.255
Wed Apr 30 09:46:24 2014   DHCP SERV = 
Wed Apr 30 09:46:24 2014   DHCP LEASE OBTAINED = Wed Apr 30 09:46:24 2014
Wed Apr 30 09:46:24 2014   DHCP LEASE EXPIRES  = Wed Apr 30 09:46:24 2014
Wed Apr 30 09:46:24 2014   DNS SERV = 
Wed Apr 30 09:46:24 2014 Intel(R) WiFi Link 5100 AGN
Wed Apr 30 09:46:24 2014   Index = 4
Wed Apr 30 09:46:24 2014   GUID = {AF6649E3-F9CB-47E6-B990-ED69F184FFF3}
Wed Apr 30 09:46:24 2014   IP = 192.168.2.3/255.255.255.0
Wed Apr 30 09:46:24 2014   MAC = 00:1e:65:8e:ad:82
Wed Apr 30 09:46:24 2014   GATEWAY = 192.168.2.1/255.255.255.255
Wed Apr 30 09:46:24 2014   DHCP SERV = 192.168.2.1/255.255.255.255
Wed Apr 30 09:46:24 2014   DHCP LEASE OBTAINED = Wed Apr 30 09:41:26 2014
Wed Apr 30 09:46:24 2014   DHCP LEASE EXPIRES  = Fri Apr 28 09:41:26 2023
Wed Apr 30 09:46:24 2014   DNS SERV = 192.168.2.1/255.255.255.255
Wed Apr 30 09:46:24 2014 Broadcom NetLink (TM) Gigabit Ethernet
Wed Apr 30 09:46:24 2014   Index = 3
Wed Apr 30 09:46:24 2014   GUID = {9249625E-CA31-4A07-B69F-90C5A67ADA41}
Wed Apr 30 09:46:24 2014   IP = 0.0.0.0/0.0.0.0
Wed Apr 30 09:46:24 2014   MAC = 00:22:68:14:14:d7
Wed Apr 30 09:46:24 2014   GATEWAY = 0.0.0.0/255.255.255.255
Wed Apr 30 09:46:24 2014   DHCP SERV = 
Wed Apr 30 09:46:24 2014   DHCP LEASE OBTAINED = Wed Apr 30 09:46:24 2014
Wed Apr 30 09:46:24 2014   DHCP LEASE EXPIRES  = Wed Apr 30 09:46:24 2014
Wed Apr 30 09:46:24 2014   DNS SERV = 
Wed Apr 30 09:46:24 2014 Initialization Sequence Completed With Errors ( see http://openvpn.net/faq.html#dhcpclientserv )
Wed Apr 30 09:46:24 2014 MANAGEMENT: >STATE:1398843984,CONNECTED,ERROR,10.242.2.106,62.209.196.181
Název: Re:OpenVPN a Windows 8.1
Přispěvatel: mhepp 30. 04. 2014, 13:44:04
Jak to tak vypadá, tak máš chybu v TUN/TAP zařízení. Takže kompletně odinstalovat klienta, včetně TUN/TAP a nainstalovat znovu.

Ověř si, že instalátor i klienta spouštíš jako administrátor.
Název: Re:OpenVPN a Windows 8.1
Přispěvatel: BobTheBuilder 30. 04. 2014, 13:49:12
Podle toho logu nemá oprávnění na některé operace - nejspíš není spuštěn s právy administrátora. U OpenVPN (OpenVPN GUI) to řeším přes naplánovanou úlohu, OpenVPN GUI se spouští minutu po přihlášení:
 - při spuštění použít uživatelský účet
 - spustit s nejvyššími oprávněními
Pro zástupce OpenVPN GUI pak nastavím "spustit tento program jako správce" (vlastnosti->kompatibilita), abych na to ani při případném ručním spuštění nezapomněl.
Název: Re:OpenVPN a Windows 8.1
Přispěvatel: breberka 30. 04. 2014, 14:54:01
A není lepší vypnout UAC a provést změnu v registru:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System]
"EnableLUA"=dword:00000000

A pak to pouštet normálně.
Název: Re:OpenVPN a Windows 8.1
Přispěvatel: Pupi1 30. 04. 2014, 15:50:14
dnes som to pustil ako Run as Administrator a prihlasil sa. zazrakom ma pripojilo. Ale vcera napr. to neslo. Neviem ci je v tom nejaka magia :D
Název: Re:OpenVPN a Windows 8.1
Přispěvatel: FAWN 30. 04. 2014, 23:25:38
Jo, podle toho logu (FlushIpNetTable failed on interface) to bude o právech. Pokud je to možné, použil bych jiného klienta. Běžně používáme na W7 a W7x64 klienta Securepoint SSL VPN (http://sourceforge.net/projects/securepoint/files/), který funguje spolehlivě bez práv.
Název: Re:OpenVPN a Windows 8.1
Přispěvatel: Radek 01. 05. 2014, 07:45:33
V mém případě mi pomohlo vypnout podporu TCPIPv6 u TAP adaptéru
Název: Re:OpenVPN a Windows 8.1
Přispěvatel: Pupi1 05. 05. 2014, 10:50:44
to FAWN:

diky za tip. ide to teraz bez problemov, pouzil som ten Securepoint.
Název: Re:OpenVPN a Windows 8.1
Přispěvatel: Lol Phirae 05. 05. 2014, 12:46:20
A není lepší vypnout UAC a provést změnu v registru:

>> Pane doktore, zlomil jsem si nehet a hrozně to bolí.
> OK, amputujem vám ruku a bolet to přestane.
Název: Re:OpenVPN a Windows 8.1
Přispěvatel: M. 05. 05. 2014, 13:03:40
To než zakazovat UAC, tak raději jít cestou eliminace OpenVPN a nasadit něco z toho, co má Win přímo v sobě nativně. Já používám SSTP a IPsec/IKEv2 a s klienty je pokoj (a vlastně pro tunu starších WinXP je v provozu i L2TP/IPsec)... Jediný problém mám s lidma, co se chtějí propojovat skrz mobil s Windowsy, že to nějak przní a IPsec varianty neprojdou.
Název: Re:OpenVPN a Windows 8.1
Přispěvatel: SYSMAN 05. 05. 2014, 14:43:53
OpenVPN není nutné spouštět pod privilegovaným userem. Po instalaci je ho ovšem nutné poprvé spustit pod privilegovaným userem, pak už to jde i pod uživatelem s právy users.
Název: Re:OpenVPN a Windows 8.1
Přispěvatel: Lol Phirae 05. 05. 2014, 14:49:48
OpenVPN není nutné spouštět pod privilegovaným userem. Po instalaci je ho ovšem nutné poprvé spustit pod privilegovaným userem, pak už to jde i pod uživatelem s právy users.

Ne, to fakt takhle nejde. Jinak viz https://github.com/jochenwierum/openvpn-manager