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:

• Instead of users' accessing server-based mail or application files on the remote server, have them replicate the database files to their local systems.
• Review your server-to-server replication and mail routing architecture across the WAN. It is best to use a hub-and-spoke design, and use Connection documents in Domino to connect the servers, mirroring the hub-and-spoke architecture. Use Notes name networks (NNNs) only at each isolated local site and then use Connection documents to interconnect the sites from the hub location.

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:

• The Notes Name Service cache in the current Location document contains a numeric IP address that it originally obtained from the Server document (Net Address field) of the target Domino server, and the Server document has since been updated with a new IP address. Using only host names in the Net Address field makes this error less likely to occur, as host names usually don't change.
• The contents of the Net Address field returned by the Notes Name Service is not the active address, either because of a typographical error, or because there is more than one enabled Notes network port for TCP/IP and the port listed first in the Server document is offering a different FQDN than the second. In this case, if you are trying to connect through the port listed second, the connection fails.
• The address returned by DNS or hosts files is not the correct address or is not correct for this location.

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:

130.103.40.1 red.acme.com red

Note Insert a tab between com and red.

For TCP/IP for the Macintosh, the host name and alias definitions should look like this:

red.acme.com A 130.103.40.1

red CN red.acme.com

Note Verify that the ordering of the name lookup services is "Host" first and "DNS" second; otherwise, the hosts file entries may not be used when you expect them to be (excluding the NetBIOS Name Service).

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.

See also

Troubleshooting TCP/IP problems for NRPC

Glossary