Cisco VPN Client will not connect to PIX 501, error with virtual adapter
Posted on 2005-04-14
I am trying to connect a PC to a PIX using VPN Client. I know the PIX is set up correctly because other PC's can connect using the same security information etc.. However the PC that fails has WinXP SP2 where the others do not have SP2.
Im using the latest version of Ciscos VPN client 4.6.02.0011.
Windows FW is off and so is McAfee.
I have already tried de-installing and installing VPN CLient. After installing the VPNClient for the second time all my network interfaces had IP addreses of 0.0.0.0 and would not appear in ipconfig! (as if i had no network interfaces)
A few expletives later... ! I used a program called winsockxpFIX (suggested in another EE thread) which returned my LAN interfaces to normal, but did not solve the VPNClient issue.
When i select the connection entry from within VPN Client and click connect i get the username and password screen appear, after entering the correct credentials The status bar on the VPN Client says "Securing Communications Channel ..." and after a while (minute or so) it says "Not Connected." Looiking in the VPN CLient Logs there are the following errors
Cisco Systems VPN Client Version 4.6.02.0011
Copyright (C) 1998-2004 Cisco Systems, Inc. All Rights Reserved.
Client Type(s): Windows, WinNT
Running on: 5.1.2600 Service Pack 2
Config file directory: C:\Program Files\Cisco Systems\VPN Client\
1 14:45:58.180 04/14/05 Sev=Warning/2 IKE/0xA3000067
Received Unexpected InitialContact Notify (PLMgrNotify:886)
2 14:46:19.260 04/14/05 Sev=Warning/3 CVPND/0xA340000D
The virtual adapter was not recognized by the operating system.
3 14:46:19.260 04/14/05 Sev=Warning/2 CM/0xE310000A
The virtual adapter failed to enable
4 14:46:19.631 04/14/05 Sev=Warning/2 IKE/0xE3000099
Failed to active IPSec SA: Unable to enable Virtual Adapter (NavigatorQM:936)
5 14:46:19.631 04/14/05 Sev=Warning/2 IKE/0xE30000A5
Unexpected SW error occurred while processing Quick Mode negotiator:(Navigator:2202)
ERROR Number 2 is probably a big clue, except im not sure where to go from now. As this is the only PC with SP2 the obvious thing to suggest is to un-install SP2, however i would rather not do that unless the experts out their suggest i should.
Thanks in advance