FP: FrontPage may not Return Correct Host Name on Windows 95

Last reviewed: March 18, 1998
Article ID: Q176931
The information in this article applies to:
  • Microsoft FrontPage 98 for Windows
  • Microsoft FrontPage 97 for Windows with Bonus Pack

IMPORTANT: This article contains information about editing the registry. Before you edit the registry, make sure you understand how to restore it if a problem occurs. For information about how to do this, view the "Restoring the Registry" Help topic in Regedit.exe or the "Restoring a Registry Key" Help topic in Regedt32.exe.

SYMPTOMS

When you start FrontPage Explorer, you receive a message box that contains a different host name than the NetBIOS name or the DNS name assigned to your computer in the Network control panel.

CAUSE

Under certain circumstances, Windows 95 will store the computer's host name in the Windows registry under the following key. This will happen when you run the Internet Explorer Connector Wizard, for example.

   HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\MSTCP\Hostname

If you later change the host name of your computer, this change may not be reflected in the Windows registry. When FrontPage queries the Registry for the host name of your computer, it may find the incorrect name stored in the registry.

RESOLUTION

To work around this behavior, erase the computer name from the Windows Registry and restore the NetBios name to the TCP/IP name by using one of the following methods:

Method 1: Change the Computer Name by Changing Network Properties

  1. Right-click the Network Neighborhood icon and then click Properties on the menu that appears.

  2. Click the Identification tab.

  3. In the Computer Name box, type a temporary name.

  4. Click OK. If you receive a message asking you to restart Windows, click Yes.

  5. Right-click the Network Neighborhood icon and then click Properties on the menu that appears.

  6. Click the Identification tab.

  7. In the Computer Name box, type the original computer name.

  8. Click OK. If you receive a message asking you to restart Windows, click Yes.

Method 2: Change the Computer Name by Editing the Registry

WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.

For information about how to edit the registry, view the "Changing Keys And Values" Help topic in Registry Editor (Regedit.exe) or the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe. Note that you should back up the registry before you edit it. If you are running Windows NT, you should also update your Emergency Repair Disk (ERD).

  1. On the Windows Start menu, click Run.

  2. In the Open box, type "regedit" (without the quotation marks).

  3. Select the following registry key:

          HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\MSTCP\Hostname
    

  4. On the Edit menu, click Delete.

  5. On the Registry menu, click Exit.

  6. Restart the computer.

STATUS

Microsoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article.


Additional query words: front page
Keywords : fpexp fpiis fppws fptcp kbdta
Technology : internet
Version : WINDOWS:97,98
Platform : WINDOWS
Hardware : x86
Issue type : kbprb


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: March 18, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.