In addition to the WWW service, Microsoft Peer Web Services for Windows NT provides two additional services: File Transfer Protocol (FTP) and gopher. These services are legacy services on the Internet, meaning that they are older protocols. However, far from being outdated, these services simplicity is often a compelling reason to consider using them in your Web site.
This chapter explains:
FTP was one of the earliest protocols used on TCP/IP networks and the Internet. FTP is used to transfer files from one computer on a network to another computer on the same network. FTP was especially useful for transferring files between different computers, such as transferring files from a UNIX computer to a computer running MS-DOS® or Windows 3.1.
Early FTP client software was character based, and was similar to using the Windows NT command prompt to list and copy files. A character-based program was used to log on to the remote computer, browse directories, and to then transfer files.
Internet Explorer simplifies this process by automatically logging you onto the FTP server if anonymous connections are permitted. Directory listings are automatically displayed as hypertext links, permitting point-and-click simplicity in traversing directories and copying files from a server to a client. (Note that you cannot copy files from a client to a server by using Internet Explorer.)
The World Wide Web (WWW) has replaced most functions of FTP. However, of the three Internet services, only FTP can be used to copy files from a client computer to a server computer. If your remote users need to do this, they must use FTP.
Also, if you have existing files that you want to make available to remote users, FTP is an extremely easy service to install and maintain. After installation, point the FTP service to your files; no additional configuration is necessary.
Files made available through FTP can be in any format, such as document files, multimedia files, or application files. If your remote clients are using Internet Explorer, the clients can specify whether to copy the file or to start a helper application to immediately display or play the file.
The FTP service requires that users log on to your workstation to use the service. Once logged on, users can navigate the directories made available to the FTP service. And on older, dedicated FTP clients, remote users can copy files to the FTP site and issue other FTP commands, including logging off.
You can configure the number of simultaneous connections allowed, and the amount of time allowed for connections.
Because users are logged on until they log off or break the connection, you can use the Connected Users button in the Service property sheet to keep track of which users are currently connected.
2. Click the Service tab.
3. Click Current Sessions.
4. If you want to disconnect a user, select the user and then click Disconnect. To disconnect all connections, click Disconnect All.
5. Click Close and then click OK.
You use Internet Service Manager to configure logon requirements for the FTP service.
If the FTP service is configured for anonymous logon, clients can log on with the user name anonymous. Traditionally, anonymous FTP users log on using their e-mail addresses as passwords. Note that Internet Explorer automatically logs on anonymously to all FTP sites that permit anonymous logon.
FTP clients are also permitted, by default, to log on with a Windows NT username and password permitted to use that computer. This allows you to control every users access permissions and file access on Windows NT File System (NTFS) drives.
Select the Allow anonymous only check box to prevent users from using usernames. With this check box enabled, any account other than anonymous cannot log on. This is useful for security because only one account, that assigned for anonymous logon, is permitted access; intruders cannot attempt to gain access with the administrator account.
2. In the Allow Anonymous Connections box, type the username and password that you want the FTP service to use when accessing resources on behalf of a client.
2. Click the Messages tab.
3. In the Welcome message box, type the welcome message you want to display when users connect.
4. In the Exit message box, type the message you want to display when users disconnect.
5. In the Maximum connections message box, type the message you want to display when a user tries to connect but cannot because the maximum number of users are already connected.
6. Click Apply and then click OK.
You can also add virtual directories, just as with the WWW service; however, because of FTPs technical limitations as an older protocol, virtual directories are not visible to users. Users can browse a virtual directory only if they know the alias of the virtual directory.
Some browsers require that the FTP listing be styled in UNIX format. You should set the FTP listing style to UNIX format for maximum compatibility with browsers.
2. In the Directory Listing Style box, select:
MS-DOS to display directories in MS-DOS format.
Read permission is set for all directories by default. Remove Read permission and set Write permission to create a dedicated directory to which users can copy files but cannot see any files left by others.
Setting Write permission will allow users to leave files on your computer.
You must set Read and Write permission by using Internet Service Manager. On NTFS drives you must also set matching permissions by using File Manager.
Read
Read permission is set for all directories by default. Remove Read permission and set Write permission to create a dedicated directory to which users can copy files, but cannot see any files left by others.
Write
Setting Write permission will allow users to place files on your computer.
Each directory can contain an annotation file, which can be used to summarize the information that the directory contains. This summary appears automatically to remote browsers.
You can add directory descriptions to show FTP users the contents of a particular directory on an FTP site. This is done by creating a file called ~ftpsvc~.ckm in that directory. Usually you want to make this a hidden file so that directory listings do not display it.
You can add directory descriptions to inform FTP users of the contents of directories on an FTP site.
2. In the Windows NT File Manager, select the file and make it a hidden file so that directory listings do not display this file.
3. From an FTP client, type Site ckm at the command prompt, or use the Registry Editor to enable annotated directories by adding the following value:
HKEY_LOCAL_MACHINE\SYSTEM
\CurrentControlSet
\Services
\MSFTPSVC
\Parameters
AnnotateDirectories | REG_DWORD |
Range: 0 or 1 Default = 0 (false that is, directory annotation is off). |
The preceding value defines the default behavior of directory annotation for newly connected users. Directory descriptions are used to inform FTP users of the contents of a directory on an FTP site. The directory description is saved in a file named ~ftpsvc~.ckm, which is usually a hidden file. When this value is 1, directory annotation is enabled.
This Registry entry does not appear by default in the Registry, so you must add an entry if you want to change its default value.
|
If Directory Annotation is enabled on your FTP service, Web browsers may display error messages when browsing your FTP directories. You can eliminate such errors by limiting each annotation file to one line or by disabling Directory Annotation.
You can add special directories to the home directories to control the root directory displayed to FTP users. These directories must be physical subdirectories; they cannot be specified by using virtual directories.
Username directories are directories in the home directory with names that match a username. If a user logs on with a username that has a matching directory in the home directory, that directory is used as the root.
You can use FTP username directories to control the root directory presented to users. FTP username directories are not created by default during setup.
The Anonymous directory is a directory in the home directory named Anonymous. If a user logs on using the password Anonymous, the directory name Anonymous is used as the root.
You can use FTP username directories to control the root directory presented to users. FTP username directories are not created by default during setup.
You can use any FTP client to connect to the computer running the FTP service. Windows NT Workstation and Windows NT Server include a character-based FTP client (this client can be started only at the command prompt).
Microsoft Windows NT includes Internet Explorer, which allows you to browse FTP sites. You use a Uniform Resource Locator (URL) to connect to an FTP site; for example, ftp://ftp.microsoft.com/.
Although the gopher service is similar to FTP because it allows you to easily publish existing archives of files, the gopher service overcomes some limitations of the FTP service. With the gopher service, you can create links to other computers or services, annotate your files and directories, and create custom menus.
The Microsoft Windows NT gopher service supports all gopher features. In addition, the gopher service supports gopher plus selector strings, which allows the server to return additional information to the client, such as administrator name, modification date, and MIME type.
To set up a gopher site, copy your files to the gopher home directory (\Inetsrv\Gophroot by default). Clients can then browse the gopher directories as easily as using File Manager. To enhance your site you can create tag files that enable links to other computers or services, to annotate your files and directories, and to create custom menus. See Tag Files, later in this chapter, for more information.
This section gives you an overview of configuring the gopher service. To configure your service you should configure the following:
2. In the Anonymous Logon box, type the username and password that you want the gopher service to use when accessing resources on behalf of a gopher client.
To enable Wide Area Information Search (WAIS) index searching, you must change the following entry in the Windows NT Registry from 0 (disabled) to 1 (enabled):
HKEY_LOCAL_MACHINE\SYSTEM
\CurrentControlSet
\Services
\GopherSVC
\CheckForWAISDB
Tag files allow you to supplement the standard gopher display returned to clients with additional information and to provide links to other computers.
All information about a file that is sent to a client comes from tag files. This information includes the name of a file displayed for the client. Typical tag files contain:
If you are running gopher plus, you can add more information to each tag file, such as the server administrators name and e-mail name, the files date of creation, and date of last modification.
You must first create the file and then store it on the gopher server, the computer running the gopher service.
You create tags for your gopher site with the gdsset utility. To see the complete syntax of the gdsset command, type gdsset at the command line with no parameters.
Tag files are hidden files. Use File Manager to set the hidden attribute for tag files.
On drives formatted using the FAT file system, the tag filename is the same as the file it describes, with .gtg appended to the filename. For example, if the content filename is Catalog.txt then the tag filename would be Catalog.txt.gtg.
On drives formatted using NTFS, the tag filename is the same as the file it describes with :gtg appended to the filename. NTFS tag files are stored in an alternate data stream. For example, if the content filename is Catalog.txt then the tag filename would be Catalog.txt:gtg. Note that a colon rather than a period is used to start the extension.
Tag files stored on FAT volumes can be edited using most ASCII-based text editors, such as Notepad. The file may need to be unhidden to edit it. Tag files stored on NTFS volumes cannot be edited by most text editors because the file is stored in an alternate data stream.
Note that if your computer is configured for NTFS, you must move the tag file manually when you move the corresponding data files. To move the tag file, first make it visible, because tag files are hidden files. Then move the file, and make hidden it again. (You can use File Manager to make files hidden or visible.)
where
This command line automatically hides the tag files you create.
To create a batch command to tag a series of files that have the same type, such as a series of text files, use the following syntax:
for %1 in (*.txt) do <echo %i&& gdsset -c -gn -f %i %I
where
Gdsset automatically hides the tag files you create.
The following command displays information stored in a tag file:
To create a batch command to tag a series of files that have the same type, such as a series of text files, use the following syntax:
The following list shows all possible gopher item type codes and what they mean. The first character is the type code.
0 A file, usually a flat text file.
1 A gopher directory.
2 A CSO phone-book server.
3 An error.
4 A Macintosh® file in Binhex format.
5 An MS-DOS binary archive.
6 A UNIX Uuencoded file.
7 An index-search server.
8 A Telnet session.
9 A binary file.
c A calendar or calendar of events.
g A graphic interchange file (GIF) graphic.
h An HTML World Wide Web hypertext page.
i An in-line text that is not an item.
I Another kind of image file.
m A BSD format mbox file.
P A PDF document.
T A TN3270 mainframe session.
: A bitmap Image (use gopher plus information for type of image).
© 1996 by Microsoft Corporation. All rights reserved.