09-16-2021 11:12 PM
Team,
In our organisation users are facing an issue of disconnection on windows machine,
Scenario- users are connected on network & in between sudden disconnection happen and in anyconnect module which appear on the windows taskbar on desktop shows network service unavailable & after few seconds profile gets appear that we created on xml and associates and authenticate and connect, automatically. All services and apps which is on network based gets disconnected. Our CEO also faced these issue, they want these sda network to be removed & revert back to traditional setup.
Drivers are also updated.
I also involved tac but got no proper response should i involve BU from cisco.. please suggest any workaround.
Solved! Go to Solution.
09-17-2021 12:56 AM
Hi @RohitSingh91693,
As you are experiencing downtime, involving TAC was the right option to do. Also, it is your best chance to get resolution. If not happy with progress speed, you can ask TAC engineer for escalation (also through your local Cisco team).
BR,
Milos
09-17-2021 12:56 AM
Hi @RohitSingh91693,
As you are experiencing downtime, involving TAC was the right option to do. Also, it is your best chance to get resolution. If not happy with progress speed, you can ask TAC engineer for escalation (also through your local Cisco team).
BR,
Milos
09-17-2021 05:04 AM
In order to possibly better assist the community needs more information.
-Version of AnyConnect and NAM?
-Have you ran a DART bundle on any of the troubled clients to dissect the logs?
-Protocol used for onboarding?
-Have you verified supplicant config?
-Is it possible that you are using computer cert or user smartcard for authentication and there is an issue with cert mapping or readers?
-Client OS type? Does this happen on all clients?
-Switchport config you are using?
-Any relevant switch debugs?
TBH I would start with this:
Upgrade AnyConnect modules to latest version on some test clients to see if problem still exists. Generate a DART bundle and go through logs. Enable extended logging with AnyConnect:
--Enable Extended Logging for AnyConnect Client--
Open AnyConnect, make sure it is in focus
press this combo: left shit+ left alt + L. no response
Right click the anyconnect icon in windows system tray. menu pops up
select extended logging so it has a check mark displayed. NAM will now log debug messages.
HTH!
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