or by ordering the NT 4 Option Pack CD-ROM from Microsoft. At the time of this writing the NT 4 Option Pack CD-ROM is no longer available.

Microsoft Windows NT Server 4

Service Pack 3

Microsoft Internet Explorer 4 or higher

RISC: 200 MHz Alpha, 64MB RAM, 200MB free disk space

TCP/IP protocol

An NTFS partition is HIGHLY recommended although not required

Note: It is possible to install IIS40 on an NT Workstation or Windows9x machine. In these instances Peer, or Personal Web Services are installed,

Microsoft Management Console - Microsoft's new "administrative console."

Internet Information Server - provides accessibility to Web pages and files over the Internet, and Intranet, or extranet.

Transaction Server - provides "transaction" functionality for complex, or multi faceted applications. The completion of the transaction is dependent upon the successful completion of each of the individual components.

Index Server - an extension of IIS that allows for site indexing by content.

Posting Acceptor - allows users to upload data to a Web server.

FrontPage Extensions - allows the use of Microsoft FrontPage for management and maintenance of the Web pages.

FTP Service - allows IIS to act as an FTP server, providing a mechanism for file transfer with FTP clients.

Microsoft Script Debugger - tool used to debug client, server, and Web document scripts.

Java Virtual Machine - provides support for Java applications on the Web server.

Internet Service Manager - an HTML based version of Internet Service Manager used to administer IIS from a Web browser.

SMTP (Simple Mail Transfer Protocol) Service - allows the transfer of email over the Internet via TCP/IP.

NNTP (Network News Transfer Protocol) Service - allows the hosting of electronic discussion groups.

Certificate Server - creates certificates to enable the use of Secure Socket Layers (SSL).

Data Access Components - a package of software components that allows linking of Web pages to various databases including SQL Server. The individual components are:

Site Server Express - a limited version of the Site Server program included with SMS. Its main components are the Content Analyzer, Usage Import, and Report Writer. Aids in the analysis of content and usage history of a Web site.

Message Queue Server - provides a stable and secure foundation for building applications that use messages to exchange data over the Internet or an Intranet.

WWW Service - provides support for HTTP requests.

Internet Connection Services for RAS - integrates NT RAS with Internet connectivity.

Administrative Snap-ins - each of the Option Pack components comes with a snap-in for the Microsoft Management Console to provide consistent, customizable centralized administration.

Development Components - resources to help customize each of the Option Pack services.

Addition of the MMC, as well as the addition of the following services:

The Metabase is created, which is used to store configuration settings of IIS. The metabase is basically a Registry for IIS specifically.

The IUSR_computername is created to allow anonymous access.

The following objects and related counters are added to Performance Monitor:

By default, the FTP Service is installed with IIS. To create a new FTP site:

From this point the FTP Site Wizard will guide the creation of the new site. You will be prompted to enter a name for the site, the IP address and TCP port the FTP site will use, the root folder location of the site, and the access permissions for the root folder. Access permission options are Read and/or Write. After configuration, you will need to manually start the FTP site.

When configuring FTP sites (and WWW sites as well) you have the option of applying the default site's master properties to all "child sites," or applying specific properties to specific sites. By default, the properties set at the default site level will be inherited by all sites created on that IIS server. If properties are set for a specific site, they will over-ride the defaults.

Both the FTP and WWW services support the creation of Virtual Directories and Virtual Servers. A virtual directory is one that does not exist on the same server that is hosting the site, or is not part of the home directory for that site. Virtual directories must be referenced using UNC paths. The purpose and advantage of a virtual directory is that it will appear to the user as an extension of the site. This allows the administrator to include directories that do not exist in the home folder in the site. A virtual server is created when one IIS server hosts multiple WWW or FTP sites. Virtual servers are supported through IP Address assignment, Name Resolution Systems, Internet Name Resolution, or Host Header Names. Virtual Servers will be covered later in this document.

The creation of a virtual server allows the administrator to incorporate bandwidth throttling into the administration of the site. Bandwidth throttling allows you to specify the maximum amount of bandwidth that the site has access to (in KB/s). It is set on the Performance tab of the Site Properties Page.

Configuration of the WWW Service is similar to the FTP Service, however there are more configurable properties, and the arrangement of those properties is slightly different.

When multiple servers are configured to use the same IP Address, you must provide some mechanism for determining the called site. This is accomplished through the use of Host Header Names. In order to use Host Headers, you must:

When creating virtual servers it is imperative that you set permissions appropriately before allowing access to the sites from the Internet. Consider authentication requirements, the use of SSL and certificates, logging, and other security concerns in the context of the purpose of the site. Will it be used for information only? As a support site? To purchase items from the internet? As an Intranet? The answers to these questions will dictate much of how your security should be defined. Remember the old adage "better safe than sorry."

1-800-I DONT CODE. Ok, if this shows up on the exam (and I doubt it will) I'm sending up the sacrificial lamb. I'm an engineer…not a programmer. Sorry folks!

Much of the configuration we addressed earlier in this document will aid greatly in the analysis of sites using Content Analyzer. WebMaps can be created from URLs or from files.

Content Analyzer contains two views: Tree and Cyberbolic. Navigation is fairly straightforward.

Generate Reports from the Tools menu of the WebMap screen, then select Generate Site Reports. Using the Site Report, you can view your site's configuration through:

By default, SMTP is configured to handle mail for one default domain. You can add aliases to the service so that SMTP can handle mail destined for those names. There are two types of domains:

1. Local domains route mail to the drop directory on the local host. Use this option when you need to specify another domain name for your mail server.

2. Remote domains route mail to other SMTP hosts. Use this option when you need to override your site' authentication, encryption, and smart host settings for a specific domain.

To create a new domain:

1. Right click the SMTP Service and select New, Domain

2. Select Remote or Local and enter the FQDN for the new domain

3. Then Right click on the new domain and select Outbound Security

4. Configure authentication and encryption settings and click OK

Configuration has been covered earlier in this document.

To create a newsgroup:

1. Right click on the NNTP server you want to add the newsgroup to and select Properties
2. From the Groups tab, select Create New Newsgroup
3. Type the name for this newsgroup in the Newsgroup text box. Also type any desired description.
4. Specify whether the newsgroup is read-only.
5. Specify if the newsgroup is to be moderated. If so, configure the moderation parameters.

NNTP expiration policies dictate how long articles will be kept, and how large the entire newsgroup can be. The absolute maximum size is 500MB.

When the NNTP service is paused, existing connections continue to be serviced.

Configuration has been covered earlier in this document.

To create a certificate request file:

1. Run the IIS Key Manager from the Internet Service Manager.
2. Use Key Manager to generate a key pair and certificate request.
3. Run CertReq to submit the certificate request to MS Certificate Server and obtain the certificate.
4. Install the certificate by copying and pasting the contents as directed.

Basic configuration of Index Server has already been covered in this document.

Index Server works in a fairly simple manner. Initially it creates a catalog of all the words in all the documents on your site. Contained in the catalog is a dictionary style entry for each word with a list of all the documents that contain that word. When a query is run, Index Server returns the list of all the documents that contain the word(s). Index Server searches only the virtual directories you specify, which by default is the entire site. If you have virtual directories that you do not want indexed, you should be sure to remove the "Index this Directory" property from that site's Home Directory tab. If your server hosts more than one site, you will want to create separate indexes for each site so that documents from one site don't show up in a query performed on the other.

When indexing a document, Index Server initially builds a word list, which is stored in RAM. When the word list becomes large enough, it is merged into a structure called a shadow index (this is called a shadow merge). The shadow index is stored on the hard drive. Shadow indexes are NOT compressed as they are optimized for speed. Occasionally, Index Server will combine shadow indexes together in a process called an annealing merge. The process of combining all the shadow merges together is called a master merge and results in a compressed structure called a master index, which is very fast to search. After a master merge the shadow indexes are deleted, and the process begins again. This process of multiple merges makes Index Server's response time the fastest possible while making query results as accurate as possible.

To create a new catalog:

1. Start, Programs, Option Pack, Index Server, Index Server Manager.
2. Right click Index Server on Local Machine and select Stop.
3. Right click Index Server on Local Machine and select New, Catalog.
4. Name the catalog.
5. Browse to the location of the site you want to index and click OK.
6. Right click the new catalog and select Properties, Web, Generation, then click OK.
7. Right click the new catalog again and select New, Directory, then browse to the default directory for the site (this will add the directory to the catalog).
8. Right click Index Server on Local Machine and select Start to begin indexing the site.

Query Forms - usually HTML files - the forms to input the data on which a query will be run.

.idq - Internet Data Query Files - the actual query file (script)

.ida - Internet Database Administration files - the file that returns the query result to the browser

.htx - HTML extension files - focus on "overall houskeeping" of Index Server instead of the actual queries.

Multipurpose Internet Mail Extensions - basically identify the type of file binary data is contained in. Think of MIME mappings as file associations. They identify what type of file this is, and can help identify what application should be used to open the file.

Managing the FTP Service involves setting the configuration parameters previously discussed to accomplish such objectives as limiting connections, timeouts, log formats, setting custom messages, directory listing styles, creating sites, testing sites, coordinating NTFS permissions, creating virtual directories and other general administrative duties. Another rather important consideration is the possibility of virtual servers and bandwidth throttling.

Also, remember that properties set on a specific site override the global properties.

Managing the WWW Service involves setting the configuration parameters previously discussed to accomplish such objectives as Operators, performance tuning, bandwidth throttling, HTTP Keep-Alives, ISAPI Filters, Home Directory parameters (including access permissions and content control, application settings, content location), default documents, Anonymous access and Authentication Control, SSL, IP and Domain Name Restrictions, HTTP headers (including content expiration, custom HTTP headers, content rating, and MIME mappings), Custom Errors, and configuration of virtual directories, virtual servers, and host headers.

The administration of security is of paramount importance in regard to the WWW Service. Another rather important consideration is the possibility of virtual servers and bandwidth throttling. Also, remember that properties set on a specific site override the global properties.

Connection to databases is accomplished through MDAC 1.5 (Microsoft Data Access Components). It contains:

In addition IIS also offers legacy support through:

Of these ADO is the most dynamic and flexible model available. Essentially a collection of ActiveX objects, it is designed to seamlessly integrate with Active Server Pages.

The ODBC Drivers essentially pass data from the Web application to an ODBC compliant database. The drivers require a DSN (Data Source Name) which can be specified as SYSTEM (all logged on users are allowed access to the database), or USER (limits connectivity with the database to s specific user with appropriate security credentials), or FILE (a text file lists multiple users who have access to the database).

To configure ODBC:

1. From the ODBC Control Panel Applet, System DSN tab, click Add.
2. Select the database driver for your database in the Create New Data Source Dialog Box, then click finish. (This method should allow all connected users access to the database).

With respect to SQL you should be aware that there are two options for connecting to a remote server, Named Pipes and TCP/IP Sockets. Using Named Pipes, authentication is accomplished through NT's NetLogon Service. This creates the possibility that a user connecting to a remote SQL server may be denied access due to the lack of an appropriate account in the SAM database of the interactive computer. With TCP/IP Sockets, authentication is performed through SQL Server authentication.

Further, if SQL's Integrated or Mixed security features are implemented on a remote server, you must use Basic authentication, as NT cannot forward Windows NT Challenge/Response credentials from an IIS server to a remote computer.

Yeah…..Right….uhm….is this the MCSE??? One more lamb, coming right up!

Server-Side Scripting refers to the process of building a dynamic Web page at the server, based on the request from a client (browser) or a server-side include. There are 3 primary processes that IIS supports to accomplish server-side scripting; Active Server Pages (ASP), Common Gateway Interfaces (CGIs), and Internet Server Application Programming Interface (ISAPI). One major advantage of server-side scripting is that the client requesting the document cannot read the scripts themselves. They are stored and executed on the server and only the output is sent to the requesting browser.

Microsoft Script Debugger - improves ASP debugging.

Transactional Scripting - Creates a transaction of the script, reducing failure or corruption from incomplete events.

HTTP 1.1 Protocol support.

Support for Internet Explorer Channels and Webcasting.

Script in .asp files is not event driven. Therefore, syntax and runtime errors are caught immediately.

ASP files have the advantage of being able to run in a separate memory space, thereby improving the stability of the server in the event of an ASP crash.

1. Neither NT Server nor IIS supplies any default CGI scripting language. For any language that will be supported, an interpreter must be installed (PERL is the most commonly used language for CGI construction).
2. The ScriptMap Registry key AND the Metabase must reflect the registration of the scripting language application.
3. The first line passed in the CGI script must be the translated path identifying the NT filing system location of the CGI executable. The second line is the executable parameters and/or switches.

To configure IIS for CGI support:

1. Create a directory to hold the scripts or use the default CGI-BIN directory.
2. Keep executable files in a separate directory from content files.
3. Install a script interpreter to support script execution.
4. Ensure that the script file directory has either Script or Execute Permission applied. Executables require the Execute Permission.
5. Mark the Script Interpreter files as Script Engines to ensure proper execution.
6. Create the Application Mapping between the script file extension and the script interpreter.
7. Set appropriate NTFS permissions for the directories that contain the Interpreter and those that will be accessed by the CGI.
8. Ensure that the CGI will access only directories that are safe for them to read.

ISAPI is far superior to CGI in terms of lower overhead, faster loading, and better scalability. ISAPIs can run as much as 20 times faster than CGIs. ISAPIs are divided into two types:

1. ISAPI Extensions - loaded when called by an application. In the form of DLLs, ISAPIs can be run in or out of process. One disadvantage of ISAPI extensions is that they execute only once regardless of the number of client requests. This means that failure of the ISAPI will disrupt all sessions that are actively calling it, and the failure could also cause the server to crash or lock.
2. ISAPI Filters - loaded with the server, and ALWAYS run in process. Can be used to customize and enhance the services provided by the server. ISAPI Filters are driven by Web server events rather than by client requests (as is the case with ISAPI extensions). Filters respond when the Web server receives an HTTP request. You can set ISAPI Filters for every Web site (the Global filters) or for specific sites. If both Global and Site filters are installed, the two filter lists are merged for the site.

1. In Internet Server Manager, select the Web site or the starting-point of the directory of an application.
2. Right click and select Properties, then the Home Directory, Virtual Directory, or Directory Tab.
3. Click on Configuration, then App Mappings tab.
4. Add the extension and file pathname, than click OK.

Much of the information needed to complete these tasks involves a thorough understanding of the Log file formats. They have been adequately discussed earlier in this document, however there are some specifics we should look at.

Log files are imported into Usage Import through its own Server Manager utility. In order to import data through the Usage Import Server Manager Utility, you must configure three levels of the log import:

1. Log Data Source - the Log file format you specified when enabling logging on the site.
2. Server - most Log files contain data on multiple servers.
3. Site

3. Specify the location of the Log file you want to import, then select File, Start Import.

2. Click File, Create Report, specify a Report Name, and Format (HTML, Word, Excel), Click OK.

The scheduler utility in Site Server Express is used to automate Site Server Express events.

1. In Usage Import select Tools, Scheduler
2. Right click on All Jobs and Select New Job, Check the Active box.
3. Specify the periodicity and time for the task to occur, click OK
4. Right click on New Job and select New Task, select Import Log File
5. Enter Log Data Source and Log Path along with any other relevant information and click OK.
6. Repeat the Process for Report Writer.

Cache Hits - The number of times a file or folder requested could be serviced from memory.

Cache Hits % - Ratio of requests as a percentage of those serviced from the cache.

Cache Misses

Cached File Handles - The number of file handles allocated for IIS.

Current Blocked Async I/O Requests - The number of requests that are refused due to bandwidth throttling limitations.

Objects - The number of objects being cached by IIS.

Files/Sec - The speed at which files are transferred by the Web Service.

Maximum Connections - The maximum number of concurrent connections since the Web Service was started.

Not Found Errors/Sec - The errors per second that are mainly generated from HTTP 404 error codes (requested document not available).

This is fairly fundamental information and can be found elsewhere at http://www.dwood.com. Specifically look for the documents pertaining to Performance Monitor, NT Server 4.0, and NT Server 4.0 in the Enterprise.

Basic Recommendations include:

1. Analyze Bandwidth Limits
2. Analyze Connection Limits
3. Set memory intensive ISAPI and Active Server processes to run in their own memory space.
4. Upgrade your Internet connection to an appropriate bandwidth.
5. Replace or convert CGI applications to ASPs or ISAPIs.
6. Logically organize your data so that related documents are kept on the same logical disk.
7. Optimize application code, including performance-testing code, not inserting comment information, and avoiding interspersing HTML and Script code.
8. Avoid large numbers of graphics, or complex graphics on Web pages.
9. Implement RAID solutions.
10. Enable HTTP Keep-Alives to optimize bandwidth.
11. Do not require SSL on folders that do not require high security.
12. Use reverse lookup with DNS only when needed.

Merge Process - If a merge is occurring, progress is indicated. A reading of 100 indicates the merge is complete.

Persistent Indexes - The number of indexes stored on the hard disk. Ideally 1.

Total # of Documents - How many objects are currently indexed by the system.

Unique Keys - How many unique words have been identified by the index.

Wordlists - How many temporary word lists have been created. After 14-20 word lists are created they are shadow-merged into a persistent index.

Index Server can also be optimized by using a web browser and opening the Index Server Manager (HTML) Page from the NT Option Pack, Index Server, Index Server Manager Menu. Cache and Index statistics will be displayed.

Other basic Recommendations include:

1. Move a catalog to a different hard disk than the corpus.
2. Implement RAID.
3. Add RAM.
4. Create multiple catalogs if you don't need the ability to query everything at once.
5. Narrow the scope of your queries by eliminating unnecessary virtual directories from the index.
6. Change the time that the daily master merge occurs.
7. Set Index Server to filter only files with known file types.

1. Disable logging (as a last resort).
2. Increase the maximum number of messages per connection in the SMTP Service. You can also decrease the retry interval for local and remote mail delivery.
3. Turn off reverse DNS lookup for incoming messages.

1. Limit the number of simultaneous connections.
2. Decrease the connection timeout.
3. Disable logging (as a last resort).

I assume this refers to the ability to interpret the data collected and presented through Performance Monitor, Content Analyzer, Usage Import, Report Writer, and any other utilities at your disposal. Those issues have been addressed or are self-evident.

With the exception of the ReMap Site command (on the Mapping menu), and the Compare and Update command, this has been addressed as well. Refer back to the topics pertaining to the use and configuration of Usage Import, Report Writer, and Content Analyzer.

Fairly basic stuff here folks:

1. Does the computer work? No, really?
2. Is NT installed correctly so that all of the components are in working order?
3. Are you running Service Pack 3 or later?
4. Do you have enough hard space?
5. Do you have enough RAM?
6. Be certain that your computer meets all of the minimum requirements to install and run IIS 4.0

Again, fairly basic stuff here. Along with the usual NT security issues, check the following areas:

1. Logon Access and Authentication. Have you set the Anonymous access or authentication methods correctly?
2. Access control. Have you set up any IP Address or Domain Name restrictions?
3. Do you have permission conflicts that are overriding the desired effect?
4. If the problem pertains to Scripts, ASPs, CGIs or ISAPIs, have you set the Script or Execute Permission on the folder containing the files or scripts?

Unable to submit a certificate request to the Certificate Server - Is Certificate Server installed and running?

Can't require SSL - Do you have an installed, signed certificate? Have you set NT Challenge/Response as the authentication method (required for SSL)?

Unable to audit - Are you using NTFS? Have you enabled auditing in User Manager and set it up in NT Explorer?

Users cannot logon using Basic authentication, but are able to using NT Challenge/Response - Basic authentication must be enabled for users to log on using a specific account without using MSCHAP. In a multi-domain environment, the default domain configured for Basic authentication must be the domain from which all Basic users will be authenticated.

Users from outside your firewall are unable to access Web sites on non-standard port addresses - Your firewall must be configured to pass specific non-standard port numbers.

Users are confronted with a logon prompt even when they want to logon anonymously - Logging on without a logon prompt or MSCHAP requires that Anonymous Authentication be enabled.

Users report that they are presented a logon prompt when they attempt to access the site, but access is still denied after entering an account name and password - You must specify an account for the users if anonymous authentication is disabled.

You can't log on to the IIS Administrative Web site - You must have MSCHAP enabled to use the Administrative Web pages.

Browsers other than Internet Explorer are unable to access your Web site - Inferior browsers (like Netscape) require Basic authentication to be authenticated as anything other than an anonymous user.

Users can't access Web site data stored on an UNC share - Are Share Permissions set correctly? Is an account name and password established for Web site access to the share?

Queries return files that shouldn't be returned - This problem can be caused by incorrect NTFS Permissions or by filtering files of all types when filtering should be restricted to known types. Also, ensure that you have separate catalogs for each separate site.

Queries don't return files that they should - The catalog may be restricted to certain directories. NTFS permissions can also have this affect.

Queries take too long to fulfill - Forcing Master merges to occur more often may help. You may also have too many users. Create more catalogs if possible. Move data to another server. Upgrade hardware. Remove "intense" applications such as SQL or Exchange.

Queries timeout or fail to return data - If the server is overloaded, this is an indication of an approaching failure. Other causes could be network connectivity or corrupted Index Server files. Try reinstalling Index Server.

In addition to the issues already discussed check the following:

1. Any Alpha or Beta versions of IIS 4.0 must be removed prior to installing IIS 4.0 final.
2. The NetLogon, Server, Computer Browser and Workstation Services must be running on the computer.
3. ODBC connection errors will occur if there are any other applications using the ODBC connector. Stop the offending applications, complete installation of IIS, and then restart the other applications.

Microsoft OLE DB Provider for ODBC Drivers error "80004005" [Microsoft] [ODBC Microsoft Access Driver] The Microsoft Jet database engine cannot open file "(unknown)". It is already opened exclusively by another user, or you need permission to view its data.

Cause - the user account (usually IUSR) does not have sufficient access rights. Check NTFS and Share Permissions.

Microsoft OLE DB Provider for ODBC Drivers error "800004005" [Microsoft] [ODBC Driver Manager] Data source not found and no default driver specified.

Cause - GLOBAL.ASA file was not properly executed. Check that the file is in the Application Root for IIS, and that users have Execute permission for this folder.

Microsoft OLE DB Provider for ODBC Drivers error "800004005" [Microsoft] [ODBC Microsoft SQL Driver] Logon Failed

Cause - The SQL server denied access to the account attempting to access the SQL server. Check that the SQL and NT account passwords match, and that the IIS connection to the SQL server maps the user's name properly.

Microsoft OLE DB Provider for ODBC Drivers error "800004005" [Microsoft] [ODBC Microsoft Access 97 Driver] Couldn't use "(unknown)"; file already in use.

Cause - The database file you are attempting to access is configured for single-user use only, and the file is already open.

Microsoft OLE DB Provider for ODBC Drivers error "800004005" [Microsoft] [ODBC Microsoft SQL Driver] [dbnmpntw] ConnectionOpen (create file)

Cause - Usually caused by incorrect permissions being applied. Very common if the path is remote and you are attempting to access it via an UNC path, particularly with the IUSR account. The IUSR account is local to the computer. One solution is to create the account on the remote computer that contains the remote database. The usernames and passwords must be identical.

Almost too simple. Search the map visually. Use the Update and Compare command, or from the WebMap window, select Tools, Quick Search, Broken Links.

Common Problems and Solutions

1. You have configured the WWW Service to use a port other than port 80.
2. You have configured the WWW Service to use SSL, and the client is not configured to use SSL, or does not have the correct digital certificate for authentication.
3. The maximum number of connections has been exceeded.
4. The connection timeout value has been set too low.
5. Correct permissions have not been applied to the WWW objects that users need to access.
6. A valid default document has not been defined.
7. Access control has been set and the user cannot access resources. This could result from the authentication method used, SSL being enabled, or IP Address restrictions.
8. You have used file types that do not have valid MIME mappings defined.
9. Unable to locate your Web server - No DNS entry.

10. Can't create a virtual site - You must specify a unique port number, IP Address, or Host Header for the Web site.

11. Can't require SSL - You must have a valid certificate installed to require SSL.

12. Can't select another IP Address - You must configure multiple IPs in the Network Applet of Control Panel.

1. Can't find server by another name - No DNS entry.
2. Browser won't find virtual site - Browser must support Host Headers, or you must use a CGI/ISAPI workaround. If you are using a port other than port 80, the port MUST be referenced in the URL.
3. Browsers with multimedia plug-ins or ask if you want to save the file to disk rather than displaying the data - a MIME type must be defined for the data types other than those already defined in the IIS default setup
4. Site has moved and browsers can't find it - You can redirect browsers to the new location of a Web site using the URL option in the Home Directory tab of the Web site's Property sheet.

Common Problems and Solutions:

1. Is the IIS installation complete, uncorrupted, and running?
2. For directory or access related problems, are directory permissions set appropriately on both the home directory and the directory in question?
3. Are the permissions and rights for the IUSR account (especially the right to log on locally) set correctly?
4. After adding a virtual directory, have you stopped and started the FTP Service?
5. For custom client connections, have you set the directory listing style to Unix?
6. If certain clients can't attach to your FTP Site running on a non-standard port, are the clients capable of attaching to an FTP server that is not running on port 21? Are they specifying the correct port number in the URL?
7. Has the maximum number of connections been reached?
8. Are there any IP Address or Domain name restrictions in place?