Microsoft Knowledge Base Email Alertz

If you follow the instructions that are described in the "Deploying Microsoft SharePoint Portal Server 2001 across an Extranet" white paper to configure an extranet Web site, you may receive the following dashboard error message when you tr

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

Article ID: 305032 - Last Review: September 14, 2007 - Revision: 2.4

Error Message Occurs When You Access Fully Qualified Domain Name of Extranet Web Site

This article was previously published under Q305032

SYMPTOMS

If you follow the instructions that are described in the "Deploying Microsoft SharePoint Portal Server 2001 across an Extranet" white paper to configure an extranet Web site, you may receive the following dashboard error message when you try to access the fully qualified domain name (FQDN) of the new Web site:
An unexpected error occurred. An error occurred while accessing the dashboard. This error may be caused by the proxy server settings for the dashboard. Contact your server administrator. If you are a server administrator, configure the proxy server settings by using the proxycfg utility. Consult the product documentation and the readme for more information about configuring the proxy server settings.

Important: You must configure the proxy server settings for the dashboard even if you are not using a proxy server.

(1) -2147221499
If you access the default intranet dashboard site, you do not receive this error message.

CAUSE

This issue can occur if you are using Network Address Translation (NAT) for the extranet Web site, but you are not using a split DNS. The host header name is mapped to the public IP address by your DNS server, but nothing is mapped to the internal IP address.

RESOLUTION

To resolve this issue for external clients, add an entry in the HOSTS file on the SharePoint Portal Server computer that points the host header name to the internal IP address. To resolve this issue for internal clients, either implement a split DNS or add an entry to the HOSTS file for the internal IP address on each client computer.

MORE INFORMATION

Split DNS maintains internal and external DNS entries for your domain on separate private and public DNS servers. See your DNS documentation for more information.

APPLIES TO
  • Microsoft SharePoint Portal Server 2001
Keywords: 
kbprb KB305032
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate