locked
SCOM 2012 ACS agent Failed connecting to collector RRS feed

  • Question

  • Hi,

    We are using SCOM 2012 on Windows 2012, when installing the SCOM agent with Audit Collection Services the ACS forwarder will report in as healthy until reboot, after reboot the forwarder state changes to failed to connect to collector. (XXX's are redacted system information).

    Forwarder unsuccessfully tried to connect to the following collector(s): XXXXXXXX:51909, status: 0x80090322 (TCP connect), source: registry addresses tried: XXX.XXX.XXX.XXX:51909 If the list of collectors is blank, then AdtAgent was unable to locate a collector. Common reasons for this message are: The machine(s) listed is not online AdtServer is not running on the machine(s) listed AdtServer on the machine(s) listed is not listening on the specified port TCP connectivity to the AdtServer machine is blocked by firewall, IPSec, or other filtering mechanism AdtServer on the machine(s) listed actively refused the connection (due to policy or current activity load) For detailed failure information, enable trace logging using the TraceFlags registry key and examine the AdtAgent.log in the \temp subdirectory of the Windows directory.

    Enabling trace logging repeats the same error, unable to connect to server. We have verified, the IP is correct, the FQDN is correct and has a forward and reverse lookup record. We have also verified via telnet that port 51909 is open in both directions. Any help would be appreciated.

    Tuesday, February 10, 2015 2:26 PM

All replies

  • If you are 100% sure port 51909 is open at Collector's side (you don't need to open it on ACS forwarder) and there's no additional firewall somewhere at the middle use wireshark and capture what's going on. 

    --- Jeff (Netwrix)

    Wednesday, February 11, 2015 2:14 PM