This tip explains how to use the SERVER command in your SYSGEN configuration. This tip is a supplement and update to the available SYSGEN documentation.
The SERVER command is used to define network connections between Comet 98 (and Comet 504) and Signature Systems server products, such as CometServe NLM, CometServe 32 or Comet Security Server. There are two places where the SERVER command is used in a SYSGEN configuration file (referred to as an "INI" file):
For example, here is a portion of an INI file that defines a Comet Server (in this case, a Novell Netware server running CometServe NLM) and two nodes. Notice that the SERVER command is used in the [SITE] segment and the [NODE] segment. The comments explain each statement in this example. See below for complete syntax information and more examples.
SYSGEN command Comment
----------------------------------------------------------------------
[SITE]
SERVER = N01,NLM,L,Comet_Server_1; Server number N01 is a Novell
Netware server running
CometServe NLM, identifying
itself as Comet_Server_1
[NODE]
SERVER = N01,FS; This node uses server N01
for both type-S directory
access and security.
[NODE]
SERVER = N01,F; This node uses server N01
for type-S directory access
only. Security comes from a
single user plug.
|
Important Notes
|
In an INI file, the [SITE] segment contains information that defines a particular Comet site, including optional descriptive information (name, address, phone number, etc.) and information identifying the Comet Servers at the site. The Comet Server information is declared using the SERVER command.
The syntax for the [SITE] SERVER command is:
[SITE]
SERVER = server-number, channel, flag, nlm-id-or-address;
The table below describes the field parameters of the [SITE] SERVER command:
|
Parameter |
Description |
|
server-number |
Since Comet is run in multiple-server environments, each server declared is referenced by a unique identifier. This is in the form N01 through N99. Though N00 is a valid server number, we recommend that you name your first server N01, thus reserving the N00 name for diagnostic purposes. |
|
channel |
This parameter defines the communications channel that is employed between the server and the Comet node. The following values may be specified: NLM, TCP See below for further information and examples of each. |
|
flag |
This parameter determines whether the server is local or remote. The following values may be specified: L (for a local server) See below for further information. |
|
nlm-name-or-address |
This parameter contains the CometServe NLM's advertised name or a network address. The specific format varies with the communications channel. Therefore, see below for more information and examples. |
This section explains how to define a server that is running the CometServe 32 File System and/or the Comet Security Server. These products use the TCP communications protocol. The syntax is:
[SITE]
SERVER = server-number, TCP, flag, IP-address;
Notes:
L disables the Dial-Up Networking "Auto-Connect" feature when a Comet node connects to a Comet Server. This prevents Comet nodes from unintentionally activating Dial-Up Networking in an attempt to connect to a locally accessible Comet Server.
R does nothing to inhibit Dial-Up Networking.
Here are two examples of this version of the SERVER command:
Example 1:
Defining a local server named N01, running CometServe 32 and/or the Comet Security Server, with an IP address of 192.168.1.1.
[SITE]
SERVER = N01,TCP,L,192.168.1.1;
Example 2:
Defining multiple servers. The first server is like example 1. The second server is a remote server named N02, running CometServe 32 and/or the Comet Security Server 32, with an IP address of 207.46.131.15.
[SITE]
SERVER = N01,TCP,L,192.168.1.1;
SERVER = N02,TCP,R,207.46.131.15;
This section explains how to define a Novell server that is running the CometServe NLM File and Security System. The syntax is:
[SITE]
SERVER = server-number, NLM, flag, nlm-name;
Notes:
These values are identified by the network administrator.
Example 1:
Defining a local Novell server named N01, with a locally advertised server name of Comet_Server_1.
[SITE]
SERVER = N01,NLM,L,Comet_Server_1;
In an INI file, the [NODE] segment contains information that defines a particular Comet node, including descriptive information and various identification values. The SERVER command is used in this section to define how each server will be used (if at all) by the node.
The syntax for the [NODE] SERVER command is:
[NODE]
SERVER = server-number,usage code;
The table below describes the field parameters of the [NODE] SERVER command:
| Parameter | Description |
| server-number | This is the number of the server used by this node, in the form N01 through N99. If a node will access multiple servers, multiple SERVER commands are required.
The server-number used here must have been previously defined under the [SITE] segment. If not, an error will be reported by SYSGEN. |
usage code |
This code defines how the server will be used.
F specifies that this server will be used for type-S directory file access. S specifies that this server will be used for security (license validation). FS or SF specifies that this server will be used for type-S directory file access and security. |
Example 1:
Defining a server for both type-S directory file access and security:
[NODE]
SERVER = N01,FS;
Example 2:
Defining a server for type-S directory file access only (security must come from single user plug):
[NODE]
SERVER = N01,F;
Example 3:
Defining multiple servers. Security will come from N01, while type-S directory file access will only come from N02 and N03.
[NODE]
SERVER = N01,S;
SERVER = N02,F;
SERVER = N03,F;