Unable to process response from x.x.x.x

[marcohernandez]

Hi All

I have noticed that the error "unable to process response from x.x.x.x"  when using anyconnect is very common and that the actions to handle it are different. Right know I have the same issue. Let's name it "the message" =)

We are running:

ASA 8.2(2)

AnyConnect 2.5.1025

In my scenario, we used to be able to connect to the ASA using AnyConnect but suddenly it stops to work showing "the message" =)

We did this procedure, but it did not worked for us

http://www.cisco.com/en/US/products/ps6120/products_tech_note09186a00809b4754.shtml#e10

My first question would be:

How can I obtain more information so I can get a better idea to handle "the message"?

The next step I am about to do is upgrade the AnyConnect Cliente to 2.5.2019. According to the release notes, this versión is supported with ASA 8.2(22)

I also notice that the AnyConnect client can be install with a component named Cisco Diagnostic and Reporting Tool (DART). Does this tool could be usefull to troubleshoot "the message"? What kind of information does DART can give us? Were can I find the files it captures?

I am planning to deploy AnyConnect 2.5.2019 with DART

[Jennifer Halim]

Here is the user error messages for AnyConnect 2.5:

http://www.cisco.com/en/US/docs/security/vpn_client/anyconnect/anyconnect25/user/messages/ac25-vpn-user-msgs.html

And yes, you are right, DART is used to diagnose/troubleshoot issue with the AnyConnect client. Here is all the information on how DART works for your reference:

http://www.cisco.com/en/US/docs/security/vpn_client/anyconnect/anyconnect30/administration/guide/ac12managemonitortbs.html#wp1058615

Hope that helps.

[marcohernandez]

Thank you Jennifer.

We deployed DART and I can see this messages related with the error. Do you know what could be the possible error. We also upgrade to AnyConnect 2.5.2019

******************************************

Date        : 02/24/2011
Time        : 21:29:05
Type        : Error
Source      : vpnui

Description : Function: MSSaxErrorHandlerImpl::fatalError
File: .\Xml\MSSaxErrorHandlerImpl.cpp
Line: 31
Invoked Function: CVCMSSaxParser
Return Code: -1072894430 (0xC00CEE22)
Description: WINDOWS_ERROR_CODE
XML Parser fatal error: Se esperaba punto y coma.

******************************************

Date        : 02/24/2011
Time        : 21:29:05
Type        : Error
Source      : vpnui

Description : Function: XmlParser::invokeParser
File: .\Xml\XmlParser.cpp
Line: 206
Invoked Function: XmlParser::invokeParser
Return Code: -1072894430 (0xC00CEE22)
Description: WINDOWS_ERROR_CODE
Error encountered during parse.

Please enter your username and password.

******************************************

Date        : 02/24/2011
Time        : 21:29:05
Type        : Error
Source      : vpnui

Description : Function: ConnectMgr::processXml
File: .\ConnectMgr.cpp
Line: 3978
Invoked Function: XmlParser::parseXml
Return Code: -1072894430 (0xC00CEE22)
Description: WINDOWS_ERROR_CODE
Unable to process response from Gateway.

******************************************

Date        : 02/24/2011
Time        : 21:29:05
Type        : Error
Source      : vpnui

Description : Function: ConnectMgr::processIfcData
File: .\ConnectMgr.cpp
Line: 1586
Invoked Function: ConnectMgr::processXml
Return Code: -1072894430 (0xC00CEE22)
Description: WINDOWS_ERROR_CODE

******************************************

Date        : 02/24/2011
Time        : 21:29:05
Type        : Information
Source      : vpnui

Description : Function: ClientIfcBase::notice
File: .\ClientIfcBase.cpp
Line: 698
Unable to process response from 216.194.136.12.

******************************************

Date        : 02/24/2011
Time        : 21:29:05
Type        : Error
Source      : vpnui

Description : Function: ConnectMgr::processIfcData
File: .\ConnectMgr.cpp
Line: 1660
Unable to process response from 216.194.136.12.

Please enter your username and password.

[Jennifer Halim · Accepted solution]

Potentially might match the following bug: CSCth11779

http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCth11779

Do you have special characters configured on your group-alias name? If not, then it's not the above bug.

[marcohernandez]

Hi Jeniffer,

I haved tested the workarround you told me in Lab environment and I could replicate the issue. Also we verified and changed the aliases with "&" and the issue was solved.

I would like to thank you for your very helpfull answer.

Warm Regards!

Marco

[Jennifer Halim]

Perfect, great to hear it's working now. Thanks...