Networking Problems (Ports Blocked)

The first step of the Security Center connection process uses named pipes to initiate the Security Center application on the MCP environment. This action requires a connection to port 139 (NetBIOS – Session) of the MCP environment. If this port is blocked by an intermediate device such as a firewall, then that connection fails.

The second step of the Security Center connection process uses TCP/IP sockets to communicate between the Windows client and the MCP program. The Windows client initiates a connection to port 57371 (Security Center – nonSSL) or 57372 (Security Center – SSL) of the MCP environment. Port 57371 (nonSSL) is used by default, unless a X.509 certificate has been generated for Security Center in Sockets keys.

Locum SafeSurvey uses ports 28348 (nonSSL) and 28349 (SSL), Locum SecureAudit uses ports 28350 (non-SSL) and 28351 (SSL), Locum RealTime Config uses port 56287, and Locum RealTime Monitor uses port 56288.