Network requirements

Most signage deployment delays are network delays — a player that can't reach the CMS through a corporate firewall. Sorting requirements with IT up front avoids the classic "screens won't activate" launch day.

The basics

Players need outbound internet to the CMS, working DNS to resolve it, and accurate time via NTP (schedules and certificates depend on the clock being right). They generally do not need inbound connections — a key security point.

Ports & firewall

Typically players need outbound 443 (HTTPS) and 80 (HTTP), 53 (DNS) and 123 (NTP). On restrictive networks, allowlist the CMS and content domains rather than opening everything. Confirm the exact endpoints with your platform and, for security, segment signage onto its own VLAN — see security best practices.

Wi-Fi vs wired

Wired Ethernet is more reliable and preferred for fixed screens; Wi-Fi suits hard-to-cable locations but needs solid coverage at the screen (not just nearby). For critical screens, plan a connectivity failover such as cellular backup.

IT checklist

• Outbound 443/80, 53, 123 open or allowlisted.
• CMS & content domains allowlisted on restrictive networks.
• DNS + NTP reachable and correct.
• Dedicated VLAN, no inbound required.
• Bandwidth planned — see bandwidth planning.

Frequently asked questions

What ports does digital signage need?
Typically outbound 443 (HTTPS) and 80, plus 53 (DNS) and 123 (NTP). Players usually need no inbound connections. Allowlist the CMS and content domains on restrictive networks.

Wired or Wi-Fi for signage?
Wired Ethernet is more reliable and preferred for fixed screens; use Wi-Fi only with strong coverage at the screen, and add cellular failover for critical displays.

Why do screens fail to activate on a corporate network?
Usually a firewall blocking outbound access to the CMS, or DNS/NTP not reachable. Allowlist the required endpoints and confirm time sync.