CSA Network Shim

[csmith]

New CSA 4.0 implementation, attempting to deploy the initial standard laptop agent kit. Installation of the kit works fine on the client laptop, which includes the installation of the network shim (prompted during interactive installation).

During startup, the local agent logs and reports: "the agent was unable to start the csanet driver". The local log file indicates this will impact some policies assigned to the kit/group (obviously).

The current thought is that a modification to the network stack, caused by an app such as VMWare or a VPN client shim may be causing a conflict.

Has anyone previously encountered this issue, or similar issues?

Thanks.....

[gfullage · Accepted solution]

This is usually due to, as you suspect, some other software that has put itself into the network stack of the PC/laptop. Usual culprits are the Cisco VPN client (or check for other VPN clients also), virus software, personal firewalls, etc.

Try removing the CSA agent, removing the suspected culprit, then reinstalling the agent. After it's installed you should then be able to reinstall he culprit and things'll run fine.

Note that this is already flagged as a bug and at least as far as the Cisco VPN client is concerned, is already fixed in the new 4.0(1) agent. I'm pretty sure it's fixed for all the other culprits as well but just haven't ran into them lately.

[csmith]

Thanks - long response in replying, but the upgrade to version 4.01 did resolve the problem. Removing the previous version of the CSA agent and installing the new kit resulted in the Shim working fine, no other applications were modified.