Sametime Community Server ports
The IBM® Sametime® Community Server listens on various ports for HTTP Services, Domino® Services, LDAP Services, Sametime and server-to-server communications.
Sametime Community Server
| Default Port | Purpose |
|---|---|
| 80 | The Sametime Community Server listens for the Sametime System Console on port 80. If you allow HTTP tunneling on port 80 during the Community Server installation, the Community Services multiplexer on the Community Server listens for HTTP connections from web browsers, and Sametime Connect Client clients on port 80. If you do not allow HTTP tunneling on port 80 during the Community Server installation, the Domino HTTP server listens for HTTP connections on this port. |
| Alternate HTTP port (8088) | If you allow HTTP tunneling on port
80 during the Community Server installation or afterward, the Domino HTTP server on which the
Community Server is installed must listen for HTTP connections on
a port other than port 80. The Sametime installation changes
the Domino HTTP port from
port 80 to port 8088 if the administrator allows HTTP tunneling on
port 80 during a Community Server installation. Note: If
you allow HTTP tunneling on port 80 during the Community Server installation,
web browsers make HTTP connections to the Community Services multiplexer
on port 80, and the Community Services multiplexer makes an server-to-server
connection to the Sametime HTTP
server on port 8088 on behalf of the web browser. This configuration enables the Sametime Community Server to support HTTP tunneling on port 80 by default following the server installation. |
| 389 | The Community Server connects to the LDAP server on this port. |
| 443 (if configured) | The Domino HTTP
server listens for HTTPS connections from the Sametime System Console
on this port by default. This port is used only if you have set up the Domino HTTP server to use Secure Sockets Layer (SSL) for web browser connections. |
| 1352 | The Domino server on which Sametime is installed listens for IBM connections from Notes® clients and Domino servers on this port. |
| 1516 | Notes NRPC. The Community Server listens for direct TCP/IP connections from other Community Servers on this port. If you installed multiple Community Servers, 1516 must be open for presence, chat, and other Community Services data to pass between the servers. |
| 1533 | Community Services
listens for direct TCP/IP connections and HTTP-tunneled connections
from the Community Services clients (such as Sametime Connect
Client and Sametime Meeting Room clients)
on this port. Community Services also listens for HTTPS connections from clients on this port by default. The Community Services clients will attempt HTTPS connections when accessing the Community Server through an HTTPS proxy server. If you do not allow HTTP tunneling on port 80 during the Sametime installation, the Community Services clients attempt HTTP-tunneled connections to the Community Services on port 1533 by default. |
| 8082 (if configured) | When HTTP tunneling
support is enabled, the Community Services clients can make HTTP-tunneled
connections to the Community Services multiplexer on port 8082 by
default. Community Services clients can make HTTP-tunneled connections
on both ports 80 and 8082 by default. Port 8082 ensures backward compatibility with previous Sametime releases. In previous releases, Sametime clients made HTTP-tunneled connections to the Community Services only on port 8082. If a Sametime client from a previous Sametime release attempts an HTTP-tunneled connection to a Community Server, the client might attempt this connection on port 8082. |
| 9092 | The Event server port on the Community Server is used for server-to-server connections between Sametime components. Make sure that this port is not used by other applications on the server. Generally, it is only necessary to change this port if you have installed multiple Sametime Community Servers on a single server computer or if another application on the server uses port 9092. If you run Sametime on a Linux™ computer, you can install multiple Sametime Community Servers on a single computer, within the same logical partition. Each Sametime Community Server instance runs on a separate partitioned IBM Domino server. If you run Sametime Community Server on Microsoft™ Windows™, you can only install one server on each Windows computer. If multiple Sametime Community Servers are running on the same computer, you must ensure that each Sametime Community Server specifies a different port as the Event server port. For example, if Sametime Community Server 1 and Sametime Community Server 2 are running in separate partitions of the same computer, you can specify port 9092 as the Event server port for Sametime Community Server 1 and port 9095 as the "Event server" port for Sametime Community Server 2. |
| 9094 | The Token Server port on the Sametime Community Server is used for server-to-server connections between Sametime components. Generally, it is only necessary to change this port if you have installed multiple Sametime Community Servers on a single server computer or if another application on the server uses port 9094. If you run Sametime on a Linux computer, you can install multiple Sametime Community Servers on a single computer within the same logical partition. Each Sametime Community Server instance runs on a separate partition of the IBM Domino server. If you run Sametime on Microsoft Windows, you can only install one server on each Windows computer. If multiple Sametime Community Servers are running on the same computer, you must ensure that each Sametime Community Server specifies a different port as the Token server port. For example, if Sametime Community Server 1 and Sametime Community Server 2 are running in separate partitions of the same computer, you might want to specify port 9094 as the Token server port for Sametime Community Server 1 and port 9096 as the Token server port for Sametime Community Server 2. |