After you follow the procedures in Installing and Activating the Software, the next step is to log in to EFT Server via the Server interface, called the Administrator Interface, and configure the client connections to EFT Server.
When you connect to EFT Server for the first time, you must configure it on the computer on which the EFT Server service is installed. After you have created the local connection and enabled remote connections, you can connect to and administer EFT Server remotely.
Even if you plan to restore the Server from a backup, you must still create the initial Server object in the Administrator interface.
Anytime you connect to the GlobalSCAPE Server service, if no Servers have been defined, the Server Setup wizard Welcome page appears. The Server Setup wizard guides you through EFT Server configuration. The wizard helps you configure Server-specific options such as allowing remote administration. After the brief Server Setup wizard is completed, you have the option to run the Site Setup wizard to configure a Site, and then the User Setup wizard to configure a user.
You may cancel out of the Server Setup wizard anytime by clicking Cancel or the X in the upper right corner; however, any settings made through the wizard are discarded, except for keys/certificates added to the key manager (by creating or importing).
You will need the following information to create and configure a Server:
If you are allowing remote administration of EFT Server and you are using SSL (Secure Sockets Layer, a protocol designed and implemented by Netscape Communications, provides for encryption of a session, authentication of a server, and optionally a client, and message authentication.), you need to know the SSL settings and have access to the SSL keys and certificates.
If you are restricting remote administration to specific IP addresses, you need to know the IP addresses and ports.
If you are using DMZ Gateway, install and configure DMZ Gateway before creating Servers and Sites. The installation and configuration of DMZ Gateway is not required before creating Servers and Sites, but the Site setup wizard asks for the DMZ Gateway information. You can configure DMZ Gateway after Site setup is complete, and then provide the DMZ Gateway connection information in EFT Server's Administrator interface.
To configure EFT Server
Do one of the following:
After installation is complete, the New Administrator Connection wizard appears.
If you have already defined a Server and want to create another one, on the main menu click File > New Server. The New Administrator Connection wizard appears.
Do one of the following:
Because you must first configure the local connection, leave This computer selected, and specify the Label for the local connection. By default, the label is LocalHost. Because LocalHost is a very common label, it is a good idea to change the label to something that is easily identifiable in error logs, reports, and remote connections. For example, GS_EFTS. You can label EFT Server anything you want; the EFT Server name is not dependent upon the computer name.
Click A remote computer.
In the Label box, provide a name for the remote Server.
In the Host address box, provide the IP address at which the remote Server allows connections.
In the Port box, provide the port through which the remote Server allows connections.
Click Next. The Administrator interface should connect to the remote Server and Server setup is complete.
Click Next. The Server Setup wizard Welcome page appears.
If you are not restoring from a backup (EFT Server Enterprise only), click Next.
If you are restoring from a backup, click Restore from Backup, then refer to Backing Up or Restoring Server Configuration for the procedure.
Click Next. The FIPS Options page appears.
When you enable FIPS mode, the ciphers, keys, and hash lengths and types that are not FIPS approved are not available. If a FIPS-approved state cannot be achieved when FIPS is enabled, the EFT Server service is stopped and an error is written to the Windows Event Log.
To use FIPS for SFTP (SSH2), select the Enable FIPS for SFTP check box.
To use FIPS for SSL, select the Enable FIPS for SSL check box.
A confirmation prompt appears when you select either check box. When you enable FIPS, the EFT Server service must be restarted. Click OK to continue with FIPS enabled or click Cancel if you do not want to use FIPS and restart the EFT Server service.
Click Next. The Remote Administration page appears.
If you do not want to allow remote administration, clear the check box.
If you want to allow remote administration, select the check box and specify the Listening port and Home IP address (or All Incoming). For security best practices and compliance with the PCI DSS, specify a port other than the default of 1100.
Click Next. If you chose remote administration, the Secure Remote Administration page appears.
Administrator account credentials are transmitted in plaintext unless SSL is enabled. Organizations complying with the PCI DSS are required to use SSL for remote administration. To enable secure remote administration, select the Use SSL for secure remote administration check box, then click Next. The SSL Certificate Options page appears.
Do one of the following:
In the Certificate and Private Key boxes, click the folder icon to browse for the private key pair files.
Click Create certificate to create one. Refer to SSL Certificate-Based Login, Creating Certificates, Importing a Certificate into the Trusted Certificate Database, and Importing Certificates from Microsoft IIS 5 for information regarding certificates.
Click Next. The Limit Remote Administrator IP Addresses page appears.
You should restrict remote administration to one or more known static IP addresses. You can configure this later and allow all IP addresses to connect for now. Otherwise, specify whether to Deny access to all remote IP addresses except for those you specify or Grant access to all remote IP addresses except for those you specify, then add the IP address exceptions to the list.
Click GRANT access or DENY access, then click Add. The IP Mask dialog box appears.
Specify the IP address or range of IP addresses to deny or grant access to the Site. You can use wildcards to select ranges of IP addresses.
If most IP addresses are allowed access, click granted, then list the exceptions.
If most IP addresses are denied access, click denied, then list the exceptions.
For example, if you click denied, then specify the range 200.200.100-200.*, all IP addresses are denied access, except those in the range 200.200.100.000 to 22.214.171.124.
Click OK to close the IP Mask dialog box. The IP address/mask appears in the Admin IP addresses filter box.
Click Next. The Auditing and Reporting page appears.
If you are using Auditing and Reporting, select the Enable auditing check box, then provide the information required to connect to the ARM database as described below. Otherwise, skip to the next step. (Auditing and reporting is a requirement of the PCI DSS.)
In the Database type area, specify whether you are using SQL Server or Oracle for the auditing database. (Oracle available in EFT Server Enterprise only.)
In the Host[\Instance Name] box, type EFT Server name or IP address.
If you are using SQL Server as the Auditing Database, \InstanceName corresponds to SQL Server's notion of named instances, a feature that allows a given computer to run multiple instances of the SQL Server Database Service. For more information, refer to .
In the Username and Password boxes, type the username and password used to connect to the database (not the EFT Server credentials).
In the Database Name box, type the name of the database.
In the Audit failure notification e-mail address box, type the e-mail address to which EFT Server is to send database connection error notifications. You can add as many e-mail addresses as needed; separate the addresses with a comma or semicolon. EFT Server uses its global SMTP e-mail settings from the SMTP Configuration to send the e-mails. You will configure those settings on the next page.
In the In case of audit database error area, specify an action for EFT Server to take if there is an error with the database. To stop recording data, select Stop auditing. To continue recording data to a file, select Audit to folder, and specify the location for the log file.
UNC paths are supported. The GlobalSCAPE Server service must run on a computer that has access to the network share, and the full UNC path must be used, that is: \\xcvd.forest.intranet.xc\Common_Files, not G:\Common.
Click Next. The specify SMTP Server Settings page appears.
In the From e-mail address box, specify the e-mail address for e-mail notifications (such as those triggered by Event Rules). This is the address that appears in the From box of e-mails sent by EFT Server. For example, type firstname.lastname@example.org.
In the SMTP host address boxes, specify the SMTP server host address and port.
If the SMTP server requires authorization, select the check box and provide the Username and Password.
Click Next. Server Setup is complete.
You are offered the option of continuing to the Site Setup wizard, or quitting the wizard, saving EFT Server settings, and configuring the Site(s) later. You must configure at least one Site to service inbound connections to EFT Server.
Click an option, then click Finish. If you chose FIPS mode for SSL and/or SSH, prompts appear explaining that EFT Server has entered FIPS mode. Click OK to dismiss the prompts.
If you chose Run the Site Setup wizard now, the Site Setup wizard Welcome page appears.
Refer to Defining Connections to EFT Server for the procedure for configuring the Site. The procedure differs depending on the user authentication type you choose.
Server Setup Wizard
Enabling FTPS, HTTPS (SSL) at the Site Level
Assigning a Certificate
Introduction to the PCI DSS HS Module