Monitoring the status of the Failover Server service. Remote interconnected sites ( Milestone Interconnect ICP)įailover Server service and Failover Recording Server serviceĬommunication between failover recording server services.įailover Recording Server Manager tray icon, local connection only.įailover Server Manager tray icon, local connection only.In addition to the inbound connections to the Recording Server service listed above, the Recording Server service establishes outbound connections to: Listening for event notifications from the drivers. In XProtect 2019 R2 systems and older, the port number was 7474. In XProtect 2014 systems or older, the port number was 6474. Additional ports will be 9002, 9003, etc. If multiple Recording Server instances are in use, every instance needs its own port. Recording Server Manager tray icon, local connection only. Retrieving video and audio streams, PTZ commands. Merging of databases after a failover recording server had been running. (Deprecated) Enabling this will open a port for non-encrypted connections and is not recommended. Listening for event messages from devices. *A 403 error will be returned when accessing HTTP to access an HTTPS-only endpoint. XProtect Smart Client and the Management ClientĬonfiguration, events, alarms, and map data.Įvent/State Subscription, Events REST API and Alarms REST API.
Only relevant if the Analytics Events feature is enabled. Listening for analytics events from external systems or devices. Only if the relevant data source is enabled.Īny system or device that sends analytics events to your XProtect system.
Listening for generic events from external systems or devices. On other computers: Data Collector service on the Management Server.Īny server sending generic events to your XProtect system. On the management server computer: Data Collector services on all other servers. Storing and retrieving log entries via the Identity Provider. Storing and retrieving events via the Identity Provider. Storing and retrieving configurations via the Identity Provider. In XProtect 2019 R2 systems and older, the port number was 7475. In XProtect 2014 systems or older, the port number was 6475. You can change the port number in the Management Client.Ĭommunication with the SNMP extension agent.ĭo not use the port for other purposes even if your system does not apply SNMP. Web service for internal communication between servers.Ĭommunication between the system and Matrix recipients. Management Server Manager tray icon, local connection only.Ĭommunication between internal processes on the server.
#SCREENS 4 PUBLIC UDP PORTS WINDOWS#
The communication from the event server to the management server uses Windows Secured Framework (WCF) and Windows authentication on port 80. When you have secured the communication with certificates, the VMS uses port 443 except for communication from the event server to the management server. When you have not secured the communication with certificates, the VMS uses port 80. However, which port the VMS uses depends on whether you have used certificates to secure the communication. The purpose of port 80 and port 443 is the same. Management Server service and related processesĪll servers and the XProtect Smart Client and the Management Client To figure out which ports need to be opened on a particular computer, you need to consider all services running on the computer. Contact Milestone support, if you need to change ports that are not configurable through the Management Client.Įach of the following sections list the ports that need to be opened for a particular service. The port numbers are the default numbers, but this can be changed. These are not explicitly listed in this doc.
If nothing else is mentioned, ports for server components must be opened for inbound connections, and ports for client components must be opened for outbound connections.ĭo keep in mind that server components can act as clients to other server components. Outbound connections are typically open by default in the Windows Firewall Therefore, these ports need to be opened for outbound connections. Client components (clients) initiate connections to particular ports on server components.Therefore, these ports need to be opened in the Windows Firewall for inbound and outbound connections Server components (services) offer their service on particular ports which is why they need to listen for client requests on these ports.
The lists also include the ports used for local processes. To ensure, for example, that the firewall blocks only unwanted traffic, you need to specify the ports that the system uses. All XProtect components and the ports needed by them are listed below.
0 kommentar(er)
