Lotus Domino Administrator 8 Help - Checking TCP/IP name resolution in NRPC

TROUBLESHOOTING

Checking TCP/IP name resolution in NRPC
If checking connectivity using an IP address appears to work, you need to check name-to-IP-address resolution. Name-to-IP address resolution within an organization's private network space usually takes one of two forms: locally stored hosts files or the Domain Name System (DNS). WINS Name Resolution or LMHOSTS resolution are not supported by IBM® Lotus® Notes® or IBM® Lotus® Domino™.

1. Check for illegal characters in the hosts file.

Make sure there are no illegal characters (such as a space or a letter) in the numeric IP address; only numbers should appear. Each section of a dotted decimal numeric IP address should be no longer than three numbers, and there should be four sections to an address (for example, 19.99.21.217).
Make sure there are no illegal characters in the Names fields; only alphabetic characters, numbers and dashes (-) should appear. Spaces are not allowed. Underscores (_) are mapped as spaces within Notes, and should be avoided.
Some IP stacks will not accept underscore characters.
Make sure there is only one correctly named hosts file being used. Rename any other hosts files on the computer (except the current one).

Note any recent changes made to the hosts file. Confirm that the information in the hosts file is correct. The target machines that a computer may contact must be defined in the local hosts file.

Operating System	Location	Explanation
Macintosh	Macintosh System Folder	Not applicable
UNIX®/Linux®	/etc/	Not applicable
Microsoft® Windows® 2000	system32 directory	Root directory might vary
Windows XP	windows\system32\drivers\etc\	The OS directory might be renamed

2. Look at the Server document and determine if the first part of the server's fully qualified domain name (FQDN) in the TCP/IP port's Net Address field is the same as the server's common name. For example:

FQDN = mailhub1.lotus.com
Server common name = Mailhub1

If this is not the case, a name resolution alias is required in the hosts file or DNS table.

Note If the first part of the FQDN is the same as the server common name, the problem may be within DNS. For more information, see the vendor's documentation for the DNS server.

3. If the Server document has changed recently, restart the server in order for the changes to take effect.

After you finish checking name resolution, see the topic Checking a TCP/IP network pathway.

Glossary

Feedback on Help or Product Usability?

Help on Help

All Help Contents

Glossary