Solving Network Connection Problems
If a client can't access a network SQL server (the login dialog won't appear, however after some time of waiting for a connection (apparent idleness) a windows with a brief cause description appears), it's recommended to find the problem as described below.
- Ensure that the server is running and offering TCP/IP network services (the Server Manager should show TCP/IP (port number)).
- Ensure the registration correctness (name, IP address and port of the server) for the TCP/IP protocol on the client computer - when the server is running in a different segment of the network; if both the client and the server run in the same segment, registration is not necessary and the server is always visible in the Control panel. Registrated servers are shown in bold text, unregistered visible servers are listed at the end of the list in normal text.
- If the server is not in the same segment as the client, ensure that these two segments are properly linked and packets of the TCP and UDP protocols are allowed to pass from one segment to the other. You can try the link between two computers using the PING utility or by clicking the Ping button in the Server connection data dialog (this test is a necessary condition not a sufficient one). The signalization of connection in the server icon color on the control panel may not correspond with the real speed (in more complex networks).
- If there's a SOCKS firewall between the server and the client, add the firewall's address to the parameters (in the Server connection data dialog) and turn it on. The test for IP connection won't probably be functioning in this case, however IP communication over a firewall will be.
- Ensure that the port the server listens to, is allowed by the network components (mainly firewalls). TCP port 5002 and UDP ports 5001 and 5002 are selected by default. The default port (5001) may be changed in the server configuration, the others are changed automatically (new_value+1, new_value+2).