RFTP Server
Windows operating system
1. Use Windows Explorer to browse to the RFTP folder (usually C:\RFTP)
2. Double click on RftpServer
UNIX operating system
1. Change directory to the directory that contains the rftp directory.
2. Type in the command:
java rftp.RftpServer
3. After the IP address is printed, hit enter once.
 Top
The RFTP Server must be running in order for users to access the server computer and transfer files. Before the server is started, a permissions file must be created to tell the server what users are allowed access to the server machine. The Security section explains how to create this file.
The server keeps track of every command that a user has entered and every action the server takes in a log file. In order to see a record of what the RFTP Server has done, see the Tracking the RFTP Server Use section where the log files are described.
Top
This is what the RFTP Server looks like when it is started on a Windows computer. The first two lines are setup and initialization. Then the RFTP Server prints out the name of its home folder, which is C:\server in this example. Next it asks the user to press any key when the computer is connected to the Internet. If you are connecting from a networked machine, you are probably already on the Internet. If you are connecting from a home computer with a dial-up connection, you need to connect to the Internet before proceeding.
Every computer on the Internet has a unique IP address, which is used to identify that computer. If you connect to the Internet using a dial-up connection, your computer will be assigned a new IP address every time you connect. The RFTP Server prints out its IP address after the user presses the enter key. This is the address that users must enter into the RFTP File Mover or the RFTP Console Interface in order to connect to the RFTP Server. The IP address does not include the text "office1/" that is printed in this example just before the address. The IP address above is "206.151.188.104".
If you see an address of 127.0.0.1, it means that your machine is NOT connected to the Internet. The only time you may use the 127.0.0.1 address is when you are purposely running both the RFTP Server and the user program from the same machine to test RFTP and are not connected to the Internet.
Next, the RFTP Server requests the name of the permissions file. See the Security section for more information on the permissions file. If the permissions file is in the home folder of the RFTP Server, the name of the file may simply be entered here. Or the entire pathname may be entered if the file is located elsewhere. Don't forget to include the file name extension on the filename. (.txt is the extension in the example.) the RFTP Server verifies that the permissions file exists and says it is ready for clients if the file exists, or tells you to start over if the permissions file doesn't exist. When the server says it is ready for clients, it will continue to run and serve clients until it is exited. The window that it runs in may be minimized. To exit the server, enter Control-C in the window.
Top
Security is provided on the server with a permissions file. This file contains the user name, password, and allowed folder, separated by tabs or spaces. The allowed folder is the name of a folder or drive. The user is allowed access to the allowed folder and all of its sub folders. An asterisk can be used to indicate that the user is allowed access to all system drives and folders.
As described in the Using the RFTP Server section, the RFTP Server prompts the administrator for the name of the permissions file. The name of the file, including extension, is entered. Each time a user starts a session, the permissions file is read and the user’s access level determined.
The RFTP Server administrator is responsible for maintaining the permissions file. The permissions file must be a plain text file, so it is best created in notepad. Create the file exactly as shown below, using login names and passwords that you will provide to your users. It is best to restrict their access to a special area created to hold only the files you want the users to have access to. It is not advisable to allow users access to systems files or Windows folders, where they could accidentally overwrite a systems file.
Permission file example:
Mary 345tr4 * User Mary has access to the entire system.
Larry br45 C:\ Separate the fields with tabs or spaces.
Janet 76hart D:\data Janet is restricted folders under the D:\data folder
JohnS poicii A:\
 
The permission file is ended with a row containing a tab or a space.
An additional layer of security is provided by restricting access to the permission file to the server machine. The permissions file on the server can not be accessed from the remote RFTP process. The permissions file name is displayed in its folder in File Mover, or listed upon request from the RFTP Console Interface, but requests to transfer to or from the permission file are denied.
Top
The RFTP Server keeps a log file of every transaction it makes during a users connection. This log file is automatically created in a folder named "log" in the home folder of the RFTP Server. The log file is named with the date and time that the RFTP Server started it. If the RFTP Server is started at 8:01 a.m. on January 22, 2000, the log file created is named 200001220801.
The log file tracks every command that is input to the RFTP Server, and the response sent back. Each connection being handled by the server is assigned a new client number. Each entry is marked with the date, client number and the command being sent to the server, or the response being sent to the client.
In the sample log file below, you can see an attempt to access the permissions file, with the access denied response, an aborted file transfer, and a complete file transfer before the user logs out.
Sun Jan 16 14:39:19 GMT+00:00 2000 CLIENT: 1 CMD_IN: PWD C:\server\
Sun Jan 16 14:39:19 GMT+00:00 2000 CLIENT: 1 CMD_OUT: 150 ***Opening data connection.***
Sun Jan 16 14:39:19 GMT+00:00 2000 CLIENT: 1 CMD_OUT: 200 ***PWD completed successfully***
Sun Jan 16 14:39:20 GMT+00:00 2000 CLIENT: 1 CMD_IN: LIST C:\server\
Sun Jan 16 14:39:20 GMT+00:00 2000 CLIENT: 1 CMD_OUT: 150 ***File status okay; about to open data connection.***
Sun Jan 16 14:39:20 GMT+00:00 2000 CLIENT: 1 CMD_OUT: 226 ***Closing data connection. Request Successful.***
Sun Jan 16 14:39:22 GMT+00:00 2000 CLIENT: 1 CMD_IN: STAT C:\server\perms.txt
Sun Jan 16 14:39:29 GMT+00:00 2000 CLIENT: 1 CMD_OUT: 500 ***File Access denied***
Sun Jan 16 14:40:38 GMT+00:00 2000 CLIENT: 1 CMD_IN: STAT C:\junk11.txt
Sun Jan 16 14:40:38 GMT+00:00 2000 CLIENT: 1 CMD_OUT: 213 ***File status:: Last Modified: Sat Dec 18 22:16:22 GMT+00:00 1999 Size: 5682336***
Sun Jan 16 14:40:38 GMT+00:00 2000 CLIENT: 1 CMD_IN: STAT C:\junk11.txt
Sun Jan 16 14:40:58 GMT+00:00 2000 CLIENT: 1 CMD_OUT: 213 ***File status:: Last Modified: Sat Dec 18 22:16:22 GMT+00:00 1999 Size: 5682336***
Sun Jan 16 14:40:58 GMT+00:00 2000 CLIENT: 1 CMD_IN: RETR C:\junk11.txt C:\junk234.txt 0
Sun Jan 16 14:40:58 GMT+00:00 2000 CLIENT: 1 CMD_OUT: 150 ***File Status ok. Opening data connection for transfer.***
Sun Jan 16 14:40:58 GMT+00:00 2000 CLIENT: 1 CMD_IN: ABOR
Sun Jan 16 14:41:04 GMT+00:00 2000 CLIENT: 1 CMD_OUT: 426 ***Requested file transfer aborted***
Sun Jan 16 14:41:04 GMT+00:00 2000 CLIENT: 1 CMD_OUT: 226 ***File transfer aborted successfully.***
Sun Jan 16 14:41:04 GMT+00:00 2000 CLIENT: 1 CMD_IN: STAT C:\junk234.txt
Sun Jan 16 14:41:26 GMT+00:00 2000 CLIENT: 1 CMD_OUT: 213 ***File status:: Last Modified: Sun Jan 16 14:41:06 GMT+00:00 2000 Size: 5682336***
Sun Jan 16 14:41:27 GMT+00:00 2000 CLIENT: 1 CMD_IN: STAT C:\junk234.txt
Sun Jan 16 14:41:27 GMT+00:00 2000 CLIENT: 1 CMD_OUT: 213 ***File status:: Last Modified: Sun Jan 16 14:41:06 GMT+00:00 2000 Size: 5682336***
.
.Sun Jan 16 14:41:43 GMT+00:00 2000 CLIENT: 1 CMD_IN: STAT C:\junk123.txt
Sun Jan 16 14:41:48 GMT+00:00 2000 CLIENT: 1 CMD_OUT: 213 ***File status:: Last Modified: Fri Nov 26 12:50:24 GMT+00:00 1999 Size: 51***
Sun Jan 16 14:41:48 GMT+00:00 2000 CLIENT: 1 CMD_IN: RETR C:\junk123.txt C:\junk234.txt 0
Sun Jan 16 14:41:48 GMT+00:00 2000 CLIENT: 1 CMD_OUT: 150 ***File Status ok. Opening data connection for transfer.***
Sun Jan 16 14:41:49 GMT+00:00 2000 CLIENT: 1 CMD_OUT: 226 ***File Transferred. Closed data Connection.***
Sun Jan 16 14:42:37 GMT+00:00 2000 CLIENT: 1 CMD_IN: QUIT
Sun Jan 16 14:43:56 GMT+00:00 2000 CLIENT: 1 CMD_OUT: 200 ***Logging out***
Top
|
