IGEL UMS Communication Ports

Which ports are used by the components of IGEL UMS and the other components of a UMS infrastructure?

Component

Service that is Listening

Port / Default Port

Type

Usage / Description

UMS server

 

30001

 

TCP/UDP

See Thin Clients Contacting UMS Server

 

UMS server (UMS HA)

 

(High Availability)

30002

TCP/

If both server and load balancer are running together on one system, the server switches to port 30002 and the load balancer uses 30001.

UMS (HA)

HA Load Balancer

61616

TCP/UDP

Communication between load balancer and server within UMS HA.

Thin client

UMS agent

30005

TCP/UDP

The UMS component on the thin client (UMS agent) is waiting for UMS server input on this port.

See UMS Contacting Thin Clients

UMS

GUI server

8443

TCP

Communication between UMS Console and UMS server

See UMS with Internal Database or UMS with External Database

UMS

HTTPS server

8443

 

File transfer with HTTPS

See UMS and Thin Clients: File Transfer

UMS

IGEL Management Interface (IMI)

8443

TCP

REST API for UMS

See IGEL Management Interface (IMI)

UMS

JWS Server

(Webserver)

9080

TCP

Unencrypted HTTP communication. Used for deployment of firmware updates, Java Webstart Console and file transfer if Allow SSL Connections only is deactivated.
By default, Allow SSL Connections only is activated, and port 8443 is used for firmware updates, console and file transfer.

UMS

 

auto

UDP

When scanning for thin clients, the UMS chooses a free port and includes it in the UDP packet sent to the thin client.

UMS (internal)

UMS internal

8005

TCP

Internal Communication on UMS server (localhost)

UMS (internal)

Embedded DB

1528

TCP

Communication between UMS server and internal database

See UMS with Internal Database

UMS database

Apache Derby

1527

TCP

Communication between UMS server and Derby database

See UMS with External Database

UMS database

MS SQL Server

1433

TCP

Communication between UMS server and SQL Server database

See UMS with External Database

UMS database

Oracle

1521

TCP

Communication between UMS server and Oracle database

See UMS with External Database

UMS database

PostgreSQL

5432

TCP

Communication between UMS server and PostgreSQL database

See UMS with External Database

IGEL download server

Universal Firmware

Update

443

TCP

HTTP connection to IGEL download server myigel.biz

See UMS Contacting the Download Server to Check for New Updates

 

MS Active Directory

MS Active Directory

389

TCP

Connection to Microsoft Active Directory server

LDAP

LDAP (secure LDAP)

636

TCP

Connection to LDAP server, e.g. OpenLDAP

Thin clients

Wake On LAN

9

UDP

Wake on LAN Magic Packet is sent to the clients

Thin clients

VNC client for shadowing

5900

TCP

Shadowing a thin client using the VNC protocol.

The port can be changed per session.

See UMS and Thin Clients: Shadowing

IGEL download server

HTTPS server

443

TCP

Automatic License Deployment (ALD): Contacting the IGEL update server in order to retrieve the data required for connecting to the license server.

See UMS Contacting the Download Server

IGEL licensing server

HTTPS server

443

TCP

See UMS Contacting the Licensing Server

IGEL's Terms & Conditions apply.