If you experience difficulties connecting to the remote database you wish to maintain, it is likely that one or more of the following issues are affecting the connection.
The remote database identity is incorrect
If the remote server address was manually entered, it might not have been entered correctly. There are three distinct parts to the identity - a name, a separator (the "@" symbol), and the address. Of these, the separator and address are the key elements. For more information on creating remote database names (identities), see the topic on manually adding servers to the server list.
The database port number is incorrect
The port normally used (default port) to connect to a remote database is 16000. However, XStudio supports user-defined port numbers for this connection, so you need to ensure the port you've assigned for the remote database connection matches the remote database server port that has been assigned.
The remote PC cannot be reached via TCP/IP
In order for XStudio to connect to a remote database server, it must be able to reach the host PC via TCP/IP.
If the server address you are trying to reach uses an IP address or internet domain name, ensure that you have a "route" to the host PC by attempting to "ping" the remote PC. Use the "address" element of the remote database server identity as the address to ping.
If the server address you're trying to reach uses a machine name notation, ensure that you can browse to the named machine (the name used in the "address" portion of the remote database identity) using Network Neighborhood or File Explorer.
Access to the remote PC is blocked
If you are certain that the remote server identity is correct and that you can reach the remote PC, ensure that both the PC running XStudio and the PC running the host application (and database server) have port 16000 available for use and unblocked. See the topic on TCP/IP Port Information for details on all ports used for database communications between XStudio and the host application.
