Problem connecting with my client

Need help configuring your VPN? Just post here and you'll get that help.

Moderators: TinCanTech, TinCanTech, TinCanTech, TinCanTech, TinCanTech, TinCanTech

Forum rules
Please use the [oconf] BB tag for openvpn Configurations. See viewtopic.php?f=30&t=21589 for an example.
Post Reply
bdescals
OpenVpn Newbie
Posts: 3
Joined: Fri Feb 23, 2018 12:55 pm

Problem connecting with my client

Post by bdescals » Fri Feb 23, 2018 1:05 pm

Hello,

I've been trying to install OpenVPN through PiVPN on my Raspberry Pi 3 B for two weeks, and when I try to connect my computer to it it doesn't wor., My client file shows:

client
dev tun
proto udp
remote xxxx 1194
resolv-retry infinite
nobind
persist-key
persist-tun
key-direction 1
remote-cert-tls server
tls-version-min 1.2
verify-x509-name xxxx name
cipher AES-256-CBC
auth SHA256
comp-lzo
verb 3
<ca>

And when I try to connect it shows this:

Fri Feb 23 13:25:03 2018 OpenVPN 2.4.4 x86_64-w64-mingw32 [SSL (OpenSSL)] [LZO] [LZ4] [PKCS11] [AEAD] built on Sep 26 2017
Fri Feb 23 13:25:03 2018 Windows version 6.2 (Windows 8 or greater) 64bit
Fri Feb 23 13:25:03 2018 library versions: OpenSSL 1.0.2l 25 May 2017, LZO 2.10
Fri Feb 23 13:25:03 2018 MANAGEMENT: TCP Socket listening on [AF_INET]127.0.0.1:25349
Fri Feb 23 13:25:03 2018 Need hold release from management interface, waiting...
Fri Feb 23 13:25:03 2018 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:25349
Fri Feb 23 13:25:03 2018 MANAGEMENT: CMD 'state on'
Fri Feb 23 13:25:03 2018 MANAGEMENT: CMD 'log all on'
Fri Feb 23 13:25:03 2018 MANAGEMENT: CMD 'echo all on'
Fri Feb 23 13:25:03 2018 MANAGEMENT: CMD 'hold off'
Fri Feb 23 13:25:03 2018 MANAGEMENT: CMD 'hold release'
Fri Feb 23 13:25:07 2018 MANAGEMENT: CMD 'password [...]'
Fri Feb 23 13:25:07 2018 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
Fri Feb 23 13:25:07 2018 Outgoing Control Channel Authentication: Using 256 bit message hash 'SHA256' for HMAC authentication
Fri Feb 23 13:25:07 2018 Incoming Control Channel Authentication: Using 256 bit message hash 'SHA256' for HMAC authentication
Fri Feb 23 13:25:07 2018 TCP/UDP: Preserving recently used remote address: [AF_INET]xxxx:1194
Fri Feb 23 13:25:07 2018 Socket Buffers: R=[65536->65536] S=[65536->65536]
Fri Feb 23 13:25:07 2018 UDP link local: (not bound)
Fri Feb 23 13:25:07 2018 UDP link remote: [AF_INET]xxxx:1194
Fri Feb 23 13:25:07 2018 MANAGEMENT: >STATE:1519388707,WAIT,,,,,,
Fri Feb 23 13:25:08 2018 MANAGEMENT: >STATE:1519388708,AUTH,,,,,,
Fri Feb 23 13:25:08 2018 TLS: Initial packet from [AF_INET]xxxx:1194, sid=7b61e9b4 594dc209
Fri Feb 23 13:25:08 2018 VERIFY OK: depth=1, CN=ChangeMe
Fri Feb 23 13:25:08 2018 VERIFY KU OK
Fri Feb 23 13:25:08 2018 Validating certificate extended key usage
Fri Feb 23 13:25:08 2018 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication
Fri Feb 23 13:25:08 2018 VERIFY EKU OK
Fri Feb 23 13:25:08 2018 VERIFY X509NAME OK: CN=server_xxx
Fri Feb 23 13:25:08 2018 VERIFY OK: depth=0, CN=server_xxx
Fri Feb 23 13:25:08 2018 Control Channel: TLSv1.2, cipher TLSv1/SSLv3 ECDHE-RSA-AES256-GCM-SHA384, 2048 bit RSA
Fri Feb 23 13:25:08 2018 [server_xxx] Peer Connection Initiated with [AF_INET]xxx:1194
Fri Feb 23 13:25:09 2018 MANAGEMENT: >STATE:1519388709,GET_CONFIG,,,,,,
Fri Feb 23 13:25:09 2018 SENT CONTROL [server_xxx]: 'PUSH_REQUEST' (status=1)
Fri Feb 23 13:25:09 2018 PUSH: Received control message: 'PUSH_REPLY,dhcp-option DNS 8.8.8.8,dhcp-option DNS 8.8.4.4,redirect-gateway def1,route-gateway 10.8.0.1,topology subnet,ping 10,ping-restart 120,ifconfig 10.8.0.5 255.255.255.0,peer-id 1,cipher AES-256-GCM'
Fri Feb 23 13:25:09 2018 OPTIONS IMPORT: timers and/or timeouts modified
Fri Feb 23 13:25:09 2018 OPTIONS IMPORT: --ifconfig/up options modified
Fri Feb 23 13:25:09 2018 OPTIONS IMPORT: route options modified
Fri Feb 23 13:25:09 2018 OPTIONS IMPORT: route-related options modified
Fri Feb 23 13:25:09 2018 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
Fri Feb 23 13:25:09 2018 OPTIONS IMPORT: peer-id set
Fri Feb 23 13:25:09 2018 OPTIONS IMPORT: adjusting link_mtu to 1625
Fri Feb 23 13:25:09 2018 OPTIONS IMPORT: data channel crypto options modified
Fri Feb 23 13:25:09 2018 Data Channel: using negotiated cipher 'AES-256-GCM'
Fri Feb 23 13:25:09 2018 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Fri Feb 23 13:25:09 2018 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Fri Feb 23 13:25:09 2018 interactive service msg_channel=728
Fri Feb 23 13:25:09 2018 ROUTE_GATEWAY 192.168.1.1/255.255.255.0 I=17 HWADDR=fc:45:96:42:a2:44
Fri Feb 23 13:25:09 2018 open_tun
Fri Feb 23 13:25:09 2018 TAP-WIN32 device [Ethernet 2] opened: \\.\Global\{50900E4A-CD55-4003-A96E-F384DC66BE30}.tap
Fri Feb 23 13:25:09 2018 TAP-Windows Driver Version 9.21
Fri Feb 23 13:25:09 2018 Set TAP-Windows TUN subnet mode network/local/netmask = 10.8.0.0/10.8.0.5/255.255.255.0 [SUCCEEDED]
Fri Feb 23 13:25:09 2018 Notified TAP-Windows driver to set a DHCP IP/netmask of 10.8.0.5/255.255.255.0 on interface {50900E4A-CD55-4003-A96E-F384DC66BE30} [DHCP-serv: 10.8.0.254, lease-time: 31536000]
Fri Feb 23 13:25:09 2018 Successful ARP Flush on interface [28] {50900E4A-CD55-4003-A96E-F384DC66BE30}
Fri Feb 23 13:25:09 2018 do_ifconfig, tt->did_ifconfig_ipv6_setup=0
Fri Feb 23 13:25:09 2018 MANAGEMENT: >STATE:1519388709,ASSIGN_IP,,10.8.0.5,,,,
Fri Feb 23 13:25:14 2018 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Fri Feb 23 13:25:14 2018 Route: Waiting for TUN/TAP interface to come up...
Fri Feb 23 13:25:19 2018 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Fri Feb 23 13:25:19 2018 Route: Waiting for TUN/TAP interface to come up...
Fri Feb 23 13:25:20 2018 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Fri Feb 23 13:25:20 2018 Route: Waiting for TUN/TAP interface to come up...
Fri Feb 23 13:25:21 2018 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Fri Feb 23 13:25:21 2018 Route: Waiting for TUN/TAP interface to come up...
Fri Feb 23 13:25:22 2018 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Fri Feb 23 13:25:22 2018 Route: Waiting for TUN/TAP interface to come up...
Fri Feb 23 13:25:23 2018 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Fri Feb 23 13:25:23 2018 Route: Waiting for TUN/TAP interface to come up...
Fri Feb 23 13:25:24 2018 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Fri Feb 23 13:25:24 2018 Route: Waiting for TUN/TAP interface to come up...
Fri Feb 23 13:25:25 2018 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Fri Feb 23 13:25:25 2018 Route: Waiting for TUN/TAP interface to come up...
Fri Feb 23 13:25:27 2018 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Fri Feb 23 13:25:27 2018 Route: Waiting for TUN/TAP interface to come up...
Fri Feb 23 13:25:28 2018 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Fri Feb 23 13:25:28 2018 Route: Waiting for TUN/TAP interface to come up...
Fri Feb 23 13:25:29 2018 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Fri Feb 23 13:25:29 2018 Route: Waiting for TUN/TAP interface to come up...
Fri Feb 23 13:25:30 2018 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Fri Feb 23 13:25:30 2018 Route: Waiting for TUN/TAP interface to come up...
Fri Feb 23 13:25:31 2018 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Fri Feb 23 13:25:31 2018 Route: Waiting for TUN/TAP interface to come up...
Fri Feb 23 13:25:32 2018 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Fri Feb 23 13:25:32 2018 Route: Waiting for TUN/TAP interface to come up...
Fri Feb 23 13:25:33 2018 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Fri Feb 23 13:25:33 2018 Route: Waiting for TUN/TAP interface to come up...
Fri Feb 23 13:25:35 2018 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Fri Feb 23 13:25:35 2018 Route: Waiting for TUN/TAP interface to come up...
Fri Feb 23 13:25:36 2018 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Fri Feb 23 13:25:36 2018 Route: Waiting for TUN/TAP interface to come up...
Fri Feb 23 13:25:37 2018 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Fri Feb 23 13:25:37 2018 Route: Waiting for TUN/TAP interface to come up...
Fri Feb 23 13:25:38 2018 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Fri Feb 23 13:25:38 2018 Route: Waiting for TUN/TAP interface to come up...
Fri Feb 23 13:25:39 2018 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Fri Feb 23 13:25:39 2018 Route: Waiting for TUN/TAP interface to come up...
Fri Feb 23 13:25:40 2018 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Fri Feb 23 13:25:40 2018 Route: Waiting for TUN/TAP interface to come up...
Fri Feb 23 13:25:42 2018 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Fri Feb 23 13:25:42 2018 Route: Waiting for TUN/TAP interface to come up...
Fri Feb 23 13:25:43 2018 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Fri Feb 23 13:25:43 2018 Route: Waiting for TUN/TAP interface to come up...
Fri Feb 23 13:25:44 2018 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Fri Feb 23 13:25:44 2018 C:\WINDOWS\system32\route.exe ADD xxxx MASK 255.255.255.255 192.168.1.1
Fri Feb 23 13:25:44 2018 Route addition via service succeeded
Fri Feb 23 13:25:44 2018 C:\WINDOWS\system32\route.exe ADD 0.0.0.0 MASK 128.0.0.0 10.8.0.1
Fri Feb 23 13:25:44 2018 Warning: route gateway is not reachable on any active network adapters: 10.8.0.1
Fri Feb 23 13:25:44 2018 Route addition via service failed
Fri Feb 23 13:25:44 2018 C:\WINDOWS\system32\route.exe ADD 128.0.0.0 MASK 128.0.0.0 10.8.0.1
Fri Feb 23 13:25:44 2018 Warning: route gateway is not reachable on any active network adapters: 10.8.0.1
Fri Feb 23 13:25:44 2018 Route addition via service failed
Fri Feb 23 13:25:44 2018 SYSTEM ROUTING TABLE
Fri Feb 23 13:25:44 2018 0.0.0.0 0.0.0.0 192.168.1.1 p=0 i=17 t=4 pr=3 a=949059 h=0 m=281/0/0/0/0
Fri Feb 23 13:25:44 2018 xxxx 255.255.255.255 192.168.1.1 p=0 i=17 t=4 pr=3 a=0 h=0 m=281/0/0/0/0
Fri Feb 23 13:25:44 2018 127.0.0.0 255.0.0.0 127.0.0.1 p=0 i=1 t=3 pr=2 a=1275385 h=0 m=331/0/0/0/0
Fri Feb 23 13:25:44 2018 127.0.0.1 255.255.255.255 127.0.0.1 p=0 i=1 t=3 pr=2 a=1275385 h=0 m=331/0/0/0/0
Fri Feb 23 13:25:44 2018 127.255.255.255 255.255.255.255 127.0.0.1 p=0 i=1 t=3 pr=2 a=1275385 h=0 m=331/0/0/0/0
Fri Feb 23 13:25:44 2018 169.254.0.0 255.255.0.0 169.254.210.137 p=0 i=17 t=3 pr=2 a=19090 h=0 m=281/0/0/0/0
Fri Feb 23 13:25:44 2018 169.254.210.137 255.255.255.255 169.254.210.137 p=0 i=17 t=3 pr=2 a=19090 h=0 m=281/0/0/0/0
Fri Feb 23 13:25:44 2018 169.254.255.255 255.255.255.255 169.254.210.137 p=0 i=17 t=3 pr=2 a=19090 h=0 m=281/0/0/0/0
Fri Feb 23 13:25:44 2018 192.168.1.0 255.255.255.0 169.254.210.137 p=0 i=17 t=3 pr=2 a=949055 h=0 m=281/0/0/0/0
Fri Feb 23 13:25:44 2018 192.168.1.149 255.255.255.255 169.254.210.137 p=0 i=17 t=3 pr=2 a=949055 h=0 m=281/0/0/0/0
Fri Feb 23 13:25:44 2018 192.168.1.255 255.255.255.255 169.254.210.137 p=0 i=17 t=3 pr=2 a=949055 h=0 m=281/0/0/0/0
Fri Feb 23 13:25:44 2018 192.168.211.0 255.255.255.0 192.168.211.1 p=0 i=2 t=3 pr=2 a=19102 h=0 m=291/0/0/0/0
Fri Feb 23 13:25:44 2018 192.168.211.1 255.255.255.255 192.168.211.1 p=0 i=2 t=3 pr=2 a=19102 h=0 m=291/0/0/0/0
Fri Feb 23 13:25:44 2018 192.168.211.255 255.255.255.255 192.168.211.1 p=0 i=2 t=3 pr=2 a=19102 h=0 m=291/0/0/0/0
Fri Feb 23 13:25:44 2018 192.168.238.0 255.255.255.0 192.168.238.1 p=0 i=14 t=3 pr=2 a=19101 h=0 m=291/0/0/0/0
Fri Feb 23 13:25:44 2018 192.168.238.1 255.255.255.255 192.168.238.1 p=0 i=14 t=3 pr=2 a=19101 h=0 m=291/0/0/0/0
Fri Feb 23 13:25:44 2018 192.168.238.255 255.255.255.255 192.168.238.1 p=0 i=14 t=3 pr=2 a=19101 h=0 m=291/0/0/0/0
Fri Feb 23 13:25:44 2018 224.0.0.0 240.0.0.0 127.0.0.1 p=0 i=1 t=3 pr=2 a=1275385 h=0 m=331/0/0/0/0
Fri Feb 23 13:25:44 2018 224.0.0.0 240.0.0.0 169.254.210.137 p=0 i=17 t=3 pr=2 a=967604 h=0 m=281/0/0/0/0
Fri Feb 23 13:25:44 2018 224.0.0.0 240.0.0.0 192.168.211.1 p=0 i=2 t=3 pr=2 a=19102 h=0 m=291/0/0/0/0
Fri Feb 23 13:25:44 2018 224.0.0.0 240.0.0.0 192.168.238.1 p=0 i=14 t=3 pr=2 a=19102 h=0 m=291/0/0/0/0
Fri Feb 23 13:25:44 2018 224.0.0.0 240.0.0.0 0.0.0.0 p=0 i=28 t=3 pr=2 a=19101 h=0 m=291/0/0/0/0
Fri Feb 23 13:25:44 2018 255.255.255.255 255.255.255.255 127.0.0.1 p=0 i=1 t=3 pr=2 a=1275385 h=0 m=331/0/0/0/0
Fri Feb 23 13:25:44 2018 255.255.255.255 255.255.255.255 169.254.210.137 p=0 i=17 t=3 pr=2 a=967604 h=0 m=281/0/0/0/0
Fri Feb 23 13:25:44 2018 255.255.255.255 255.255.255.255 192.168.211.1 p=0 i=2 t=3 pr=2 a=19102 h=0 m=291/0/0/0/0
Fri Feb 23 13:25:44 2018 255.255.255.255 255.255.255.255 192.168.238.1 p=0 i=14 t=3 pr=2 a=19102 h=0 m=291/0/0/0/0
Fri Feb 23 13:25:44 2018 255.255.255.255 255.255.255.255 0.0.0.0 p=0 i=28 t=3 pr=2 a=19101 h=0 m=291/0/0/0/0
Fri Feb 23 13:25:44 2018 SYSTEM ADAPTER LIST
Fri Feb 23 13:25:44 2018 Realtek PCIe GBE Family Controller
Fri Feb 23 13:25:44 2018 Index = 17
Fri Feb 23 13:25:44 2018 GUID = {F98957B4-837F-4BF7-8EB6-08A03BF6A12C}
Fri Feb 23 13:25:44 2018 IP = 169.254.210.137/255.255.0.0 192.168.1.149/255.255.255.0
Fri Feb 23 13:25:44 2018 MAC = fc:45:96:42:a2:44
Fri Feb 23 13:25:44 2018 GATEWAY = 192.168.1.1/255.255.255.255
Fri Feb 23 13:25:44 2018 DNS SERV = 80.58.61.250/255.255.255.255 80.58.61.254/255.255.255.255
Fri Feb 23 13:25:44 2018 Bluetooth Device (Personal Area Network)
Fri Feb 23 13:25:44 2018 Index = 16
Fri Feb 23 13:25:44 2018 GUID = {F00A84E2-15AE-4A8B-B746-EEA51B273597}
Fri Feb 23 13:25:44 2018 IP = 0.0.0.0/0.0.0.0
Fri Feb 23 13:25:44 2018 MAC = 94:e9:79:b3:bb:34
Fri Feb 23 13:25:44 2018 GATEWAY = 0.0.0.0/255.255.255.255
Fri Feb 23 13:25:44 2018 DHCP SERV =
Fri Feb 23 13:25:44 2018 DHCP LEASE OBTAINED = Fri Feb 23 13:25:44 2018
Fri Feb 23 13:25:44 2018 DHCP LEASE EXPIRES = Fri Feb 23 13:25:44 2018
Fri Feb 23 13:25:44 2018 DNS SERV =
Fri Feb 23 13:25:44 2018 VMware Virtual Ethernet Adapter for VMnet1
Fri Feb 23 13:25:44 2018 Index = 2
Fri Feb 23 13:25:44 2018 GUID = {14F25282-F4E1-4AE0-8F68-843282A8EDF9}
Fri Feb 23 13:25:44 2018 IP = 192.168.211.1/255.255.255.0
Fri Feb 23 13:25:44 2018 MAC = 00:50:56:c0:00:01
Fri Feb 23 13:25:44 2018 GATEWAY = 0.0.0.0/255.255.255.255
Fri Feb 23 13:25:44 2018 DHCP SERV = 192.168.211.254/255.255.255.255
Fri Feb 23 13:25:44 2018 DHCP LEASE OBTAINED = Fri Feb 23 13:22:22 2018
Fri Feb 23 13:25:44 2018 DHCP LEASE EXPIRES = Fri Feb 23 13:52:22 2018
Fri Feb 23 13:25:44 2018 DNS SERV =
Fri Feb 23 13:25:44 2018 VMware Virtual Ethernet Adapter for VMnet8
Fri Feb 23 13:25:44 2018 Index = 14
Fri Feb 23 13:25:44 2018 GUID = {E13E0C69-9D09-458A-8174-B25AAD98B8C2}
Fri Feb 23 13:25:44 2018 IP = 192.168.238.1/255.255.255.0
Fri Feb 23 13:25:44 2018 MAC = 00:50:56:c0:00:08
Fri Feb 23 13:25:44 2018 GATEWAY = 0.0.0.0/255.255.255.255
Fri Feb 23 13:25:44 2018 DHCP SERV = 192.168.238.254/255.255.255.255
Fri Feb 23 13:25:44 2018 DHCP LEASE OBTAINED = Fri Feb 23 13:22:22 2018
Fri Feb 23 13:25:44 2018 DHCP LEASE EXPIRES = Fri Feb 23 13:52:22 2018
Fri Feb 23 13:25:44 2018 PRI WINS = 192.168.238.2/255.255.255.255
Fri Feb 23 13:25:44 2018 SEC WINS =
Fri Feb 23 13:25:44 2018 DNS SERV =
Fri Feb 23 13:25:44 2018 TAP-Windows Adapter V9
Fri Feb 23 13:25:44 2018 Index = 28
Fri Feb 23 13:25:44 2018 GUID = {50900E4A-CD55-4003-A96E-F384DC66BE30}
Fri Feb 23 13:25:44 2018 IP = 0.0.0.0/0.0.0.0
Fri Feb 23 13:25:44 2018 MAC = 00:ff:50:90:0e:4a
Fri Feb 23 13:25:44 2018 GATEWAY = 0.0.0.0/255.255.255.255
Fri Feb 23 13:25:44 2018 DHCP SERV = 0.0.0.0/255.255.255.255
Fri Feb 23 13:25:44 2018 DHCP LEASE OBTAINED = Fri Feb 23 13:25:44 2018
Fri Feb 23 13:25:44 2018 DHCP LEASE EXPIRES = Fri Feb 23 13:25:44 2018
Fri Feb 23 13:25:44 2018 DNS SERV =
Fri Feb 23 13:25:44 2018 Initialization Sequence Completed With Errors ( see http://openvpn.net/faq.html#dhcpclientserv )
Fri Feb 23 13:25:44 2018 MANAGEMENT: >STATE:1519388744,CONNECTED,ERROR,10.8.0.5,xxxx,1194,,

Does anyone know what is going on? Because people told me that it wass the IP adress that it was in the DHCP range, but now I assigned it to 254, in order to be out of this range (before it was in the 130).

Thank you a lot for your help!

TinCanTech
OpenVPN Protagonist
Posts: 11137
Joined: Fri Jun 03, 2016 1:17 pm

Re: Problem connecting with my client

Post by TinCanTech » Fri Feb 23, 2018 3:01 pm

You must start the Windows DHCP Client Service.

bdescals
OpenVpn Newbie
Posts: 3
Joined: Fri Feb 23, 2018 12:55 pm

Re: Problem connecting with my client

Post by bdescals » Sat Feb 24, 2018 5:40 pm

Hi, excuse my ignorance, but, how can I do that? Thank you a lot!

TinCanTech
OpenVPN Protagonist
Posts: 11137
Joined: Fri Jun 03, 2016 1:17 pm

Re: Problem connecting with my client

Post by TinCanTech » Sat Feb 24, 2018 7:04 pm

google it .. :roll:

bdescals
OpenVpn Newbie
Posts: 3
Joined: Fri Feb 23, 2018 12:55 pm

Re: Problem connecting with my client

Post by bdescals » Mon Feb 26, 2018 8:20 am

Hello, I verified that the DHCP Client was running, and I stopped the firewall also, but now I have this message

[oconf=]
Mon Feb 26 09:16:30 2018 OpenVPN 2.4.4 x86_64-w64-mingw32 [SSL (OpenSSL)] [LZO] [LZ4] [PKCS11] [AEAD] built on Sep 26 2017
Mon Feb 26 09:16:30 2018 Windows version 6.2 (Windows 8 or greater) 64bit
Mon Feb 26 09:16:30 2018 library versions: OpenSSL 1.0.2l 25 May 2017, LZO 2.10
Mon Feb 26 09:16:30 2018 MANAGEMENT: TCP Socket listening on [AF_INET]127.0.0.1:25341
Mon Feb 26 09:16:30 2018 Need hold release from management interface, waiting...
Mon Feb 26 09:16:30 2018 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:25341
Mon Feb 26 09:16:30 2018 MANAGEMENT: CMD 'state on'
Mon Feb 26 09:16:30 2018 MANAGEMENT: CMD 'log all on'
Mon Feb 26 09:16:30 2018 MANAGEMENT: CMD 'echo all on'
Mon Feb 26 09:16:30 2018 MANAGEMENT: CMD 'hold off'
Mon Feb 26 09:16:30 2018 MANAGEMENT: CMD 'hold release'
Mon Feb 26 09:16:33 2018 MANAGEMENT: CMD 'password [...]'
Mon Feb 26 09:16:33 2018 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
Mon Feb 26 09:16:33 2018 Outgoing Control Channel Authentication: Using 256 bit message hash 'SHA256' for HMAC authentication
Mon Feb 26 09:16:33 2018 Incoming Control Channel Authentication: Using 256 bit message hash 'SHA256' for HMAC authentication
Mon Feb 26 09:16:33 2018 TCP/UDP: Preserving recently used remote address: [AF_INET]77.210.16.54:1194
Mon Feb 26 09:16:33 2018 Socket Buffers: R=[65536->65536] S=[65536->65536]
Mon Feb 26 09:16:33 2018 UDP link local: (not bound)
Mon Feb 26 09:16:33 2018 UDP link remote: [AF_INET]77.210.16.54:1194
Mon Feb 26 09:16:33 2018 MANAGEMENT: >STATE:1519632993,WAIT,,,,,,
Mon Feb 26 09:16:33 2018 MANAGEMENT: >STATE:1519632993,AUTH,,,,,,
Mon Feb 26 09:16:33 2018 TLS: Initial packet from [AF_INET]77.210.16.54:1194, sid=0f8b05a8 770cafa7
Mon Feb 26 09:16:33 2018 VERIFY OK: depth=1, CN=ChangeMe
Mon Feb 26 09:16:33 2018 VERIFY KU OK
Mon Feb 26 09:16:33 2018 Validating certificate extended key usage
Mon Feb 26 09:16:33 2018 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication
Mon Feb 26 09:16:33 2018 VERIFY EKU OK
Mon Feb 26 09:16:33 2018 VERIFY X509NAME OK: CN=server_agBu79dPlJtSJ4US
Mon Feb 26 09:16:33 2018 VERIFY OK: depth=0, CN=server_agBu79dPlJtSJ4US
Mon Feb 26 09:16:33 2018 Control Channel: TLSv1.2, cipher TLSv1/SSLv3 ECDHE-RSA-AES256-GCM-SHA384, 1024 bit RSA
Mon Feb 26 09:16:33 2018 [server_agBu79dPlJtSJ4US] Peer Connection Initiated with [AF_INET]77.210.16.54:1194
Mon Feb 26 09:16:34 2018 MANAGEMENT: >STATE:1519632994,GET_CONFIG,,,,,,
Mon Feb 26 09:16:34 2018 SENT CONTROL [server_agBu79dPlJtSJ4US]: 'PUSH_REQUEST' (status=1)
Mon Feb 26 09:16:35 2018 PUSH: Received control message: 'PUSH_REPLY,dhcp-option DNS 8.8.8.8,dhcp-option DNS 8.8.4.4,redirect-gateway def1,route-gateway 10.8.0.1,topology subnet,ping 10,ping-restart 120,ifconfig 10.8.0.2 255.255.255.0,peer-id 0,cipher AES-256-GCM'
Mon Feb 26 09:16:35 2018 OPTIONS IMPORT: timers and/or timeouts modified
Mon Feb 26 09:16:35 2018 OPTIONS IMPORT: --ifconfig/up options modified
Mon Feb 26 09:16:35 2018 OPTIONS IMPORT: route options modified
Mon Feb 26 09:16:35 2018 OPTIONS IMPORT: route-related options modified
Mon Feb 26 09:16:35 2018 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
Mon Feb 26 09:16:35 2018 OPTIONS IMPORT: peer-id set
Mon Feb 26 09:16:35 2018 OPTIONS IMPORT: adjusting link_mtu to 1625
Mon Feb 26 09:16:35 2018 OPTIONS IMPORT: data channel crypto options modified
Mon Feb 26 09:16:35 2018 Data Channel: using negotiated cipher 'AES-256-GCM'
Mon Feb 26 09:16:35 2018 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Mon Feb 26 09:16:35 2018 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Mon Feb 26 09:16:35 2018 interactive service msg_channel=0
Mon Feb 26 09:16:35 2018 ROUTE_GATEWAY 192.168.1.1/255.255.255.0 I=17 HWADDR=fc:45:96:42:a2:44
Mon Feb 26 09:16:35 2018 open_tun
Mon Feb 26 09:16:35 2018 TAP-WIN32 device [Ethernet 2] opened: \\.\Global\{50900E4A-CD55-4003-A96E-F384DC66BE30}.tap
Mon Feb 26 09:16:35 2018 TAP-Windows Driver Version 9.21
Mon Feb 26 09:16:35 2018 Set TAP-Windows TUN subnet mode network/local/netmask = 10.8.0.0/10.8.0.2/255.255.255.0 [SUCCEEDED]
Mon Feb 26 09:16:35 2018 Notified TAP-Windows driver to set a DHCP IP/netmask of 10.8.0.2/255.255.255.0 on interface {50900E4A-CD55-4003-A96E-F384DC66BE30} [DHCP-serv: 10.8.0.254, lease-time: 31536000]
Mon Feb 26 09:16:35 2018 Successful ARP Flush on interface [28] {50900E4A-CD55-4003-A96E-F384DC66BE30}
Mon Feb 26 09:16:35 2018 do_ifconfig, tt->did_ifconfig_ipv6_setup=0
Mon Feb 26 09:16:35 2018 MANAGEMENT: >STATE:1519632995,ASSIGN_IP,,10.8.0.2,,,,
Mon Feb 26 09:16:40 2018 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Mon Feb 26 09:16:40 2018 Route: Waiting for TUN/TAP interface to come up...
Mon Feb 26 09:16:45 2018 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Mon Feb 26 09:16:45 2018 Route: Waiting for TUN/TAP interface to come up...
Mon Feb 26 09:16:46 2018 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Mon Feb 26 09:16:46 2018 Route: Waiting for TUN/TAP interface to come up...
Mon Feb 26 09:16:47 2018 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Mon Feb 26 09:16:47 2018 Route: Waiting for TUN/TAP interface to come up...
Mon Feb 26 09:16:49 2018 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Mon Feb 26 09:16:49 2018 Route: Waiting for TUN/TAP interface to come up...
Mon Feb 26 09:16:50 2018 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Mon Feb 26 09:16:50 2018 Route: Waiting for TUN/TAP interface to come up...
Mon Feb 26 09:16:51 2018 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Mon Feb 26 09:16:51 2018 Route: Waiting for TUN/TAP interface to come up...
Mon Feb 26 09:16:52 2018 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Mon Feb 26 09:16:52 2018 Route: Waiting for TUN/TAP interface to come up...
Mon Feb 26 09:16:53 2018 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Mon Feb 26 09:16:53 2018 Route: Waiting for TUN/TAP interface to come up...
Mon Feb 26 09:16:54 2018 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Mon Feb 26 09:16:54 2018 Route: Waiting for TUN/TAP interface to come up...
Mon Feb 26 09:16:55 2018 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Mon Feb 26 09:16:55 2018 Route: Waiting for TUN/TAP interface to come up...
Mon Feb 26 09:16:56 2018 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Mon Feb 26 09:16:56 2018 Route: Waiting for TUN/TAP interface to come up...
Mon Feb 26 09:16:57 2018 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Mon Feb 26 09:16:57 2018 Route: Waiting for TUN/TAP interface to come up...
Mon Feb 26 09:16:58 2018 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Mon Feb 26 09:16:58 2018 Route: Waiting for TUN/TAP interface to come up...
Mon Feb 26 09:16:59 2018 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Mon Feb 26 09:16:59 2018 Route: Waiting for TUN/TAP interface to come up...
Mon Feb 26 09:17:00 2018 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Mon Feb 26 09:17:00 2018 Route: Waiting for TUN/TAP interface to come up...
Mon Feb 26 09:17:02 2018 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Mon Feb 26 09:17:02 2018 Route: Waiting for TUN/TAP interface to come up...
Mon Feb 26 09:17:03 2018 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Mon Feb 26 09:17:03 2018 Route: Waiting for TUN/TAP interface to come up...
Mon Feb 26 09:17:04 2018 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Mon Feb 26 09:17:04 2018 Route: Waiting for TUN/TAP interface to come up...
Mon Feb 26 09:17:05 2018 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Mon Feb 26 09:17:05 2018 Route: Waiting for TUN/TAP interface to come up...
Mon Feb 26 09:17:06 2018 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Mon Feb 26 09:17:06 2018 Route: Waiting for TUN/TAP interface to come up...
Mon Feb 26 09:17:07 2018 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Mon Feb 26 09:17:07 2018 Route: Waiting for TUN/TAP interface to come up...
Mon Feb 26 09:17:08 2018 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Mon Feb 26 09:17:08 2018 Route: Waiting for TUN/TAP interface to come up...
Mon Feb 26 09:17:09 2018 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Mon Feb 26 09:17:09 2018 Route: Waiting for TUN/TAP interface to come up...
Mon Feb 26 09:17:10 2018 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Mon Feb 26 09:17:10 2018 C:\WINDOWS\system32\route.exe ADD 77.210.16.54 MASK 255.255.255.255 192.168.1.1
Mon Feb 26 09:17:10 2018 ROUTE: CreateIpForwardEntry succeeded with dwForwardMetric1=25 and dwForwardType=4
Mon Feb 26 09:17:10 2018 Route addition via IPAPI succeeded [adaptive]
Mon Feb 26 09:17:10 2018 C:\WINDOWS\system32\route.exe ADD 0.0.0.0 MASK 128.0.0.0 10.8.0.1
Mon Feb 26 09:17:10 2018 Warning: route gateway is not reachable on any active network adapters: 10.8.0.1
Mon Feb 26 09:17:10 2018 Route addition via IPAPI failed [adaptive]
Mon Feb 26 09:17:10 2018 Route addition fallback to route.exe
Mon Feb 26 09:17:10 2018 env_block: add PATH=C:\WINDOWS\System32;C:\WINDOWS;C:\WINDOWS\System32\Wbem
Mon Feb 26 09:17:10 2018 C:\WINDOWS\system32\route.exe ADD 128.0.0.0 MASK 128.0.0.0 10.8.0.1
Mon Feb 26 09:17:10 2018 Warning: route gateway is not reachable on any active network adapters: 10.8.0.1
Mon Feb 26 09:17:10 2018 Route addition via IPAPI failed [adaptive]
Mon Feb 26 09:17:10 2018 Route addition fallback to route.exe
Mon Feb 26 09:17:10 2018 env_block: add PATH=C:\WINDOWS\System32;C:\WINDOWS;C:\WINDOWS\System32\Wbem
Mon Feb 26 09:17:10 2018 SYSTEM ROUTING TABLE
Mon Feb 26 09:17:10 2018 0.0.0.0 0.0.0.0 192.168.1.1 p=0 i=17 t=4 pr=3 a=1193345 h=0 m=281/0/0/0/0
Mon Feb 26 09:17:10 2018 0.0.0.0 128.0.0.0 10.8.0.1 p=0 i=17 t=4 pr=3 a=0 h=0 m=26/0/0/0/0
Mon Feb 26 09:17:10 2018 77.210.16.54 255.255.255.255 192.168.1.1 p=0 i=17 t=4 pr=3 a=0 h=0 m=25/0/0/0/0
Mon Feb 26 09:17:10 2018 127.0.0.0 255.0.0.0 127.0.0.1 p=0 i=1 t=3 pr=2 a=1519671 h=0 m=331/0/0/0/0
Mon Feb 26 09:17:10 2018 127.0.0.1 255.255.255.255 127.0.0.1 p=0 i=1 t=3 pr=2 a=1519671 h=0 m=331/0/0/0/0
Mon Feb 26 09:17:10 2018 127.255.255.255 255.255.255.255 127.0.0.1 p=0 i=1 t=3 pr=2 a=1519671 h=0 m=331/0/0/0/0
Mon Feb 26 09:17:10 2018 128.0.0.0 128.0.0.0 10.8.0.1 p=0 i=17 t=4 pr=3 a=0 h=0 m=26/0/0/0/0
Mon Feb 26 09:17:10 2018 169.254.0.0 255.255.0.0 169.254.210.137 p=0 i=17 t=3 pr=2 a=4146 h=0 m=281/0/0/0/0
Mon Feb 26 09:17:10 2018 169.254.210.137 255.255.255.255 169.254.210.137 p=0 i=17 t=3 pr=2 a=4146 h=0 m=281/0/0/0/0
Mon Feb 26 09:17:10 2018 169.254.255.255 255.255.255.255 169.254.210.137 p=0 i=17 t=3 pr=2 a=4146 h=0 m=281/0/0/0/0
Mon Feb 26 09:17:10 2018 192.168.1.0 255.255.255.0 169.254.210.137 p=0 i=17 t=3 pr=2 a=1193341 h=0 m=281/0/0/0/0
Mon Feb 26 09:17:10 2018 192.168.1.149 255.255.255.255 169.254.210.137 p=0 i=17 t=3 pr=2 a=1193341 h=0 m=281/0/0/0/0
Mon Feb 26 09:17:10 2018 192.168.1.255 255.255.255.255 169.254.210.137 p=0 i=17 t=3 pr=2 a=1193341 h=0 m=281/0/0/0/0
Mon Feb 26 09:17:10 2018 192.168.211.0 255.255.255.0 192.168.211.1 p=0 i=2 t=3 pr=2 a=4156 h=0 m=291/0/0/0/0
Mon Feb 26 09:17:10 2018 192.168.211.1 255.255.255.255 192.168.211.1 p=0 i=2 t=3 pr=2 a=4156 h=0 m=291/0/0/0/0
Mon Feb 26 09:17:10 2018 192.168.211.255 255.255.255.255 192.168.211.1 p=0 i=2 t=3 pr=2 a=4156 h=0 m=291/0/0/0/0
Mon Feb 26 09:17:10 2018 192.168.238.0 255.255.255.0 192.168.238.1 p=0 i=14 t=3 pr=2 a=4157 h=0 m=291/0/0/0/0
Mon Feb 26 09:17:10 2018 192.168.238.1 255.255.255.255 192.168.238.1 p=0 i=14 t=3 pr=2 a=4157 h=0 m=291/0/0/0/0
Mon Feb 26 09:17:10 2018 192.168.238.255 255.255.255.255 192.168.238.1 p=0 i=14 t=3 pr=2 a=4157 h=0 m=291/0/0/0/0
Mon Feb 26 09:17:10 2018 224.0.0.0 240.0.0.0 127.0.0.1 p=0 i=1 t=3 pr=2 a=1519671 h=0 m=331/0/0/0/0
Mon Feb 26 09:17:10 2018 224.0.0.0 240.0.0.0 169.254.210.137 p=0 i=17 t=3 pr=2 a=1211890 h=0 m=281/0/0/0/0
Mon Feb 26 09:17:10 2018 224.0.0.0 240.0.0.0 192.168.238.1 p=0 i=14 t=3 pr=2 a=4157 h=0 m=291/0/0/0/0
Mon Feb 26 09:17:10 2018 224.0.0.0 240.0.0.0 192.168.211.1 p=0 i=2 t=3 pr=2 a=4157 h=0 m=291/0/0/0/0
Mon Feb 26 09:17:10 2018 224.0.0.0 240.0.0.0 0.0.0.0 p=0 i=28 t=3 pr=2 a=4157 h=0 m=291/0/0/0/0
Mon Feb 26 09:17:10 2018 255.255.255.255 255.255.255.255 127.0.0.1 p=0 i=1 t=3 pr=2 a=1519671 h=0 m=331/0/0/0/0
Mon Feb 26 09:17:10 2018 255.255.255.255 255.255.255.255 169.254.210.137 p=0 i=17 t=3 pr=2 a=1211890 h=0 m=281/0/0/0/0
Mon Feb 26 09:17:10 2018 255.255.255.255 255.255.255.255 192.168.238.1 p=0 i=14 t=3 pr=2 a=4157 h=0 m=291/0/0/0/0
Mon Feb 26 09:17:10 2018 255.255.255.255 255.255.255.255 192.168.211.1 p=0 i=2 t=3 pr=2 a=4157 h=0 m=291/0/0/0/0
Mon Feb 26 09:17:10 2018 255.255.255.255 255.255.255.255 0.0.0.0 p=0 i=28 t=3 pr=2 a=4157 h=0 m=291/0/0/0/0
Mon Feb 26 09:17:10 2018 SYSTEM ADAPTER LIST
Mon Feb 26 09:17:10 2018 Realtek PCIe GBE Family Controller
Mon Feb 26 09:17:10 2018 Index = 17
Mon Feb 26 09:17:10 2018 GUID = {F98957B4-837F-4BF7-8EB6-08A03BF6A12C}
Mon Feb 26 09:17:10 2018 IP = 169.254.210.137/255.255.0.0 192.168.1.149/255.255.255.0
Mon Feb 26 09:17:10 2018 MAC = fc:45:96:42:a2:44
Mon Feb 26 09:17:10 2018 GATEWAY = 192.168.1.1/255.255.255.255
Mon Feb 26 09:17:10 2018 DNS SERV = 80.58.61.250/255.255.255.255 80.58.61.254/255.255.255.255
Mon Feb 26 09:17:10 2018 Bluetooth Device (Personal Area Network)
Mon Feb 26 09:17:10 2018 Index = 16
Mon Feb 26 09:17:10 2018 GUID = {F00A84E2-15AE-4A8B-B746-EEA51B273597}
Mon Feb 26 09:17:10 2018 IP = 0.0.0.0/0.0.0.0
Mon Feb 26 09:17:10 2018 MAC = 94:e9:79:b3:bb:34
Mon Feb 26 09:17:10 2018 GATEWAY = 0.0.0.0/255.255.255.255
Mon Feb 26 09:17:10 2018 DHCP SERV =
Mon Feb 26 09:17:10 2018 DHCP LEASE OBTAINED = Mon Feb 26 09:17:10 2018
Mon Feb 26 09:17:10 2018 DHCP LEASE EXPIRES = Mon Feb 26 09:17:10 2018
Mon Feb 26 09:17:10 2018 DNS SERV =
Mon Feb 26 09:17:10 2018 VMware Virtual Ethernet Adapter for VMnet1
Mon Feb 26 09:17:10 2018 Index = 2
Mon Feb 26 09:17:10 2018 GUID = {14F25282-F4E1-4AE0-8F68-843282A8EDF9}
Mon Feb 26 09:17:10 2018 IP = 192.168.211.1/255.255.255.0
Mon Feb 26 09:17:10 2018 MAC = 00:50:56:c0:00:01
Mon Feb 26 09:17:10 2018 GATEWAY = 0.0.0.0/255.255.255.255
Mon Feb 26 09:17:10 2018 DHCP SERV = 192.168.211.254/255.255.255.255
Mon Feb 26 09:17:10 2018 DHCP LEASE OBTAINED = Mon Feb 26 09:07:54 2018
Mon Feb 26 09:17:10 2018 DHCP LEASE EXPIRES = Mon Feb 26 09:37:54 2018
Mon Feb 26 09:17:10 2018 DNS SERV =
Mon Feb 26 09:17:10 2018 VMware Virtual Ethernet Adapter for VMnet8
Mon Feb 26 09:17:10 2018 Index = 14
Mon Feb 26 09:17:10 2018 GUID = {E13E0C69-9D09-458A-8174-B25AAD98B8C2}
Mon Feb 26 09:17:10 2018 IP = 192.168.238.1/255.255.255.0
Mon Feb 26 09:17:10 2018 MAC = 00:50:56:c0:00:08
Mon Feb 26 09:17:10 2018 GATEWAY = 0.0.0.0/255.255.255.255
Mon Feb 26 09:17:10 2018 DHCP SERV = 192.168.238.254/255.255.255.255
Mon Feb 26 09:17:10 2018 DHCP LEASE OBTAINED = Mon Feb 26 09:07:53 2018
Mon Feb 26 09:17:10 2018 DHCP LEASE EXPIRES = Mon Feb 26 09:37:53 2018
Mon Feb 26 09:17:10 2018 PRI WINS = 192.168.238.2/255.255.255.255
Mon Feb 26 09:17:10 2018 SEC WINS =
Mon Feb 26 09:17:10 2018 DNS SERV =
Mon Feb 26 09:17:10 2018 TAP-Windows Adapter V9
Mon Feb 26 09:17:10 2018 Index = 28
Mon Feb 26 09:17:10 2018 GUID = {50900E4A-CD55-4003-A96E-F384DC66BE30}
Mon Feb 26 09:17:10 2018 IP = 0.0.0.0/0.0.0.0
Mon Feb 26 09:17:10 2018 MAC = 00:ff:50:90:0e:4a
Mon Feb 26 09:17:10 2018 GATEWAY = 0.0.0.0/255.255.255.255
Mon Feb 26 09:17:10 2018 DHCP SERV = 0.0.0.0/255.255.255.255
Mon Feb 26 09:17:10 2018 DHCP LEASE OBTAINED = Mon Feb 26 09:17:10 2018
Mon Feb 26 09:17:10 2018 DHCP LEASE EXPIRES = Mon Feb 26 09:17:10 2018
Mon Feb 26 09:17:10 2018 DNS SERV =
Mon Feb 26 09:17:10 2018 Initialization Sequence Completed With Errors ( see http://openvpn.net/faq.html#dhcpclientserv )
Mon Feb 26 09:17:10 2018 MANAGEMENT: >STATE:1519633030,CONNECTED,ERROR,10.8.0.2,77.210.16.54,1194,,[/oconf]

Could you please help me? Because I don't know what else to do. Thank you a lot

TinCanTech
OpenVPN Protagonist
Posts: 11137
Joined: Fri Jun 03, 2016 1:17 pm

Re: Problem connecting with my client

Post by TinCanTech » Mon Feb 26, 2018 12:28 pm

Please post your server config and log.

Post Reply