Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

Engineers toolset v10.3 conflict with Cisco Clean Access Agent

I was on v9 of the toolset and everything worked fine. But once I upgraded to v10.3 I started getting an API error and a conflict with my Cisco Clean Access Agent. I could not access any of my network resources. I had to completely uninstall the toolset in order to regain access.

Has anyone else had this problem?

Find more posts tagged with

Accepted answers

All comments

greg

similler - what version CCA Agent are you running? Any configuration information you can give would be helpful in trying to replicate...

Thanks,

Greg

similler

Thank you for the response. I am running v4.1.3.1 of the Cisco Clean Access Agent.

During the Solarwinds Engineers toolset upgrade from v9 to 10.4, I had to disable the clean access agent in order for it to install properly. Once my upgrade was complete I re-enabled the clean access agent. The next time I fired up my VPN connectivity I started getting the API error. I was able to connect to my remote network but I was not able to open any network resources (as if the clean access agent wasn't running). I verified that the agent was infact running. I un-installed the Solarwinds Egineers toolset v10.4 and the error went away and I was again able to access my network resources through VPN.

jeff.stewart

This sounds really bizarre. Everyone on our team has the agent on their machines and we aren't seeing this. We are using a different version of the agent.

similler

What version of the cisco agent are you running? I am actually running the engineers toolset v10.4 (not v10.3).