Issues with Netscaler 12 client

[malcolmchalmers]

We are in the process of doing a test rollout of the NetScaler Gateway 12.0.58.15 client and have run into an odd problem.

If we have a McAfee Agent - Repository policy enforced on the client that points to all our distributed repositories, whenever the Agent does a get and enforce policies it kills the NetScaler app and the VPN connection drops.

If we have a McAfee Agent - Repository policy enforced that only points to the ePO server, the connection stays up regardless of what the McAfee Agent does.

Anyone seen this before?

[cdinet · Accepted solution]

Here is what happens when a client gets a policy with all repos enabled.  It has to ping each one to get a distance or hop value, depending on whether you are using ping time or subnet distance.  Then once it gets a response from the repos, it uses those values to sort the repositories in the correct order for them to use per the policy.  It does not ping the disabled repositories.  So, depending on how many enabled repositories you have, the gateway could be getting a flood of ping requests that it can't handle all at once. 

When you have only the epo server enabled, then that is the only repository it pings, as well as any agent handlers.

If you want the systems to use repositories, I might suggest enabling only a few instead of all for those particular clients that would be using vpn.

[malcolmchalmers]

Thanks, I'll try a policy with only 5 or 6 repositories in it and see how we go.