Since Apache's .htaccess password protection and FrontPage use the same file, you cannot use Apache's .htaccess or the cPanel Password Protect Directories feature to password protect a directory if you have FrontPage installed. You can still password protect a directory using FrontPage by following these instructions.

Note: A FrontPage sub web and a folder under your domain are basically the same.

1.	First, you will need to create a sub web that you want to protect. This sub web is the name of the directory you want to protect and CANNOT exist. Once in FrontPage:
	Select File -> New -> Web
	Click on 'Empty Web' In the text box labeled 'Specify the location of the new web' put in your complete domain name and the name of the folder or sub web you wish to create (i.e. http://www.yourdomain.com/folder)
	Then click on 'OK' and wait while you new sub web is created.
2.	Now that your new sub web is created, you will need to set the password protection for this sub web. You should already be in your new sub web. To verify, look at the URL in the title of FrontPage. To password protect this sub web
	Select 'Tools' -> 'Security' -> 'Permissions'.
	A 'Permissions' box will appear.
	Click 'Use unique permissions for this web' and click 'Apply'.
	Click on the 'Users' tab in the permissions box. You will see your current username listed. DO NOT remove this username.
	Click 'Only registered users have browse access'.
	Click 'Apply'.
	Click the 'Add' button
	Fill in the 'Name' 'Password' and 'Confirm Password' text fields and click 'OK'. If you want to add more users just go click on the 'Add' button again and fill in the new users information.
	Click on 'OK' and the 'Permissions' box should disappear.

Now only your FrontPage username/password and the user(s) you just setup can view that sub web or directory.

The most common cause is the use of FTP in uploading FrontPage generated webpages. This can damage the FrontPage extensions. In this case the FrontPage extensions will need to be reinstalled. This can be done in your cPanel Control Panel. If you are utilizing FrontPage to create your site, you MUST use the file upload feature in the FrontPage program to deliver these pages to the web server. If FrontPage webpages are transferred by another FTP client, FrontPage extensions will become damaged. And even though the pages may be successfully uploaded, they will not be viewable (translatable by a web browser) due to corrupted code.

To check the status of your FrontPage extensions, go to your cPanel control panel. Click on the FrontPage Extensions icon. If it says "FrontPage Extensions are: uninstalled", click "Install". If it says "FrontPage Extensions are: installed" and you still suspect they're broken, it doesn't hurt to uninstall them, then re-install them. You may have to re-publish some or all of your files after this, but it usually does clear up the problem.

SOLUTION 1: If your main entry (home) page is already created but is still named default.htm, you must rename it index.htm or index.html. If you already have an index.htm or index.html page, you MUST DELETE the default.htm page before your index page will show up.

NOTE: You may see that the page is renamed on the server.

SOLUTION 2: Check to make sure you are publishing to the entire correct URL including the trailing slash. Frequently we find that FrontPage users inadvertently upload to root instead of into the public_html directory because they either are trying to publish to an IP or did not use the trailing slash (depending on the version of FP, this may make a difference). If your index.html page is not inside public_html, it will not show up online.

That's your problem -- the capital "I" in Index.html (or Index.htm etc.). File names are case-sensitive. The server looks for an index.html or index.htm for its home page -- with all lowercase letters. Rename your file index.html or index.htm with all lowercase and that should make your home page visible as the home page.

This difficulty arises when the uploading link times out in the process of copying the web to our server. The only suggestion Microsoft has offered so far is to break the main web into a group of sub webs on your PC, then upload these individually.

We often see this error being reported even when the extensions have been installed. If you get this error, please reinstall the FrontPage extensions from your Control Panel.

NOTE: The extensions are easily corrupted. Please use ONLY FrontPage Explorer to update your web site on the server, not FTP.

Although rare, this does happen when FrontPage extensions have been badly corrupted beyond what cPanel can fix. The extensions will have to be completely uninstalled and then reinstalled by us onto your hosting account. Submit a HelpDesk ticket to request this. After we fix it, you will probably have to reupload part or all of your site as well as re-create password protection on any pages you have set up with password protection.

This will happen when the "Destination Web Name" is filled in when publishing to our server. This box should be left blank. If you put any other name in this box it will create a subdirectory off of your root web and copy all of your files into it. Your site will exist under a subdirectory instead of in the top level /public_html where it should be.

These problems are generally due to incorrect permissions on either the directory, file(s), or cgi script(s) that are associated with them. Please don't change the permissions of your files or directories unless you have a specific reason for doing so and you know what effect it will have on your site.

The call to a cgi script using the Secure Server must not be within a webbot. Use a normal cgi call in your html script for Secure Server calls.

The /public_html directory must be world readable AND you need to recalculate links BEFORE publishing (or after editing directly on the server). If it still doesn't work: access the remote server and go to the /public_html/_vti_txt/default.wti directory. Delete any files that begin with "ALL". Don't delete any other files. Then using Windows Explorer, do the same thing on your PC. Recalculate links, test locally with your browser and Publish with FrontPage.

Cancel the operation and reinstall the FP extensions. They have been damaged. You can ininstall/reinstall FrontPage extensions from within your web hosting account cPanel control panel.

Yes, if you use FTP or the cPanel File Manager function to upload your files, you can upload to your files to your ip/~yourusername/ before the DNS resolves. You can also view your uploaded web pages online by http://yourActualAssignedIP/~yourusername/ before the DNS resolves (the trailing slash is NECESSARY when accessing your web site by IP).

Keep in mind that some functions and file types may not be fully operational until the DNS has resolved. Examples include PHP pages and scripts utilizing MySQL.

If you use FrontPage to upload your site you will have to wait for the DNS to resolve so you can publish to www.yourdomain.com. Publishing to an IP from FrontPage will cause problems in your site.

Because of Microsoft policies, we are not allowed to provide technical support for the FrontPage client. We can only verify that the FrontPage server extensions are working correctly. However, we have provided you with the following information as a courtesy:

Should you need assistance with FrontPage 2002 please visit http://support.microsoft.com/default.aspx?scid=fh;EN-US;fp2002#faq558

If you encounter the message "Server error: Cannot close file filename.htm.tmp" (where filename is the actual name of the file) while publishing to your account, this means you have reached or exceeded the allowed disk storage for your hosting account. You will need to either remove files from your account, or upgrade your hosting account to a higher plan to ensure you can upload all the files you want to have in your account.