|
 |
 |
 |
 |
Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms
of Use |
Trademarks
Article ID: 829039 - Last Review: December 3, 2007 - Revision: 1.2 Internal client computers cannot connect to the externally accessible fully qualified domain name of the Windows Small Business Server 2003-based server When you try to locate a service on the server that is running Microsoft Windows Small Business Server 2003 from a client computer on the local area network, you may receive the following error message: The page cannot be displayed
The page you are looking for is currently unavailable. The Web site might be experiencing technical difficulties, or you may need to adjust your browser settings. At the bottom of the error message, you may see the following information: Cannot find server or DNS Error This problem may occur after you configure Windows Small Business Server 2003 to permit a connection from the Internet through a router device. This problem may occur if both of the following conditions are true: - Windows Small Business Server has only one network adapter and is configured behind a router device.
- A client computer tries to access the server by specifying the externally accessible fully qualified domain name (FQDN).
Note Typically, users on the local area network do not use the external domain name of the server. However, Microsoft Outlook Mobile Access (OMA) users require access to the external domain name of the server to synchronize OMA devices. This problem occurs only with certain models and certain firmware revisions of router devices. For additional information about the devices that this problem is known to occur with, see the "More Information" section of this article. To work around this problem, configure the internal client computers to resolve the external FQDN of the Windows Small Business Server-based server to the internal IP address of that server. To do this, create a new Domain Name Services (DNS) zone for the external FQDN of the server. To create a new DNS zone, follow these steps: - Click Start, point to Administrative Tools, and then click DNS.
- Expand your server, right-click Forward Lookup Zones, and then click New Zone.
- In the New Zone Wizard, click Next, leave the Primary zone option selected, and then click Next.
- Click the replication option that you want, and then click Next.
- In the Zone name box, type the external FQDN that your internal client computers require access to. For example, type www.example.com.
- Click Next.
- Leave the Allow only secure dynamic updates (recommended for Active Directory) option selected, click Next, and then click Finish.
- Expand Forward Lookup Zones, expand the new zone that you created, right-click the new zone that you created, and then click New Host (A).
- Leave the Name box blank, and then type the internal IP address of the Windows Small Business Server-based server in the IP address box.
- Click to select the Create associated pointer (PTR) record check box, and then click Add Host.
- When you receive a message that states that the host record www.example.com was successfully created, click OK.
- Click Done, and then exit DNS.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article. This problem occurs with certain router devices and is also known as a "loopback support" problem. This problem occurs with the following router devices: - Microsoft Wireless Base Station MN-500
- Microsoft Wired Base Station MN-100
- D-Link Broadband VPN Router DI-804
- 3Com OfficeConnect Cable/DSL Gateway 3C855
This problem may be resolved by a firmware update for these devices. Contact your hardware vendor to inquire about a device firmware update that fixes the loopback support problem.
For information about how to contact computer hardware manufacturers, click the appropriate article number in the following list to view the article in the Microsoft Knowledge Base:
65416Â
(http://kbalertz.com/Feedback.aspx?kbNumber=65416/
)
Hardware and Software Third-Party Vendor Contact List, A-K
60781Â
(http://kbalertz.com/Feedback.aspx?kbNumber=60781/
)
Hardware and Software Third-Party Vendor Contact List, L-P
60782Â
(http://kbalertz.com/Feedback.aspx?kbNumber=60782/
)
Hardware and Software Third-Party Vendor Contact List, Q-Z
Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.
APPLIES TO- Microsoft Windows Small Business Server 2003 Premium Edition
- Microsoft Windows Small Business Server 2003 Standard Edition
| kberrmsg kbbug kbnofix KB829039 |
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
|
 |
 |
 |
 |
 |
 |
 |
| |