SEE Configuring
a Binding for more information.Security Server Configuration
Once installed, the BlueZone Security Server is easy to configure and operate. Every configuration requires a minimum of two components; a Binding, and a Connection. It is also possible to have one Binding and many Connections.
A Binding specifies addresses to be used for incoming client connections and the outgoing host connection. The Security Server can be configured to support either one or two network interface connections (NIC). If the server that Security Server is installed on has one NIC card and one IP Address, then you will be using the same NIC and IP Address for both the incoming and outgoing connections. Use the same IP Address for both bindings.
If the server has two NIC cards and two IP Addresses, the Security Server can act as a bridge or router spanning different network segments. For example, one NIC can have an external IP Address accessible via the public Internet and the other NIC an internal IP Address and connected to an Intranet segment.
Also, Bindings may span dissimilar networks, such as Ethernet to Token-ring, provided TCP/IP is bound to both NICs in the Windows operating system Network Settings. A Binding must be defined before a Connection can be defined.
SEE Configuring
a Binding for more information.
A Connection defines a path through the Security Server through which clients will use to access host applications. Each connection requires a "unique" port number that is assigned by the Security Server administrator.
SEE Configuring
a Connection for more information.
The Security Server's active configuration is stored in the Windows Registry. You will notice that if you make any changes to the configuration, and you close down the Security Server Manager, you will be asked if you want to save the current configuration to the Registry.
To store the active configuration in the Windows Registry,
click the Save 
icon located on the ToolBar
or select File::Save from the
MenuBar.
You can save an active Security Server configuration to a file at any time. It is recommenced that you periodically save your Security Server configuration and store it to a safe location. This will make it much easier to restore a Security Server to full functionality in the event of a serious hard drive crash, or if the server has to be rebuilt or replaced.
To save the active configuration to a file, select File::Save As from the MenuBar.
To import a configuration from a file, simply choose File::Open from the MenuBar.