|< Day Day Up >|| |
In this section we list some problem determination aids that may help to identify and correct network issues.
For Notes and Domino to work properly with TCP/IP, the protocol stack must be configured properly. In other words, Notes connectivity relies on TCP/IP communication.
In all TCP/IP troubleshooting, first verify basic TCP/IP connectivity and configuration.
The PING executable verifies IP-level connectivity. Example 5-1 shows some examples.
Example 5-1: Examples of PING command
prompt> PING 18.104.22.168 (ping by address) prompt> PING Name (ping by Server [possibly Alias] Name) prompt> PING Name.company.com (ping by FQDN Name)
If PING fails here, TCP/IP is not set up properly on the local machine. The site's network administrators should be contacted for technical assistance.
In the server document of the Domino Directory, make sure the Notes server's common name in the TCP port's Net Address Field is the same name as the TCP Host name; see Example 5-2. If this is not the case, a name resolution alias is required in the HOSTS file or in the DNS table.
Example 5-2: Naming the server
Notes Server Name = Mail1 TCPIP Host Name = Mail1 Domain Name = company.com TCPIP Fully Qualified Domain Name = Mail1.company.com
If any of these changes are made, you must restart the involved Domino server before changes to the Server Document will be enacted.
If you are having network problems, take a look at your firewall. Some default firewalls, even those by SuSE and Red Hat, are configured to protect a workstation rather than a server. This may cause your server firewall to hold back traffic for your TCP/IP applications.
Here are other commands you may find helpful when debugging network problems.
Issue the command TRACEROUTE to determine what lies between the source and the destination of IP traffic.
The TRACEROUTE command determines the route from one host to another through a network, and displays an ordered list of the routers in the path. There is a man page (Linux manual online) with the different parameters that you can use with this command.
This utility serves as the main diagnostic tool for DNS, and is supplied with the operating system. As with DNS, you must have TCP/IP installed before you can use it. NSLOOKUP is to DNS as PING is to general IP connectivity—the first tool you turn to for testing. It queries DNS name servers and shows you the results it receives. The command we used on our test systems was nslookup -sil.
Use NETSTAT to see what IP address is connecting to the server and on which port. The format will be <IPAddress>:<port> (for example, 10.10.10.10:1352). Use the command netstat -an. To make reading the output easier, consider redirecting to an output file, for example:
netstat -an > netstat.txt
The HOMETEST command can test the system configuration including HOSTNAME, DOMAINORIGIN, and NSINTERADDR, which are defined in the TCPIP DATA file.
HOMETEST verifies that the host tables or name server (depending on the NSINTERADDR statement) can resolve the fully qualified domain name (defined by HOSTNAME and DOMAINORIGIN statements) for your site.
In addition, the Internet addresses corresponding to your site HOSTNAME are checked against the HOME list. This is defined in the PROFILE TCPIP file. A warning message is issued if any addresses are missing from the HOME list.
Verify that the TCPIP virtual machine has been started before you use the HOMETEST statement.
|< Day Day Up >|| |