Microsoft Knowledge Base Email Alertz

(828054) - When you use a computer that is internal to your network to try to contact your Microsoft Windows Small Business Server 2003-based server by using its publicly registered fully qualified domain name (FQDN), and you do not use the FQDN for the server...

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: 828054 - Last Review: December 3, 2007 - Revision: 3.2

You cannot open a Web page that is on a Windows Small Business Server 2003-based server by using its FQDN

SYMPTOMS

When you use a computer that is internal to your network to try to contact your Microsoft Windows Small Business Server 2003-based server by using its publicly registered fully qualified domain name (FQDN), you may receive the following error message:
DNS error - Page cannot be displayed.

CAUSE

This problem may occur if your server's publicly registered FQDN resolves to the external side of a network address translation (NAT) device that is connected to the Internet and that publishes back to the internal server. When this situation occurs, and Internet Explorer tries to locate your server's publicly registered FQDN, the connection is blocked, and you receive the error message that is mentioned in the "Symptoms" section. The router views the request as sourced from an IP address that is contained in its own internal network. The router assumes that the request has been spoofed and drops the packet. The originating client never receives a response, and the browser displays the error.

RESOLUTION

First, contact your router manufacturer to see if a firmware update exists for the issue. If no update is available, or the update does not resolve the issue, you can connect to the server by using the NetBIOS server name in the URL. Another method is to add an additional forward lookup zone to DNS with a name that is the same as the external domain name. To do this, follow these steps:
  1. Click Start, click Run, and then type dnsmgmt.msc. Click OK. The DNS Management Console appears.
  2. Double-click your server name in the console tree.
  3. In the details pane, right-click Forward Lookup Zone, and then click New Zone. The New Zone Wizard appears. Click Next.
  4. On the Zone Type page, click Primary Zone, and then click Next.
  5. On the Active Directory Zone Replication Scope page, click Next.
  6. On the Zone Name page, in the Zone Name box, type the fully qualified domain name of your external domain. For example, type www.externaldomainname.com. Click Next.
  7. On the Dynamic Update page, click Do not allow dynamic updates, and then click Next. Click Finish to close the New Zone Wizard.
  8. Right-click the new zone in the DNS Management Console details pane, and then click New Host (A). The New Host dialog box appears.
  9. Leave the Name field empty. In the IP address box, type the Server Local Area IP address, and then click Add Host.

    Note If the FQDN includes “www", add this to the Name field in step 9.
.

WORKAROUND

To work around this problem, you can add a Domain Name System (DNS) record on the Windows Small Business Server computer that resolves the server's external FQDN to the server's internal IP address. This does not affect the IP address that computers on the Internet use when they connect to the server's FQDN. To do this, follow these steps:
  1. Click Start, point to Administrative Tools, and then click DNS.
  2. Right-click the server object in DNS, and then click New Zone.
  3. Click Next on the first page of the New Zone Wizard.
  4. On the Zone Type page, click Primary zone, and then click Next
  5. On the Active Directory Zone Replication Scope page, click To all domain controllers in the Active Directory domain, and then click Next.
  6. On the Forward or Reverse Lookup Zone page, click Forward lookup zone, and then click Next.
  7. On the Zone Name page, type the server's external FQDN, and then click Next.

    For example, type www.example.com, and then click Next.
  8. On the Dynamic Update page, click Do not allow dynamic updates, and then click Next,
  9. Click Finish to complete the wizard.
  10. Double-click Forward Lookup Zones, and then click the new zone.
  11. Right-click the new zone, and then click New Host (A).
  12. In the New Host dialog box, leave the Name box empty, type the server's internal IP address in the IP address box, and then click Add Host.
  13. On client computers that are running Microsoft Windows XP or Microsoft Windows 2000 Professional, open a command prompt window, and then run the ipconfig /flushdns command.

APPLIES TO
  • Microsoft Windows Small Business Server 2003 Premium Edition
  • Microsoft Windows Small Business Server 2003 Standard Edition
Keywords: 
kbprb KB828054
       

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