 |
The FirstClass network store
About the FirstClass network store
The FirstClass network store contains all FirstClass data including messages, users, conferences, groups, files, configuration files, and the Directory that you have created on your system. As this information is different for every organization, every network store is unique.
The FirstClass network store (FCNS) folder
The network store is located in the FCNS (Windows) or fcns (Mac OS X or Linux) folder. Many of the files and folders in this folder are used only by the server.
The network store is located:
Windows: drive:\FCServer\FCNS
Mac OS X: /Library/FirstClass Server/Volumes/Master/fcns
Linux: /var/opt/fcsd/volumes/master/fcns
 WarningIt is vital that you maintain the integrity of your network store folder. Do not:
• rename it
• move it to a different volume
• move it from the root of the volume on which it is located
• change, delete, or move anything other than the log files, statistics files, NETINFO file, modem definition (MDM) files, database extension files, or connection scripts
• add files or folders to any folders in the network store folder
• merge multiple network store folders into a single folder.
If you make unauthorized changes to the network store, the server may not start, or it may damage data files. To start the server, reverse the changes.
If you add, change or delete files in the network store, it might be damaged. If this happens, restore or reinstall your server.
The Logfiles folder
The Logfiles (Windows) or logfiles (Mac OS X or Linux) folder contains the server's log files. For information, see Daily log files.
The Stats.dir folder
The Stats.dir (Windows) or stats.dir (Mac OS X or Linux) folder contains the statistics files. For information, see Server monitoring.
The Server folder
The Server folder contains support files for the server as well as the following files and folders:
Dbext (Windows) or dbext (Mac OS X) |
Contains any database extension Dynamic Link Libraries (DLLs) installed on the server. When you first install your server, this folder is empty. |
Modems |
Contains the modem definition (MDM) files. In addition, there may be an Other Modems folder that contains additional MDM files. |
Ports |
Contains the session configuration files for the modem ports on the server. |
Scripts |
Contains the connection script files. |
Netinfo file |
Allows you to configure IPX, AppleTalk, and TCP/IP connections. You can use NotePad, TextEdit, or any text editor to view and edit this file. The Netinfo file can contain the parameters described below. Parameters must be in upper case with spaces before and after the equal signs. |
The Index folder
The Index folder contains daily files that list the state of the index each day.
Netinfo file parameters
APPLETALK (Windows only) |
Disables or enables the AppleTalk protocol. Syntax APPLETALK = n where n can be either zero (to disable the protocol) or 1 (to enable it) Default APPLETALK = 1 |
IPX (Windows only) |
Disables or enables the IPX protocol. Syntax IPX = n where n can be either zero (to disable the protocol) or 1 (to enable it) Default IPX = 1 |
TCPGUIPORT |
Sets the port number of the main port that accepts connections from users of the FirstClass client software for Mac OS X and Windows who are connecting with TCP/IP. Syntax TCPGUIPORT = n where n is the port number Default TCPGUIPORT = 510 This is the standard FCP port, and is the recommended value. If you don't specify a TCPGUIPORT, 510 is used.  NotesConnections through this port do not use the error correction component of the FirstClass protocol (FCP), because the TCP/IP protocol handles error correction. The TCPGUIPORT accepts connections over network and remote sessions. The number of network sessions the port can support is determined by the number of network sessions you configure on your server. The number of remote sessions the port can support is determined by the number of surplus remote sessions in the server. The server comes with two remote sessions. You can purchase additional remote sessions. Users of terminal emulators can connect to this port by pressing Enter/Return twice. Users who autoregister on any port other than the TCPGUIPORT, TCPRGUIPORT, or UDPPORT are defined as regular users. |
TCPGUIPORT2 |
Creates an optional, additional port for users of the FirstClass client software for Mac OS X and Windows who are connecting with TCP/IP. Syntax TCPGUIPORT2 = n where n is the port number Example TCPGUIPORT2 = 3000 This is the recommended value. There is no default value. Notes Connections through this port do not use the error correction component of the FirstClass protocol (FCP), because the TCP/IP protocol handles error correction. This port accepts connections over network and remote sessions. The number of network sessions the port can support is determined by the number of network sessions you configure on your server. The number of remote sessions the port can support is determined by the number of surplus remote sessions in the server. The server comes with two remote sessions. You can purchase additional remote sessions. Users of terminal emulators can connect to this port by pressing Enter/Return twice. Users who autoregister on any port other than the TCPGUIPORT, TCPRGUIPORT, or UDPPORT are defined as regular users. |
TCPCLUIPORT |
Sets the port number of the TCP/IP port that accepts connections from users connecting to the server with a terminal emulator or telnet client. Syntax TCPCLUIPORT = n where n is the port number Default TCPCLUIPORT = 23 This is the recommended value. If you don't specify a TCPCLUIPORT, 23 is used. Notes This port does not accept connections from the FirstClass client software for Mac OS X or Windows. Connections to this port are
immediate. Users do not need to start their sessions by pressing Enter/Return twice. This port supports the telnet protocol and telnet negotiation. This TCPCLUI port handles line terminators differently from the standard CLUI. Normally, only a CR is accepted as a line terminator in the CLUI. The TCPCLUI port, however, also accepts CRLF and CRLFNULL as acceptable line terminators. If you are using a terminal scripting program, ensure it pauses at least 10 milliseconds (ms) after sending a line terminator. If you are supporting older systems or clients (prior to 5.5), use port number 3003. |
TCPRGUIPORT |
Creates an optional, remote TCPGUI port. Syntax TCPRGUIPORT = n where n is the port number Example TCPRGUIPORT = 3004 This is the recommended value. Notes This port accepts native TCP/IP GUI connections, but command-line users can connect by pressing Enter/Return twice. Users who
autoregister on any port other than the TCPGUIPORT, TCPRGUIPORT, or UDPPORT are defined as regular users. |
TCPFCPPORT |
Creates an optional port for use with a terminal server. Syntax TCPFCPPORT = n where n is the port number Example TCPFCPPORT = 3002 This is the recommended value. There is no default value. If you don't specify a TCPFCPPORT, no TCPFCP port is created. Notes The terminal server has a TCP/IP connection to the server; therefore, this connection does not require error correction. The connection between the FirstClass client software and the terminal server, however, passes through a modem and over telephone lines. Therefore, it requires error correction. A TCPFCP port uses the
FirstClass protocol (FCP) to guarantee the integrity of the information passing between the FirstClass client software and the TCP/IP terminal server. This port accepts connections only from users connecting with a remote session. Thus the number of simultaneous TCP connections the server can support is limited by the number of surplus remote sessions on the server. The TCPFCP port runs the full FCP error-correcting sliding window packet link on top of a TCP connection. It is intended for use with connections that are not TCP from end to end (for example, when clients dial into a terminal server connected
to the FirstClass server through TCP/IP). For these types of connections, FCP does its own error correction. The TCPFCP connection can also be used to handle users connecting with a Communications Toolbox TCP/IP tool such as the Outland TCP Tool. If you are running a terminal server, you must configure it to automatically connect to the server on the TCPFCP port after it answers an incoming call. Users who
autoregister on port 3002 are defined as remote users. |
UDPPORT |
Sets the port number that accepts connections from users of the FirstClass client software for Mac OS X and Windows who are connecting with UDP/IP. Syntax UDPPORT = n where n is the port number Default UDPPORT = 810 This is the standard FCP port for UDP, and is the recommended value. If you don't specify a UDPPORT, 810 is used. Notes Connections through this port use the flow control and error correction features of the FirstClass protocol (FCP), making this a more useful choice than TCP/IP for a slow network connection (such as a modem connection through an ISP). The UDPPORT accepts connections over network and remote sessions. The number of network sessions the port can support is determined by the number of network sessions you configure on your server. The number of remote sessions the port can support is determined by the number of surplus remote sessions in the server. The server comes with two remote sessions. You can purchase additional remote sessions. Users who autoregister on any port other than the TCPGUIPORT, TCPRGUIPORT, or UDPPORT are defined as regular users. |
| |
