klsphotos
asked on
Error: Secure VPN connection terminated by Peer. Reason 433 (Reason not specified by peer)
Hi Experts,
I am hoping you can help me with this. I am not a Cisco person so please be patient.
I have the error above. The windows account that does the ldap connection I recently disabled not knowing it was the account that does this for the vpn. I reenabled it but users are still getting this error. I thought for sure this was why. I have restarted the servers but still nothing?
Nothing else on the config side has changed. Any ideas? Does something on the switch have to be restarted?
Thank you,
Karen
I am hoping you can help me with this. I am not a Cisco person so please be patient.
I have the error above. The windows account that does the ldap connection I recently disabled not knowing it was the account that does this for the vpn. I reenabled it but users are still getting this error. I thought for sure this was why. I have restarted the servers but still nothing?
Nothing else on the config side has changed. Any ideas? Does something on the switch have to be restarted?
Thank you,
Karen
ASKER
We tried several accounts, all get the same error. The account I mentioned was the account set in the ASA for ldap was disabled. I reenabled it but they are still getting the error above.
ok but you just said two things there - You tried several accounts, all the same error. Was this all on the same laptop? Where is this laptop connected to? If I'm testing VPN on a users machine I MUST be NOT on my network otherwise it won't work. If you tested 3 different accounts on this users machine (including the one you disabled) and they all get the same error then it isn't an account specific problem.
This laptop you are testing on - hard wired? WiFi on as well?
This laptop you are testing on - hard wired? WiFi on as well?
ASKER
Hi Atrevido,
The user who reported the issue is not here. He tried on 2 systems, same error. He connected to my machine through join.me and logged into a server fine so no issue with his account. Another user here connected externally and tested and same error. My creds did not work remotely either same error.
The service account that processes the ldap connections was recently disabled by me because I didn't know what it was. It's renabled but everyone is still getting the same error.
Both hard wired and wifi connections during testing, the error is consistent. The domain controllers have been restarting just to rule out any issue there but still same error.
The only changes recently made were disabling of some AD user and computer accounts.
Hope that made sense. Thank you for your help.
Karen
The user who reported the issue is not here. He tried on 2 systems, same error. He connected to my machine through join.me and logged into a server fine so no issue with his account. Another user here connected externally and tested and same error. My creds did not work remotely either same error.
The service account that processes the ldap connections was recently disabled by me because I didn't know what it was. It's renabled but everyone is still getting the same error.
Both hard wired and wifi connections during testing, the error is consistent. The domain controllers have been restarting just to rule out any issue there but still same error.
The only changes recently made were disabling of some AD user and computer accounts.
Hope that made sense. Thank you for your help.
Karen
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
You never told me you moved the OU. You said disabled but never moved OU's. Attached is a snapshot of the config in the firewall and why that is important information. ALso, OU names and special characters are very important for the ASA as it is very picky. So good luck with that.
AAA-programming-ASA.pdf
AAA-programming-ASA.pdf
ASKER
Hi Atrevido,
I didn't realize it was relevant to mention it until I researched the error on my own and tested it and discovered that that was the was. I posted this so that if others had the issue, they could check as well. The OU needs to go where I moved it so I will tackle that project at another time.
Thank you for that document, that looks like it came from the same article I found about this issue. Here is the link so others can read the whole article:
http://supertekboy.com/2014/01/23/cisco-vpn-reason-433-reason-not-specified-by-peer/
Thank you for your help.
I didn't realize it was relevant to mention it until I researched the error on my own and tested it and discovered that that was the was. I posted this so that if others had the issue, they could check as well. The OU needs to go where I moved it so I will tackle that project at another time.
Thank you for that document, that looks like it came from the same article I found about this issue. Here is the link so others can read the whole article:
http://supertekboy.com/2014/01/23/cisco-vpn-reason-433-reason-not-specified-by-peer/
Thank you for your help.
ASKER
I researched on my own, I had to get it fixed and this resolved the issue.
Often 433 error means invalid username, or password or locked account. Try changing the password on that account and unlocking it. Then have the user try again with new password.