We are having an issue with a few servers that have changed IP or DNS in the past few weeks. The server listed in this trace (NotesSTR) has had a DNS change, but the change has not followed into Domino. The following trace:
trace notesstr
Determining path to server NOTESSTR
Available Ports: TCPIP
Checking normal priority connection documents only…
Allowing wild card connection documents…
Enabling name service requests and probes…
Address found in local TCPIP names table for NOTESSTR
‘Address found in local TCPIP names table’ - sounds like the local hosts file. If not:
I would start on one of the servers:
Step1:
Ping (OS) for both, none hierarchical Servername and DNS name works (yes the machine pinging itself)? (IF not, check local hosts file, too)
Step2:
Can the server be reached from a client on the same machine? (could be a browser, if the http runs, or a Client installed on the server
Serverdocument (if you change anything there, domino needs a restart).
Connection documents on the client
Step3:
Step 1 and 2 for another server (and on this other server)
Step4:
Can one Server ping the other one (Servername in DNS and none hierarchical Servername) - both directions. As the servers can’t reach each other, there is no replication of names.nsf, and every server checks usually only its own one.
Step5
can the client on each of the servers reach each of the other servers.
Tips:
Changing something in the server document is not effective before domino gets restarted.
If you change anything else in the directory (names.nsf), Crtl-Shift-F9 to refresh all views before restarting might make a difference (at least this was true historically).
Restarting the server should be good for all the other commands (caches and alike) you descripe, too - there is no help in typing them into the console over and over.