IBM Lotus Sametime 7.5.1 | Release Notes |
Services connections on ports 443 or 563. This design in the Sametime 2.5 server accomodates the multiple IP address issues discussed in "Connecting to the Community Services on port 443 when the Domino HTTP server is configured to listen for SSL connections on port 443" above.
The Sametime 2.5 Connect client is also hard-coded to prepend the string "Community-" to its Host setting when its "Community port" setting specifies port 443 or 563. For example, assume the following settings exist in the Sametime Connectivity tab of a Sametime 2.5 Connect client:
zHost - "sametimeserver1.acme.com"
zCommunity port - Either port 443 or port 563 is specified.
With this configuration, the Sametime 2.5 Connect client attempts the connection to the server name "Community-sametimeserver1.acme.com" even though the string "sametimeserver1.acme.com" is entered in its Host setting.
Because the Sametime 2.5 Connect client automatically prepends the string "Community-" to its host name, it is not necessary to enter the string "Community-servername" in the Sametime 2.5 Connect client when this client connects to a Sametime 7.5.x server that is configured to listen for HTTPS connections on multiple IP addresses.
Note also that when a Sametime 7.5.x server listens for HTTPS-tunneled connections from Sametime 2.5 Connect clients, the additional DNS name assigned to the Community Services on the Sametime 7.5.x server must begin with the "Community-" string, as described in "Connecting to the Community Services on port 443 when the Domino HTTP server is configured to listen for SSL connections on port 443" above. If the Sametime 7.5.x Community Services DNS name does not begin with the "Community-" string, the Sametime 2.5 Connect client cannot connect to the Sametime 7.5.x server.
Sametime 7.5.x Connect client compatibility issue when connecting to a Sametime 2.5 server on port 443 or 563
If a Sametime 7.5.x Connect client connects via HTTPS-tunneling to a Sametime 2.5 server on port 443 or 563, the Sametime 7.5.x Connect client does not prepend the "Community-" string to its host name when making the connection to the Sametime 2.5 server.
The Sametime 2.5 server is hard-coded to prepend the string "Community-" to its server name when listening for HTTPS connections on port 443 or 563. To ensure the Sametime 7.5.x Connect client can connect to the Sametime 2.5 Community Services on port 443 or 563, the string "Community-" must be manually added to the Host name in the Sametime Connectivity tab in the Sametime 7.5.x Connect client.
Manually adding the "Community-" string to the Host name in the Sametime 7.5.x Connect client ensures that the client attempts the connections on the name on which the Sametime 2.5 server listens for the connections.
For example, to ensure a Sametime 7.5.x Connect client can connect on port 443 or 563 to the Sametime
2.5server named "sametimeserver1.acme.com," the following settings must exist in the Sametime Connectivity tab of the Sametime 7.5.x Connect client:
zHost - "Community-sametimeserver1.acme.com."
zCommunity port - Either port 443 or port 563 is specified. (Specify the port on which the Sametime 2.5 server listens for HTTPS-tunneled connections).
Community Services multiplexer on Sametime 7.5.x server does not forward HTTPS connections on port 443 to the Domino HTTP server
A Sametime 7.5.x server can simulaneously listen for HTTP connections to multiple services on port 80 when the Sametime server machine includes a single IP address. For example:
zA Web browser can connect to the Domino HTTP server on a Sametime server on port 80.
zA Sametime Connect client can make an HTTP-tunneled connection to the Sametime
