PreviousCCIIPX Configuration CCITCP ConfigurationNext"

Chapter 4: CCINETB Configuration

CCINETB is supported on Windows 95, Windows 98 and Windows NT systems only.

4.1 CCI Support for NetBIOS

4.1.1 CCI Support Modules for NetBIOS

In order to enable CCI support for the NetBIOS transport API, one executable module is provided:

4.1.2 Configuring the Environment for Using CCINETB

The CCINETB module uses a NetBIOS interface to communicate over NetBEUI. Although Windows 95 and Windows NT offer NetBIOS interfaces running over other protocols such as TCP/IP, it is recommended that you use CCINETB with NetBEUI only. If communication over any other protocol is required, you should use the associated CCI module for that protocol.

4.1.3 Which Protocol will CCINETB Use?

On Windows NT, CCINETB will, by default, interrogate the Registry and use the LAN Adapter number of the NetBEUI protocol. If, for some reason, this fails, CCINETB attempts to use LANA 0 (LAN Adapter Zero).

4.1.4 Using CCINETB on Windows 95

Unlike Windows NT, CCINETB cannot discover the location of the NetBEUI logical Lan Adaptor (LANA) automatically, only the default LANA is defined on Windows 95, that is always LANA 0. So in Windows 95 some manual configuration may be required if NetBEUI is installed as well as other protocols.

4.1.5 Multiple Protocols on Windows 95

On Windows 95, it may be necessary to configure the default protocol to ensure that the NetBIOS interface is being used over the NetBEUI protocol. CCINETB will, by default, attempt to use the LAN Adapter number of the default protocol and the default protocol always uses LANA 0 (LAN Adapter Zero).

4.1.6 Setting the Default Protocol on Windows 95

You can set the adapter that CCINETB will use by following the directions for setting the AdapterLoc parameter below or you can ensure that CCINETB uses the NetBEUI protocol by setting NetBEUI to be the default protocol under Windows 95 as follows:

  1. Select the Network option in the Control Panel


  2. Click on the Configuration tab.


  3. Double click on the NETBEUI network adapter protocol binding that you want CCINETB to use.


  4. Click on the Advanced tab


  5. Examine the check box 'Set This Protocol To Be The Default Protocol'.


  6. Ensure that the check box Set This Protocol To Be The Default Protocol is selected


  7. Click. on OK.
  8. Shutdown and restart Windows 95 so that the changes take effect.

4.1.7 Using Multiple Adapters on Windows 95

On Windows 95, if you have configured more than one adapter, you must ensure that the NetBEUI protocol is only bound to a single adapter, the one that will be used by CCINETB. To do this:

  1. Select the Network option in the Control Panel


  2. Click on the Configuration tab.


  3. If there are multiple entries for NetBEUI, select, in turn, those that will not be used by CCINETB and then click on Remove.



  4. Click on OK.
  5. Shutdown and restart Windows 95 so that the changes take effect.

4.2 Configuring CCINETB Parameters

4.2.1 CCI.INI File Options for CCINETB

You can tune CCINETB using the tuning options described below. You set the ones you want to change in the file CCI.INI.

Why would I need to use any CCI.INI options?

CCINETB can be used without any additional configuration by following the instructions above. It is possible, however, to configure some of the default parameters that CCINETB uses via the CCI.INI file.

You can create the CCI.INI file using any text editor. The CCI.INI configuration file must be placed in a directory defined on the system PATH.

What form do CCI.INI options take?

A sample CCINETB section of a CCI.INI file could look like:-



4.2.2 Available CCI.INI Options for CCINETB

The CCINETB parameters which are listed below must be specified in the [ccinetb-base] section of the CCI.INI file:

4.3 Application Configuration

CCI Client/Server applications use the CCI Server Name and Machine Name parameters to enable the CCI Client to specify the CCI Server with which to communicate.

The CCI Server identifies itself on the network by using the Server Name parameter. The CCI Client specifies the CCI Server using the Server Name. Additionally, if it only wants to find this Server running on a particular machine in the network, it needs to specify the Machine Name parameter.

4.3.1 CCINETB Server Name

Both CCI server and CCI client applications need to have a Server Name specified: server applications need to register themselves as available under this name (or what fixed port to use); and clients need to specify which server they wish to contact.
This can be any valid alphanumeric string (up to 14 characters in length). Strings must be terminated with either a space (" ") or a NULL (binary zero) byte.

Names presented with a length greater than this limit will be rejected with a bad parameter message, to avoid the possibility of a truncated name allowing connection of a client to an unwanted service.

4.3.2 CCINETB Machine Name

No Machine Name configuration is available for CCINETB, any configuration options detected will be ignored.

Copyright © 1999 MERANT International Limited. All rights reserved.
This document and the proprietary marks and names used herein are protected by international law.

PreviousCCIIPX Configuration CCITCP ConfigurationNext"