What ports does Tarantella use?

This page lists the ports used by Tarantella and their purpose. It also lists the direction and protocol information needed to configure firewalls for use with Tarantella. The ports are divided into ports used for:

connections between client devices and Tarantella servers;
connections between Tarantella servers and application servers;
connections between Tarantella servers; and
Netlet connections to a Tarantella server.

Ports used for connections between client devices and Tarantella servers

Source	Destination	Destination port	Purpose
Client	Web server on the Tarantella host	80/tcp	Standard, unencrypted HTTP requests and responses used to display webtops.
Client	Web server on the Tarantella host	443/tcp	Secure, encrypted HTTPS requests and responses used to display webtops.
Client	Tarantella server	3144/tcp	Standard, unencrypted connections used for control and application display updates.
Client	Tarantella server	5307/tcp	SSL-based secure, encrypted connections to Tarantella servers which are using the Tarantella Security Pack. Used for control and application display updates.

Notes

Client devices must be able to access the web server on any host on which Tarantella is installed.
If you are using Tarantella in "firewall forwarding mode", all the traffic that would normally flow through ports 443 and 5307 flows only through the firewall forwarding port, which is usually port 443.
Ports 80 and 443 are registered ports for web servers.
Ports 3144 and 5307 are ports registered for use only by Tarantella.

Ports used for connections between Tarantella servers and application servers

Source	Destination	Destination port	Purpose
Tarantella server	Application server	22/tcp	Used to connect to X and character applications using Secure SHell (SSH).
Tarantella server	Application server	23/tcp	Used to connect to Windows, X and character applications using telnet.
Application server	Tarantella server	137/udp	Used for WINS services with client drive mapping. The server binds to this port at start-up only if WINS services are currently enabled.
Tarantella server	Windows server	137/udp	Required for NT login authority to work.
Application server	Tarantella server	139/tcp	Used for client drive mapping services. The server binds to this port at start-up, whether or not client drive mapping services are currently enabled.
Tarantella server	Windows server	139/tcp	Required for NT login authority to work.
Tarantella server	LDAP directory server	389/tcp	Used to authenticate users and/or provide webtop content using LDAP.
Tarantella server	Application server	512/tcp	Used to connect to X applications using rexec.
Tarantella server	Application server	513/tcp	Used to connect to X or character applications using rlogin.
Tarantella server	Application server	514/tcp	Used to connect to Windows or X applications using rcmd.
Application server	Tarantella server	515/tcp	Used to send print jobs from the application server to a Tarantella server.
Tarantella server	LDAP directory server	636/tcp	Used to authenticate users and/or provide webtop content using SSL-based LDAP (LDAPS).
Tarantella server	RSA SecurID/ACE Server^®	1024/udp to 65535/udp	Used to authenticate users using SecurID/ACE.
Tarantella server	Application server	3389/tcp	Used to connect to Windows applications configured to use the Windows Terminal Services protocol.
Tarantella server	Application server	3579/tcp	Used for connections between the primary Tarantella server and the Tarantella load balancing service running on an application server.
Application server	Tarantella server	3579/udp	Used for connections between the Tarantella load balancing service running on an application server and the primary Tarantella server.
RSA SecurID/ACE Server	Tarantella server	5500/udp	Used to authenticate users using SecurID/ACE.
Tarantella server	Application server	5999/tcp	Used to connect to Windows applications, if the application configured to use the Wincenter protocol and the connection method is telnet.
Application server	Tarantella server	6010/tcp and above	Used to connect X applications with the protocol engines running on the Tarantella server.

Notes

Ports 22, 23, 512, 513, 514, 3389 and 5999 only need to be opened if they are required to run applications through Tarantella. The ports actually used depends on the application type, the connection method used to log in to the application server and (for Windows applications) the protocol used.
Ports 137 and 139 may be used by products providing Windows file and print services, such as Samba or SCO VisionFS. You only need to open these ports if you are using client drive mapping or the NT login authority.
Ports 389/636 are only required if you are using an LDAP directory server.
Ports 1024 to 65535 are only required if you are using the SecurID login authority. For the RSA ACE/Server^® to communicate to the RSA ACE/Agent^® through a firewall, all ports from 1024 to 65535/udp must be open from the Master and Slave IPs to the Agent IPs.
Ports 3579 tcp and udp are ports registered for use only by Tarantella. You only need to open these ports if you are using Tarantella Advanced Load Management.
Port 5500 is only required if you are using the SecurID login authority. For the RSA ACE/Agent to authenticate to the Master ACE/Server through a firewall, port 5500/udp must be open from the Agent IP to the Master and Slave IP.

Ports used for connections between Tarantella servers

Source	Destination	Destination port	Purpose
Tarantella server	Another Tarantella server	5427/tcp	Used for connections between Tarantella servers to allow array replication and sharing of both static and dynamic data across the array.

Notes

Connections on port 5427 are required to establish and run arrays.
All array members must be able to connect to any other member of the array.
Port 5427 is registered for use only by Tarantella.

Ports used for Netlet connections to a Tarantella server

Source	Destination	Destination port	Purpose
Sun™ ONE Portal server	Web server on the Tarantella host	80/tcp	Standard, unencrypted HTTP requests and responses used to display webtops.
Sun™ ONE Portal server	Tarantella server	3144/tcp	Standard, unencrypted connections used for control and application display updates.
Client	Netlet applet	4000/tcp, 4002/tcp ...	Used for login and control. One port for each Tarantella array member.
Client	Netlet applet	4001/tcp, 4003/tcp ...	Used for application connections. One port for each Tarantella array member.
Tarantella Native Client	Netlet applet	8087/tcp	Used to connect the Native Client to the Netlet applet.
Sun™ ONE Portal server	Tarantella server	30144/tcp	Used for Netlet-originated connections to a Tarantella server. The Gateway on the Portal Server connects to port 30144 on the Tarantella server.

Notes

You only need to open port 30144 if you are using the Netlet to secure Tarantella network traffic.
The Netlet applet is on the client and so firewalls should not interfere with client to Netlet applet connections.
Port 8087 is only used if you are using a Native Client with the Netlet. It is added to the Netlet rules by default. You can remove this rule if you are not using Native Clients with the Netlet.

Related topics
Security and Tarantella Using Tarantella with firewalls What is an array? Introducing application server load balancing