Using an Internet Browser or Windows Explorer as an FTP Client
While full featured FTP client programs provide the power and flexibility needed for larger projects, there are some situations where a lite FTP client will be suitable.
Using software that is already installed on your computer allows you to side step having to remember and type tedious manual FTP commands, eliminates the worries of licensing 3rd party software products, and provides you with a user interface for your FTP session.
This document provides some general suggestions on how to use your browser (IE, Netscape, etc.) or Windows Explorer as a lite FTP client.
Connect to the Correct Port
I'm sure you've noticed the "http://" at the beginning of a URL. This prefix signifies that your session is attempting to connect to port 80 (the HTTP port) on the remote server. Instead of connecting to port 80, an FTP session generally will connect to the server on port 21. To specify this in the address that you use, you will need to begin the address with "ftp://". For example, if our FTP server is named "TuxBox" and resides in the domain "Testnet1.com", I could connect to its FTP server by typing "ftp://tuxbox.testnet1.com". This is illustrated in the graphics below.
Windows Explorer
Internet Explorer ®
Netscape Navigator ®
Connecting in the manner described above should work for any FTP site that allows anonymous access.
But what about security?
Anonymous FTP Servers are an integral part of the internet. In fact, the installation of Red Hat Linux 9 ®that runs this website was downloaded from Duke University's anonymous FTP site (found on http://www.redhat.com/download/mirror.html).
Although such Open-Access sites hold this indispensable position, most FTP sites require a username and password to gain access (or will require a username and password to allow uploading).
In this example, will connect to our fictitious FTP site, tuxbox.testnet1.com, with our fictitious user "FTPUser" whose password is "S3cr3t1" (like the words "Secret One").
To connect to an FTP site with a username and password, this information must be entered into the URL. Microsoft ® Internet Explorer ® and Windows Explorer allow you to add only the username to the URL. After a connection is initiated, Explorer will prompt you for a password.
This information is added to he URL in a similar form that you would type an email address. Enter the username, followed by an @ symbol, followed by the site you are connecting to (ie. "ftp://FTPUser@tuxbox.testnet1.com").
Note: This method DOES NOT work with Netscape browsers. For Netscape and many other browsers, you will need to enter the password into the URL also (as described below).
You may also enter the password (along with the username) in the URL, instead of being prompted for a password.
To enter the password into the URL follow this syntax: "ftp://" + username (ie. FTPUser) + colon (:) + password (ie. S3cr3t1) + @ symbol + sitename (ie. tuxbox.testnet1.com).
ftp://FTPUser:S3cr3t1@tuxbox.testnet1.com
Netscape Navigator ®
Internet Explorer ®
The above methods of connecting work with Internet Explorer ®, Windows Explorer, and Netscape ® browsers; however, IE, and Windows Explorer gain a major advantage when used as an FTP client.
Netscape and many other browsers retain the username and password information in the URL once connected to the site. This username and password information remains in the address bar for the entire FTP session, revealing your password to any onlookers who may choose to peer over your shoulder. This is not good.
IE and Windows Explorer will automatically remove the username and password information from the URL after you are connected to the FTP site. Much, much better in this implementation.
The graphics below depict our FTPUser connected to the same site, and connected using the same URL (user and pass included), with different browsers.
Netscape Navigator ® Exploded Address Bar Showing Username and Password
Internet Explorer ® Exploded Address Bar NOT Showing Username and Password
Fusion 13 has taken painstaking effort to ensure the validity of its data;
however, the information contained in this document is provided without warranty.
The data presented is offered simply as a suggestion.
Fusion 13 can in no way be held responsible for how these suggestions are implemented in any environment.
