Follow these steps to require users to provide a valid Windows user name and password to access a folder in IIS 6.0: In IIS Manager, navigate to the folder that you want to password-protect, right-click the folder, and then click Properties. Yes. You can use an ISAPI filter to hide banner information. For example, you can write a custom ISAPI filter, or you can install the UrlScan security tool.

In order to require a username and password to access part or all of a web site, you need to 1) create a password file (with appropriate read priviledges) and 2) create a confirguration file in the folder to be protected. Here are the direct instructions for the impatient: If you browse to http://www.math.mcmaster.ca/~your_username/folder_to_protect, you should be asked for a username and password.

Yes, you can, directly from your control panel. Select hosting management and click on the permission icon in File Manager, next to the file you want to manage (by setting up permission on none). Access will occur with one of the FTP users already configured.

If you log into your domain control panel, you should see an icon or text link that says "Web Protect". Once you click that link you will be taken to a page to select the folder you would like to have password protected and you can assign usernames and passwords.

There are many security features in IIS 6.0. The default installation of IIS 6.0 is "locked." Other new features include selectable cryptographic services, advanced digest authentication, and configurable access control of processes. To increase reliability IIS 6.0 has a kernel mode HTTP service, dedicated application processes, and a self-healing mechanism.

The default configuration settings in IIS 6.0 meet or exceed the security configuration settings specified by the IIS Lockdown Tool. You do not need to run the IIS Lockdown Tool for new installations of IIS 6.0. If you are upgrading a server running IIS 4.0 or IIS 5.0, you should run the IIS Lockdown Tool before you upgrade to Windows Server 2003 and IIS 6.0. For more information about the IIS Lockdown Tool, see Running the IIS Lockdown Tool on our TechNet site.

You cannot password protect folders larger than 4 GB located on a volume that uses the FAT file system. Reasons? Folder Password Expert saves the folder contents to a locked file. The largest file that can exist on Fat32 (Windows 9x/Me) is 4 GB. To create a file larger than 4 GB, you must use Windows NT/2000/XP with the NTFS file system. Also, please note: even if you use the NTFS file system, the folder must not contain a file larger than 4 GB.

Do not tell anyone your password. The administrator of a computer system NEVER needs to know anyone else’s password.

First of all, if you use Windows 95, 98, or Me, you can restrict booting in the safe mode by modifying the MSDOS.SYS file. Please review the section "Using Folder Guard: Giving your computer bullet-proof protection" in Folder Guard Help. Also, it is possible to configure your computer so that Folder Guard would perform the protection of folders even in the safe mode, on both Windows Me/98/95 and Windows XP/2000/NT systems. However this information is provided to the licensed customers only.

No, MySecretFolder can protect only one "root" secret folder at a time. (If you select another folder, the previously protected folder will become unprotected.) However, the "root" secret folder can contain an unlimited number of subfolders and files, and all of them will be protected when you protect the "root" secret folder.

You must verify two configuration options to ensure that IIS 6.0 serves .shtml files. Because a .shtml file contains server-side directives, Server Side Includes must be set to "Allowed" in the IIS Manager Web Service Extensions node. In addition, if the default document on your Web site contains the .shtml extension, the file name and extension must be added to the default content page list on the Documents tab of the Web site Properties page.

IIS 6.0 does include FTP user isolation. When you enable FTP User Isolation, the user's top-level directory appears as the root of the FTP site, so other users cannot view or overwrite content. Within the user's specific site, the user can create, modify, or delete files and folders. For information on how to set up and enable FTP user isolation, see Chapter 8: Configuring Internet Sites and Services in section II of the IIS 6.0 Resource Kit, which you can download free.

When IIS 6.0 is running in worker process isolation mode, you can configure application pools recycling based on memory consumption. When the application pool has consumed the specified amount of memory, the worker process serving that application pool is recycled and the memory is freed. This occurs when worker process recycling is configured so that a worker process is never active long enough to meet the idle timeout threshold.

The answer varies depending on the hardware and software configurations of your server as well as the types of content it hosts. If you are setting up your application pools with unique identities, depending on the applications and memory resources of your server, you will reach a limit of about 60 application pools. There are finite limits to some system resources that are allocated with each new logon session. This means that 60 processes can run concurrently as distinct accounts. IIS 6.

or invalid method (HTTP verb), HTTP Error 405 - The HTTP verb used to access this page is not allowed.

By default, earlier versions of IIS allowed unknown file types to be transfered from the server. IIS 6.0 has much tighter security, and therefore a MIME type for analysis files must be explicitly added in order for them to be transfered via "Open from URL." Open the IIS Manager and expand the left-hand treeview until you see the node for the subweb or virtual directory where your analyses are stored. Click "OK".

Set providerObj = GetObject("winmgmts://MachineName/root/MicrosoftIISv2") Set appPool = providerObj.Get("IIsApplicationPool='w3svc/AppPools/DefaultAppPool'") return_value = appPool.Recycle Some properties in the IIS 6.0 metabase have the Secure attribute, which means that these properties are always encrypted when they are sent across the network.

Yes...but not from within Debtinator. This is something that's on my list of neat features that might be good to implement, but in all seriousness I'm in the debt management business, not the encryption business, and I don't know if I want to try to implement security in this manner. If there's a huge public outcry in favor of it, I could be persuaded to bump it up. In the interim, here's a reasonably easy way to protect it (and anything else you want).

The changes you made in <MCMS Intallation Folder>\IIS_CMS will be intact. WAE v2.0 is installed in a different folder, you chouse during installation process. WAE v2.0 uses MS XML 3.0. This ActiveX is shipped with many applications and installed on most computers. If it is not installed on a client machine it will be downloaded and installed during first access to WAE.

If you have lost the Master Password of Folder Guard, you can reset it by running the Emergency Recovery Utility. If you have forgotten an unlocking password for a folder, or some other password used by Folder Guard, simply run Folder Guard and use its appropriate command to set up a new password.