Lotus Domino Administrator 8 Help - Checking the Domino Directory for errors that affect server access

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 tab Check this

Server name Make sure that the full hierarchical server name is spelled correctly.

Domain name Make sure that the name is spelled correctly.

Port If a COM port is listed, remove it. X.PC COM ports are only handled in the ports configuration section.

Notes Network Make sure that at least one IBM® Lotus® Notes® Network is enabled. Each port requires a unique Notes network name.

Field on the Restrictions tab Check this

Access server Delete 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 server Delete 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.

After you create the new Server document,

copy the public key into it

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:

Load updall names.nsf -r

If you suspect that the Domino Directory is corrupted, do one of the following:

Run the Fixup task. Use this task if the database is in Domino 5 or higher format and if you're not using transaction logging, or if the database is in Domino 4 format.
Run the Fixup task with the -J option. Use this task if the database is in Domino 5 or higher format and you are using transaction logging. If you use a backup utility certified for Domino 5 and you run Fixup -J, perform a full backup of the database as soon as Fixup finishes.

In addition, if you suspect a corrupted Domino Directory, try using a backup of the Domino Directory (if one is available), or create a new replica of the Domino Directory.

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.

Passthru connections -- Troubleshooting

Server access -- Troubleshooting

Glossary

Feedback on Help or Product Usability?

Help on Help

All Help Contents

Glossary

Field on the Network Configuration tab	Check this
Server name	Make sure that the full hierarchical server name is spelled correctly.
Domain name	Make sure that the name is spelled correctly.
Port	If a COM port is listed, remove it. X.PC COM ports are only handled in the ports configuration section.
Notes Network	Make sure that at least one IBM® Lotus® Notes® Network is enabled. Each port requires a unique Notes network name.

Field on the Restrictions tab	Check this
Access server	Delete 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 server	Delete 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.