Additional FTP Information

FTP facilities provided by EKC to our customers:

EKC, Inc. provides our customers with a secure FTP server.   This server provides customers both classic File Transfer Protocol (FTP) and secured FTP via FTP/S to electronically deploy machine-readable materials to our customers.   Userids and Passwords are assigned to obtain access to our FTP Server.

This server may be used for downloading EKC products and maintenance for products intended for use by our customers.   Additionally, this facility may be used to upload machine readable materials that may be required to properly support EKC products on customer systems.

Background Information: classic FTP:

This form of FTP is the original FTP that has been around for almost a half or a century and is very reliable but not secure.   It is possible to view data as it is being transmitted by monitoring the connection, which may cause security concerns.   Many organizations have prohibited the use of this protocol in favor of FTPS or SFTP.

Classic FTP normally runs on ports 21 and either 20 or a random port depending on the FTP mode.   Our FTP server currently supports both PORT (active) and PASV (passive) modes.   PASV is recommended.   Make sure it is properly set ON in your FTP client or your Browser's advanced options.   Active FTP establishes a connection on port 21 and passes data on port 20. Passive FTP establishes a connection using port 21, and passes data on a random port (set by the FTP server).

Background Information: Secured FTP (FTP/S):

EKC, Inc. also provides FTP/S (File Transfer Protocol over Secure Sockets Layers) to electronically deploy machine-readable materials to our customers in a secured environment using SSL.

FTPS runs on port 990 (Implicit FTPS) and and sometimes on port 21 (Explicit FTPS).   If a client connects to port 990, the assumption is that the client intends to perform SSL, (SSL data encapsulation is provided).   Connecting on port 21 with the intention to use SSL will require sending an "AUTH SSL" or "AUTH TLS" command,  after which an SSL handshake is performed providing a secured SSL connection.

Accessing EKC's FTP server in your environment:

To access anyone's FTP server, you have to have access to the required TCP ports needed for the type of FTP you are requiring and the proper credentials required to access the target server.

You get your credentials (userid and password) from EKC.   If you do not already have them, please call EKC to obtain them.

Normally, organizations have at least one firewall between your point of access and your Internet Gateway router.   Unless your software to access FTP and your network is properly configured, accessing the EKC FTP server is impossible.   EKC receives support calls about FTP connectivity.   To date, other than forgotten userids and passwords, and granting access to specific downloads, no changes had to be made to EKC's FTP server or its firewalls to resolve customer FTP issues.

You can use any FTP client capable of the desired FTP protocol you choose to access our FTP server.   This includes mainframe computers, workstations with FTP clients, and workstations with a browser capable of the desired FTP protocol.

Best way to access FTP on a workstation:

Obtain an FTP client, such as FileZilla FTP, CORE FTP or IPSwitch FTP client.   There are others you can choose from.   Once you have a client installed, you can create a "SITE" and proceed to execute your FTP task.

Click on a FTP link on this website:

Its behavior is dependent on what version of the browser you are running:

What to expect using a browser:

Most browsers have some sort of FTP provision.   Some are better than others, even within the same software vendor.
It would appear to be a "work in progress".

It may work fine, requesting a signon and presenting you with an "Explorer" view of your folders.  
It may not work at all, resulting in a verity of browser messages.
It may work, but with poor interface issues, such as making you sign on for every request.
Please note, as of this writing, we know of no browsers that support FTPS or SFTP.

You may be presented with a complete list of the FTP root directory with a navigational message in front of it:

Final Thoughts:

Please, make sure there is nothing on your end that is causing you problems.   Make sure you have FTP ability throughout your network between the facility you are using all the way through to the Internet.   Make sure your FTP client is properly configured.  Insure you have the proper credentials and your intent is EKC related, (our FTP server normally does not contain materials for non-EKC products).

Facilities like personal firewalls on your workstation and what your workstation is attached to can and will present problems if not configured for this type of service.

EKC hopes your experience using our FTP server is a favorable one.   If you need assistance, please feel free to contact EKC.

Heartbleed Update:

In response to the revelation of the Heartbleed bug, EKC has upgraded our secure FTP server in accordance with the directions from the manufacturer.

EKC has also tested our FTP and web servers using tools provided by multiple security services, both before and after the FTP server upgrade, and have found no exposures that are a consequence of the Heartbleed bug.

EKC is committed to protecting the information provided by our customers in the course of problem determination and continues to make every effort to insure that confidential information is not subject to exposure.   We will continue to monitor the situation with regard to the Heartbleed bug and any other potential security issues with respect to our FTP and web sites.

If you feel you need additional help, please feel free to email us at:
or call our Technical Support Department at: (847) 296-8035.