PreviousGetting Started with Pervasive.SQL (Workgroup edition) (9.1 revision 1) Next

Setting Up TCP/IP Support

Show this topic in Library frames

By default, TCP/IP is supported between Pervasive.SQL clients and remote engines or between multiple Workgroup engines. If you have modified the default settings or need to verify that TCP/IP support is available, refer to this section.

Enabling TCP/IP Support

Follow this procedure to ensure that the database engine can communicate with clients over TCP/IP networks.

  1. From the Start menu, choose Programs4Pervasive.SQL 9 SP1 (9.1)4Pervasive.SQL Control Center.
  2. In the Pervasive.SQL Explorer window, double-click on Engines to display a list of the engines registered with Pervasive.SQL Control Center.
  3. Right-click on the icon representing your target engine and select Properties. Login if prompted. Click on Communication Protocols.
  4. In the window to the right, a list of Supported protocols displays. If the list of Supported protocols shows the value TCP/IP checked, then TCP/IP is already supported.
  5. If the list of Selected protocols does not include TCP/IP, then you should select the checkbox next to TCP/IP and click OK.

  6. You need to restart the engine for the changes to take effect.
  7. Remember that you also need to confirm that the client software on your other Workgroup computers are configured to use TCP/IP, as well. Please refer to Chapter 7, Configuring Network Communications for Clients.

Enabling Multihomed TCP/IP Support

Follow this procedure when your Windows server computer has two network cards installed.

  1. From the Start menu, choose Programs4Pervasive.SQL 9 SP1 (9.1)4Pervasive.SQL Control Center.
  2. In the window, double-click on Engines to display a list of the engines registered with Pervasive.SQL Control Center.
  3. If the engine you want to configure is not listed, right-click on Engines and choose New Server.

  4. Right-click on the icon representing your target engine and select Properties. Login if prompted. Click on Communication Protocols. In the window to the right, you can see the current setting for TCP/IP Multihomed.
  5. If you want the server engine to listen for client connections on both network cards, select the checkbox. If you want the server engine to listen on only one card, deselect the checkbox. Click OK. If you only have one network card, this setting is ignored.
  6. If your server computer has two network cards, and you set the value of TCP/IP Multihomed to Off, you must edit the setting Listen IP Address and specify the TCP/IP address of the card you want the database engine to listen to. If you do not specify an IP address, the database engine will not receive communications from either network card.
  7. You need to restart the server engine for the changes to take effect. You do not need to make any changes to client settings.

Chapter contents
Publication contents

Prev topic: Default Engine Settings
Next topic: Setting Up NetBIOS Support