Which Network Ports & Hosts Does a Control4 System Use?

August 17, 2026 by

Tabita Castro

Ports used within Control4 system communication

ssh	22	tcp	# SSH
telnet	23	tcp	# Telnet - no longer used
send-mail	25	tcp	# Mail email Notification
tftp	69	udp	# Firmware Update TFTP
www	80	tcp	# HTTP - update downloads & and other Web Services
ntp	123	tcp	# Network Time Protocol
https	443	tcp	# Remote Access
syslog	514	udp	# System Logging Daemon
snmpd	705	tcp	# Simple Network Management Protocol Dameon
ssdp	1900	udp	# SSDP Multicast Discovery Port
ssdp	1901	udp	# SSDP Firmware Multicast Discovery Port
sddp	1902	udp	# SDDP Multicast Discovery Port
turn balancer	3478	tcp	# TURN Balancer
turn server	5000	tcp	# TURN Server
turn server	5001	tcp	# TURN Server
director	5020	tcp	# Director - unsecure
director	5021	tcp	# Director - secure port for ssl
sip server port	5080	tcp/udp	# SIP Server Port
sip server port	5081	tcp	# SIP Server Port
ioserver	5100	tcp	# Device IO Server
ioserver-s1	5101	tcp	# Device Serial Port 1 Data Channel
ioserver-s2	5102	tcp	# Device Serial Port 2 Data Channel
ioserver-s3	5103	tcp	# Device Serial Port 3 Data Channel
zserver	5105	tcp	# Zigbee Server - EmberNet (1.7.4 and prior)
netusb	5110	tcp	# Net USB Server (mounts shares and tracks USB devices)
upmand	5111	tcp	# Update Manager
navigator	5115	tcp	# Navigator
c4server	5116	tcp	# Button - identification
DeviceAdministrator(MIBs)	5117	tcp	#T3's and Android on EA controllers only
zserver	5205	tcp	# telnet localhost 5205 Embernet Updater Zserver
navigator	5215	tcp	# Navigator
Rhapserver	5555	tcp	# Rhapsody Server
sysman	5800	tcp	# System Manager
sysman secure	5810	tcp	# System Manager Secure
device administrator (ssl)	5811	tcp	# Service Administrator (ssl) - EA Controllers Only (Navigator)
audioserver	6000	tcp	# Audio Server
audioclient	6100	tcp	# Audio Client Control Channel
stream1	6200	tcp	# Audio Client Data Stream 1
stream2	6201	tcp	# Audio Client Data Stream 2
stream3	6202	tcp	# Audio Client Data Stream
stream4	6203	tcp	# Audio Client Data Stream
amgserver	6500	tcp	# AMG and C4lookup - media lookup server
intercom	6700	tcp	# intercom
shaird/sharport-sync	6750-6790	tcp	# shaird/shairport-sync
imaged	6800	tcp	# imaged daemon
zserver2	7900	tcp	# ZigBee Server - ZigBee Pro
zap	7910	tcp	# ZigBee Access Point - ZigBee Pro
mib	8750	udp	# Firmware MIB
raproxy	25021	tcp	# Remote Access SSL Proxy Server
turn servers	see below	tcp	# turn servers

SAMBA file sharing

netbios-ns	137	udp	# NetBIOS Name Service
netbios-dgm	138	udp	# NetBIOS Datagram Service
netbios-ssn	139	tcp	# NetBIOS Session Service
microsoft-ds	445	tcp	# Microsoft Directory Service

Ports used by Rhapsody service

TCP 80, 554, 4040, 7070, 8080, 443 (Secure Socket Layer for sign in), 1755 (MMS Windows Media requests)

UDP 6970-32,000, 1755 (MMS Windows Media resend requests)

HTTP 80 (AutoUpdate, Messaging Service, and HTTP Cloaking)

Rhapsody Direct servers require:

Ports 80 (metadata, search, and RAD requests) & 443 (library, playback, admin requests) to communicate with your Rhapsody Direct device

ATTENTION: Control4 does not recommend or support port forwarding systems as a means of remote access. Control4 offers an extremely secure solution in the form of 4Sight and Anywhere Access.

For further details please see the following links:

Do not use Port Forwarding

CE Pro article about Shodan web-crawler

This is a list of hosts and ports that need to be reachable from our controllers.

Additionally, controllers must be able to receive UDP return packets from remote.control4.com from UDP 5080 without being fragmented.

Most services are hosted in AWS

Exceptions (IP block: 204.246.138.128/25): w2-prod-slc (weather) and drivers

rms2.control4.com

54.89.100.174 (C4 controller patch management and diagnostics)