Confirming that TCP/IP is configured properly (2024)

Procedure

1. Use the ping command with the remotesystem's TCP/IP address -- for example, ping 192.9.200.1. If thisis unsuccessful, the TCP/IP software is not properly installed andconfigured. TCP/IP must be working before you can use it. Contactthe TCP/IP software vendor or operating system vendor if you needassistance.
2. Use the ping command with the FQDN ofthe remote server -- for example, ping mail05.boston.renovations.com.If this is unsuccessful, the host-name-to-IP-address translation isn'tworking. If you can't ping by host name, the server or workstationwill not be able to communicate with the server running on the remotesystem.
3. If you use a local hosts file, make sure that it containsthe server name and IP address of every HCL Domino® server withwhich you want to communicate.
4. If you use DNS, make sure that you have properly configuredthe TCP/IP software on this system to query the correct DNS server.Make sure that your DNS records include the server name and IP addressof every Domino® server withwhich you want to communicate.

   Note: Makesure that your IP host names do not contain illegal characters suchas spaces, underscores ( _ ), or ampersands (&).

5. If you use the Network Information Service (NIS), makesure that you have properly configured the UNIX™ system for NIS. Make sure that the NIShosts map contains the server name and IP address of every Domino® server with which youwant to communicate.
6. Depending on your name-resolution practices, do one ofthe following:
   • If your Domino® servernames are the same as the DNS host names, make sure you have followedthe instructions in the following topics (see the related links):
     • Ensuring DNS resolves on Windows™ systems
     • Ensuring DNS resolves in NRCP
     • Ensuring DNS resolves in advanced TCP/IP configurations
   • If your Domino® servernames are different from the DNS host names, use the ping commandto verify that all of the DNS names which represent the Domino® server are responding from the correctnetwork areas, as well as the Domino® servername, if needed.
   • If you are using IP addresses in Connection documents, use the ping commandto verify the IP address itself.
   • If you are using network address translation (NAT), verify thataccess is possible from both the internal network and external Internetusing the appropriate IP addresses. If you are using name-resolverservices, make sure that the external DNS offers out the public addressand the internal DNS offers out the private address.