Connecting to client has failed.

This forum is for admins who are looking to build or expand their OpenVPN setup.

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
rafff
OpenVpn Newbie
Posts: 1
Joined: Fri Feb 18, 2011 9:44 am

Connecting to client has failed.

Post by rafff » Fri Feb 18, 2011 10:28 am

I start OpenVPN server and I finally get:
Fri Feb 18 11:16:11 2011 IFCONFIG POOL: base=10.8.0.2 size=253
Fri Feb 18 11:16:11 2011 IFCONFIG POOL LIST
Fri Feb 18 11:16:11 2011 client1,10.8.0.2
Fri Feb 18 11:16:11 2011 Initialization Sequence Completed


Then I start OpenVPN client and i get allert window:
"Connecting to client has failed."


OpenVPN server log (Vista):
[...]
Fri Feb 18 11:17:19 2011 192.168.1.1:60248 [client1] Peer Connection Initiated with 192.168.1.1:60248
Fri Feb 18 11:17:21 2011 client1/192.168.1.1:60248 PUSH: Received control message: 'PUSH_REQUEST'
Fri Feb 18 11:17:21 2011 client1/192.168.1.1:60248 SENT CONTROL [client1]: 'PUSH_REPLY,route-gateway 10.8.0.1,ping 10,ping-restart 120,ifconfig 10.8.0.2 255.255.255.0' (status=1)
Fri Feb 18 11:17:23 2011 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)

OpenVPN client log (Win7):
Fri Feb 18 11:17:22 2011 SENT CONTROL [server]: 'PUSH_REQUEST' (status=1)
Fri Feb 18 11:17:22 2011 PUSH: Received control message: 'PUSH_REPLY,route-gateway 10.8.0.1,ping 10,ping-restart 120,ifconfig 10.8.0.2 255.255.255.0'
Fri Feb 18 11:17:22 2011 OPTIONS IMPORT: timers and/or timeouts modified
Fri Feb 18 11:17:22 2011 OPTIONS IMPORT: --ifconfig/up options modified
Fri Feb 18 11:17:22 2011 OPTIONS IMPORT: route-related options modified
Fri Feb 18 11:17:22 2011 WARNING: Since you are using --dev tun with a point-to-point topology, the second argument to --ifconfig must be an IP address. You are using something (255.255.255.0) that looks more like a netmask. (silence this warning with --ifconfig-nowarn)
Fri Feb 18 11:17:22 2011 There is a problem in your selection of --ifconfig endpoints [local=10.8.0.2, remote=255.255.255.0]. The local and remote VPN endpoints must exist within the same 255.255.255.252 subnet. This is a limitation of --dev tun when used with the TAP-WIN32 driver. Try 'openvpn --show-valid-subnets' option for more info.
Fri Feb 18 11:17:22 2011 Exiting


It has to be added that I have no problems with connection between server and the other OpenVPN client installed on WinXP. :-)

I tried to turn off firewalls on both computers, but it changed nothing.

Any suggestions?

User avatar
janjust
Forum Team
Posts: 2703
Joined: Fri Aug 20, 2010 2:57 pm
Location: Amsterdam
Contact:

Re: Connecting to client has failed.

Post by janjust » Fri Feb 18, 2011 10:31 am

WARNING: Since you are using --dev tun with a point-to-point topology, the second argument to --ifconfig must be an IP address. You are using something (255.255.255.0) that looks more like a netmask. (silence this warning with --ifconfig-nowarn)
this warning says it pretty much: something seems wrong with your client config file; compare the client config file to the working one on XP. Posting your server and client config files will also help :mrgreen:

Post Reply