Beantwortet: Seit letztem win 10 Update verbindet VPN Manager nur noch, wenn Firewall aus

P

peterpan176

New Member
Hallo und guten Morgen,

ich habe seit einigen Tagen das Problem das sich der VPN nur noch verbindet wenn ich vorher die Firewall des VPN (Bei Tunnelstart, Bei Programmstart aktivieren) ausschalte. Bisher funktionierte das immer.

Wenn der Tunnel gestartet ist läßt sich die Firewall wieder aktivieren. Das ist aber

1. unbequem
2. riskant, wenn mna es im Eifer des Gefechts vergißt

Ich würde mich freuen wenn es für dieses Problem eine Lösung gibt.

Hier ein Protokoll eines gescheiterten Tunnelstarts:


*************************************

04.06.2017 08:40:57 Debug Debug: config connect called
04.06.2017 08:40:57 Log DisconnectReason set to NoDisconnect in connect_thread
04.06.2017 08:40:57 Log Debug: connect_thread started
04.06.2017 08:40:58 Log State Change Event - Initializing
04.06.2017 08:40:58 Log Waiting for system to get ready..
04.06.2017 08:40:58 Log Waiting for OpenVPN.exe to get ready
04.06.2017 08:40:58 Log OpenVPN.exe ready
04.06.2017 08:40:58 Log Checking firewall and DNS leak protection settings
04.06.2017 08:40:59 Log Waiting for network to get ready
04.06.2017 08:41:00 Debug Debug: Serviceconnection connect called
04.06.2017 08:41:00 Management Connecting to management interface 127.0.0.1:11203
04.06.2017 08:41:01 Log MANAGEMENT: CMD 'state on'
04.06.2017 08:41:01 Log MANAGEMENT: CMD 'hold release'
04.06.2017 08:41:01 Log MANAGEMENT: CMD 'username 'Auth' "<Username Removed>"'
04.06.2017 08:41:02 Log MANAGEMENT: CMD 'password [...]'
04.06.2017 08:41:02 Log NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
04.06.2017 08:41:02 Log Outgoing Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication
04.06.2017 08:41:02 Log Incoming Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication
04.06.2017 08:41:02 Log LZO compression initializing
04.06.2017 08:41:02 Log Control Channel MTU parms [ L:1626 D:1140 EF:110 EB:0 ET:0 EL:3 ]
04.06.2017 08:41:02 Log Data Channel MTU parms [ L:1626 D:1300 EF:126 EB:407 ET:0 EL:3 ]
04.06.2017 08:41:02 Log Fragmentation MTU parms [ L:1626 D:1300 EF:125 EB:407 ET:1 EL:3 ]
04.06.2017 08:41:02 Log Local Options String (VER=V4): 'V4,dev-type tun,link-mtu 1606,tun-mtu 1500,proto UDPv4,comp-lzo,mtu-dynamic,keydir 1,cipher AES-256-CBC,auth SHA512,keysize 256,tls-auth,key-method 2,tls-client'
04.06.2017 08:41:02 Log Expected Remote Options String (VER=V4): 'V4,dev-type tun,link-mtu 1606,tun-mtu 1500,proto UDPv4,comp-lzo,mtu-dynamic,keydir 0,cipher AES-256-CBC,auth SHA512,keysize 256,tls-auth,key-method 2,tls-server'
04.06.2017 08:41:02 Log TCP/UDP: Preserving recently used remote address: [AF_INET]178.162.194.30:1149
04.06.2017 08:41:02 Log Socket Buffers: R=[65536->65536] S=[65536->65536]
04.06.2017 08:41:02 Log UDP link local: (not bound)
04.06.2017 08:41:02 Log UDP link remote: [AF_INET]178.162.194.30:1149
04.06.2017 08:41:02 Log MANAGEMENT: >STATE:1496558462,WAIT,,,,,,
04.06.2017 08:41:02 State WAIT
04.06.2017 08:41:02 Log MANAGEMENT: >STATE:1496558462,AUTH,,,,,,
04.06.2017 08:41:02 State AUTH
04.06.2017 08:41:02 Log TLS: Initial packet from [AF_INET]178.162.194.30:1149, sid=c2f1cb2a 57f51b94
04.06.2017 08:41:02 Log WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
04.06.2017 08:41:02 Log VERIFY OK: depth=1, C=CH, ST=Zug, L=Zug, O=Perfect Privacy, CN=Perfect Privacy, emailAddress=admin@perfect-privacy.com
04.06.2017 08:41:02 Log VERIFY OK: nsCertType=SERVER
04.06.2017 08:41:02 Log VERIFY OK: depth=0, C=CH, ST=Zug, O=Perfect Privacy, CN=Server_frankfurt.perfect-privacy.com, emailAddress=admin@perfect-privacy.com
04.06.2017 08:41:02 Log Control Channel: TLSv1.2, cipher TLSv1/SSLv3 DHE-RSA-AES256-GCM-SHA384, 4096 bit RSA
04.06.2017 08:41:02 Log [Server_frankfurt.perfect-privacy.com] Peer Connection Initiated with [AF_INET]178.162.194.30:1149
04.06.2017 08:41:03 Log MANAGEMENT: >STATE:1496558463,GET_CONFIG,,,,,,
04.06.2017 08:41:03 State GET_CONFIG
04.06.2017 08:41:03 Log SENT CONTROL [Server_frankfurt.perfect-privacy.com]: 'PUSH_REQUEST' (status=1)
04.06.2017 08:41:03 Log PUSH: Received control message: 'PUSH_REPLY,topology subnet,redirect-gateway def1,sndbuf 131072,rcvbuf 131072,comp-lzo adaptive,route-gateway 10.0.192.1,redirect-gateway ipv6,route-ipv6 2000::/3,ping 10,ping-restart 60,dhcp-option DNS 178.162.209.143,dhcp-option DNS 217.114.218.30,ifconfig-ipv6 fdbf:1d37:bbe0:0:12::135/112 fdbf:1d37:bbe0:0:12::1,ifconfig 10.0.192.35 255.255.255.0,peer-id 24'
04.06.2017 08:41:03 Log OPTIONS IMPORT: timers and/or timeouts modified
04.06.2017 08:41:03 Log OPTIONS IMPORT: compression parms modified
04.06.2017 08:41:03 Log LZO compression initializing
04.06.2017 08:41:03 Log OPTIONS IMPORT: --sndbuf/--rcvbuf options modified
04.06.2017 08:41:03 Log Socket Buffers: R=[65536->131072] S=[65536->131072]
04.06.2017 08:41:03 Log OPTIONS IMPORT: --ifconfig/up options modified
04.06.2017 08:41:03 Log OPTIONS IMPORT: route options modified
04.06.2017 08:41:03 Log OPTIONS IMPORT: route-related options modified
04.06.2017 08:41:03 Log OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
04.06.2017 08:41:03 Log OPTIONS IMPORT: peer-id set
04.06.2017 08:41:03 Log OPTIONS IMPORT: adjusting link_mtu to 1629
04.06.2017 08:41:03 Log Data Channel MTU parms [ L:1609 D:1300 EF:109 EB:407 ET:0 EL:3 ]
04.06.2017 08:41:03 Log Data Channel Encrypt: Cipher 'AES-256-CBC' initialized with 256 bit key
04.06.2017 08:41:03 Log Data Channel Encrypt: Using 512 bit message hash 'SHA512' for HMAC authentication
04.06.2017 08:41:03 Log Data Channel Decrypt: Cipher 'AES-256-CBC' initialized with 256 bit key
04.06.2017 08:41:03 Log Data Channel Decrypt: Using 512 bit message hash 'SHA512' for HMAC authentication
04.06.2017 08:41:03 Log interactive service msg_channel=0
04.06.2017 08:41:03 Log ROUTE_GATEWAY 192.168.2.1/255.255.255.0 I=8 HWADDR=d0:50:99:93:a0:6d
04.06.2017 08:41:03 Log GDG6: remote_host_ipv6=n/a
04.06.2017 08:41:03 Log NOTE: GetBestInterfaceEx returned error: Element nicht gefunden. (code=1168)
04.06.2017 08:41:03 Log ROUTE6: default_gateway=UNDEF
04.06.2017 08:41:03 Log open_tun
04.06.2017 08:41:03 Log TAP-WIN32 device [Ethernet 2] opened: \\.\Global\{B9B35B01-BA1A-455A-906F-390584D2968B}.tap
04.06.2017 08:41:03 Log TAP-Windows Driver Version 9.21
04.06.2017 08:41:03 Log TAP-Windows MTU=1500
04.06.2017 08:41:03 Log Set TAP-Windows TUN subnet mode network/local/netmask = 10.0.192.0/10.0.192.35/255.255.255.0 [SUCCEEDED]
04.06.2017 08:41:03 Log Notified TAP-Windows driver to set a DHCP IP/netmask of 10.0.192.35/255.255.255.0 on interface {B9B35B01-BA1A-455A-906F-390584D2968B} [DHCP-serv: 10.0.192.254, lease-time: 31536000]
04.06.2017 08:41:03 Log DHCP option string: 0608b2a2 d18fd972 da1e
04.06.2017 08:41:03 Log Successful ARP Flush on interface [9] {B9B35B01-BA1A-455A-906F-390584D2968B}
04.06.2017 08:41:03 Log do_ifconfig, tt->did_ifconfig_ipv6_setup=1
04.06.2017 08:41:03 Log MANAGEMENT: >STATE:1496558463,ASSIGN_IP,,10.0.192.35,,,,,fdbf:1d37:bbe0:0:12::135
04.06.2017 08:41:04 State ASSIGN_IP
04.06.2017 08:41:04 Log NETSH: C:\WINDOWS\system32\netsh.exe interface ipv6 set address interface=9 fdbf:1d37:bbe0:0:12::135 store=active
04.06.2017 08:41:04 Log add_route_ipv6(fdbf:1d37:bbe0:0:12::/112 -> fdbf:1d37:bbe0:0:12::135 metric 0) dev Ethernet 2
04.06.2017 08:41:04 Log C:\WINDOWS\system32\netsh.exe interface ipv6 add route fdbf:1d37:bbe0:0:12::/112 interface=9 fe80::8 store=active
04.06.2017 08:41:04 Log env_block: add PATH=C:\WINDOWS\System32;C:\WINDOWS;C:\WINDOWS\System32\Wbem
04.06.2017 08:41:04 Log updown_v6.bat Ethernet 2 1500 1609 10.0.192.35 255.255.255.0 init
04.06.2017 08:41:04 Log env_block: add PATH=C:\WINDOWS\System32;C:\WINDOWS;C:\WINDOWS\System32\Wbem
04.06.2017 08:41:07 Log TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
04.06.2017 08:41:07 Log Route: Waiting for TUN/TAP interface to come up...
04.06.2017 08:41:09 Log TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
04.06.2017 08:41:09 Log Route: Waiting for TUN/TAP interface to come up...
04.06.2017 08:41:10 Log TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
04.06.2017 08:41:10 Log Route: Waiting for TUN/TAP interface to come up...
04.06.2017 08:41:11 Log TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
04.06.2017 08:41:11 Log To many Tap Init errors, Disconnecting and reinstalling TAP Adapter
04.06.2017 08:41:11 Log Tunnel Frankfurt Disconnect Called Reason:Error
04.06.2017 08:41:11 Debug Debug: Serviceconnection Disconnect called
04.06.2017 08:41:11 Log State Change Event - Stopping
04.06.2017 08:41:11 Log Route: Waiting for TUN/TAP interface to come up...
04.06.2017 08:41:11 Debug killConnection called
04.06.2017 08:41:11 Management Sending signal to close connection
04.06.2017 08:41:11 Log MANAGEMENT: CMD 'exit'
04.06.2017 08:41:11 Management Disconnecting from management interface
04.06.2017 08:41:11 Debug SendDisconnect done
04.06.2017 08:41:11 Management Disconnecting from management interface
04.06.2017 08:41:11 Debug DisconnectLogic done
04.06.2017 08:41:12 Log State Change Event - Stopped
04.06.2017 08:41:12 Log state changes to stoped, reason: Error
04.06.2017 08:41:12 Log Handle disconnect for reason Error error:WaitingForTapAdapters
04.06.2017 08:41:12 Error Tunnel Frankfurt Disconnect Called Reason:WaitGlobalAction but disconnect reason already is Error
 
Solution
PP Frank
Gehe ins Windows Netzwerkcenter, dort in Windows Firewall, aktiviere die Firewall und setze diese auf Standard zurück. Danach sollte alles gehen
Sort by date Sort by votes
Gehe ins Windows Netzwerkcenter, dort in Windows Firewall, aktiviere die Firewall und setze diese auf Standard zurück. Danach sollte alles gehen
 
Upvote 0 Downvote
Solution
You must log in or register to reply here.
Back
Top