Configuring and Managing Internet Information Server
Internet Information Server provides a graphical administration tool called Internet Service Manager that you can use to monitor, configure, and control the Internet services.
Internet Service Manager is the central location from which you can control all of the computers running Internet Information Server in your organization. You can run Internet Service Manager on any computer that is running Windows NT Workstation or Windows NT Server and that is connected through the network to your Web server. With remote administration you can administer your Web servers from the server computer itself, from a management workstation on the corporate local area network (LAN), or even over the Internet.
Internet Service Manager uses the Windows NT security model, so only validated administrators are allowed to administer services, and administrator passwords are transmitted in encrypted form over the network.
In addition to Internet Service Manager, Internet Information Server provides an HTML-based Internet Service Manager that you can run from any Web browser. You can perform the same administration tasks by using either version of Internet Service Manager. In this guide, any reference to Internet Service Manager refers to both versions of the tool unless otherwise noted.
This chapter tells you how to:
You can also find all the computers on your network that are running Internet Information Server.
2. In the Server Name box, type the Web servers host name, IP address, or NetBIOS name.
2. From the list of servers displayed, double-click the one you want to connect to.
Note If you are running other Internet services, such as Network News Transfer Protocol (NNTP) and Simple Mail Transfer Protocol (SMTP), they will be listed in the Report view of Internet Server Manager, along with the WWW, FTP, and gopher services.
The following illustration lists the functions of the buttons and icons in Internet Service Manager; you can also use the Properties and View drop-down menus for the same functions.
Connect to servers and view property sheets
2 Finds all Web servers on the network.
3 Displays property sheets to configure the selected service.
Start, stop, or pause a service
5 Stops the selected service.
6 Pauses the selected service.
Select which services should be displayed
8 Displays the gopher service in the Internet Service Manager main window.
9 Displays the WWW service in the Internet Service Manager main window.
Start Key Manager to create a Security Sockets Layer key
Make any necessary adjustments to services
12 Displays the property sheets for a service when you double-click it.
13 Displays server and service status.
Servers view displays services running on network computers by computer name. Click the plus symbol next to a computer name to see which services that computer is running. Double-click a service name to see its property sheets. Servers view is most useful for sites running multiple Web servers when you need to know the status of the services installed on a specific computer.
Services view lists the services on every selected computer, grouped by service name. Click the plus symbol next to a service name to see the computers running that service. Double-click the computer name under a service to see the property sheets for the service running on that computer. Services view is most useful for sites with widely distributed Web servers when you need to know which computers are running a particular service.
2. From the Properties menu, choose Start Service, Stop Service, or Pause Service.
In Internet Service Manager, double-click a computer name or a service name to display its property sheets. Click the tab at the top of each property sheet to display the properties for that category. After setting the properties for the service, click OK to return to the main Internet Service Manager window. Detailed information about each property sheet is included in later chapters on security, directories, and logging.
Note In special circumstances, you may need to use Registry Editor (Regedt32.exe) to configure Internet Information Server or Windows NT Server. See Chapter 10, Configuring Registry Entries, for information on registry entries and when you need to use them.
By using the Logging property sheet, you can also select the format you want for logging, either Standard format or National Center for Supercomputing (NCSA) Common Log File format.
See Chapter 7, Logging Server Activity, for more information.
You can also set the maximum network bandwidth for outbound traffic, to control (throttle) the maximum amount of traffic on your site. For more information, see the following section.
Limiting the bandwidth dedicated to users of Microsoft Internet Information Server is especially useful if your Internet line has multiple purposes. Limiting bandwidth allows other operations (such as e-mail and remote logons) to use the same line without being slowed down by too much activity on the Web server.
2. Click the Advanced tab.
3. Select Limit Network Use by all Internet Services on this computer.
4. Select the number of kilobytes per second you want to allow for Internet services.
5. Click Apply and then click OK.
If the bandwidth being used remains below the level you set, client requests for information are answered. If the bandwidth is close to the value you set, client requests are delayed until the network traffic decreases. Delaying responses enables the Web server to smooth out network traffic volumes without actually denying browser requests. If the bandwidth exceeds the level you set, client requests to read files are rejected and requests to transfer files are delayed until the bandwidth equals or falls below the set value.
Click the DNS tab to configure DNS settings, such as hostname, domain names, and DNS servers, to resolve names.
Use the Startup button to specify whether the service starts automatically when your server restarts. If you have a specific reason, you can also use this dialog box to override the account used by the WWW service as set in the Service property sheet of Internet Service Manager. You should change this setting only if it is part of your security strategy; otherwise, use the default settings in the Log On As box.
File access control is not available on file allocation table (FAT) file systems. You can convert your file system to NTFS with the Convert.exe utility. See the Windows NT documentation for more information.
Internet Information Server automatically installs Windows NT Performance Monitor counters for the WWW, FTP, and gopher services, as well as Internet Information Services Global. You can use these counters with the Windows NT Performance Monitor for real-time measurement of your Internet service use. A list of these counters and their descriptions follows. Except where noted otherwise, each counter is available to monitor any of the three services. (For example, you can monitor Connection Attempts for WWW, FTP, or gopher; but you can monitor Current CGI Requests for the WWW service only.
Note The WWW service appears in the Windows NT Performance Monitor as the HTTP Service.
|Aborted Connections||Total number of connections disconnected due to error or over-the-limit requests made to gopher service|
|Bytes Received/sec||Rate at which data bytes are received by service|
|Bytes Sent/sec||Rate at which data bytes are sent by service|
|Bytes Total/sec||Rate of total bytes transferred by service (sum of bytes sent and received)|
|CGI Requests||The total number of Common Gateway Interface (CGI) requests executed since WWW service startup; CGI requests invoke custom gateway executables, which the administrator can install to add forms processing or other dynamic data sources|
|Connection Attempts||Number of connection attempts made to service|
|Connections/sec||Rate at which HTTP requests are currently being handled|
|Connections in Error||Total number of connections (since service startup) that resulted in errors when processed by gopher service|
|Current Anonymous Users||Number of anonymous users currently connected to service|
|Current CGI Requests||Current number of CGI requests simultaneously being processed by WWW service (includes WAIS index queries)|
|Current Connections||Current number of connections to the service (sum of anonymous and non-anonymous users)|
|Current ISAPI Extension Requests||Current ISAPI extension requests simultaneously being processed by WWW service|
|Current NonAnonymous Users||Number of non-anonymous users currently connected to a specific (WWW, FTP, or gopher) service|
|Files Received||Total files received by (uploaded to) service since service startup (WWW or FTP only)|
|Files Sent||Total files sent by (downloaded from) service since service startup|
|Files Total||Total files transferred by server since service startup (WWW or FTP only)|
|Get Requests||Total number of HTTP GET requests received by WWW service; GET requests are generally used for basic file retrievals or image maps, though they can be used with forms|
|Gopher Plus Requests||The total number of Gopher Plus requests received by gopher service since service startup|
|Head Requests||Total number of HTTP HEAD requests received by WWW service; HEAD requests typically indicate that a client is querying the state of a document they already have to see if it needs to be refreshed|
|ISAPI Extension Requests||Total number of HTTP ISAPI extension requests received by WWW service; ISAPI Extension Requests are custom gateway dynamic-link libraries (DLLs), which the administrator can install to add forms processing or other dynamic data sources|
|Logon Attempts||Number of logon attempts made by service since service startup|
|Maximum Anonymous Users||Largest number of anonymous users simultaneously connected to service since service startup|
|Maximum CGI Requests||Largest number of CGI requests simultaneously processed by the WWW service since service startup|
|Maximum Connections||Largest number of users simultaneously connected to service since service startup|
|Maximum ISAPI Extension Requests||Largest number of ISAPI extension requests simultaneously processed by WWW service since service startup|
|Maximum NonAnonymous Users||Largest number of non-anonymous users simultaneously connected to service since service startup|
|Not Found Errors||Number of requests that could not be satisfied by service because requested document could not be found; typically reported as HTTP 404 error code to client|
|Other Request Methods||Number of HTTP requests that are not GET, POST, or HEAD methods; may include PUT, DELETE, LINK, or other methods supported by gateway applications|
|Post Requests||Number of HTTP requests using POST method; generally used for forms or gateway requests|
|Total Anonymous Users||Total number of anonymous users that have ever connected to service since service startup|
|Total NonAnonymous Users||Total number of non-anonymous users that have connected to service since service startup|
|Cache Flushes||Total number of times since service startup that cache has been flushed|
|Cache Hits||Total number of times since service startup a file-open, directory-listing, or service-specific object's request was found in the IIS cache|
|Cache Hits %||Ratio of cache hits to all cache requests|
|Cache Misses||Total number of times since service startup a file-open, directory-listing, or service-specific object's request was not found in the cache|
|Cache Size||Configured maximum size of the shared HTTP, FTP, and gopher memory cache|
|Cache Used||Current number of bytes containing cached data in shared memory cache (includes directory listings, file handle tracking, and service-specific objects)|
|Cached File Handles||Current number of open file handles cached by all Internet Information Server services|
|Current Blocked Async I/O Requests||Current number of asynchronous I/O requests blocked by bandwidth throttling|
|Directory Listings||Current number of cached directory listings cached by all Internet Information Server services|
|Measured Async I/O Bandwidth usage||Measured bandwidth in bytes of asynchronous I/O averaged over one minute|
|Objects||Current number of objects cached by all of Internet Information Server services (includes file-handle tracking objects, directory-listing objects, and service-specific objects)|
|Total Allowed Async I/O Requests||Total asynchronous I/O requests allowed by bandwidth throttling since service startup|
|Total Blocked Async I/O Requests||Total asynchronous I/O requests blocked by bandwidth throttling since service startup|
|Total Rejected Async I/O Requests||Total asynchronous I/O requests rejected by bandwidth throttling since service startup|
© 1996 by Microsoft Corporation. All rights reserved.