Greetings,
I have a ASL v4 VPN configuration that is currently working with Windows 2000 clients running SSH Sentinel v1.4.1_72. The VPN is a AES_PFS x509 configuration.
I have downloaded and installed the latest version of the new Astaro VPN client. I went through install and the config, imported the PKCS#12 cert and am able to establish a link (green light, green link bar in the monitor) on a WindowsXP SP1 laptop. The connection is via ethernet/IP.
I can consistently make a successful connection but I am unable to pass any packets across the link. If I run a traceroute to an IP on the other side of the VPN link the path follows the non-VPN default gateway path.
When doing a 'netstat -rn' or 'ipconfig /all' there is no listing of the Astaro VPN virtual nic. The netstat output shows nothing other than the address routes of the default ethernet and local loopback.
Shouldn't the Astaro VPN virtual nic appear in ipconfig and netstat? The nic does appear in the Control Panel/Network Connections window and is listed as enabled. When running a command shell window and doing the ipconfig or netstat nothing shows.
I uninstalled and reinstalled (with a reboot inbetween) but nothing changes.
When I would go through the connect process via Astaro VPN Monitor I could watch the IPSec Live Log in ASL v4 and see the IKE and transaction and everything looks okay. The configuration has the remote user's certificate with a Virtual IP. The config in Astaro VPN client has the Virtual IP listed in manual address, the internal IP network listed as the destination network and the ASL v4 external IP as the VPN gateway IP.
Can anyone suggest a cause to what I am experiencing?
Thanks,
Jeff
(ps: sorry about Bush being president for another 4 years. we tried to vote him out..) [:(]
This thread was automatically locked due to age.
