Open the ports listed in the following table on the firewall for proper communication between Secure Configuration Manager components.
|
Port Number |
Component Computer |
Port Use |
|---|---|---|
|
700 |
Security Agent for Windows (Deployment Agent) |
Used by the Deployment Agent and remote computer during deployment. |
|
1433 |
Database |
Used by Microsoft SQL Server if you are using a default instance of SQL Server. This port is also used by the Windows console to listen for communication from the database. When used by Core Services, the port uses bi-directional communications to communicate with the Windows console and the database. |
|
1621 |
Core Services |
Used by Core Services to listen for communication from the Windows agent or standalone AutoSync server when both the agent or standalone AutoSync server and the Core Services computer are in FIPS mode. |
|
1622 |
Security Agent for Windows |
Used by the Windows agent to listen for communications from Core Services. This port uses bi-directional communications. |
|
1622 |
UNIX Agent |
Used by the UNIX agent to listen for communication from Core Services. Core Services uses this port to run reports and actions. This port uses bi-directional communications. |
|
1626 |
Core Services |
Used by Core Services to communicate with Agents using SSL (Secure Sockets Layer) protocol. Agents include Windows and UNIX agents. SSL is a protocol developed by Netscape for ensuring security and privacy in Internet communications. SSL uses a private key to encrypt data that is transferred over the SSL connection. |
|
1627 |
Core Services |
Used by Core Services to listen for communication from the Security Agent for Windows or UNIX. |
|
8044 |
Core Services |
Used by Core Services to communicate with the Windows console computer. This port uses bi-directional communications. |
|
8044 |
Web Server |
Used by the Web server that is embedded in Core Services, which supports the Web console. The Web server uses port 8044 by default, but this port is configurable. |
|
2005 |
Security Agent for Windows |
Used by the Windows agent to interact with the utility tools in Secure Configuration Manager. Ensure that this port is reserved for Secure Configuration Manager. NOTE:If this port is already reserved and not available for Secure Configuration Manager, you can use any other free port, but ensure that you change the port number in the HKEY_LOCAL_MACHINE\SOFTWARE\NetIQ\VigilEnt registry accordingly. |
|
TCP 8045 |
Dashboard |
Used by the Dashboard infrastructure for communication with the Dashboard Website. |
|
TCP 8044 |
Core Services computer |
Used by the Dashboard for communication with the Secure Configuration Manager Core Services computer. |
|
TCP 9200 |
Analytics Database |
Used by the Dashboard for communication with Dashboard Database using its REST services. |
|
TCP 9300 |
Analytics Database |
Used by the Dashboard for communication with Dashboard Database using its native protocol. |
NOTE:If you have used non-default ports for the Analytics Database, Dashboard, and Core Services computers, ensure that those ports are open.