I'm noticing some nuances after upgrading a couple of my servers to 5.2. If I connect to a server via Remote Desktop that has been upgraded to 5.2, I am unable to interact with the agent the same way I was with 5.1. For example, I am not able to right click on the tray icon to disable the security. I've done a rule comparison of the 5.1 and 5.2 agent UI rule, but I am not seeing any differences to warrant the behavior I'm seeing.
Well, I spoke too soon. I attempted to do another server and it's got the same problem. Now the difference between the one that works and the one that doesn't is the service pack version. The one that works is on SP1, and the one that doesn't is running SP2. So, it appears that there may be an issue with SP2 and CSA 5.2.
This sounds like a similar issue in which the agent appears to be disabled when RDP'd into the server, however, the service is actually running. When I RDP using the console switch, it appears as it should. I have a TAC case open and this issue is supposed to be resolved with the next 5.2 patch due out any day.
We have configured the outside and inside Interface with official ipv6 adresses, set a default route on outside Interface to our router, we also have definied a rule , which also gets hits, to permit tcp from inside Interface to any6.
In Syslog I also se...