Connected, but can't access HDA

[jtupnsmoke]

I have successfully connected to my HDA using HDACONNECT3 on my windows machine. The network i am on is different from my HDA's network so that shouldn't be the problem. When I ping my hda, i get a time out. Below is the log from hdaconnect saying it connected successfully. Anyone have any suggestions?

Mon Oct 11 11:02:06 2010 OpenVPN 2.1_rc15 i686-pc-mingw32 [SSL] [LZO2] [PKCS11] built on Nov 19 2008
Mon Oct 11 11:02:06 2010 WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info.
Mon Oct 11 11:02:06 2010 NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Mon Oct 11 11:02:06 2010 LZO compression initialized
Mon Oct 11 11:02:06 2010 Control Channel MTU parms [ L:1542 D:138 EF:38 EB:0 ET:0 EL:0 ]
Mon Oct 11 11:02:06 2010 Data Channel MTU parms [ L:1542 D:1450 EF:42 EB:135 ET:0 EL:0 AF:3/1 ]
Mon Oct 11 11:02:06 2010 Local Options hash (VER=V4): '41690919'
Mon Oct 11 11:02:06 2010 Expected Remote Options hash (VER=V4): '530fdded'
Mon Oct 11 11:02:06 2010 Socket Buffers: R=[8192->8192] S=[8192->8192]
Mon Oct 11 11:02:06 2010 UDPv4 link local: [undef]
Mon Oct 11 11:02:06 2010 UDPv4 link remote: 174.49.37.190:1194
Mon Oct 11 11:02:07 2010 TLS: Initial packet from 174.49.37.190:1194, sid=f043ee43 6dfe33eb
Mon Oct 11 11:02:07 2010 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
Mon Oct 11 11:02:07 2010 VERIFY OK: depth=1, /C=US/ST=CA/L=SanJose/O=HomeHDA/OU=VPN/CN=yourhda.com/emailAddress=info@homehda.com
Mon Oct 11 11:02:07 2010 VERIFY OK: depth=0, /C=US/ST=CA/L=SanJose/O=HomeHDA/OU=VPN/CN=server/emailAddress=info@homehda.com
Mon Oct 11 11:02:08 2010 Data Channel Encrypt: Cipher 'BF-CBC' initialized with 128 bit key
Mon Oct 11 11:02:08 2010 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Mon Oct 11 11:02:08 2010 Data Channel Decrypt: Cipher 'BF-CBC' initialized with 128 bit key
Mon Oct 11 11:02:08 2010 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Mon Oct 11 11:02:08 2010 Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 1024 bit RSA
Mon Oct 11 11:02:08 2010 [server] Peer Connection Initiated with 174.49.37.190:1194
Mon Oct 11 11:02:09 2010 SENT CONTROL [server]: 'PUSH_REQUEST' (status=1)
Mon Oct 11 11:02:09 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 Oct 11 11:02:09 2010 OPTIONS IMPORT: timers and/or timeouts modified
Mon Oct 11 11:02:09 2010 OPTIONS IMPORT: --ifconfig/up options modified
Mon Oct 11 11:02:09 2010 OPTIONS IMPORT: route options modified
Mon Oct 11 11:02:09 2010 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
Mon Oct 11 11:02:09 2010 ROUTE default_gateway=192.168.0.1
Mon Oct 11 11:02:09 2010 TAP-WIN32 device [Local Area Connection 2] opened: \\.\Global\{04D24CA8-6722-4F08-BBF3-AFF66C11C5EB}.tap
Mon Oct 11 11:02:09 2010 TAP-Win32 Driver Version 9.4
Mon Oct 11 11:02:09 2010 TAP-Win32 MTU=1500
Mon Oct 11 11:02:09 2010 Notified TAP-Win32 driver to set a DHCP IP/netmask of 10.8.0.6/255.255.255.252 on interface {04D24CA8-6722-4F08-BBF3-AFF66C11C5EB} [DHCP-serv: 10.8.0.5, lease-time: 31536000]
Mon Oct 11 11:02:09 2010 Successful ARP Flush on interface [19] {04D24CA8-6722-4F08-BBF3-AFF66C11C5EB}
Mon Oct 11 11:02:11 2010 TEST ROUTES: 2/2 succeeded len=2 ret=1 a=0 u/d=up
Mon Oct 11 11:02:11 2010 C:\WINDOWS\system32\route.exe ADD 192.168.1.0 MASK 255.255.255.0 10.8.0.5
Mon Oct 11 11:02:11 2010 C:\WINDOWS\system32\route.exe ADD 10.8.0.1 MASK 255.255.255.255 10.8.0.5
Mon Oct 11 11:02:11 2010 Initialization Sequence Completed

[cpg]

Seems ok.

Can you ping your HDA by it's internal IP?

Also, looking at your HDA's connection log perhaps can shed some light into the issue.

[jtupnsmoke]

I get a time out when I try to ping the internal address, which is 192.168.1.10. I will check the logs and see if I can find anything. Everything seems to be connecting fine, but it still isn't working.