Prev | Getting Started with Pervasive.SQL (Server edition) | Next |
Using SPX to Connect to a NetWare Server
This section documents the use of SPX when connecting to a Pervasive.SQL server running on a NetWare machine.
Configuring Pervasive.SQL to use SPX
SPX is a native protocol to NetWare. There should be no special requirements for operating Pervasive.SQL with SPX on NetWare. However, note the following:
SPX is not the default protocol for Pervasive.SQL. Consequently, if you have both TCP/IP and SPX installed, Pervasive.SQL attempts to use TCP/IP first. If you want SPX to be used, follow these steps:
To Configure your Clients to use SPX with NetWare Servers if Both TCP/IP and SPX are Installed:
- Click Start, point to Programs and select Pervasive.SQL V8.
- Select Control Center.
- Expand Pervasive.SQL Engines and expand the desired engine.
- Expand Configuration and expand Client.
- Select the Communication protocols and, in the right-hand pane, right-click on Supported protocols.
- Highlight Microsoft TCP/IP from the list of selected protocols and click the < button to move it off the selected list.
- Click OK.
To use SPX with NetWare, also ensure that your network packet size is appropriate for your network. By default the Receive Packet Size option of the Configuration utility (detailed in the Advanced Operations Guide) is set to 1500, which is the correct value for Ethernet networks. If, however, you have a Token-ring network, use the Configuration utility to modify your Receive Packet Size to 4096.
Using Either Microsoft or Novell's SPX when Connecting to NetWare Servers
If you select Novell SPX using the Supported Protocols setting in the Configuration utility, this means that all Pervasive SPX calls will be made through the Novell component NWIPXSPX.DLL. Both Novell and Microsoft support this DLL, so you could be using Microsoft SPX even though the Pervasive setting shows that you are using Novell SPX.
To determine which version of SPX (Microsoft or Novell) you are using from your Windows workstation:
- Click Start, point to Settings and select Control Panel. Double-click Network, and look for IPX/SPX in the list. If the entry says "IPX/SPX compatible-protocol", you have Microsoft's SPX installed. Otherwise, you are using Novell's IPX/SPX protocol.
- Click Start, point to Settings and select Control Panel. Double-click Network and Dial-up Connections, select Local Area Connection and click Properties. Look for IPX/SPX in the list. If the entry says "IPX/SPX compatible-protocol", you have Microsoft's SPX installed. Otherwise, you are using Novell's IPX/SPX protocol.
Pervasive.SQL supports both the Microsoft and Novell versions of SPX. If you do not use the Novell Client 32 to communicate with the NetWare server, you could encounter a Status Code 3119 when you first attempt a connection to the NetWare server. Subsequent connections should clear that condition.
Changing the Default Server Listening Port (Advanced)
Most users should never have to use this procedure. This procedure should only be performed by a system administrator.
In normal TCP/IP operation, clients use a particular port number to communicate with servers. Pervasive.SQL by default listens on port 1583. For TCP/IP to function properly, all clients and all servers must use the same port.
Pervasive recommends that you do not modify the server listening port unless you have a conflict with port number of 1583. If you do have a conflict, you can override the Pervasive Database port settings with an entry in the SERVICES file for each machine. The SERVICES file is located at:
SYS:\ETC\SERVICESFor example, if you wanted to change the listening port to 80 for Pervasive.SQL, you would add the following entry in your SERVICES file:
psql 80/tcpAfter changing your server listening port, you must stop and restart your Pervasive.SQL services for the changes to take effect. See "Using Pervasive.SQL" in Pervasive.SQL User's Guide.
Note
Entries in the NetWare SERVICES file are NOT case-sensitive.
Prev Using TCP/IP to Connect to a NetWare Server |
Contents Up Check for Revisions | Next Using TCP/IP to Connect to a Windows NT/2000 Server |