If dsedit does not make a successful connection, make sure that all the basic Net-Library requirements have been met:
Adaptive Server or Open Server is running on a server machine.
A network hardware connection exists between your PC and the server machine.
Your PC meets minimum hardware and software requirements.
The network vendor’s software is installed and running on your PC.
The connection information in sql.ini is correct.
If these requirements have been met, determine the point at which dsedit failed by reviewing the messages it displays.
If dsedit cannot connect to a server, it displays a message box.
If dsedit finds the connection information but notifies you that the server is not responding:
Verify that the server is running. If you have access to the machine running the server, try using isql to log in to the server. Otherwise, ask your System Administrator to verify that the server you need is running.
Verify that the networking software and hardware are properly configured. For example, check connectors, plugs, and so on, and confirm that your network software is running.
Check for any network error messages displayed in the message boxes, or check the system event log for errors.
Ask your System Administrator to verify that your connection information provides the correct values to connect to the machine running the server, or use the utilities provided with your network software to verify this.
If you cannot resolve the problem yourself, have your designated Sybase support contact call Sybase Technical Support to report the problem. See “Information you need for Sybase Technical Support”.
