Novell IPX/SPX Client Connections

The following procedure describes how to test a network connection when using the native Novell Internet Package Exchange/Sequenced Package Exchange (IPX/SPX) protocol.

    To check an IPX/SPX connection

1. Check the connection between the client and the network.

   The client must be connected to the network. If it is connected, you will get the message "Attached to server servername" after NETX.COM is loaded (for MS-DOS- and Windows-based clients). For Windows NT - based clients, check the Event Viewer to ensure that the NWLink network support software was properly loaded.

2. Check the connection between the server and the network.

   The server must be connected to the network. Under Windows NT, check the Event Log for a message containing "ODS: server-side."

3. Check the local connection to SQL Server using the service name.

   You should be able to make a local connection to SQL Server with Novell NetWare as the default Net-Library. If you can connect locally using named pipes but cannot connect locally using the Novell NetWare Net-Library, SQL Server is not registered properly on the network.

4. Check the network connection between the client and the server.

   If you can connect locally (as described in step 3) but cannot connect from a client across the network, check that:

   • The server is accessible to the client. You can test this by typing the following from the client:

     isql /L
     

     This option makes a call to dbserverenum, which returns the list of available servers from the Bindery. In the list of "Announced network servers," you should see the name of the server you want to connect to. If the server name is not in this list, you will not be able to connect. If the other steps have been done but the server name is not listed, this usually indicates a network problem. Check the SQL Server event log to be sure that the SPX support loaded properly (you will see an error message if it did not). Next, try to eliminate any possible bridge or router problems by attempting to connect from clients on the same LAN segment as the server.

   • The client can connect to a file server on the local area network where the SQL Server is located.

   Failing either of these tests indicates a network routing or configuration problem.

If you are having trouble with connections being dropped or client applications "hanging," this usually indicates a network error. Problems can occur when there are no free network buffers to service requests or when there are conflicts over shared network or memory resources.

If you are running into stability problems running Windows-based client applications over Novell IPX/SPX, the first step is to verify that you have the latest NetWare drivers available for your hardware configuration. SQL Server client applications will run on most systems using "monolithic" NetWare drivers, as long as they meet the minimum version levels specified in Chapter 4, "Configuring Clients." On some hardware, however, the newer "ODI" NetWare drivers are required for reliable operations.

If problems persist with the latest NetWare drivers, you may need to change the setting for the NWShareHandles and/or the RestoreDrives parameters. The effects of these parameters depend on the interrupt load on your system, so your hardware configuration may require a setting different from the default. In Windows for Workgroups version 3.1, these settings can be made through the Network application in the Control Panel. Select the Networks button and then select Novell NetWare in the Other Networks in Use box. Choose the Settings button and try different combinations of the NWShare Handles and Restore Drives check boxes. Try changing just the NWShare Handles setting first. If you are running Windows 3.1, you will need to add or change the [NetWare] section in the SYSTEM.INI file with a text editor. The section should look like this:

[NetWare]
NWShareHandles=TRUE
RestoreDrives=FALSE

The default for both of these settings is FALSE.