Cisco AnyConnect NAM wireless issue

vancamt76 · ‎03-15-2012

We are currently working on deploying NAM into our Secure Mobility Client. We've found that this works beautifully on some machines and chokes horribly on others. Windows XP has a higher success rate than our Win 7 images. I have a particular user who has NAM installed (version 3.0.5075) who can no longer connect to our wireless network, which uses WPA2/AES and RADIUS authentication to an ACS server. If I disable the NAM client in Anyconnect, Windows relinquishes control and will allow the user to connect; as soon as I enable NAM, the wireless supplicant just keeps showing "Associating" and I do not see anything on the wireless controller or ACS logs so this user is not even getting that far. So far, I've tried pushing a new NAM profile through ASDM, deleting and recreating the configuration file in C:\ProgramData\Cisco\Cisco AnyConnect Secure Mobility Client\Network Access Manager\system, and multiple network repairs. There doesn't seem to be much in the way of documentation that I could find to assist in troubleshooting.

I have created a DART bundle and can attach if it would be helpful to someone to provide assistance. I've found this peculiar piece within the bundle:

601: SAMUSARAN: Mar 15 2012 12:10:56.732 +0500: %NAM-6-INFO_MSG: %[tid=5960]: Symbolic name: ({824DC894-2E9B-4929-A7A6-F6B8EEC18AA6}), MacAddr: (0024d6-09ef24), Mtu: (1514), Media: (802.11abg), Encryption: (AES, TKIP, WEP, NONE), Auth: (OPEN, SHARED, WPA-1X, WPA-PSK, 11i-1X, 11i-PSK)
602: SAMUSARAN: Mar 15 2012 12:10:56.732 +0500: %NAM-6-INFO_MSG: %[tid=5960]: Starting wifi connection, trying ssid zebes ...
180: SAMUSARAN: Mar 15 2012 12:10:56.732 +0500: %NAMSSO-7-DEBUG_MSG: %[tid=8672]: Tx Msg: <?xml version="1.0" encoding="UTF-8"?><SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ssc="http://www.cisco.com/ssc" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"> <SOAP-ENV:Body> <networkStateEvent> <sequenceNumber>52</sequenceNumber> <groupName>Local networks</groupName> <networkName>zebes</networkName> <networkState>Stopped</networkState> <adapterName></adapterName> <serverVerifiedName></serverVerifiedName> </networkStateEvent> </SOAP-ENV:Body></SOAP-ENV:Envelope>
603: SAMUSARAN: Mar 15 2012 12:10:56.733 +0500: %NAM-6-INFO_MSG: %[tid=5960]: Connection Association Started(wpa2EnterpriseAes)
604: SAMUSARAN: Mar 15 2012 12:10:56.756 +0500: %NAM-3-ERROR_MSG: %[tid=5960][comp=SAE]: NET (0) ***ERROR: S_nwifiConnect: WlanConnect() returned 1399: HANDLE=45, GUID*=00773148 {824DC894-2E9B-4929-A7A6-F6B8EEC18AA6}, WLAN_CONNECTION_PARAMETERS dump follows
605: SAMUSARAN: Mar 15 2012 12:10:56.756 +0500: %NAM-3-ERROR_MSG: %[tid=5960][comp=SAE]: NET (0) 0000 01 00 00 00 88 F8 7C 00 00 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00 ......|.................
606: SAMUSARAN: Mar 15 2012 12:10:56.756 +0500: %NAM-3-ERROR_MSG: %[tid=5960][comp=SAE]: NET (0) Failed to set SSID
607: SAMUSARAN: Mar 15 2012 12:10:56.756 +0500: %NAM-3-ERROR_MSG: %[tid=5960]: Connection Association Failed (Failure: AC_ERR_FAILURE[-1])
608: SAMUSARAN: Mar 15 2012 12:10:56.756 +0500: %NAM-3-ERROR_MSG: %[tid=5960]: Internal error 4, contact software manufacturer
609: SAMUSARAN: Mar 15 2012 12:10:56.756 +0500: %NAM-7-DEBUG_MSG: %[tid=5960]: CssError for function 'acPortAssociate' => -1{error} [PortManagerImpl.cpp:169]
610: SAMUSARAN: Mar 15 2012 12:10:56.756 +0500: %NAM-7-DEBUG_MSG: %[tid=5960]: AssociationInfoProxy is empty
611: SAMUSARAN: Mar 15 2012 12:10:56.762 +0500: %NAM-7-DEBUG_MSG: %[tid=5960]: Network zebes: AccessStateMachine current state = ACCESS_ASSOCIATING, received adapterState = associating
612: SAMUSARAN: Mar 15 2012 12:10:56.762 +0500: %NAM-7-DEBUG_MSG: %[tid=5960]: Network zebes: AccessStateMachine new state = ACCESS_ASSOCIATING
613: SAMUSARAN: Mar 15 2012 12:10:56.762 +0500: %NAM-7-DEBUG_MSG: %[tid=5960]: Network zebes: NetworkStateMachine current state USER_T_DISCONNECTED, received access event ACCESS_ASSOCIATING
614: SAMUSARAN: Mar 15 2012 12:10:56.762 +0500: %NAM-7-DEBUG_MSG: %[tid=5960]: Network zebes: NetworkStateMachine new state USER_T_DISCONNECTED
615: SAMUSARAN: Mar 15 2012 12:10:56.762 +0500: %NAM-7-DEBUG_MSG: %[tid=5960]: Entered AceStateMachineImpl::handleEvent in state Configuration::STARTED: processing AccessSM state change to Network::ACCESS_ASSOCIATING
616: SAMUSARAN: Mar 15 2012 12:10:56.763 +0500: %NAM-7-DEBUG_MSG: %[tid=5960]: Number of networks in connecting state = 1

Etts Equinox · ‎12-10-2015

i have the same problem.

i get the same error Failure: AC_ERR_FAILURE[-1]

can anyone have a solution for this issue

thanks

PraveenKellaka55979 · ‎03-19-2022

Does anyone got a fix for this issue?

thanks.

Mike.Cifelli · ‎03-19-2022

Hi @PraveenKellaka55979 please start a new post with new information that may help the community better assist you with your issue.

-AnyConnect version

-NAM profile wireless settings (protocol used for onboarding, etc.)

-Have you run a DART bundle locally on a troubled client? Can you share any discovered errors?

-Client OS type?

-Description of wireless setup

-Any other relevant information