I have two Sametime 6.5.1 servers configured and working correctly, with all Sametime services starting up. I want them to appear in the same community, but this is not working. When I connect to one Sametime server, I cannot chat or attend meetings set up on the other Sametime server.
I have added the relevant connection documents on both servers, and checked the ACLs of all databases. Names.nsf is replicating between the servers, so I have some connectivity. Any ideas where else I can look? Does SSO need to be set up on the servers? Are there any documents on this subject i can refer to? I have followed all points listed in the Sametime Administrators Guide.
Check the Community options available within the SameTime administration tool. Sometimes the LIM configuration doesn't pick up that your servers are connected and doesn't automatically add them to this list for you.
Check the following steps:
1. Ensure that both LIM servers are configured on the Basics tab of the server documents with "Is this a Sametime Server?:" set to "Yes"
2. Create Sametime connection documents between the two servers -- that is, one connection from A to B, and a corresponding connection from B to A.
Initially create these Sametime connection documents as "Local Area Network", include all the information on the Basics Tab (Source and Destination Server/Domain, Port, and optional network address) and set Replication to "Disabled" and Routing to "None". Save the document and then change the connection type back to "Sametime" and choose "Allow Connections" -- "from the internet" and "from within my organisation" -- as appropriate.
3. Open the SameTime centre from a browser, such as http://yourserver.co.uk/stcenter.nsf
4. Choose the "Administer the Server" Link (log in)
5. Choose the "Configuration" twistie from the navigator and then select "Community".
6. Click on the "Servers in this community" Tab.
Now review the servers listed on this page. If you don't see any servers in this list, your Sametime servers can't see one another in the community (i.e., if you are connected to server "A", you should see server "B" in this list and vise-versa). I am expecting that neither of your servers are listed here.
For server "A":
7. Enter the canonicalised ("Notes") name of the server in the "Destination Server" field (eg: Notes01/NotesWeb).
8. Enter the IP Address, or DNS name in the "Destination server IP address" field (e.g. notes01.notes.net).
9. Click the "Add" button.
10. Click the "Update" button.
Once all these steps have been completed, you should be able to chat almost immediately with members connected to the other community servers and participate in meetings running on the other systems.
SSO is not essential, or even required here, as the Sametime servers in the "community" resolve the chat transmissions on behalf of your connected clients. In effect, you don't actually log in to the other server in the community to chat.
One final note: it may be necessary to replicate the Domino directory (names.nsf) and restart your servers for the community to be instated.
The other things to check are the open ports and/or restrictions on any firewall(s) that may exist between the two servers. Just because port 1352 is open and the NAB can replicate, that does not mean the other required ports the Sametime servers use are also open.
Do you have comments on this Ask the Expert question and response? Let us know.
Dig Deeper on Lotus Sametime Instant Messaging
Related Q&A from Mathew Newman
SearchDomino.com Sametime administration expert Mathew Newman explains-step-by-step how to enable communication between multiple Lotus Sametime ... Continue Reading
If Lotus Sametime users on different "home" servers cannot see each other online, you may need to change your Sametime server awareness by creating ... Continue Reading
SearchDomino.com's Sametime administration expert Mathew Newman offers advice to a Lotus Notes administrator looking for resources for deploying ... Continue Reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.