ASA Database Administration Guide
Client/Server Communications
Troubleshooting network communications
The following list presents some common problems and their solutions.
For information about troubleshooting connections to the database or database server, see Troubleshooting connections and Troubleshooting server startup.
If you receive the message Unable to start—server not found when trying to start the client, the client cannot find the database server on the network. Check for the following problems:
Under the TCP/IP protocol, clients search for database servers by broadcasting a request. Such broadcasts will typically not pass through gateways, so any database server on a machine in another (sub)network, will not be found. If this is the case, you must supply the host name of the machine on which the server is running using the -x option.
A firewall between the client and server may be preventing the connection. For more information, see Connecting across a firewall.
Your network drivers are not installed properly or the network wiring is not installed properly.
If you receive the message Unable to initialize any communication links, no link can be established. The probable cause is that your network drivers have not been installed. The server tries to start communication links using all available protocols unless you have specified otherwise using the -x option. Check your network documentation to find out how to install the driver you wish to use.
You must use the TCP/IP protocol if you are connecting via jConnect.
If you are trying to connect to a database server on your local machine, make sure the Search Network For Database Servers option on the Database tab of the Connect dialog is cleared. You can select this option if you are trying to connect to a database server running on a machine other than your local machine.
For more information about network communication parameters, see Network communications parameters.