User gets error message: "Sametime server is unreachable or not configured properly" when trying to login.
If this is just for one user, check out causes 1, 2, and 3. If everyone is having the problem, check out causes 3, 4, and 5.
1. Password incorrect in person document
2. Password "corrupt" in person document. By corrupt I mean that the user can still login via web browser but not via embedded or stand-alone ST client.
3. Incorrect Sametime server entry in the person document.
4. Sametime server has been removed from a ST cluster, but the server still contains a Cluster Information document in the stconfig.nsf database.
5. ST Server field set in person docs via an agent. The agent used the abbreviated format.
1. Reset the password. Refresh the Directory views (Ctrl-Shift-F9) or wait until the server's update task updates the view indexes.
2. Reset the password. Refresh the Directory views (Ctrl-Shift-F9) or wait until the server's update task updates the view indexes.
3. Complete the entry. Use the abbreviated canonical name. (e.g. enoch/Mindwatering).
Note: I have seen cases where this would make it not work when DNS is not properly functioning. Basically, the servers and clients have to resolve the server. Verify that the Server document's FQDN field and the port DNS entries should be valid and resolvable.
4. If no longer part of the cluster and the Cluster Information document still exists, remove the document from the stconfig.nsf. Now the ST server will use it's own name as the target for the ST clients to connect. Restart the ST server and try to connect again.
5. This is similar to 3. Basically, if you set this field via an agent, you have to use the full canonical version of the name. (e.g. CN=enoch/O=Mindwatering). If you hand enter the value, it get stored correctly in canoical format, but an agent doesn't use the GUI and has to set it with full canonical name versus the abbreviated one.