Article ID: 875520 - Last Review: October 9, 2011 - Revision: 2.0 You may receive an error message when you try to change the replication scope of a DNS zone on a DNS server that is a Windows Server 2003-based domain controller
On This PageSYMPTOMSOn a Microsoft Windows Server 2003-based domain controller, you configure a Domain Name System (DNS) server and then create a DNS zone under Forward Lookup Zones. This DNS zone is integrated with the Active Directory directory service. You disconnect and rejoin the DNS zone to Active Directory. After you do this, you try to change the replication scope of the zone to all DNS servers in the Active Directory domain. In this case, you may not be able to reset the replication zone. Additionally, you may receive the following error message: The replication scope could not be set. For more information, see "DNS zone replication in Active Directory" in Help and Support. The error was: The name limit for the local computer network adapter card was exceeded. RESOLUTIONService pack informationTo resolve this problem, obtain the latest service pack for Windows Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:889100
(http://support.microsoft.com/kb/889100/
)
How to obtain the latest service pack for Windows Server 2003
Hotfix informationA supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix. Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: http://support.microsoft.com/contactus/?ws=support
(http://support.microsoft.com/contactus/?ws=support)
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.PrerequisitesNo prerequisites are required.Restart requirementYou must restart the computer after you apply this hotfix.Hotfix replacement informationThis hotfix does not replace any other hotfixes.File informationThe English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.Windows Server 2003, x86-based versionsCollapse this table
Windows Server 2003, Itanium-based versionsCollapse this table
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
This feature was first included in Windows Server 2003 Service Pack 1.
MORE INFORMATIONSteps to reproduce this problem
824684
(http://support.microsoft.com/kb/824684/
)
Description of the standard terminology that is used to describe Microsoft software updates
| Other Resources Other Support Sites
CommunityGet Help NowArticle Translations
|






Windows Live
Facebook
Twitter
Linkedin
Digg it
Yahoo
Delicious
StumbleUpon
Yammer
Reddit
Technorati
FriendFeed
Email
Back to the top
