TROUBLESHOOTING


TCP/IP error messages -- Client or server
These sections describe common error messages on an IBM® Lotus® Notes® client or IBM® Lotus® Domino® server using NRPC services over TCP/IP.

Network operation did not complete in the specified amount of time.
The connection pathway between the client or server system and the target server was unable to sustain the session. This happens when a system is accessing a remote server over a slow or very congested WAN. Possible solutions to this problem are:

If this error occurs over a LAN, you may be experiencing frame and/or packet sizing problems because you have a mixed-topology network or because your network routers' routing tables are converging. In these cases, the network pathway to or from the target Domino server cannot forward the TCP/IP packet stream.

If you are using a remote VPN connection across the Internet, with some VPN client software you can encounter packet sizing issues on the Notes client or Domino server and/or with the firewall system's VPN services.

The connection has timed out.
The establishment of the connection took longer than the expected default of 5 seconds. This can happen when the connection is over a dial-on-demand ISDN modem connection, remote bridge, or router. From the Port Setup dialog box, increase the TCP/IP connection-time-out interval. On a normal LAN, it is best to enter a value of no greater than 10 seconds, as the client or server won't retry the connection until the timer has expired.

To access the Port Setup dialog on a Notes client, use File - Preferences - User Preferences and click Ports. To access this dialog box for a Domino server, use the Domino Administrator's Configuration tab and select Server - Setup Ports from the Tools pane.

Once in the Port Setup dialog box, select the TCP/IP port and click the port name Options button.

The server is not responding. Possible explanation.
Variations of this error can occur when name-to-address resolution has completed on the local system, but the server would not respond to that address. The causes of this error include:

To resolve problems associated with this error, follow all the steps in the topic How to troubleshoot TCP/IP problems in NRPC. To resolve problems involving more than one enabled Notes network port for TCP/IP, see the topic Ensuring DNS resolves in advanced TCP/IP configurations.

The Remote server is not a known TCP/IP host.
This message appears if the translation from server name to TCP/IP address fails. Follow these steps to troubleshoot the problem:

1. Verify that the server name is correct.

2. If you use a local hosts file for name resolution, enter the server's IP address and host name in the hosts file. If the server name does not match the TCP/IP host name, which is also known as the fully qualified domain name, enter the server name as an alias for the host name. For example, for the Domino server Red/Sales/Acme, enter:


3. If you use the Network Information Service (NIS) for name resolution, ask the UNIX® system administrator responsible for the NIS domain to register the server's IP address and host name. If the server name does not match the TCP/IP host name, request that the server name be registered as an alias for the host name.

4. If you're using DNS for name resolution, ask the administrator responsible for the DNS domain to register the server's IP address and host name. If the server name does not match the TCP/IP host name, request that the server name be registered as an alias (CNAME) for the host name and place the host name in the TCP/IP port's Net Address field in the Server document. For example, for a Domino server named Sales/Boston/Acme with a host name of app01 for the A record, the CNAME record would be sales. The Net Address field contains either the simple host name, app01, or the FQDN, app01.acme.com. In the case of port mapping, each port-mapped server's common name is added as a CNAME to the A record for the base port-mapping server.

For more information on DNS resolves, see the topics Checking TCP/IP name resolution in NRPC and Ensuring DNS resolves in TCP protocols.

Related topics