TROUBLESHOOTING


Checking the Domino Directory for errors that affect server access
Many conditions that prevent proper access to servers can be traced to the Domino Directory.

1. Verify that these fields in the Server document contain the correct information and spelling. For each change you make, be sure to save the Server document before attempting to access the server again.
Field on the Network Configuration tabCheck this
Server nameMake sure that the full hierarchical server name is spelled correctly.
Domain nameMake sure that the name is spelled correctly.
PortIf a COM port is listed, remove it. X.PC COM ports are only handled in the ports configuration section.
Notes NetworkMake sure that at least one IBM® Lotus® Notes® Network is enabled. Each port requires a unique Notes network name.
Field on the Restrictions tabCheck this
Access serverDelete the contents of this field if it contains any information. Only those names or groups listed in the field are allowed to access the server.
Not access serverDelete the contents of this field if it contains any information. The users or groups listed in the field are not allowed to access the server.


2. Make sure the Server document isn't corrupted. To determine if it is corrupted, create a new Server document and use it instead of the old one. If the new Server document resolves the problem, it's likely that the original Server document is corrupted. Be sure to create a backup of the original Server document by either copying and pasting the original into another Server document or by backing up the database.
3. Verify that the Certified public key in the server ID file is the same as the Public key. To do this, copy the certified key and paste it into a text file, and then compare the two key values, which should be the same. If the values differ, the server ID was probably created with the same name based on a different Certifier key. Before altering the key, create a backup of the Domino Directory.

4. Check Group documents in the Domino Directory for correct user and server names. In particular, check the Group documents for groups listed in the "Access server" and "Not access server" fields in the Server document. In addition, be sure to check the Group Type setting of these Group documents. The Group type assigned to a group can affect server access.

5. Resolve any replication or save conflicts in the Groups and People views.

6. Make sure that all views in the Domino Directory are updated and not damaged. To rebuild all of the views in that database, enter this command at the console:


7. Replace the design of the Domino Directory. Select File - Application - Replace Design. This ensures that the Domino Directory is using the correct template file (PUBNAMES.NTF).

8. Check Server document form in the Domino Directory for customizations that are not supported.

9. Make sure that passthru is properly enabled on the Server document.

Related topics