CONFIGURING


Confirming that TCP/IP is configured properly
Before you can use TCP/IP for communication, confirm that the configuration is properly set up.

Procedure

1. Use the ping command with the remote system's TCP/IP address -- for example, ping 192.9.200.1. If this is unsuccessful, the TCP/IP software is not properly installed and configured. TCP/IP must be working before you can use it. Contact the TCP/IP software vendor or operating system vendor if you need assistance.

2. Use the ping command with the FQDN of the remote server -- for example, ping mail05.boston.renovations.com. If this is unsuccessful, the host-name-to-IP-address translation isn't working. If you can't ping by host name, the server or workstation will not be able to communicate with the server running on the remote system.

3. If you use a local hosts file, make sure that it contains the server name and IP address of every IBM® Domino® server with which you want to communicate.

4. If you use DNS, make sure that you have properly configured the TCP/IP software on this system to query the correct DNS server. Make sure that your DNS records include the server name and IP address of every Domino server with which you want to communicate.


5. If you use the Network Information Service (NIS), make sure that you have properly configured the UNIX™ system for NIS. Make sure that the NIS hosts map contains the server name and IP address of every Domino server with which you want to communicate.

6. Depending on your name-resolution practices, do one of the following:

Related tasks
Ensuring DNS resolves in advanced TCP/IP configurations
Ensuring DNS resolves in NRPC
Ensuring DNS resolves on Windows systems -- All TCP protocols
Ensuring DNS resolves in NRPC -- Alternative practices
Ensuring DNS resolves in NRPC -- Best practices