CCIIPX Configuration

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

In this Chapter

CCI Support for Novell NetWare IPX

CCI Support Modules for IPX

In order to enable CCI support for the Novell NetWare IPX transport, one executable module is provided:

Novell NetWare IPX Configuration

There is no specific configuration of the Novell NetWare or operating system environment required to run CCIIPX, however there are restrictions on the supported IPX protocol providers which can operate with CCIIPX, these differ between operating systems.

Microsoft Windows 95

Microsoft Windows NT

CCIIPX cannot use the Microsoft IPX compatible transport as shipped with Windows 95 or Windows NT, these IPX transports do not provide the interface support level required for CCIIPX.

Configuring CCIIPX Parameters

CCI.INI File Options for CCIIPX

You can tune CCIIPX 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?

The CCIIPX module has been developed to be a reliable and easy to configure protocol option in the CCI suite. In almost all circumstances CCIIPX will work correctly straight out of the box with no need to configure anything. If however some system tuning is required the following options are available under a heading of [cciipx-base] in the CCI.INI file.

CCI.INI can be located in a number of locations for testing and deployment. On Windows systems of all types the Windows root directory is a good location as it is visible from all applications. There may be configuration sections for more than one CCI protocol module in any CCI.INI file.

If you only want to affect the behavior of a single application, rather than affecting every application on the system, put the CCI.INI file (containing the CCIIPX entries for this application) in the current directory - the directory from where the application is being run.

What form do CCIIPX CCI.INI options take?

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

[cciipx-base] 
 REPORT_CONNTYPES=n 
 CRC_SEND=n 
 CRC_FORCE_RECV=n
 CRC_REPORT_FAILS=n
 CRC_RETRY=y
 MAX_PKT_SIZE=17872 

Acceptable entries for yes/no options are, "Y","y","YES" or "yes", and "N","n","NO", or "no". Mixed case words such as "Yes" are NOT accepted and default settings will be used if their use is attempted. Numeric values must always be entered in decimal format, use of HEX and OCTAL values is not supported and will lead to unpredictable results. Any unwanted entries in the CCI.INI file can be commented out using ";" as the first character of the line.

Available CCI.INI Options for CCIIPX

Basic CCI.INI Options for CCIIPX

Advanced CCI.INI Options for CCIIPX

Application Configuration

CCIIPX 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.

CCIIPX 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 47 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.

CCIIPX Machine Name

This is a parameter that only needs to be specified by CCI client applications.

There are two aspects to the use of Machine Name