FrontPage Search Returns Invalid Links When Using Index Server (246652)
The information in this article applies to:
- FrontPage 2000 Server Extensions from Microsoft
- Microsoft Index Server 2.0
This article was previously published under Q246652 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 issue a search using a Microsoft FrontPage Search component against an Index Server catalog, the links that are returned to the browser contain the NetBIOS name of the server rather than the fully qualified domain name FQDN (for example, www.microsoft.com). Users who access the site using the FQDN cannot access the computer using the NetBIOS name.
CAUSE
The FrontPage Server Extensions write a .htx file in the _derived folder that is used in formatting the results page. This page contains the following code:
<base href="http://servername/pagename.htm">
where servername is either the NetBIOS name or the FQDN.
For example, if you connect as http://www.microsoft.com., then the base href equals that and the links contain the FQDN of the server. If you connect using the NetBIOS name, the base href equals the NetBIOS name.
RESOLUTION
To resolve this issue, always use the FQDN.
When you are connected with FrontPage, click Recalculate Hyperlinks on the Tools menu and the .htx file will be rewritten with the FQDN.
If you are on a local area network (LAN) that does not have a Domain Name System (DNS), you can use a hosts file to resolve the name. For additional information, click the article number below
to view the article in the Microsoft Knowledge Base:
228760 How to Use a HOSTS File to Test a Site That Uses Host Headers
WORKAROUND
To work around, use the Server Extensions Wide Area Information Server (WAIS) search engine. To do this, follow these steps: WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may
require you to reinstall your operating system. Microsoft cannot guarantee that you can solve
problems that result from using Registry Editor incorrectly. Use Registry Editor at your own
risk. - Start Registry Editor (Regedt32.exe).
- To make a global setting for every virtual server on the computer, lLocate the following key in the registry:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\All Ports
To change the setting for one virtual server, locate the following registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web\Server Extensions\Ports\Port /LM/W3SVC/#:
where the number sign (#) is the server instance that you want to effect. For additional information, click the article number below
to view the article in the Microsoft Knowledge Base:
214515 How to Determine which Virtual Server References
On the Edit menu, click New, and then click String Value.Add the following registry values:
Value Name: NoIndexServer
Value: 1
Close the Registry Editor.Open the Web in FrontPage. On the Tools menu, click Recalculate Hyperlinks.
All searches will now use the FrontPage Server Extensions search engine.
| Modification Type: | Major | Last Reviewed: | 10/22/2003 |
|---|
| Keywords: | kbpending kbprb KB246652 |
|---|
|