VPN stop working after changing Amahi server IP address

[henryguoxp]

MY windowns clint VPN HDAconnect worked before when amahi server ip was default ip 192.168.1.10, but I can not access HDA anymore after I changed amahi server/DHCP/DNS ip to 192.168.168.10 (also changed router ip to 192.168.168.1, and forward TCP/UDP 1194 to 192.168.168.10 on router) by using HDA-change-gw and hda-change-dns commands, the HDAconnect symbol "A" is green after I enter my user/password. I got message "Windows cannot access \\hda" or " Windows cannot find \\\hda'....".
my windows is windows7.

Here is the HomeHDA.log from HDAconnect:

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

[bigfoot65]

This may require action from support. Recommend you send a note to support stating what you did. Your HDA profile does not match your current configuration now, so that is probably the issue.