error changing scope

  • Thread starter Thread starter Tommy Doan
  • Start date Start date
T

Tommy Doan

We have added a new name server in our 3 domain forest. The initial 2
servers are in one domain; the new one will go into a different domain. This
requires a replication scope from our initial "All domain controllers in the
AD domain" to "All DNS servers in the forest." However, when I try to change
the scope for the reverse lookup zones on the existing name servers, I
consistently get an error. I had no problem setting the scope on the new
name server.

The error states "The name limit for the local computer network adapter card
was exceeded." I was unable to find any helpful KB articles. Will I need to
remove all records from that zone first, then change the scope and wait for
replication to replace the records? Thanks.
 
In
Tommy Doan in said:
We have added a new name server in our 3 domain forest. The initial 2
servers are in one domain; the new one will go into a different
domain. This requires a replication scope from our initial "All
domain controllers in the AD domain" to "All DNS servers in the
forest." However, when I try to change the scope for the reverse
lookup zones on the existing name servers, I consistently get an
error. I had no problem setting the scope on the new name server.

The error states "The name limit for the local computer network
adapter card was exceeded." I was unable to find any helpful KB
articles. Will I need to remove all records from that zone first,
then change the scope and wait for replication to replace the
records? Thanks.
Click to expand...


Do you have Exchange installed? Any other LDAP applications installed on the
DC? (Which will conflict). Did you make any modifications to anything at
all? What Event log errors are you getting (post the Event ID # please). Are
you only using your internal DNS servers in your IP properties?

319504 - Error Message The Name Limit for the Local Computer Network Adapter
Card Was Exceeded:
http://support.microsoft.com/?kbid=319504


--
Regards,
Ace

Please direct all replies ONLY to the Microsoft public newsgroup so all
can benefit. This posting is provided "AS-IS" with no warranties and
confers no rights.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory

HAM AND EGGS: A day's work for a chicken; A lifetime commitment for a
pig. --
=================================
 
Both of our original name servers are domain controllers with very few
modifications from a default installation. We try to keep our DC's very
simple with no other applications or services installed, so I can't think of
any software locally that may cause a conflict that would result in the
error. They are running Server 2003. We do have an Exchange organization but
Exchange is not installed on these DC's. Each of our name servers point only
to themselves as resolvers. Thanks for the reply.


"Ace Fekay [MVP]"
 
In
Tommy Doan in said:
Both of our original name servers are domain controllers with very few
modifications from a default installation. We try to keep our DC's
very simple with no other applications or services installed, so I
can't think of any software locally that may cause a conflict that
would result in the error. They are running Server 2003. We do have
an Exchange organization but Exchange is not installed on these DC's.
Each of our name servers point only to themselves as resolvers.
Thanks for the reply.
Click to expand...

No problem. One question, do you have mutliple domains and Exchange is
installed on another domain?

--
Regards,
Ace

Please direct all replies ONLY to the Microsoft public newsgroup so all
can benefit. This posting is provided "AS-IS" with no warranties and
confers no rights.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory

HAM AND EGGS: A day's work for a chicken; A lifetime commitment for a
pig. --
=================================
 
Yes, we have multiple domains in the forest. The top-level domain holds the
two original name servers. A child domain holds the new name server as well
as our Exchange organization. Do you think you're onto something? Thanks for
the reply.


"Ace Fekay [MVP]"
 
In
Tommy Doan in said:
Yes, we have multiple domains in the forest. The top-level domain
holds the two original name servers. A child domain holds the new
name server as well as our Exchange organization. Do you think you're
onto something? Thanks for the reply.
Click to expand...

Not sure if it will help, but make sure all domains are in the same mode and
possibly run a /domainprep. Maybe the mode has something to do with it more
so than the domainprep since all that does is create a couple local groups,
but you never know!


--
Regards,
Ace

Please direct all replies ONLY to the Microsoft public newsgroup so all
can benefit. This posting is provided "AS-IS" with no warranties and
confers no rights.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory

HAM AND EGGS: A day's work for a chicken; A lifetime commitment for a
pig. --
=================================
 
No dice. This is a very mature forest; the creation date at the forest root
is 9/14/2000. All domains and the forest are at Windows 2003 functional
level. Domainprep and forestprep we run soon after Server 2003 RTM was
released. Plus, keep in mind that I was able to change the scope on the new
name server with no problem when it was first introduced. My guess is that
this is somehow related to the number of records contained in the existing
name servers. Thanks for the reply.


"Ace Fekay [MVP]"
 
In
Tommy Doan in said:
No dice. This is a very mature forest; the creation date at the
forest root is 9/14/2000. All domains and the forest are at Windows
2003 functional level. Domainprep and forestprep we run soon after
Server 2003 RTM was released. Plus, keep in mind that I was able to
change the scope on the new name server with no problem when it was
first introduced. My guess is that this is somehow related to the
number of records contained in the existing name servers. Thanks for
the reply.
Click to expand...

Well, it was a stab at it! Curious, did you try the one suggestion in that
article about the MaxUserPort value? Just curious. You can always change it
back if it doesn't help.

--
Regards,
Ace

Please direct all replies ONLY to the Microsoft public newsgroups
so all can benefit.

This posting is provided "AS-IS" with no warranties or guarantees
and confers no rights.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory

HAM AND EGGS: A day's work for a chicken;
A lifetime commitment for a pig.
 
Tommy, it seems like there's a dupe in AD, meaning the same zone exists in
the Domain NC and the DomainDnsZones app partition. My feeling is to choose
one DC, change the scope to a Primary (text file), delete the zones on the
other DCs, wait for that data to replicate. THen use ADSIEdit to delete the
zone data from the DomainNC (name container) and the DomainDnsZones app
partition. Let that repicate. Then on the one you changed it to a Primary,
set the scope to AD replication in the DomainDnsZones app partition (the
center selection inthe scope replication properties), let that replicate and
then recreate the zone on the other DCs.

It's a proven method to fix this!

Ace
 
Back
Top