Connectivity Requirements

For the Cisco CDA to function properly, it must be able to communicate freely with all the consumer devices, Active Directory domain controller machines, and target syslog servers that are configured with it. If Windows Firewall (or any other comparable third-party firewall software) is running on any of the Active Directory domain controller machines, then the firewall software on each of these endpoints must be configured with the necessary exceptions to allow this communication to flow freely.

This section uses the Windows Firewall as an example and details the exceptions that must be defined on any of the endpoints that might be running Windows Firewall.

For any other comparable third-party firewall software, refer to that vendor's documentation on how to configure the corresponding exceptions.

Windows Firewall Exceptions to be Configured on Each Separate Active Directory Domain Controller Machine

For each separate Active Directory domain controller machine that is configured on the Cisco CDA machine using the GUI, if Windows Firewall is enabled on that separate domain controller machine, then you must define a Windows Firewall exception on that particular domain controller machine that will allow the necessary WMI-related communication.

If that domain controller machine is running Windows Server 2008 or Windows Server 2008 R2, then you can configure this WMI-related exception using the following Windows command line (written in a single line):

netsh advfirewall firewall set rule group=”Windows Management Instrumentation (WMI)" new enable=yes

If that domain controller machine is running Windows Server 2003 or Windows Server 2003 R2 (with SP1 or later installed), then you can configure this WMI-related exception using the following Windows command line (written in a single line):

netsh firewall set service RemoteAdmin enable

Related Topics:

 • Supported Operating Systems

 • Hardware Requirements

 • Active Directory Requirements for Successful Connection with Cisco CDA