Skip to content
English
  • There are no suggestions because the search field is empty.

Network and System Firewall Readiness

Overview

Before commissioning begins, it is essential to confirm that all security controls — both at the network and system level — allow visability components to communicate without restriction.

Firewall rules and endpoint security tools are one of the most common causes of deployment delays. Validating these ahead of time ensures that systems can communicate as expected and allows commissioning to proceed without unnecessary troubleshooting.

But the goal here is simple: You do not need to change your organization’s security model — only ensure that:

👉 Required communication is allowed from end to end

This includes:

  • Across the network
  • Between VLANs
  • Through firewalls
  • At the operating system level
  • Within endpoint protection policies

Network Firewall and Segmentation

Network firewalls and routing policies must allow communication between all visability components.

At a Minimum

  • Required ports below are open between all systems
  • Inter-VLAN communication is allowed where segmentation exists
  • No network-level rules are blocking communication between:
    • System Manager and Display Nodes
    • Display Nodes and source systems
    • Client interfaces and the System Manager

If systems are deployed across multiple VLANs or network segments, routing and firewall rules must be configured and validated accordingly.

Ports and Protocol List

The vis|ability platform is dependent upon specific ports and protocols. Network and desktop security allowances must be configured for this traffic to traverse the network and communicate with host systems.

The below table identifies ports for each vis|ability software module. These ports must be opened on any firewall for the respective service or application to function normally. It is recommended that you do not change these default ports.

*Minimum Ports required for Client Server communication
Protocol Listening Port Component Service/App Description
TCP/IP *59081 Nexus Service SSL/Encrypted
TCP/IP 59082 (Reserved)    
TCP/IP 59083 (Reserved)    
TCP/IP 59084 (Reserved)    
TCP/IP 59085 MUX Service RTSP Server Port
TCP/IP 59086 MUX Service RTSP over HTTP Port
TCP/IP *59087 MUX    
TCP/IP *59088 MUX    
TCP/IP 59089 MAS (optional, def. 443) Service Mobility Server
TCP/IP 59090 Unreal (1935) Service Mobility - Streaming Server IN
TCP/IP 59091 Unreal (5119) Service Mobility - Streaming Server OUT
TCP/IP *59092 MUX Service HTTPS Web Service for LiveView
TCP/IP 59093 WebClient BlazorServer (optional, def. 443) Service HTTPS Web Server
TCP/IP 59094 Interface Server Service Interface for APIs/SDKs SSL
TCP/IP 59095 Interface Server Service Interface for APIs/SDKs
TCP/IP 59096 Link Integrator Service Link REST API
TCP/IP 59097 WebPortal (optional, def. 443) Service HTTPS Web Service
TCP/IP 59098 WebHook Server (optional, def. 443) Service HTTPS POST Webhooks
TCP/IP 59099 (Reserved)    

Windows Firewall Configuration

Even when network firewall rules are correctly configured, communication can still be blocked at the system level.

Each vis|ability system must be reviewed to ensure that Windows Firewall is not preventing required traffic.

What to Validate

  • Windows Firewall is:
    • Configured to allow required visability services, or
    • Adjusted to permit necessary inbound and outbound communication
  • Required services (web access, streaming, control communication) are accessible between systems

Endpoint Protection and Antivirus Considerations

Endpoint protection platforms — including antivirus, EDR, and security monitoring tools — can interfere with visability operation if not properly configured.

These tools may block:

  • Application processes
  • Network communication
  • Streaming traffic
  • Background services

What to Validate

  • Endpoint protection or antivirus software is installed and accounted for
  • Exceptions are defined for:
    • vis|ability applications and services
    • Required network communication paths
  • Security policies do not block or quarantine vis|ability components

Common Symptoms of Security-Related Blocking

  • Systems are reachable on the network but cannot communicate properly
  • Display Nodes appear offline or fail to register
  • Streams are available but fail to load
  • Intermittent or inconsistent system behavior

These issues are often caused by local or network-level security controls rather than the visability system itself.