NOTE: To enable your web space to work properly with MS FrontPage, log in to your control panel (see above for instructions), and click on the "FrontPage Extensions" icon in the "Account Settings" section. If you do not see "FrontPage extensions are currently: installed", select the "Install / Reinstall Extensions" button. Your site will now work with your FrontPage publishing features.

NOTE: In order to publish your files using the "Publish Web" feature of FrontPage, you may need to specify the location you will publish to as either "" or "" - note the addition of "%2f" in the second example. Which method you use will depend on the version of FrontPage that you are using, so you may need to try both to see which works for your version. For more information, please visit;en-us;265159


^ Top

Publishing your website using FrontPage

Once you are ready to start uploading your website through FrontPage (either to start testing, or because it's complete), just go to the File menu, then click on "Publish Web...

The screen below will appear, asking you for the "location" of your website. There, you should enter "http://", followed by your domain (like "").

If this is the first time you are publishing, click on Options, then click on "Publish all pages, overwriting any already on the destination". Do that so that you make sure FrontPage replaces the default main page Buffalo Web Services places on your main directory during account configuration.

NOTE: if your domain is new (less than 4 days old), or it's in the process of being transferred over to our servers, you should enter the IP number and Username assigned to your account, instead of the domain name (for example: ""). DO NOT USE YOUR DOMAIN NAME ON THIS SCREEN IF THE DOMAIN IS NEW OR BEING TRANSFERRED!

Then, click on the Publish button. FrontPage will then connect to the server, ask for your username and password, and then it will start uploading all files. Use the username and password assigned to your account (you can find it on your welcome email) if it's the first time, or the password you changed the original one to on your account's control panel. Remember that uppercase and lowercase letters *do* make a difference.

^ Top

I still see Buffalo Web Services's default "Welcome to the new home of..." page when I go to my website, even after I've already published my site

Make sure the filename of your site's main page is called either index.htm, or index.html. That is the file the server looks for when someone goes to your website. If it's already called that, choose "Publish all pages, overwriting any already on the destination" when publishing so that your FrontPage software replaces the default index.htm file on your account. If you still see it, then it's a problem of your browser's/ISP's cache. Click here for more information.

^ Top

After publishing your web, some pages or images are broken, even though they have been uploaded and work fine on your home computer

This happens very often. Please keep in mind that uppercase and lowercase letters make a difference - if your HTML code refers to "image.jpg" but the file is named "image.JPG", the image will not be displayed on the page. The link won't find "image.jpg", because the file it is looking for should be named "image.JPG".

^ Top

Some webbots (counters, search functions, etc.) don't work or you receive a "FrontPage Run-Time Component Page" message when submitting data through a FrontPage-generated form

If you get this message, FrontPage did not correctly configured the form's HTML code to correctly point to the webbot on the server. Forms are configured while FrontPage is *uploading* them. If you upload the pages without FrontPage, via FrontPage's built-in FTP (using "" in the Publish screen above instead of ""), or via a FTP client, you will get such error. If you are correctly uploading them via FrontPage (using the http:// method) and you still get that, choose "Publish all pages, overwriting any already on the destination" when publishing. If you still get it, then it's a problem of your browser's cache or ISP's cache. If, after clearing the browser's/ISP's cache, you still get that message you might also want to try reinstalling FrontPage's extensions on your account by going to the "Features" section on your account's control panel, then publishing again.

^ Top

Common error messages

You might encounter any of the following error messages when uploading your website to our servers with FrontPage 2000/2002, or while creating your website:

"The following pages in your front-page web contain dynamic FrontPage Components, such as a search form or a FrontPage form handler. They will not work because the server you are publishing to does not have the FrontPage Server Extensions installed"

This message should be ignored. Contrary to the error message, all our servers do have the FrontPage Server Extensions installed. This error usually appears before you start publishing your website, even while you are making your website. Still, FrontPage will give you this error even though it does not yet know what server it is going to connect to.

"This form is being created on a Disk-Based Web or the FrontPage Server Extensions have not been configured to send e-mail. Please direct your system administrator or Internet Service Provider to the instructions in "Setting up E-Mail Options in Windows" or "Setting up E-Mail options on UNIX" in the Server Extensions Resource Kit. If you do not have the Server Extensions Resource Kit, you can find it at"

Would you like to remove the E-Mail recipient?"

This message should be ignored, as FrontPage Server Extensions are already configured to send e-mail on our servers.

"The server could not complete your request. Contact your Internet Service Provider or web server administrator to make sure that the server has the FrontPage Server Extensions installed. For more information, click Details"

The connection between your computer and our servers may be slow. Because of this, FrontPage gets tired of waiting for the server to respond or an upload to finish.

"Enter your user name and password for your proxy server." FrontPage Repeatedly Prompts for User Name and Password When You Open a Web

This is likely to be an authentication issue. If you have re-installed your Front Page extensions, you may need to reset your password to the original one. Also, the main .htacess in your public_html folder might be missing. Don't use Front Page, try publishing using WS_FTP instead.

"The folder 'http://servername' isn't accessible. The folder may be located on an unavailable volume or protected with a password. For details see C:\TEMP\wecerr.txt

The server sent a response which FrontPage could not parse"

To resolve this problem, obtain Microsoft Office 2000 Service Release 1/1a (SR-1/SR-1a).

"listing pages" stays there and won't finish

This could happen for several reasons. First, try it again during off-peak hours. Maybe the connection is slow and your think it's just taking a long time to index your site. Second, your site is too big and Front Page is trying to reindex your site.

"Error 500: Server Error. This server has encountered an internal error which prevents it from fulfilling your request. The most likely cause is a misconfiguration. Please ask the administrator to look for messages in the server's error log"

Most Front Page problems are due to it's extensions. Try deleting and reinstalling your Front Page extensions through your web site's Control Panel.

^ Top

Additional advice about FrontPage

  • FTP (file transfer protocol) is the standard protocol used to upload files from one computer to a web server. The publish feature in FrontPage is not very dependable. You are better off to publish your site using a standard FTP client such as WS_FTP
  • You can create far better websites when you don't depend on FrontPage's wizards. You may want to consider other page creation software like CoffeCup or DreamWeaver, or consider using SitePro, our online site-builder
  • FrontPage is not perfect. Even though most of its error messages blame the FrontPage extensions on the server, most of the time it is not the case.