CueServer 2 uses several different Ethernet protocols to communicate with other devices on the network.
The following table lists each of the TCP and UDP port numbers used by CueServer’s various features and facilities:
|22||TCP||SSH||Incoming||Terminal access to CueServer’s internal command shell. This is only necessary for advanced users or factory troubleshooting.|
|23||TCP||Telnet||Incoming||[Depreciated] Terminal access to CueServer’s internal command shell. This is only necessary for advanced users or factory troubleshooting. No longer active beginning with Firmware Version 3.1|
|68||UDP||DHCP||Bidirectional||Used by DHCP service if enabled. Not active if CueServer is given a static IP address.|
|80||TCP||HTTP||Incoming||CueServer’s internal web server. Used for communication with CueServer Studio, virtual touchscreens, Insite touchscreens, user’s custom web content, and the CueServer web-based API.|
|123||UDP||NTP||Bidirectional||Used for polling Network Time Protocol servers. Only active when NTP service is enabled.|
|5568||UDP||sACN||Outgoing||Streaming ACN (sACN) data packets. This port is only active when configured to receive and/or transmit sACN protocol.|
|6038||UDP||KiNET||Outgoing||KiNET v1 and v2 data packets. This port is only active when configured to receive and/or transmit KiNET protocol.|
|6454||UDP||Art-Net||Outgoing||Art-Net data packets. This port is only active when configured to receive and/or transmit Art-Net protocol.|
|52737||UDP||CueServer||Bidirectional||Used for CueServer auto-discovery, CueScript commands, and CueStation Hub Protocol.|
Port Forwarding for CueServer Studio
To provide access to a CueServer for CueServer Studio remotely, it is only necessary to open Port 80. All communication between CueServer Studio and CueServer devices occurs over this port, with the sole exception of auto-discovery. The auto-discovery function cannot work across different networks, so it is necessary to use the “Add Remote” feature in Studio to add the CueServer to the list of available devices.