vpn connection error

Post Reply
pinniger
Posts: 4
Joined: Mon Jun 28, 2010 11:21 am

vpn connection error

Postby pinniger » Mon Jun 28, 2010 11:24 am

When I check the vpn form the control panel when i log into amahi.org, its says the vpn is working. but when I try to connect from my computer at work it says I get an ip address, but i dont have access to anything on my network.

windows xp pro
hdaconnect client

here is the log from hda connect. Any ideas?

Code: Select all

Mon Jun 28 12:57:48 2010 OpenVPN 2.0.9 Win32-MinGW [SSL] [LZO] built on Oct 1 2006 Mon Jun 28 12:57:48 2010 IMPORTANT: OpenVPN's default port number is now 1194, based on an official port number assignment by IANA. OpenVPN 2.0-beta16 and earlier used 5000 as the default port. Mon Jun 28 12:57:48 2010 WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info. Mon Jun 28 12:57:48 2010 LZO compression initialized Mon Jun 28 12:57:48 2010 Control Channel MTU parms [ L:1542 D:138 EF:38 EB:0 ET:0 EL:0 ] Mon Jun 28 12:57:48 2010 Data Channel MTU parms [ L:1542 D:1450 EF:42 EB:135 ET:0 EL:0 AF:3/1 ] Mon Jun 28 12:57:48 2010 Local Options hash (VER=V4): '41690919' Mon Jun 28 12:57:48 2010 Expected Remote Options hash (VER=V4): '530fdded' Mon Jun 28 12:57:48 2010 UDPv4 link local: [undef] Mon Jun 28 12:57:48 2010 UDPv4 link remote: 69.23.90.214:1194 Mon Jun 28 12:57:48 2010 TLS: Initial packet from 69.23.90.214:1194, sid=2efa72ff d402fc9e Mon Jun 28 12:57:48 2010 VERIFY OK: depth=1, /C=US/ST=CA/L=SanJose/O=HomeHDA/OU=VPN/CN=yourhda.com/emailAddress=info@homehda.com Mon Jun 28 12:57:48 2010 VERIFY OK: depth=0, /C=US/ST=CA/L=SanJose/O=HomeHDA/OU=VPN/CN=server/emailAddress=info@homehda.com Mon Jun 28 12:57:48 2010 Data Channel Encrypt: Cipher 'BF-CBC' initialized with 128 bit key Mon Jun 28 12:57:48 2010 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication Mon Jun 28 12:57:48 2010 Data Channel Decrypt: Cipher 'BF-CBC' initialized with 128 bit key Mon Jun 28 12:57:48 2010 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication Mon Jun 28 12:57:48 2010 Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 1024 bit RSA Mon Jun 28 12:57:48 2010 [server] Peer Connection Initiated with 69.23.90.214:1194 Mon Jun 28 12:57:50 2010 SENT CONTROL [server]: 'PUSH_REQUEST' (status=1) Mon Jun 28 12:57:50 2010 PUSH: Received control message: 'PUSH_REPLY,route 192.168.1.0 255.255.255.0,dhcp-option DNS 192.168.1.10,dhcp-option DOMAIN home.com,route 10.8.0.1,topology net30,ping 10,ping-restart 220,ifconfig 10.8.0.6 10.8.0.5' Mon Jun 28 12:57:50 2010 Options error: Unrecognized option or missing parameter(s) in [PUSH-OPTIONS]:5: topology (2.0.9) Mon Jun 28 12:57:50 2010 OPTIONS IMPORT: timers and/or timeouts modified Mon Jun 28 12:57:50 2010 OPTIONS IMPORT: --ifconfig/up options modified Mon Jun 28 12:57:50 2010 OPTIONS IMPORT: route options modified Mon Jun 28 12:57:50 2010 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified Mon Jun 28 12:57:50 2010 TAP-WIN32 device [Local Area Connection 2] opened: \\.\Global\{8DCDD143-F1BE-47ED-9BED-82630A660336}.tap Mon Jun 28 12:57:50 2010 TAP-Win32 Driver Version 8.4 Mon Jun 28 12:57:50 2010 TAP-Win32 MTU=1500 Mon Jun 28 12:57:50 2010 Notified TAP-Win32 driver to set a DHCP IP/netmask of 10.8.0.6/255.255.255.252 on interface {8DCDD143-F1BE-47ED-9BED-82630A660336} [DHCP-serv: 10.8.0.5, lease-time: 31536000] Mon Jun 28 12:57:50 2010 NOTE: could not get adapter index for \DEVICE\TCPIP_{8DCDD143-F1BE-47ED-9BED-82630A660336}, status=55 : The specified network resource or device is no longer available. Mon Jun 28 12:57:52 2010 TEST ROUTES: 0/2 succeeded len=2 ret=0 a=0 u/d=up Mon Jun 28 12:57:52 2010 Route: Waiting for TUN/TAP interface to come up... Mon Jun 28 12:57:54 2010 TEST ROUTES: 0/2 succeeded len=2 ret=0 a=0 u/d=up Mon Jun 28 12:57:54 2010 Route: Waiting for TUN/TAP interface to come up... Mon Jun 28 12:57:55 2010 TEST ROUTES: 0/2 succeeded len=2 ret=0 a=0 u/d=up Mon Jun 28 12:57:55 2010 Route: Waiting for TUN/TAP interface to come up... Mon Jun 28 12:57:57 2010 TEST ROUTES: 0/2 succeeded len=2 ret=0 a=0 u/d=up Mon Jun 28 12:57:57 2010 Route: Waiting for TUN/TAP interface to come up... Mon Jun 28 12:57:58 2010 TEST ROUTES: 0/2 succeeded len=2 ret=0 a=0 u/d=up Mon Jun 28 12:57:58 2010 Route: Waiting for TUN/TAP interface to come up... Mon Jun 28 12:57:59 2010 TEST ROUTES: 0/2 succeeded len=2 ret=0 a=0 u/d=up Mon Jun 28 12:57:59 2010 Route: Waiting for TUN/TAP interface to come up... Mon Jun 28 12:58:00 2010 TEST ROUTES: 0/2 succeeded len=2 ret=0 a=0 u/d=up Mon Jun 28 12:58:00 2010 Route: Waiting for TUN/TAP interface to come up... Mon Jun 28 12:58:01 2010 TEST ROUTES: 0/2 succeeded len=2 ret=0 a=0 u/d=up Mon Jun 28 12:58:01 2010 Route: Waiting for TUN/TAP interface to come up... Mon Jun 28 12:58:02 2010 TEST ROUTES: 0/2 succeeded len=2 ret=0 a=0 u/d=up Mon Jun 28 12:58:02 2010 Route: Waiting for TUN/TAP interface to come up... Mon Jun 28 12:58:03 2010 TEST ROUTES: 0/2 succeeded len=2 ret=0 a=0 u/d=up Mon Jun 28 12:58:03 2010 Route: Waiting for TUN/TAP interface to come up... Mon Jun 28 12:58:04 2010 TEST ROUTES: 0/2 succeeded len=2 ret=0 a=0 u/d=up Mon Jun 28 12:58:04 2010 Route: Waiting for TUN/TAP interface to come up... Mon Jun 28 12:58:05 2010 TEST ROUTES: 0/2 succeeded len=2 ret=0 a=0 u/d=up Mon Jun 28 12:58:05 2010 Route: Waiting for TUN/TAP interface to come up... Mon Jun 28 12:58:06 2010 TEST ROUTES: 0/2 succeeded len=2 ret=0 a=0 u/d=up Mon Jun 28 12:58:06 2010 Route: Waiting for TUN/TAP interface to come up... Mon Jun 28 12:58:07 2010 TEST ROUTES: 0/2 succeeded len=2 ret=0 a=0 u/d=up Mon Jun 28 12:58:07 2010 Route: Waiting for TUN/TAP interface to come up... Mon Jun 28 12:58:08 2010 TEST ROUTES: 0/2 succeeded len=2 ret=0 a=0 u/d=up Mon Jun 28 12:58:08 2010 Route: Waiting for TUN/TAP interface to come up... Mon Jun 28 12:58:09 2010 TEST ROUTES: 0/2 succeeded len=2 ret=0 a=0 u/d=up Mon Jun 28 12:58:09 2010 Route: Waiting for TUN/TAP interface to come up... Mon Jun 28 12:58:10 2010 TEST ROUTES: 0/2 succeeded len=2 ret=0 a=0 u/d=up Mon Jun 28 12:58:10 2010 Route: Waiting for TUN/TAP interface to come up... Mon Jun 28 12:58:11 2010 TEST ROUTES: 0/2 succeeded len=2 ret=0 a=0 u/d=up Mon Jun 28 12:58:11 2010 Route: Waiting for TUN/TAP interface to come up... Mon Jun 28 12:58:12 2010 TEST ROUTES: 0/2 succeeded len=2 ret=0 a=0 u/d=up Mon Jun 28 12:58:12 2010 Route: Waiting for TUN/TAP interface to come up... Mon Jun 28 12:58:13 2010 TEST ROUTES: 0/2 succeeded len=2 ret=0 a=0 u/d=up Mon Jun 28 12:58:13 2010 Route: Waiting for TUN/TAP interface to come up... Mon Jun 28 12:58:14 2010 TEST ROUTES: 0/2 succeeded len=2 ret=0 a=0 u/d=up Mon Jun 28 12:58:14 2010 Route: Waiting for TUN/TAP interface to come up... Mon Jun 28 12:58:16 2010 TEST ROUTES: 0/2 succeeded len=2 ret=0 a=0 u/d=up Mon Jun 28 12:58:16 2010 Route: Waiting for TUN/TAP interface to come up... Mon Jun 28 12:58:17 2010 TEST ROUTES: 0/2 succeeded len=2 ret=0 a=0 u/d=up Mon Jun 28 12:58:17 2010 Route: Waiting for TUN/TAP interface to come up... Mon Jun 28 12:58:18 2010 TEST ROUTES: 0/2 succeeded len=2 ret=0 a=0 u/d=up Mon Jun 28 12:58:18 2010 Route: Waiting for TUN/TAP interface to come up... Mon Jun 28 12:58:19 2010 TEST ROUTES: 0/2 succeeded len=2 ret=0 a=0 u/d=up Mon Jun 28 12:58:19 2010 Route: Waiting for TUN/TAP interface to come up... Mon Jun 28 12:58:20 2010 TEST ROUTES: 0/2 succeeded len=2 ret=0 a=0 u/d=up Mon Jun 28 12:58:20 2010 Route: Waiting for TUN/TAP interface to come up... Mon Jun 28 12:58:21 2010 TEST ROUTES: 0/2 succeeded len=2 ret=0 a=0 u/d=up Mon Jun 28 12:58:21 2010 Route: Waiting for TUN/TAP interface to come up... Mon Jun 28 12:58:22 2010 TEST ROUTES: 0/2 succeeded len=2 ret=0 a=0 u/d=up Mon Jun 28 12:58:22 2010 route ADD 192.168.1.0 MASK 255.255.255.0 10.8.0.5 The route addition failed: Either the interface index is wrong or the gateway does not lie on the same network as the interface. Check the IP Address Table for the machine. Mon Jun 28 12:58:22 2010 route ADD 10.8.0.1 MASK 255.255.255.255 10.8.0.5 The route addition failed: Either the interface index is wrong or the gateway does not lie on the same network as the interface. Check the IP Address Table for the machine. Mon Jun 28 12:58:22 2010 Initialization Sequence Completed With Errors ( see http://openvpn.net/faq.html#dhcpclientserv )
Top
User avatar
cale250
Posts: 33
Joined: Wed May 19, 2010 6:56 pm
Location: US of A
Contact:
Contact cale250

Re: vpn connection error

Postby cale250 » Mon Jun 28, 2010 3:37 pm

A couple things don't work with most VPNs:
- If you're trying to access the VPN when you're already inside of your network, it won't work. It's only designed to work from the outside.
- If you are running on a network with the same IP range (run cmd and then type ipconfig), it won't work either. Try another network or wifi hotspot.

Hope that helps. ;)
Top
Post Reply

Return to “VPN”

Who is online

Users browsing this forum: No registered users and 21 guests