During installation, the srvbuild process adds entries to the interfaces file for your new Adaptive Server, Backup Server, Monitor Server, and XP Server.
To access a Sybase server through the interfaces file, each server must be included in the interfaces file on the client computer.
To add a server entry to the sql.ini file on your PC-client computer:
From the Microsoft Windows task bar, select Start | Programs | Sybase | dsedit.
Click OK on the first window to open the InterfacesDriver window.
Select ServerObject from the menu, and click Add.
In the Input Server Name box, enter the name of the server for which you are creating an entry.
Click OK.
In the Attributes column, double-click the server address row you just added.
In the ProtocolNetwork Address, click Add.
From the drop-down list in the Protocol box, select TCP, NAMEPIPE, or SPX.
By default, connections from client products to Adaptive Server are enabled through the Named Pipes and Winsock network protocols.
In the Network Address box, you can enter either the server name or the IP address, along with the server port number. For example:
machine_name, 4100
where machine_name is the name of the computer, and 4100 is the port number the server is using to “listen” for clients.
Windows now accepts TCP-style connection information:
[SERVER] MASTER=NLWNSCK,huey,2222 QUERY=NLWNSCK,huey,2222
or
[SERVER] MASTER=TCP,heuy,2222 QUERY=TCP,heuy,2222
The preferred format is to use TCP and a space between the host_name and port_number, because it is supported across all platforms. You can edit the sql.ini with any standard ASCII text editor.
To find the IP address for a machine, use ypmatch on a UNIX box.
To
connect to a UNIX server, the entries you add to sql.ini must match
the entries in the interfaces file on the UNIX
system.
For instructions on using dsedit or dscp to modify interfaces file entries or to create new interfaces file entries for existing servers, see the Utility Guide.
For additional information on using dsedit on the client computer, see the Open Client/Server Configuration Guide for Desktop Platforms and the Open Client/Server Supplement.
For specific information about entries for connections to Monitor Server and Historical Server, see:
Monitor Server User’s Guide
Historical Server User’s Guide
