HIST:
25OCT2000 RE #0157 covers server ver.1.01.0.1025
31OCT2000 001MJ    converted to html
08MAR2002 001AR    New parameter supported - LogLevel. Server can be run as a service

MARX CBNET Server (MPINET Server) currently is implemented for the following OS families:

• Win32 (Win XP/2000/NT4, Win Me/98);
• Netware (NW5.x, NW4.x, NW3.2);

Installation under Windows

To install server under Windows – you should:

• You need to install the proper CRYPTO-BOX device drivers, to have access to CRYPTO-BOX. The driver files depend on installed Windows version: XP/2000/NT4 or Me/98. Refer to PPK readme file or the manual for more information about drivers installation.
• Place server kernel (CBNETSRV.SRV) and launcher (CBNETSRV.EXE) file into the same directory on your hard drive (for example – C:\CBNETSRV). You should also have server configuration file (CBNETSRV.CFG) there. Refer to MPINET Server. Configuring for information about this file.
• To start server automatically – you should add CBNETSRV.EXE to Startup and restart computer. To do it manually – you should simply launch CBNETSRV.EXE.
• To start server as a service – you should activate CBNETSRV.EXE dialog window, stop the server and check "Run as service" box. Then you can start server manually and logoff or restart computer without logging in. NOTE: You must have administrator rights to change server run mode.

If server application was launched the proper icon will appear on the system start bar. By doubleclicking on this icon you can activate CBNETSRV dialog to see log file and to start/stop the server. By right mouse click you can start/stop/exit the server

Installation under Netware

To install server under Netware – you should:

• Place server kernel (CBNETSRV.NLM) and driver (CBNETDRV.NLM) file into the \SYSTEM directory of SYS: volume (SYS:\SYSTEM - directory). The server launch command should be included into the AUTOEXEC.NCF. (for NW3.2 – NW4.x – load cbnetsrv, for NW5 - cbnetsrv). You should also have server configuration file (CBNETSRV.CFG) there. Refer to MPINET Server. Configuring for information about this file.
• For IPX/SPX support SPXS.NLM should be started before server is launched.
• To start server automatically – you should restart computer, to do it manually – run commands load cbnetsrv (for NW3.2-NW4.x) or cbnetsrv (for NW5). To stop server – run command unload cbnetsrv.

Configuring:

Server could be configured in a three ways (they are listed from lowest priority to highest):

• default parameter settings;
• settings, reassigned by values obtained from the configuration file (CFG file);
• settings, reassigned by values specified in the command line.

The following parameters are supported:

• DebugLevel=<n> - specifies the level of debug information that will be added to debug log file (CBNETSRV.DBG)

• LogLevel=<n> - specifies the level of information that will be added to log file (CBNETSRV.LOG)

• Net_TCP=<Enabled|Disabled> - identifies that TCP/IP transport should be used
• Net_SPX=<Enabled|Disabled> - identifies that IPX/SPX transport should be used (must be Enabled for Netware by default !!!)
• Net_NetBIOS=<Enabled|Disabled> - identifies that NetBIOS transport should be used
• TCP_Dta_Port=<n> - specifies port, used to accept client TCP/IP connections
• UDP_Adv_Port=<n> - specifies port, used to accept client TCP/IP advertisement requests
• SPX_Dta_Port=<n> - specifies IPX socket, used to accept client IPX/SPX connections
• IPX_Adv_Port=<n> - specifies port, used to accept client IPX/SPX advertisement requests
• NetBIOS_Name=<Name> - specifies server name for NetBIOS protocol (This name should be unique and differ from other CBNET servers on the net !!!)
• NetBIOS_Port=<n> - specifies server port (must be between 0x20 and 0x255 !!!)
• AdminPassword=<value> - specifies ID and password for administrative access
• KeepAliveTimeout=<n> - specifies client keep-alive timeout in seconds (360 – by default; it should be at least 60 !!!)

The configuration parameters should be stored in the CBNETSRV.CFG file, such way: ##### - comment sections must be started with "#"

[GROUP1] - #group tags must be started with "["
param1=val1
param2=val2
# params & and values are separated with "="
# it's strictly prohibited to specify more than one (param=val) pair
# in one string
param1=val1 param2= val2
# PROHIBITED !!!!!
# it's strictly prohibited to include comment section in that string
# where (param,value) pair is specified
param1=val1 # description of param,1
# PROHIBITED !!!!!

To set parameters in the command line – do the following:

CBNETSRV.EXE -DebugLevel=3 -TCP_Dta_Port=8000 (for example)

The server log information is saved in two files:

• CBNETSRV.LOG – general log information, also output to console;
• CBNETSRV.DBG. – debug level log, information (defined with DebugLevel parameter).

For Win32 the log files are generated in the same directory, where server kernel and launcher files are placed. For Netware these files are generated in SYS:\ETC – directory.

The server could be remotely administered via HTTP – browser. For this purpose – you should have TCP/IP support on server and client (remote administrator) computer. You can use Internet Explorer or Netscape Communicator (or any other browser) to connect to server.

http://xxx.xxx.xxx.xxx:8756, where xxx.xxx.xxx.xxx – IP address of the server and 8765 – default TCP_Dta_Port.

For administrative login – you should specify login name and password (default – admin:cbnetserver), stored in AdminPassword parameter.

The main administrative functions allow administrator to:

• view server OS/CBNET version info;
• view connected clients (users) list;
• disconnect any client (user);
• view attached CRYPTO-BOX list;
• restart or shutdown server.

You also can view the server log information, which corresponds to information, output to server console and stored in CBNETSRV.LOG – file.

Now a special Administrative Console is under development. It should provide server administering, using any transport protocol (not only TCP/IP, but also IPX/SPX and NetBIOS)

There are several limitations, existing in the current version of CBNET server.

NetBIOS support limitations

• the advertising isn’t supported for NetBIOS protocol. Client should specify server name for NetBIOS connect directly (default – server computer name, may be redefined with NetBIOS_Name parameter);
• NetBIOS over TCP/IP is disabled. If you wish to support NetBIOS transport – you should install NetBIOS support over NetBEUI or IPX/SPX.

By now IPX/SPX transport is supported only for Netware server.

To support administering over HTTP – you should install on server (client) –side TCP/IP.