I have downloaded and installed my agent kit on a WinXP machine. But for some reason it is not registering with the CSA MC. Any idea why? The CSAMC is in a different subnet, but 443 is open for communication. Does the MC need other ports open to talk to the agent?
I was going to suggest editing the host file as well. Currently, we have several networks that cannot talk to each other, legal reasons, but allow certain communication to pass in order to keep monitoring tools operation. I have no idea what his environment is like, but if for nothing else, modify the file and hit poll.
If it still does not work, I would suggest looking and making sure you have enough valid licenses. *Shrugs* could be an issue.
Here is a listing of the various error codes that CSA (used to be Okena) prints when there is a communication issue between an agent and the MC.. Usually the issue is either licensing or CSAMC access restrictions, but this list has all of the causes. Please rate if this helps.
Table of ContentsIntroductionVersion HistoryPossible Future
UpdatesDocuments PurposeNAT Operation in ASA 8.3+ SectionsRule Types
Network Object NATTwice NAT / Manual NATRule Types used per SectionNAT
Types used with Twice NAT / Manual NAT and Network Obje...
Table of Contents Introduction:This document describes details on how
NAT-T works. Background: ESP encrypts all critical information,
encapsulating the entire inner TCP/UDP datagram within an ESP header.
ESP is an IP protocol in the same sense that TCP an...