FTP Client Connections

Beyond FTP will perform standard FTP client operations when communicating with a remote FTP server.  It portrays FTP servers in the same manner that it portrays local devices and remote Beyond FTP servers.  The only difference is that FTP server names begin with the prefix “ftp:” which is automatically assigned when the address book entry is created. 

There are several things to keep in mind when accessing FTP servers:

1.   The address book entry can be called anything.  The FTP server has no name per se.

2.   Beyond FTP displays a dummy drive level when the connection is opened.  This is always drive “C”, regardless of the actual drive name used by the FTP server.  All file names are displayed in standard Microsoft format.  The FTP Client Interface performs all translations necessary to communicate with a particular FTP server.

3.   Directories and files are displayed by interpreting the information returned by the FTP server in response to a LIST command.  Most FTP server types are automatically recognized by Beyond FTP.  However, there are those cases where a template must be created.  This allows you to define the manner in which Beyond FTP will translate the file and directory displays into usable information.  These templates are required for IBM MVS and AS400 systems, and any system running a Madgoat FTP server.

4.   Beyond FTP sends complete path information to the FTP server when changing directories and performing file actions.  This provides flexibility to operate outside of the default path assigned to the user account.  Some FTP servers are unable to accommodate this information.  Beyond FTP must be instructed to perform individual changes for each directory level before issuing the “put” or the “get” on a pathless file name.  All operations are performed relative to the current path, whatever it may be.  Specifying relative pathing increases overhead where multiple directory levels are involved, and limits access to the default directory assigned to the user account by the FTP server.

5.   Engaging an encryption algorithm causes files to be sent to the remote server in encrypted form.  They are automatically decrypted when retrieved by another Beyond FTP client or server.  The decryption succeeds if the same key is used for both the put and the get.