Welcome, Guest. Please login or register.
Did you miss your activation email?
Sunday 15 December 2024, 06:53:49 pm

Login with username, password and session length

Download the latest community FREE version  HERE
14261 Posts in 4377 Topics by 6517 Members
Latest Member: Sandro
Search:     Advanced search
+  EFW Support
|-+  Support
| |-+  VPN Support
| | |-+  OPENVPN on Endian Community not Connecting
0 Members and 3 Guests are viewing this topic. « previous next »
Pages: [1] Go Down Print
Author Topic: OPENVPN on Endian Community not Connecting  (Read 16192 times)
arainguy
Jr. Member
*
Offline Offline

Posts: 2


« on: Sunday 29 April 2012, 01:22:13 am »

Upgraded my Endian from 2.2 to 2.5 and now can not Connect the VPN. Get the below message in Openvpn Client while connecting

Sat Apr 28 19:15:49 2012 OpenVPN 2.1.1 i686-pc-mingw32 [SSL] [LZO2] [PKCS11] built on Dec 11 2009
Sat Apr 28 19:15:54 2012 WARNING: No server certificate verification method has been enabled. .
Sat Apr 28 19:15:54 2012 NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Sat Apr 28 19:15:54 2012 LZO compression initialized
Sat Apr 28 19:15:54 2012 UDPv4 link local: [undef]
Sat Apr 28 19:15:54 2012 UDPv4 link remote: 86.98.69.11:1194
Sat Apr 28 19:16:55 2012 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
Sat Apr 28 19:16:55 2012 TLS Error: TLS handshake failed
Sat Apr 28 19:16:55 2012 SIGUSR1[soft,tls-error] received, process restarting
Sat Apr 28 19:16:57 2012 WARNING: No server certificate verification method has been enabled.
Logged
kashifmax
Sr. Member
****
Offline Offline

Gender: Female
Posts: 108


« Reply #1 on: Tuesday 01 May 2012, 10:28:56 pm »

I think TLS (tls-auth) or something else is missing on client configuration file...
Logged
arainguy
Jr. Member
*
Offline Offline

Posts: 2


« Reply #2 on: Wednesday 02 May 2012, 07:38:45 am »

I think TLS (tls-auth) or something else is missing on client configuration file...


I hired a IT guy and he solved the Issue.

The problem was with the IP address that the router DHCP gave.
Logged
Pages: [1] Go Up Print 
« previous next »
Jump to:  

Page created in 0.063 seconds with 18 queries.
Powered by SMF 1.1 RC2 | SMF © 2001-2005, Lewis Media Design by 7dana.com