Network requirements (TCP/IP) for client/server products

Synergy/DE client/server software (SQL OpenNet, xfServer, xfServerPlus) all use TCP/IP for data transport. On Windows, License Manager server also uses TCP/IP to communicate.

When installing Synergy/DE client/server products, you need to have a thorough understanding of the installation, configuration, and troubleshooting of TCP/IP on the targeted client and server machines. Synergy/DE Developer Support cannot provide assistance with TCP/IP configuration issues. However, we provide a utility, synxfpng, for troubleshooting connections to xfServer, SQL OpenNet, and License Manager server.

Before any client/server communication can occur, the client has to be able to locate and then connect to the host machine. You can use either an IP address or a host name to identify the host machine (except for a configuration that includes backup license server; see Configuring a backup license server (Windows)). If there is a firewall between the client and the server, it will have to be configured to allow communication on the specified port.)

If you use a host name to identify the server, either the etc/hosts file is used or the client machine performs a request to a DNS (Domain Name Server—a machine that all clients use to convert names to IP addresses). Machines are usually configured to use a primary DNS and, if the lookup fails there, try a secondary DNS. The fail over time (the length of time the machine will look for the DNS before reporting a failure) can be several minutes.

A typical problem at installation time is that connections are very slow. This is usually due to a DNS lookup problem. You can use synxfpng to test this. See synxfpng utility for details.

Note

For OpenVMS TCP/IP requirements, see TCP/IP (Alpha).