It is currently 15.12.2017 21:30


All times are UTC




Post new topic Reply to topic  [ 5 posts ] 
Author Message
 Post subject: Verbindungsproblem mit OpenVPN und Remotedesktop
PostPosted: 04.07.2017 11:06 
DES
DES

Joined: 04.07.2017 09:37
Posts: 2
Hallo zusammen,
ich bin neu in diesem Forum und möchte zuerst alle recht herzlich begrüßen :)

Natürlich bewegt mich zur Anmeldung in diesem Forum ein Problem seitens OpenVPN und hoffe dass ich hier die Lösung finden werde.

Zu meinem Problem:
Ich habe unter einer Windows-Kiste (Server 2012 R2) einen VPN-Server installiert mit folgender Konfiguration...

Server.conf:
Code:
# Which local IP address should OpenVPN
# listen on? (optional)
;local a.b.c.d

# Which TCP/UDP port should OpenVPN listen on?
# If you want to run multiple OpenVPN instances
# on the same machine, use a different port
# number for each one.  You will need to
# open up this port on your firewall.
port 1194

# TCP or UDP server?
;proto tcp
proto udp

# "dev tun" will create a routed IP tunnel,
# "dev tap" will create an ethernet tunnel.
# Use "dev tap0" if you are ethernet bridging
# and have precreated a tap0 virtual interface
# and bridged it with your ethernet interface.
# If you want to control access policies
# over the VPN, you must create firewall
# rules for the the TUN/TAP interface.
# On non-Windows systems, you can give
# an explicit unit number, such as tun0.
# On Windows, use "dev-node" for this.
# On most systems, the VPN will not function
# unless you partially or fully disable
# the firewall for the TUN/TAP interface.
;dev tap
dev tun

# Windows needs the TAP-Win32 adapter name
# from the Network Connections panel if you
# have more than one.  On XP SP2 or higher,
# you may need to selectively disable the
# Windows firewall for the TAP adapter.
# Non-Windows systems usually don't need this.
;dev-node MyTap

# SSL/TLS root certificate (ca), certificate
# (cert), and private key (key).  Each client
# and the server must have their own cert and
# key file.  The server and all clients will
# use the same ca file.
#
# See the "easy-rsa" directory for a series
# of scripts for generating RSA certificates
# and private keys.  Remember to use
# a unique Common Name for the server
# and each of the client certificates.
#
# Any X509 key management system can be used.
# OpenVPN can also use a PKCS #12 formatted key file
# (see "pkcs12" directive in man page).
ca "D:\\OpenVPN\\easy-rsa\\keys\\ca.crt"
cert "D:\\OpenVPN\\easy-rsa\\keys\\SERVER\\SERVER.crt"
key "D:\\OpenVPN\\easy-rsa\\keys\\SERVER\\SERVER.key"  # This file should be kept secret

# Diffie hellman parameters.
# Generate your own with:
#   openssl dhparam -out dh2048.pem 2048
dh "D:\\OpenVPN\\easy-rsa\\keys\\dh2048.pem"

# Network topology
# Should be subnet (addressing via IP)
# unless Windows clients v2.0.9 and lower have to
# be supported (then net30, i.e. a /30 per client)
# Defaults to net30 (not recommended)
;topology subnet

# Configure server mode and supply a VPN subnet
# for OpenVPN to draw client addresses from.
# The server will take 10.8.0.1 for itself,
# the rest will be made available to clients.
# Each client will be able to reach the server
# on 10.8.0.1. Comment this line out if you are
# ethernet bridging. See the man page for more info.
server 10.39.112.0 255.255.255.0

# Maintain a record of client <-> virtual IP address
# associations in this file.  If OpenVPN goes down or
# is restarted, reconnecting clients can be assigned
# the same virtual IP address from the pool that was
# previously assigned.
ifconfig-pool-persist "D:\\OpenVPN\\config\\Ipp.txt"

# Configure server mode for ethernet bridging.
# You must first use your OS's bridging capability
# to bridge the TAP interface with the ethernet
# NIC interface.  Then you must manually set the
# IP/netmask on the bridge interface, here we
# assume 10.8.0.4/255.255.255.0.  Finally we
# must set aside an IP range in this subnet
# (start=10.8.0.50 end=10.8.0.100) to allocate
# to connecting clients.  Leave this line commented
# out unless you are ethernet bridging.
;server-bridge 10.8.0.4 255.255.255.0 10.8.0.50 10.8.0.100

# Configure server mode for ethernet bridging
# using a DHCP-proxy, where clients talk
# to the OpenVPN server-side DHCP server
# to receive their IP address allocation
# and DNS server addresses.  You must first use
# your OS's bridging capability to bridge the TAP
# interface with the ethernet NIC interface.
# Note: this mode only works on clients (such as
# Windows), where the client-side TAP adapter is
# bound to a DHCP client.
;server-bridge

# Push routes to the client to allow it
# to reach other private subnets behind
# the server.  Remember that these
# private subnets will also need
# to know to route the OpenVPN client
# address pool (10.8.0.0/255.255.255.0)
# back to the OpenVPN server.
push "route 192.168.10.0 255.255.255.0"
;push "route 192.168.20.0 255.255.255.0"

# To assign specific IP addresses to specific
# clients or if a connecting client has a private
# subnet behind it that should also have VPN access,
# use the subdirectory "ccd" for client-specific
# configuration files (see man page for more info).

# EXAMPLE: Suppose the client
# having the certificate common name "Thelonious"
# also has a small subnet behind his connecting
# machine, such as 192.168.40.128/255.255.255.248.
# First, uncomment out these lines:
;client-config-dir ccd
;route 192.168.40.128 255.255.255.248
# Then create a file ccd/Thelonious with this line:
#   iroute 192.168.40.128 255.255.255.248
# This will allow Thelonious' private subnet to
# access the VPN.  This example will only work
# if you are routing, not bridging, i.e. you are
# using "dev tun" and "server" directives.

# EXAMPLE: Suppose you want to give
# Thelonious a fixed VPN IP address of 10.9.0.1.
# First uncomment out these lines:
;client-config-dir ccd
;route 10.9.0.0 255.255.255.252
# Then add this line to ccd/Thelonious:
#   ifconfig-push 10.9.0.1 10.9.0.2

# Suppose that you want to enable different
# firewall access policies for different groups
# of clients.  There are two methods:
# (1) Run multiple OpenVPN daemons, one for each
#     group, and firewall the TUN/TAP interface
#     for each group/daemon appropriately.
# (2) (Advanced) Create a script to dynamically
#     modify the firewall in response to access
#     from different clients.  See man
#     page for more info on learn-address script.
;learn-address ./script

# If enabled, this directive will configure
# all clients to redirect their default
# network gateway through the VPN, causing
# all IP traffic such as web browsing and
# and DNS lookups to go through the VPN
# (The OpenVPN server machine may need to NAT
# or bridge the TUN/TAP interface to the internet
# in order for this to work properly).
;push "redirect-gateway def1 bypass-dhcp"

# Certain Windows-specific network settings
# can be pushed to clients, such as DNS
# or WINS server addresses.  CAVEAT:
# http://openvpn.net/faq.html#dhcpcaveats
# The addresses below refer to the public
# DNS servers provided by opendns.com.
;push "dhcp-option DNS 208.67.222.222"
;push "dhcp-option DNS 208.67.220.220"

# Uncomment this directive to allow different
# clients to be able to "see" each other.
# By default, clients will only see the server.
# To force clients to only see the server, you
# will also need to appropriately firewall the
# server's TUN/TAP interface.
;client-to-client

# Uncomment this directive if multiple clients
# might connect with the same certificate/key
# files or common names.  This is recommended
# only for testing purposes.  For production use,
# each client should have its own certificate/key
# pair.
#
# IF YOU HAVE NOT GENERATED INDIVIDUAL
# CERTIFICATE/KEY PAIRS FOR EACH CLIENT,
# EACH HAVING ITS OWN UNIQUE "COMMON NAME",
# UNCOMMENT THIS LINE OUT.
;duplicate-cn

# The keepalive directive causes ping-like
# messages to be sent back and forth over
# the link so that each side knows when
# the other side has gone down.
# Ping every 10 seconds, assume that remote
# peer is down if no ping received during
# a 120 second time period.
keepalive 10 120

# For extra security beyond that provided
# by SSL/TLS, create an "HMAC firewall"
# to help block DoS attacks and UDP port flooding.
#
# Generate with:
#   openvpn --genkey --secret ta.key
#
# The server and each client must have
# a copy of this key.
# The second parameter should be '0'
# on the server and '1' on the clients.
tls-auth "D:\\OpenVPN\\easy-rsa\\keys\\ta.key" 0 # This file is secret

# Select a cryptographic cipher.
# This config item must be copied to
# the client config file as well.
# Note that 2.4 client/server will automatically
# negotiate AES-256-GCM in TLS mode.
# See also the ncp-cipher option in the manpage
cipher AES-256-CBC

# Enable compression on the VPN link and push the
# option to the client (2.4+ only, for earlier
# versions see below)
;compress lz4-v2
;push "compress lz4-v2"

# For compression compatible with older clients use comp-lzo
# If you enable it here, you must also
# enable it in the client config file.
;comp-lzo

# The maximum number of concurrently connected
# clients we want to allow.
;max-clients 100

# It's a good idea to reduce the OpenVPN
# daemon's privileges after initialization.
#
# You can uncomment this out on
# non-Windows systems.
;user nobody
;group nobody

# The persist options will try to avoid
# accessing certain resources on restart
# that may no longer be accessible because
# of the privilege downgrade.
persist-key
persist-tun

# Output a short status file showing
# current connections, truncated
# and rewritten every minute.
status "D:\\OpenVPN\\log\\openvpn-status.log"

# By default, log messages will go to the syslog (or
# on Windows, if running as a service, they will go to
# the "\Program Files\OpenVPN\log" directory).
# Use log or log-append to override this default.
# "log" will truncate the log file on OpenVPN startup,
# while "log-append" will append to it.  Use one
# or the other (but not both).
;log         openvpn.log
;log-append  openvpn.log

# Set the appropriate level of log
# file verbosity.
#
# 0 is silent, except for fatal errors
# 4 is reasonable for general usage
# 5 and 6 can help to debug connection problems
# 9 is extremely verbose
verb 3

# Silence repeating messages.  At most 20
# sequential messages of the same message
# category will be output to the log.
;mute 20

# Notify the client that when the server restarts so it
# can automatically reconnect.
explicit-exit-notify 1

# User management.
# auth-user-pass-verify "D:\\OpenVPN\\config\\auth.bat" via-env


Die VPN-Verbindung soll über ein Windows-Notebook hergestellt werden, hierfür verwende ich folgende Konfiguration...

Client.conf:
Code:
##############################################
# Sample client-side OpenVPN 2.0 config file #
# for connecting to multi-client server.     #
#                                            #
# This configuration can be used by multiple #
# clients, however each client should have   #
# its own cert and key files.                #
#                                            #
# On Windows, you might want to rename this  #
# file so it has a .ovpn extension           #
##############################################

# Specify that we are a client and that we
# will be pulling certain config file directives
# from the server.
client

# Use the same setting as you are using on
# the server.
# On most systems, the VPN will not function
# unless you partially or fully disable
# the firewall for the TUN/TAP interface.
;dev tap
dev tun

# Windows needs the TAP-Win32 adapter name
# from the Network Connections panel
# if you have more than one.  On XP SP2,
# you may need to disable the firewall
# for the TAP adapter.
;dev-node MyTap

# Are we connecting to a TCP or
# UDP server?  Use the same setting as
# on the server.
;proto tcp
proto udp

# The hostname/IP and port of the server.
# You can have multiple remote entries
# to load balance between the servers.
remote das.ist.meine.ip 1194
;remote my-server-2 1194

# Choose a random host from the remote
# list for load-balancing.  Otherwise
# try hosts in the order specified.
;remote-random

# Keep trying indefinitely to resolve the
# host name of the OpenVPN server.  Very useful
# on machines which are not permanently connected
# to the internet such as laptops.
resolv-retry infinite

# Most clients don't need to bind to
# a specific local port number.
nobind

# Downgrade privileges after initialization (non-Windows only)
;user nobody
;group nobody

# Try to preserve some state across restarts.
persist-key
persist-tun

# If you are connecting through an
# HTTP proxy to reach the actual OpenVPN
# server, put the proxy server/IP and
# port number here.  See the man page
# if your proxy server requires
# authentication.
;http-proxy-retry # retry on connection failures
;http-proxy [proxy server] [proxy port #]

# Wireless networks often produce a lot
# of duplicate packets.  Set this flag
# to silence duplicate packet warnings.
;mute-replay-warnings

# SSL/TLS parms.
# See the server config file for more
# description.  It's best to use
# a separate .crt/.key file pair
# for each client.  A single ca
# file can be used for all clients.
ca "C:\\Program Files\\OpenVPN\\Keys\\ca.crt"
cert "C:\\Program Files\\OpenVPN\\Keys\\Client01.crt"
key "C:\\Program Files\\OpenVPN\\Keys\\Client01.key"

# Verify server certificate by checking that the
# certicate has the correct key usage set.
# This is an important precaution to protect against
# a potential attack discussed here:
#  http://openvpn.net/howto.html#mitm
#
# To use this feature, you will need to generate
# your server certificates with the keyUsage set to
#   digitalSignature, keyEncipherment
# and the extendedKeyUsage to
#   serverAuth
# EasyRSA can do this for you.
remote-cert-tls server

# If a tls-auth key is used on the server
# then every client must also have the key.
tls-auth "C:\\Program Files\\OpenVPN\\Keys\\ta.key" 1

# Select a cryptographic cipher.
# If the cipher option is used on the server
# then you must also specify it here.
# Note that 2.4 client/server will automatically
# negotiate AES-256-GCM in TLS mode.
# See also the ncp-cipher option in the manpage
cipher AES-256-CBC

# Enable compression on the VPN link.
# Don't enable this unless it is also
# enabled in the server config file.
#comp-lzo

# Set log file verbosity.
verb 3

# Silence repeating messages
;mute 20

auth-nocache


Wird eine VPN-Verbindung vom Notebook zum Server hergestellt, wird diese aufgebaut...soweit alles bestens.
Möchte ich nun eine Remotedesktopverbindung zum Server starten wird diese ab und zu aufgebaut und wenn die Verbindung steht bricht diese innerhalb von ein paar Sekunden ab. Eine erneute Remotedesktopverbindung ist dann nur in den seltensten Fällen möglich.
Ferner Funktioniert VPN sowie Remotedesktop, wenn sich beide Geräte im gleichen Netzwerk (Zu Hause) befinden, das Problem besteht einzig wenn ich versuche von Unterwegs (Internetzugang bei Freundin bzw. per Hotspot am Handy) auf den Server zuzugreifen.

Was ich versucht bzw. getestet habe:
- OpenVPN auf beiden PCs neu installiert und neu konfiguriert
- Firewall geprüft (Port 1194 habe ich in der Fritzbox als UDP und zusätzlich TCP zum Server freigegeben, Port 1194 an beiden Windows-PCs in der windowseigenen Firewall freigegeben, beide windowseigenen Firewalls zum testen deaktiviert, Firewallport von 1194 auf 4145 geändert)

Server-Log:
Code:
Tue Jul 04 12:31:18 2017 OpenVPN 2.4.3 x86_64-w64-mingw32 [SSL (OpenSSL)] [LZO] [LZ4] [PKCS11] [AEAD] built on Jun 20 2017
Tue Jul 04 12:31:18 2017 Windows version 6.2 (Windows 8 or greater) 64bit
Tue Jul 04 12:31:18 2017 library versions: OpenSSL 1.0.2l  25 May 2017, LZO 2.10
Tue Jul 04 12:31:18 2017 Diffie-Hellman initialized with 2048 bit key
Tue Jul 04 12:31:18 2017 Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
Tue Jul 04 12:31:18 2017 Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
Tue Jul 04 12:31:18 2017 interactive service msg_channel=0
Tue Jul 04 12:31:18 2017 ROUTE_GATEWAY 192.168.10.50/255.255.255.0 I=12 HWADDR=d4:3d:7e:31:d1:b4
Tue Jul 04 12:31:18 2017 open_tun
Tue Jul 04 12:31:18 2017 TAP-WIN32 device [VPN] opened: \\.\Global\{EF989F45-13DC-4F9E-A2C2-1C17B9981CFC}.tap
Tue Jul 04 12:31:18 2017 TAP-Windows Driver Version 9.21
Tue Jul 04 12:31:18 2017 Notified TAP-Windows driver to set a DHCP IP/netmask of 10.39.112.1/255.255.255.252 on interface {EF989F45-13DC-4F9E-A2C2-1C17B9981CFC} [DHCP-serv: 10.39.112.2, lease-time: 31536000]
Tue Jul 04 12:31:18 2017 Sleeping for 10 seconds...
Tue Jul 04 12:31:28 2017 Successful ARP Flush on interface [16] {EF989F45-13DC-4F9E-A2C2-1C17B9981CFC}
Tue Jul 04 12:31:28 2017 do_ifconfig, tt->did_ifconfig_ipv6_setup=0
Tue Jul 04 12:31:28 2017 C:\Windows\system32\route.exe ADD 10.39.112.0 MASK 255.255.255.0 10.39.112.2
Tue Jul 04 12:31:28 2017 ROUTE: CreateIpForwardEntry succeeded with dwForwardMetric1=20 and dwForwardType=4
Tue Jul 04 12:31:28 2017 Route addition via IPAPI succeeded [adaptive]
Tue Jul 04 12:31:28 2017 Could not determine IPv4/IPv6 protocol. Using AF_INET6
Tue Jul 04 12:31:28 2017 Socket Buffers: R=[65536->65536] S=[65536->65536]
Tue Jul 04 12:31:28 2017 setsockopt(IPV6_V6ONLY=0)
Tue Jul 04 12:31:28 2017 UDPv6 link local (bound): [AF_INET6][undef]:1194
Tue Jul 04 12:31:28 2017 UDPv6 link remote: [AF_UNSPEC]
Tue Jul 04 12:31:28 2017 MULTI: multi_init called, r=256 v=256
Tue Jul 04 12:31:28 2017 IFCONFIG POOL: base=10.39.112.4 size=62, ipv6=0
Tue Jul 04 12:31:28 2017 ifconfig_pool_read(), in='MOBiLE,10.39.112.8', TODO: IPv6
Tue Jul 04 12:31:28 2017 succeeded -> ifconfig_pool_set()
Tue Jul 04 12:31:28 2017 ifconfig_pool_read(), in='Client01,10.39.112.20', TODO: IPv6
Tue Jul 04 12:31:28 2017 succeeded -> ifconfig_pool_set()
Tue Jul 04 12:31:28 2017 ifconfig_pool_read(), in='Client02,10.39.112.28', TODO: IPv6
Tue Jul 04 12:31:28 2017 succeeded -> ifconfig_pool_set()
Tue Jul 04 12:31:28 2017 ifconfig_pool_read(), in='Client03,10.39.112.40', TODO: IPv6
Tue Jul 04 12:31:28 2017 succeeded -> ifconfig_pool_set()
Tue Jul 04 12:31:28 2017 IFCONFIG POOL LIST
Tue Jul 04 12:31:28 2017 MOBiLE,10.39.112.8
Tue Jul 04 12:31:28 2017 Client01,10.39.112.20
Tue Jul 04 12:31:28 2017 Client02,10.39.112.28
Tue Jul 04 12:31:28 2017 Client03,10.39.112.40
Tue Jul 04 12:31:28 2017 Initialization Sequence Completed
Tue Jul 04 12:31:45 2017 das.ist.meine.ip TLS: Initial packet from [AF_INET6]::ffff:das.ist.meine.ip:52824, sid=7c295c8e cda798b7
Tue Jul 04 12:31:45 2017 das.ist.meine.ip VERIFY OK: ...Zertifikatdaten...
Tue Jul 04 12:31:45 2017 das.ist.meine.ip VERIFY OK: ...Zertifikatdaten...
Tue Jul 04 12:31:45 2017 das.ist.meine.ip peer info: IV_VER=2.4.3
Tue Jul 04 12:31:45 2017 das.ist.meine.ip peer info: IV_PLAT=win
Tue Jul 04 12:31:45 2017 das.ist.meine.ip peer info: IV_PROTO=2
Tue Jul 04 12:31:45 2017 das.ist.meine.ip peer info: IV_NCP=2
Tue Jul 04 12:31:45 2017 das.ist.meine.ip peer info: IV_LZ4=1
Tue Jul 04 12:31:45 2017 das.ist.meine.ip peer info: IV_LZ4v2=1
Tue Jul 04 12:31:45 2017 das.ist.meine.ip peer info: IV_LZO=1
Tue Jul 04 12:31:45 2017 das.ist.meine.ip peer info: IV_COMP_STUB=1
Tue Jul 04 12:31:45 2017 das.ist.meine.ip peer info: IV_COMP_STUBv2=1
Tue Jul 04 12:31:45 2017 das.ist.meine.ip peer info: IV_TCPNL=1
Tue Jul 04 12:31:45 2017 das.ist.meine.ip peer info: IV_GUI_VER=OpenVPN_GUI_11
Tue Jul 04 12:31:45 2017 das.ist.meine.ip Control Channel: TLSv1.2, cipher TLSv1/SSLv3 ECDHE-RSA-AES256-GCM-SHA384, 2048 bit RSA
Tue Jul 04 12:31:45 2017 das.ist.meine.ip [Client01] Peer Connection Initiated with [AF_INET6]::ffff:das.ist.meine.ip:52824
Tue Jul 04 12:31:45 2017 Client01/das.ist.meine.ip MULTI_sva: pool returned IPv4=10.39.112.22, IPv6=(Not enabled)
Tue Jul 04 12:31:45 2017 Client01/das.ist.meine.ip MULTI: Learn: 10.39.112.22 -> Client01/das.ist.meine.ip
Tue Jul 04 12:31:45 2017 Client01/das.ist.meine.ip MULTI: primary virtual IP for Client01/das.ist.meine.ip: 10.39.112.22
Tue Jul 04 12:31:47 2017 Client01/das.ist.meine.ip PUSH: Received control message: 'PUSH_REQUEST'
Tue Jul 04 12:31:47 2017 Client01/das.ist.meine.ip SENT CONTROL [Client01]: 'PUSH_REPLY,route 192.168.10.0 255.255.255.0,route 10.39.112.1,topology net30,ping 10,ping-restart 120,ifconfig 10.39.112.22 10.39.112.21,peer-id 0,cipher AES-256-GCM' (status=1)
Tue Jul 04 12:31:47 2017 Client01/das.ist.meine.ip Data Channel: using negotiated cipher 'AES-256-GCM'
Tue Jul 04 12:31:47 2017 Client01/das.ist.meine.ip Data Channel Encrypt: Cipher 'AES-256-GCM' initialized with 256 bit key
Tue Jul 04 12:31:47 2017 Client01/das.ist.meine.ip Data Channel Decrypt: Cipher 'AES-256-GCM' initialized with 256 bit key
Tue Jul 04 12:36:38 2017 das.ist.meine.ip TLS: Initial packet from [AF_INET6]::ffff:das.ist.meine.ip:36782, sid=a1c5cc9a b5abb29e
Tue Jul 04 12:36:38 2017 das.ist.meine.ip VERIFY OK: ...Zertifikatdaten...
Tue Jul 04 12:36:38 2017 das.ist.meine.ip VERIFY OK: ...Zertifikatdaten...
Tue Jul 04 12:36:38 2017 das.ist.meine.ip peer info: IV_VER=2.4.3
Tue Jul 04 12:36:38 2017 das.ist.meine.ip peer info: IV_PLAT=win
Tue Jul 04 12:36:38 2017 das.ist.meine.ip peer info: IV_PROTO=2
Tue Jul 04 12:36:38 2017 das.ist.meine.ip peer info: IV_NCP=2
Tue Jul 04 12:36:38 2017 das.ist.meine.ip peer info: IV_LZ4=1
Tue Jul 04 12:36:38 2017 das.ist.meine.ip peer info: IV_LZ4v2=1
Tue Jul 04 12:36:38 2017 das.ist.meine.ip peer info: IV_LZO=1
Tue Jul 04 12:36:38 2017 das.ist.meine.ip peer info: IV_COMP_STUB=1
Tue Jul 04 12:36:38 2017 das.ist.meine.ip peer info: IV_COMP_STUBv2=1
Tue Jul 04 12:36:38 2017 das.ist.meine.ip peer info: IV_TCPNL=1
Tue Jul 04 12:36:38 2017 das.ist.meine.ip peer info: IV_GUI_VER=OpenVPN_GUI_11
Tue Jul 04 12:36:39 2017 das.ist.meine.ip Control Channel: TLSv1.2, cipher TLSv1/SSLv3 ECDHE-RSA-AES256-GCM-SHA384, 2048 bit RSA
Tue Jul 04 12:36:39 2017 das.ist.meine.ip [Client01] Peer Connection Initiated with [AF_INET6]::ffff:das.ist.meine.ip:36782
Tue Jul 04 12:36:39 2017 MULTI: new connection by client 'Client01' will cause previous active sessions by this client to be dropped.  Remember to use the --duplicate-cn option if you want multiple clients using the same certificate or username to concurrently connect.
Tue Jul 04 12:36:39 2017 MULTI_sva: pool returned IPv4=10.39.112.22, IPv6=(Not enabled)
Tue Jul 04 12:36:39 2017 MULTI: Learn: 10.39.112.22 -> Client01/das.ist.meine.ip
Tue Jul 04 12:36:39 2017 MULTI: primary virtual IP for Client01/das.ist.meine.ip: 10.39.112.22
Tue Jul 04 12:36:40 2017 Client01/das.ist.meine.ip PUSH: Received control message: 'PUSH_REQUEST'
Tue Jul 04 12:36:40 2017 Client01/das.ist.meine.ip SENT CONTROL [Client01]: 'PUSH_REPLY,route 192.168.10.0 255.255.255.0,route 10.39.112.1,topology net30,ping 10,ping-restart 120,ifconfig 10.39.112.22 10.39.112.21,peer-id 1,cipher AES-256-GCM' (status=1)
Tue Jul 04 12:36:40 2017 Client01/das.ist.meine.ip Data Channel: using negotiated cipher 'AES-256-GCM'
Tue Jul 04 12:36:40 2017 Client01/das.ist.meine.ip Data Channel Encrypt: Cipher 'AES-256-GCM' initialized with 256 bit key
Tue Jul 04 12:36:40 2017 Client01/das.ist.meine.ip Data Channel Decrypt: Cipher 'AES-256-GCM' initialized with 256 bit key
Tue Jul 04 12:43:11 2017 Client01/das.ist.meine.ip [Client01] Inactivity timeout (--ping-restart), restarting
Tue Jul 04 12:43:11 2017 Client01/das.ist.meine.ip SIGUSR1[soft,ping-restart] received, client-instance restarting


Client-Log:
Code:
Tue Jul 04 12:36:35 2017 OpenVPN 2.4.3 x86_64-w64-mingw32 [SSL (OpenSSL)] [LZO] [LZ4] [PKCS11] [AEAD] built on Jun 20 2017
Tue Jul 04 12:36:35 2017 Windows version 6.1 (Windows 7) 64bit
Tue Jul 04 12:36:35 2017 library versions: OpenSSL 1.0.2l  25 May 2017, LZO 2.10
Tue Jul 04 12:36:35 2017 MANAGEMENT: TCP Socket listening on [AF_INET]127.0.0.1:25340
Tue Jul 04 12:36:35 2017 Need hold release from management interface, waiting...
Tue Jul 04 12:36:36 2017 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:25340
Tue Jul 04 12:36:36 2017 MANAGEMENT: CMD 'state on'
Tue Jul 04 12:36:36 2017 MANAGEMENT: CMD 'log all on'
Tue Jul 04 12:36:36 2017 MANAGEMENT: CMD 'echo all on'
Tue Jul 04 12:36:36 2017 MANAGEMENT: CMD 'hold off'
Tue Jul 04 12:36:36 2017 MANAGEMENT: CMD 'hold release'
Tue Jul 04 12:36:36 2017 Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
Tue Jul 04 12:36:36 2017 Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
Tue Jul 04 12:36:36 2017 MANAGEMENT: >STATE:1499164596,RESOLVE,,,,,,
Tue Jul 04 12:36:36 2017 TCP/UDP: Preserving recently used remote address: [AF_INET]das.ist.meine.ip:1194
Tue Jul 04 12:36:36 2017 Socket Buffers: R=[8192->8192] S=[8192->8192]
Tue Jul 04 12:36:36 2017 UDP link local: (not bound)
Tue Jul 04 12:36:36 2017 UDP link remote: [AF_INET]das.ist.meine.ip:1194
Tue Jul 04 12:36:36 2017 MANAGEMENT: >STATE:1499164596,WAIT,,,,,,
Tue Jul 04 12:36:37 2017 MANAGEMENT: >STATE:1499164597,AUTH,,,,,,
Tue Jul 04 12:36:37 2017 TLS: Initial packet from [AF_INET]das.ist.meine.ip:1194, sid=81ddc0c7 d9f2313e
Tue Jul 04 12:36:37 2017 VERIFY OK: ...Zertifikatdaten...
Tue Jul 04 12:36:37 2017 VERIFY KU OK
Tue Jul 04 12:36:37 2017 Validating certificate extended key usage
Tue Jul 04 12:36:37 2017 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication
Tue Jul 04 12:36:37 2017 VERIFY EKU OK
Tue Jul 04 12:36:37 2017 VERIFY OK: ...Zertifikatdaten...
Tue Jul 04 12:36:37 2017 Control Channel: TLSv1.2, cipher TLSv1/SSLv3 ECDHE-RSA-AES256-GCM-SHA384, 2048 bit RSA
Tue Jul 04 12:36:37 2017 [SERVER] Peer Connection Initiated with [AF_INET]das.ist.meine.ip:1194
Tue Jul 04 12:36:38 2017 MANAGEMENT: >STATE:1499164598,GET_CONFIG,,,,,,
Tue Jul 04 12:36:38 2017 SENT CONTROL [SERVER]: 'PUSH_REQUEST' (status=1)
Tue Jul 04 12:36:38 2017 PUSH: Received control message: 'PUSH_REPLY,route 192.168.10.0 255.255.255.0,route 10.39.112.1,topology net30,ping 10,ping-restart 120,ifconfig 10.39.112.22 10.39.112.21,peer-id 1,cipher AES-256-GCM'
Tue Jul 04 12:36:38 2017 OPTIONS IMPORT: timers and/or timeouts modified
Tue Jul 04 12:36:38 2017 OPTIONS IMPORT: --ifconfig/up options modified
Tue Jul 04 12:36:38 2017 OPTIONS IMPORT: route options modified
Tue Jul 04 12:36:38 2017 OPTIONS IMPORT: peer-id set
Tue Jul 04 12:36:38 2017 OPTIONS IMPORT: adjusting link_mtu to 1624
Tue Jul 04 12:36:38 2017 OPTIONS IMPORT: data channel crypto options modified
Tue Jul 04 12:36:38 2017 Data Channel: using negotiated cipher 'AES-256-GCM'
Tue Jul 04 12:36:38 2017 Data Channel Encrypt: Cipher 'AES-256-GCM' initialized with 256 bit key
Tue Jul 04 12:36:38 2017 Data Channel Decrypt: Cipher 'AES-256-GCM' initialized with 256 bit key
Tue Jul 04 12:36:38 2017 interactive service msg_channel=0
Tue Jul 04 12:36:38 2017 ROUTE_GATEWAY 192.168.43.1/255.255.255.0 I=12 HWADDR=58:94:6b:f3:1d:c8
Tue Jul 04 12:36:38 2017 open_tun
Tue Jul 04 12:36:38 2017 TAP-WIN32 device [VPN] opened: \\.\Global\{658587C7-4F2E-4A4B-9C5D-281A2403EAF9}.tap
Tue Jul 04 12:36:38 2017 TAP-Windows Driver Version 9.21
Tue Jul 04 12:36:38 2017 Notified TAP-Windows driver to set a DHCP IP/netmask of 10.39.112.22/255.255.255.252 on interface {658587C7-4F2E-4A4B-9C5D-281A2403EAF9} [DHCP-serv: 10.39.112.21, lease-time: 31536000]
Tue Jul 04 12:36:38 2017 Successful ARP Flush on interface [19] {658587C7-4F2E-4A4B-9C5D-281A2403EAF9}
Tue Jul 04 12:36:38 2017 do_ifconfig, tt->did_ifconfig_ipv6_setup=0
Tue Jul 04 12:36:38 2017 MANAGEMENT: >STATE:1499164598,ASSIGN_IP,,10.39.112.22,,,,
Tue Jul 04 12:36:43 2017 TEST ROUTES: 2/2 succeeded len=2 ret=1 a=0 u/d=up
Tue Jul 04 12:36:43 2017 MANAGEMENT: >STATE:1499164603,ADD_ROUTES,,,,,,
Tue Jul 04 12:36:43 2017 C:\Windows\system32\route.exe ADD 192.168.10.0 MASK 255.255.255.0 10.39.112.21
Tue Jul 04 12:36:43 2017 ROUTE: CreateIpForwardEntry succeeded with dwForwardMetric1=20 and dwForwardType=4
Tue Jul 04 12:36:43 2017 Route addition via IPAPI succeeded [adaptive]
Tue Jul 04 12:36:43 2017 C:\Windows\system32\route.exe ADD 10.39.112.1 MASK 255.255.255.255 10.39.112.21
Tue Jul 04 12:36:43 2017 ROUTE: CreateIpForwardEntry succeeded with dwForwardMetric1=20 and dwForwardType=4
Tue Jul 04 12:36:43 2017 Route addition via IPAPI succeeded [adaptive]
Tue Jul 04 12:36:43 2017 Initialization Sequence Completed
Tue Jul 04 12:36:43 2017 MANAGEMENT: >STATE:1499164603,CONNECTED,SUCCESS,10.39.112.22,das.ist.meine.ip,1194,,


Weis jemand Rat?
Selbstverständlich habe ich auch schon Google befragt und auch massenhaft Ergebnisse erhalten, mitunter hatte ich auch etwas von Routingproblem gelesen, was ich aber ehrlich gesagt nicht ganz glaube.

Danke schonmal für eure Ratschläge.

Gruß,
Blattlaus


Top
Offline Profile  
Reply with quote  
 Post subject: Re: Verbindungsproblem mit OpenVPN und Remotedesktop
PostPosted: 04.07.2017 14:24 
Profi
Profi

Joined: 23.10.2007 12:10
Posts: 2191
Hallo,
dazu würde ich erst mal die Logs befragen (spezielle rdp und evtl. (win)Firewall).

Tunnel sollte ja nach wie vor stehen...
Config sind nett gedacht, aber wer in aller Welt soll sich die relevanten 10 Zeilen unter den (gefühlten) 1000 Kommentarzeilen raussuchen :)

ansonsten: wie kommst du auf Routing ? ... hast du denn so "um die Ecke" gestaltet, dass es ohne Routing nicht geht ?
Kann mich auch an kein RDP-Problem mit (openVPN)Clients erinnern bei gut 10 Jahren Fernwartung u.ä.
Den Rest müsste man konkret sehen (Log lesen, wer wirft warum ab?)

Fred


Top
Offline Profile  
Reply with quote  
 Post subject: Re: Verbindungsproblem mit OpenVPN und Remotedesktop
PostPosted: 17.07.2017 14:00 
DES
DES

Joined: 04.07.2017 09:37
Posts: 2
Hallo zusammen,

ich habe mich selbst nochmal meinem Problem so gut es ging angenommen und bin nicht wirklich weiter gekommen...

Hatte nun nochmals OpenVPN auf allen Geräten deinstalliert und neu installiert, Zertifikate sowie die .conf Dateien neu generiert/erstellt.

Immer und immer wieder das gleiche Problem.
Mein Notebook baut die VPN-Verbindung auf, ab und an funktioniert sie und wenn dann bricht sie mehrfach nach ca. 5-15Sekunden ab und reconnected, es kommt auch vor dass der wiederholte Verbindungsaufbau gar nicht mehr geht.
Getestet über ein entfernter DSL-Anschluss sowie Mobilverbindung.

Witzigerweise funktioniert die VPN-Verbindung samt Remotedesktopverbindung mit der gleichen Konfigurationsdatei (aber mit anderen Zertifikaten) auf einem Samsung Galaxy S6 tadellos...

...ich verstehe die Welt nicht mehr.

@Fred:
Danke für deine Antwort, genau das ist der Punkt wo ich mich etwas schwer tue.
Wo bzw. wie außer dem VPN-Log kann ich in weitere Log-Dateien einsehen, wie zum Beispiel RDP?

Gruß,
Blattlaus


Top
Offline Profile  
Reply with quote  
 Post subject: Re: Verbindungsproblem mit OpenVPN und Remotedesktop
PostPosted: 18.07.2017 08:51 
Profi
Profi

Joined: 23.10.2007 12:10
Posts: 2191
BlattlausLR wrote:
Hallo zusammen,

ich habe mich selbst nochmal meinem Problem so gut es ging angenommen und bin nicht wirklich weiter gekommen...

Hatte nun nochmals OpenVPN auf allen Geräten deinstalliert und neu installiert, Zertifikate sowie die .conf Dateien neu generiert/erstellt.

Immer und immer wieder das gleiche Problem.
Mein Notebook baut die VPN-Verbindung auf, ab und an funktioniert sie und wenn dann bricht sie mehrfach nach ca. 5-15Sekunden ab und reconnected, es kommt auch vor dass der wiederholte Verbindungsaufbau gar nicht mehr geht.
Getestet über ein entfernter DSL-Anschluss sowie Mobilverbindung.
das VPN-Log nennt dir einen Grund !
sowohl clientseitig auch serverseitig Logs ansehen!
Ich hoffe doch für dich, dass du mindestens jetzt welche schreibst :)
(kann man später wieder abstellen)

Quote:
Witzigerweise funktioniert die VPN-Verbindung samt Remotedesktopverbindung mit der gleichen Konfigurationsdatei (aber mit anderen Zertifikaten) auf einem Samsung Galaxy S6 tadellos...

...ich verstehe die Welt nicht mehr.

@Fred:
Danke für deine Antwort, genau das ist der Punkt wo ich mich etwas schwer tue.
Wo bzw. wie außer dem VPN-Log kann ich in weitere Log-Dateien einsehen, wie zum Beispiel RDP?

Gruß,
Blattlaus

oha... das ist Windoof-Kram ! (zählt nicht zu "täglich Brot" und ich muss auch immer erst eine Suchmaschine befragen, wo genau :) -> Server-Log-Files eben )
Müsste ich auch suchen, was wo steht, überlasse es aber besser dem, der auf die WindowsServerIdee gekommen ist!
Win-srv kommen bei mir nicht ohne (große) Not auf den Tisch ;-)

Ansonsten:
schmeiss deisen ganzen ipcifig-Kram raus! der kann ganz gur selber das regeln und recht passabel, wenn schon, dann mittels ccd IP zuweisen.
Bevorzuge auch *.p12 Zertifikate, da kann man nix "verwuseln"
Ansonsten ... meine.ip ist nett, aber der Anfang (erste oder ersten zwei Ziffern) wäre hilfreicher.
Code:
Tue Jul 04 12:36:39 2017 MULTI: new connection by client 'Client01' will cause previous active sessions by this client to be dropped.  Remember to use the --duplicate-cn option if you want multiple clients using the same certificate or username to concurrently connect.

war der Zertifikatverwusel-Plan ?
Ich persönlich finde es etwas daneben, ein Zertifikat für viele zu verwenden ....(viele= mehr als einer!) -

F.


Top
Offline Profile  
Reply with quote  
 Post subject: Re: Verbindungsproblem mit OpenVPN und Remotedesktop
PostPosted: 25.07.2017 09:13 
AES 256 bit
AES 256 bit

Joined: 27.11.2012 18:37
Posts: 272
Hi,
Quote:
Immer und immer wieder das gleiche Problem.
Mein Notebook baut die VPN-Verbindung auf, ab und an funktioniert sie und wenn dann bricht sie mehrfach nach ca. 5-15Sekunden ab und reconnected, es kommt auch vor dass der wiederholte Verbindungsaufbau gar nicht mehr geht.

Wenn das mit einem anderen Gerät (Galaxy) funktioniert, dann sollte wohl Serverseitig alles in Ordnung sein und Dein Notebook hat ein Problem. Wie das @dl5ym schon richtig gepostet hat, die Logs geben Dir Auskunft. Ich tippe mal auf die Aushandlung des tls-Handshakes, wenn Du selbsterstellte Zertifikate verwendest.
Gruß orcape


Top
Offline Profile  
Reply with quote  
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 5 posts ]  Moderator: Moderators

All times are UTC


Who is online

Users browsing this forum: Bing [Bot], Google [Bot] and 7 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group
Theme created StylerBB.net