Event Id 213

  • Thread starter Thread starter Jeff
  • Start date Start date
J

Jeff

This weekend we upgraded our PDC to a 2KDC running Active
Directory. I have two other BDCs running 4.0 right now
so we are still running mixed mode. Everything seemed to
work fine but when I came in this morning, I saw tons of
DNS issues. Everything worked though because of WINS.
At this point, I believe everything is working except for
one error. All the servers report Event ID 213. This
says that the License Logging service cannot be contacted
on the DC. I read Microsoft KB Artice 296681 which says
to change the server. This did not fix it primarily
because the DC is where it should be. Im starting to
think it is a problem with the DC Locator but im really
not 100% sure with DNS. Any help would be
appreachiated. Thanks.

..
 
In
Jeff said:
This weekend we upgraded our PDC to a 2KDC running Active
Directory. I have two other BDCs running 4.0 right now
so we are still running mixed mode. Everything seemed to
work fine but when I came in this morning, I saw tons of
DNS issues. Everything worked though because of WINS.
At this point, I believe everything is working except for
one error. All the servers report Event ID 213. This
says that the License Logging service cannot be contacted
on the DC. I read Microsoft KB Artice 296681 which says
to change the server. This did not fix it primarily
because the DC is where it should be. Im starting to
think it is a problem with the DC Locator but im really
not 100% sure with DNS. Any help would be
appreachiated. Thanks.

.
Click to expand...

See if these articles help.

http://www.eventid.net/display.asp?eventid=213&source=

Replication of License Manager Information Unsuccessful:
http://support.microsoft.com/?id=198132

Apparently points to an issue where the DC can't be located by querying DNS
and the subsequent connection using RPC. If this is the case and it comes
down to a DNS issue, one thing you can confirm is to make sure that your DNS
addresses in all your machine properties only point to your internal DNS
server that is hosting the AD domain name.

AD Services are located by querying DNS since DNS stores all resource and
service locations. If there is an external DNS server listed in your IP
properties, that server can't provide the answer. If this is the case, I
would suggest to remove that DNS IP and just use your own and setup a
FOrwarder for Internet resolution. Heres's a tutorial on how to setup a
forwarder, below Step 3 in this article:
http://support.microsoft.com/?id=300202

Hope that helps.


--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
Thanks. As it turns out, one of the biggest problems was
that none of our member servers changed to the new
domain. All of them were in the downlevel domain and
could not contact DNS. Last night we changed them to
the .local domain and everything is working fine.
 
In
Jeff said:
Thanks. As it turns out, one of the biggest problems was
that none of our member servers changed to the new
domain. All of them were in the downlevel domain and
could not contact DNS. Last night we changed them to
the .local domain and everything is working fine.
Click to expand...

Ok, good. At least you figured it out.

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.

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