Using the COM API on a Remote Computer

You can use the EFT COM API on a computer on which you have installed the remote administration interface or on which you have installed the necessary DLL files. For example, you might want to communicate with EFT using a PowerShell script from the remote computer that does not have the administration interface installed. To do this, you must first copy the applicable DLL files to a folder on the remote computer and register SFTPCOMInterface.DLL on the remote computer using regsvr32 (described below).

NOTE: Remote administration is not allowed after the trial expires if you do not activate the software.

Before you can connect from the remote EFT administrator interface, you must configure the Server. You must do this locally, on the EFT COM API computer.

  • Before attempting to connect to a remote EFT COM API, first be sure that the remote EFT COM API service is running, and that it allows remote administration.

If you have configured remote administration, but are unable to connect to EFT COM API, one or more of the following could be preventing the connection:

  • The IP address of the computer on which you are attempting to connect to EFT COM API is listed in the Remote Administration Ban IP list.

  • Your SSL certificate is expired or invalid.

  • Remote administration is not enabled.

  • The remote administration port value has changed.

  • EFT COM API’s IP address has changed since the last login.

  • The firewall settings of the computer on which EFT COM API is installed are blocking the connection.

  • There is a version mismatch between your administration interface and the EFT COM API service you are trying to administer.

  • The administrator account with which you are attempting the remote connection does not have access permission to EFT COM API.

  • Network errors

Copying Required DLL Files to the Remote Computer

Administering EFT COM API remotely requires that you copy the following DLL files in ..\Program Files\Common Files\Globalscape\SFTPCOMInterface from the EFT COM API computer to the computer that will be making the remote COM calls

  • sftp2.dll

  • log4cplus.dll

  • SSL.dll

  • SFTPCOMInterface.dll (You must register SFTPCOMInterface.dll on the remote computer, as shown below.)

All DLL files should be copied to the same folder as the SFTPCOMInterface.dll and should not be moved after the SFTPCOMInterface.dll is registered using regsvr32.exe, as described below:

To register SFTPCOMInterface.dll

  • In the directory on the remote computer to which you copied the above files, run regsvr32. For example, type:

Regsvr32.exe SFTPCOMInterface.dll

For more information about the Registration Tool (regsvr32.exe), refer to Explanation of Regsvr32 usage and error messages on the Microsoft Support site (for both 32-bit and 64-bit OS).

Below are several facts to consider regarding remote administration:

  • You are prohibited from creating certificates for EFT COM API while remotely administering EFT COM API because this action can create a security breach. Any certificates you create remain on the computer on which you created them, unless you take steps to deliver and associate these files with another computer.

  • Organizations complying with the PCI DSS are required to use SSL for remote administration. If you attempt to allow remote administration on a Site configured with "strict security settings for PCI DSS," a message warns you that this setting violates PCI DSS, and allows you to "continue with reason" or disable the feature.

  • File browse operations are disabled for remote administration. You can, however, type a path that is relevant to the EFT COM API computer (not the remote interface). You are able to browse for a Settings Template folder, because you are browsing the VFS, not the physical folders.

  • When the trial period has expired, all remote connections are disallowed.

  • You cannot configure remote administration remotely.

  • You must configure the local connection before you can configure a remote connection.

  • For remote Active Directory connections, the connecting account must have access to the computer on which EFT COM API is installed.

  • You should restrict remote administration to one or more known static IP addresses.

  • By default, all IP addresses are granted remote access to EFT COM API. EFT COM API allows you to grant access to only one specific IP address or a range of IP addresses, or deny access to one specific address or a range of addresses.

  • For command-line login, the EFT COM API listening IP address must be set to a specific IP address, not "All Incoming." Remote administration must be configured and EFT COM API must be in the same domain as the computer from which you are attempting to log in.

  • If you are logged in to EFT COM API remotely, your username and password are passed to the Windows System Services on the computer running EFT COM API. The account that you log on with must have administrative rights to make any changes to the Globalscape EFT COM API service running on that computer.

  • If you are using SQL Express as your database, you may not be able to generate a report remotely, unless the connecting account is a trusted SQL Server connection (e.g., if SQL Server and the remote computer are in the same domain, or if SQL Server is configured to allow "mixed authentication.")

  • When objects are created, added, removed, modified, enabled, disabled, started, or stopped remotely, the action is logged to the database and reported in the Admin - Audit Log report.

  • The EFT COM API variable for remote EFT COM API connections is %CONNECTION.REMOTE_IP%.

 

NOTE: For help using the COM API, refer to the online help for the COM API.