TROUBLESHOOTING

"TCP/IP host unknown" and "Remote system not responding"
Messages such as "TCP/IP host unknown" and "Remote system not responding" usually indicate problems with the TCP/IP setup. If you have a direct Internet connection and are able to use the IP address to ping the remote host successfully, the Web Navigator may not be running. If you use host names instead of actual IP addresses in Connection documents, there may be a problem with name resolution. To fix this problem, check the hosts file to verify that your domain name system (DNS) can resolve the name to the IP address. If you do not have a DNS, add the entry to the server's local hosts file, which maps host names to IP addresses. The hosts file is usually located in the same directory as the protocol software. It has a format similar to:
Domino server nameIP Host nameIP Fully Qualified Domain NameIP AddressComment
Salt/Sales/Acmesaltsalt.usa.com123.3.12.24.5#Salt server
Pepper/Support/Acmepepperpepper.usa.com123.3.12.678#Pepper server
If the host name is the Domino server's common name, then the hosts file or DNS will require an alias link as shown here:
Domino server nameIP Host nameIP Fully Qualified Domain NameIP Alias name entryIP Address Comment
Red/Marketing/Acmerubyruby.usa.comred within the host file or red CNAME ruby for the DNS 123.3.12.212#Red server
Purple/IS/Acmevioletpepper.usa.compurple within the host file or purple CNAME violet for the DNS123.3.12.83#Purple server
See also