FTP Server Connection Guide TRIP and Cross-content page 1/16
Table of Contents 1 Introduction...3 2 System Requirements...4 3 General policy about customer folders...5 4 FTP Server...6 4.1 Server Overview...6 4.2 Server Details...6 5 Connection Methods...6 5.1 Command Based FTP Clients...6 5.2 GUI Based FTP Clients...7 5.3 Internet Explorer as a FTP client (Downloading only)...8 5.4 Windows Explorer as a FTP client (Downloading and uploading)...9 6 FTP Client Compability... 10 7 FTP Reply Codes... 11 7.1 Reply Code Overview... 11 7.2 Reply Code table sorted by Function Groups... 12 7.3 Reply Code table in numeric order... 14 8 Contact Information... 16 8.1 Technical Support... 16 8.2 Product Manager... 16 page 2/16
1 Introduction Dear customer, This document is a guide about using the TRIP products FTP server at Tieto Sweden AB. If you experience any technical problems with the ftp server or the connection, please contact TRIP Support Sweden at tripsupport@tieto.com. If you have any questions about the content such as products or versions, please contact the TRIP product manager. See all Contact information at the last section of this document. This is a personal document and is not to be redistributed. Thank you! page 3/16
2 System Requirements A proper installed and configured FTP Client software that is compatible with the specifications described in the RFC:959 memo that is available at URL http://www.w3.org/protocols/rfc959/. No other special requirements such as platforms och O/S versions. page 4/16
3 General policy about customer folders Following is applicable for both customers as Tieto personel. A customer folder with a personal login allows the user to upload files. For this reason, a higher level of security is desirable, both for Tieto as for the customer. In order to achieve a sufficient level of security, it is good practice to only use the ftp area as a buffer zone and delete files when each upload has been retrieved by the receiver, at latest at the end of the working day. Keep sensitive files at your own LAN (Local Area Network) instead. Files and folders that have a modified date older than 3 days will be deleted by a scheduled task at midnight every day. This means that all files should be contained in compressed files with the current date, such as ZIP or tar files. If not, it will be deleted at 24:00 the same day. page 5/16
4 FTP Server 4.1 Server Overview This FTP Server is not registered with a domain on the Internet. Connection is only possible using the IP address. 4.2 Server Details FTP Server details Description Host name TEMS-TRIP (Not used for connection) IP-address 193.12.180.102 Hardware HP Proliant ML110 G5 C2D Intel Core 2 Duo E7400 2.80GHz Internal memory: 4GB HDD: SATA 250 GB + 1 TB Operating System Windows 2003 Server x64 FTP Server FTP Server for Microsoft Internet Information Service version 6.0 with NTFS user authentication. Configurated to handle both active and passive ftp connections. User tripcust Password Contact TRIP Support to receive a password. 5 Connection Methods 5.1 Command Based FTP Clients A typical command based client is started from a command prompt with following syntax: FTP [-v] [-d] [-i] [-n] [-g] [-s:filename] [-a] [-w:windowsize] [-A] [host] -v Suppresses display of remote server responses. -n Suppresses auto-login upon initial connection. -i Turns off interactive prompting during multiple file transfers. -d Enables debugging. -g Disables filename globbing (see GLOB command). -s:filename Specifies a text file containing FTP commands; the commands will automatically run after FTP starts. -a Use any local interface when binding data connection. -A login as anonymous. -w:buffersize Overrides the default transfer buffer size of 4096. host Specifies the host name or IP address of the remote host to connect to. During a ftp client session, type? <RET> to list all commands. To get help for each command, type? <command>. N/B: Remember to use correct transfer type for the files to be copied, i.e. binary or ascii. page 6/16
5.2 GUI Based FTP Clients A GUI (Graphic User Interface) based client is often the most conveniant way to connect to a FTP server. There are many GUI FTP clients available with different methods of creating new connections, so we just demonstrate on of them here as an example: Example, creating a new connection with WRQ Reflection FTP client: IP address 193.12.180.102 and select user login (not Anonymous). Note the Advanced button where more settings can be done while running the connsction wizard in Reflection FTP. Set username tripcust and only Save password if you are a single user on your client host login. Finnish the Wizard and start a connection. page 7/16
5.3 Internet Explorer as a FTP client (Downloading only) Many of the web browsers available today are also able to connect thru a built in ftp service. However, it is rare that they have all of the functionality that is needed to get full control over a ftp connection, at least by default. More about different web browsers are described under the section Recommended FTP Clients in this document. Here are some notes about connecting to an ftp server thru Internet Explorer 7: The ftp adress is entered in the URL field of the web browser with the user name: You will be asked for username and password in a popup windows There are som restrictions in web browsers regarding ftp connections that sometimes is hard to get around. Limitations and notes about the most common ftp connections are listed in the table under FTP Client Compability. page 8/16
5.4 Windows Explorer as a FTP client (Downloading and uploading) First, Internet Options needs to be authorized to view FTP outside Internet Explorer. In Windows 7, go to Start and enter "inetcpl.cpl" in field Search programs and files and press Enter. Internet Options should appear. Select tab Advanced and check Enable FTP folder view (outside Internet Explorer) under section Browsing. Click Apply/OK. Start Windows Explorer. Enter the FTP URL without user name and press Return. and login page 9/16
6 FTP Client Compability Table below describes a selected list of possible FTP clients. FTP Client Details DOS Cmd command window DOS Cmd command window and CygWin FTP client. Reflection FTP Client (all versions) PuTTY FTP Client (all versions) Filezilla FTP Client (all versions) BulletProof FTP Client (all versions) Microsoft Internet Explorer version 6 Microsoft Internet Explorer version 7 and later. Microsoft Windows Explorer Mozilla Firefox version 1.5 and later. Opera Safari for MacOS Safari for Windows version 3.0.3 and later. Description Full functionality with folder browsing from home Full functionality with folder browsing from home Full functionality with folder browsing from home Full functionality with folder browsing from home Full functionality with folder browsing from home Not tested. Not recommended. Checkbox Tools, Internet Options, Advanced, Enable FTP folder view must be enabled. Limited functionality. Does not start in home directory and connection must contain a full path to the ftp user s home Not recommended. Checkbox Tools, Internet Options, Advanced, Enable FTP folder view can be enabled or disabled. Limited functionality. Does not start in home directory and connection must contain a full path to the ftp user s home In version 6 and 7 of Internet Explorer, checkbox Tools, Internet Options, Advanced, Enable FTP folder view must be enabled. Full functionality with folder browsing at home Full functionality with folder browsing from root home Not tested yet. Not tested yet. Not recommended for security reasons. Safari can t open the page ftp://193.12.180.102/. This occurs since Safari always connects to FTP servers anonymous. A workaround is to enter the username and password in the FTP URL like this: ftp://<username>:<password>@193.12.180.102 page 10/16
7 FTP Reply Codes 7.1 Reply Code Overview An FTP reply consists of a three digit number followed by some text. The three digits of the reply each have a special significance. There are five values for the first digit of the reply code: 1yz Positive Preliminary reply 2yz Positive Completion reply 3yz Positive Intermediate reply 4yz Transient Negative Completion reply 5yz Permanent Negative Completion reply The following function groupings are encoded in the second digit: x0z Syntax - These replies refer to syntax errors, x1z Information - These are replies to requests for information, such as status or help. x2z Connections - Replies referring to the control and data connections. x3z Authentication and accounting - Replies for the login process and accounting procedures. x4z Unspecified as yet. x5z File system These replies indicate the status of the Server file system vis-a-vis the requested transfer or other file system action. The third digit gives a finer gradation of meaning in each of the function categories, specified by the second digit. The lists (same list in two different orders) of return codes below will illustrate this. page 11/16
7.2 Reply Code table sorted by Function Groups Code Function Group Description 200 Command okay. 500 Syntax error, command unrecognized. This may include errors such as command line too long. 501 Syntax error in parameters or arguments. 202 Command not implemented, superfluous at this site. 502 Command not implemented. 503 Bad sequence of commands. 504 Command not implemented for that parameter. 110 Restart marker reply. In this case, the text is exact and not left to the particular implementation; it must read: MARK yyyy = mmmm Where yyyy is User-process data stream marker, and mmmm server's equivalent marker (note the spaces between markers and "="). 211 System status, or system help reply. 212 Directory status. 213 File status. 214 Help message. On how to use the server or the meaning of a particular non-standard command. This reply is useful only to the human user. 215 NAME system type. Where NAME is an official system name from the list in the Assigned Numbers document. 120 Service ready in nnn minutes. 220 Service ready for new user. 221 Service closing control connection. Logged out if appropriate. 421 Service not available, closing control connection. This may be a reply to any command if the service knows it must shut down. 125 Data connection already open; transfer starting. 225 Data connection open; no transfer in progress. 425 Can't open data connection. 226 Closing data connection. Requested file action successful (for example, file transfer or file abort). 426 Connection closed; transfer aborted. 227 Entering Passive Mode (h1,h2,h3,h4,p1,p2). 230 User logged in, proceed. 530 Not logged in. 331 User name okay, need password. 332 Need account for login. 532 Need account for storing files. 150 File status okay; about to open data page 12/16
connection. 250 Requested file action okay, completed. 257 "PATHNAME" created. 350 Requested file action pending further information. 450 Requested file action not taken. File unavailable (e.g., file busy). 550 Requested action not taken. File unavailable (e.g., file not found, no access). 451 Requested action aborted. Local error in processing. 551 Requested action aborted. Page type unknown. 452 Requested action not taken. Insufficient storage space in system. 552 Requested file action aborted. Exceeded storage allocation (for current directory or dataset). 553 Requested action not taken. File name not allowed. page 13/16
7.3 Reply Code table in numeric order Code Function Group Description 110 Restart marker reply. In this case, the text is exact and not left to the particular implementation; it must read: MARK yyyy = mmmm Where yyyy is User-process data stream marker, and mmmm server's equivalent marker (note the spaces between markers and "="). 120 Service ready in nnn minutes. 125 Data connection already open; transfer starting. 150 File status okay; about to open data connection. 200 Command okay. 202 Command not implemented, superfluous at this site. 211 System status, or system help reply. 212 Directory status. 213 File status. 214 Help message. On how to use the server or the meaning of a particular non-standard command. This reply is useful only to the human user. 215 NAME system type. Where NAME is an official system name from the list in the Assigned Numbers document. 220 Service ready for new user. 221 Service closing control connection. Logged out if appropriate. 225 Data connection open; no transfer in progress. 226 Closing data connection. Requested file action successful (for example, file transfer or file abort). 227 Entering Passive Mode (h1,h2,h3,h4,p1,p2). 230 User logged in, proceed. 250 Requested file action okay, completed. 257 "PATHNAME" created. 331 User name okay, need password. 332 Need account for login. 350 Requested file action pending further information. 421 Service not available, closing control connection. page 14/16 This may be a reply to any command if the service knows it must shut down. 425 Can't open data connection. 426 Connection closed; transfer aborted. 450 Requested file action not taken. File unavailable (e.g., file busy). 451 Requested action aborted. Local error in processing. 452 Requested action not taken. Insufficient storage space in system.
500 Syntax error, command unrecognized. This may include errors such as command line too long. 501 Syntax error in parameters or arguments. 502 Command not implemented. 503 Bad sequence of commands. 504 Command not implemented for that parameter. 530 Not logged in. 532 Need account for storing files. 550 Requested action not taken. File unavailable (e.g., file not found, no access). 551 Requested action aborted. Page type unknown. 552 Requested file action aborted. Exceeded storage allocation (for current directory or dataset). 553 Requested action not taken. File name not allowed. page 15/16
8 Contact Information 8.1 Technical Support TRIP and Cross-content Support Sweden Email tripsupport@tieto.com Phone +46 (0)10 48 12151 Fax +46 (0)10 48 12152 8.2 Product Manager Vesa A Vainio Product Manager Tieto Email vesa.a.vainio@tieto.com Mobile +358 40 530 2656 P.O.Box 300 02631 Espoo Finland page 16/16