04-26-2011 08:57 AM
I am running ASA version 8.4(1), and anyconnect version 3.0.1047. My SSL VPN works fine, but i run into an issue with one user . his account did not work , and everytime users logged in it got this message "VPN Server could not parse request".
I found the problem after getting a user information meaning his username and password. His password had "&" as one of the special characters. when we change it to something that does not have that , it works just fine.
We are using microsoft NPS server as radius. but when i run a test within CLI it works just fine, only when anyconnect asks to authenticate it fails.
Anyone had the similar problem?
Thanks
Solved! Go to Solution.
04-26-2011 10:47 AM
Marcin,
This could a re-occurance of:
Would you be able to test the workaround?
Marcin
EDIT
Looks like this one:
04-26-2011 10:47 AM
Marcin,
This could a re-occurance of:
Would you be able to test the workaround?
Marcin
EDIT
Looks like this one:
04-27-2011 08:50 AM
Thank you sir.
I should've looked at the bug tool, but it just not enough time...
Thanks again..
01-10-2012 01:42 AM
Can you copy the content from BugToolKit so other users can get the correct answer?
We have the same problem for some users at my job.
Thanks
01-10-2012 01:55 AM
Anton,
Here you go,
M.
CSCtn75204 AnyConnect 3.0 VPN Server could not parse request with & or < in passwd
Symptom: AnyConnect 3.0 client reports "VPN Server could not parse request" error during user authentication. Conditions: Issue is observed when user password includes a "&" or "<" character. Workaround: Utilize a password that does not include these special characters.
Fixed in 3.0.2035
01-10-2012 02:03 AM
Thanks. Our customer used a "&" character in his password, but it works now after he changed his password!
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide