INF: Using Alternate Socket Number with NIK for NetWare

ID: Q96871

The information in this article applies to:

SUMMARY

An alternate socket number is required when running more than one instance of the Network Integration Kit (NIK) for NetWare on the same computer. For example, if you need to connect to both a SQL Server and an Open Data Services gateway on the same computer, you will need to start two instances of the NIK, and one of them has to use an alternate socket number. However, if the socket number is not specified in certain format, the NIK will not work.


MORE INFORMATION

By default, NIK for NetWare uses socket number 843E (hexadecimal). You can specify an alternate socket number using the -s option in the NIK command line. However, the socket number has to be specified in hexadecimal format using the "0x" prefix. For example, to start NIK using socket number 843F, you will need to specify it in the following format:

netmgr -Nssmsspxp -Syour_nik -s0x843F -Lnik.log

If you omit the "0x" prefix, the NIK will start without error, but will fail to register itself in the NetWare file server's bindery. As a result, clients will not connect to this instance of NIK successfully. 


Keywords          : kb3rdparty kbhw SSrvServer 
Version           : 
Platform          : OS/2 
Issue type        :

Last Reviewed: March 16, 1999