Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Community Member

Can't Connect to VPN Client

I am trying to resolve a connection issue with Cisco VPN Client Ver 5.0.00.0340. Below is the log file data and the messages I get when I try to connect the VPN. I added the VPN I.P. to my ZA-AV firewall trusted zone, and I have attempted the connection with and without personal firewall. I also verified the password and username.

System OS: Vista Home Premium (pre-loaded)

There were no reported issues during installation of VPN client software:

Firewall is ZoneAlarm v7.x

Log reports:

Cisco Systems VPN Client Version 5.0.00.0340

Client Type(s): Windows, WinNT

Running on: 6.0.6000

Config file directory: C:\Program Files\Cisco Systems\VPN Client\

1 18:55:47.664 12/25/07 Sev=Warning/3 IKE/0xE3000057

The received HASH payload cannot be verified

2 18:55:47.664 12/25/07 Sev=Warning/2 IKE/0xE300007E

Hash verification failed... may be configured with invalid group password.

3 18:55:47.664 12/25/07 Sev=Warning/2 IKE/0xE300009B

Failed to authenticate peer (Navigator:904)

4 18:55:47.664 12/25/07 Sev=Warning/2 IKE/0xE30000A7

Unexpected SW error occurred while processing Aggressive Mode

negotiator:(Navigator:2237)

6 REPLIES
Cisco Employee

Re: Can't Connect to VPN Client

Based upon the below message in the logs, the Group Name and Password is not matching.

Hash verification failed... may be configured with invalid group password.

Make sure that the Group Name and Password on both the VPN Server and Client is the same.

Regards,

Arul

Community Member

Re: Can't Connect to VPN Client

Hey Arul,

yes they do match

Community Member

Re: Can't Connect to VPN Client

Group2 encryption?

Community Member

Re: Can't Connect to VPN Client

Not sure I understand this question. Thank you.

Community Member

Re: Can't Connect to VPN Client

What he is trying to say is that on the VPN termination device are you using Diffie-Hielman group 2?

Community Member

Re: Can't Connect to VPN Client

Arul, thank you.

Watch that caps lock. Turns out this was solution. All other userids were set under lower case. The one assigned to me was set in upper case, even though the access info I was provided indicated lower case.

262
Views
5
Helpful
6
Replies
CreatePlease to create content