Network and proxy issues are the second most common category of digital
signage problems. Corporate networks add layers of complexity: proxy servers, content filtering,
802.1X authentication, VLAN segmentation, and firewall rules. A player that works perfectly on
a simple home network fails in a corporate environment because one of these layers blocks
connectivity. This guide addresses each network layer systematically.
Network Layers to Check
Layer 1: Physical
- Ethernet cable connected and link light active
- Correct patch panel port — verify switch port assignment
- Cable quality — Cat5e minimum for reliable Gigabit
Layer 2: VLAN and Switch
- Player on correct VLAN? Verify switch port VLAN assignment
- VLAN has DHCP? Player needs an IP address
- Inter-VLAN routing configured? Management station must reach player VLAN
- 802.1X required? Configure authentication in player network settings
Layer 3: IP and Routing
- Player has IP? Check via player display (information overlay) or DHCP server
- Default gateway correct? Player must route to internet for Arya/data feeds
- DNS resolving? Verify with specific domain resolution tests
Layer 4–7: Proxy and Firewall
- Proxy required? Configure proxy address, port, and credentials in player settings
- Proxy authentication? Enter credentials — some proxies require domain\username format
- Content filtering? Add required domains to the proxy allow-list
- Firewall rules? Allow outbound 443 (HTTPS), 80 (HTTP), 123 (NTP)
Required Network Access
| Service | Destination | Port | Protocol |
|---|
| Arya cloud | arya.spinetix.com | 443 | HTTPS |
| Data feeds | Various API endpoints | 443 / 80 | HTTPS / HTTP |
| NTP (time sync) | pool.ntp.org | 123 | UDP |
| DNS | Corporate DNS / 8.8.8.8 | 53 | UDP/TCP |
| Firmware updates | SpinetiX servers | 443 | HTTPS |
Key Parameters
| Parameter | Value | Why It Matters |
|---|
| DHCP | Recommended for most deployments | Automatic IP assignment |
| Proxy | Address + port + auth | Corporate network compliance |
| 802.1X | Certificate-based auth | Secure network access |
| DNS | Corporate or public | Domain name resolution |
| Firewall | Outbound 443, 80, 123 | Arya, feeds, time sync |
Common Mistakes
- Testing from your laptop instead of the player's network. Your laptop may have unrestricted internet while the player's VLAN has proxy/firewall restrictions. Always test connectivity from the player's perspective.
- Forgetting proxy authentication. Configuring the proxy address without credentials causes silent failures. All requests are blocked but the player doesn't show a clear error — it just can't reach any URL.
- VLAN misconfiguration. The player is on a different VLAN than expected — it has an IP but can't reach the internet or the management station. Verify the switch port VLAN assignment matches the network design.
- No NTP sync. Without NTP, the player's clock drifts. Scheduled content plays at wrong times, HTTPS certificate validation fails (wrong date), and log timestamps are unreliable. Ensure NTP access (port 123 outbound).
Network configuration, proxy setup, and 802.1X documentation.
