Solved

LicenseService - Original Domain Controller gone

Posted on 2001-09-06
8
266 Views
Last Modified: 2008-03-17
I keep getting these errors in the event log how do I get rid of them or is it even a problem?:  I can
give more points if it is necessary.

Replication of license information failed because the License Logging Service on server xxx.xxx.corp
could not be contacted.

Background:

I tried to upgrade my NT4 domain controller to W2K.. Drivers weren't right so I couldn't.  

I got smart and decided to create a temporary machine so I installed NT4, upgraded to W2K and made it
the Domain Controller (nt4 is a backup domain controller now).  Then I added my cleanly installed machine
to the domain and PERMANENTLY REMOVED the temporary one.  I followed the instructions in help to make it look like
the Master Domain Controller, but this is the one error I can't get rid of.
0
Comment
Question by:loucks
  • 5
  • 3
8 Comments
 
LVL 25

Accepted Solution

by:
dew_associates earned 300 total points
Comment Utility
loucks,

You didn't replicate the license service when making these changes. What's happening is that information from the Microsoft License Logging service (LLS) is not being replicated from a licensing server, in either Per Seat or Per Server mode, to the License Master server (your old PDC). When this occurs, you get the error, "Replication of license information failed because the license logging service on server <servername> could not be contacted."
The normal issue is that the LLS on one server cannot communicate with a License Master server.

You need to start the license service on the new DC!

Dennis
0
 

Author Comment

by:loucks
Comment Utility
Well, we are definitely getting there.. When I went to the new domain controller and looked at the LLS service, I noticed that it said it was starting...  Well, I realized I hadn't restarted the computer after making the changes... So I did that and it isn't giving errors now and the service started...

For an extra 200 points, I will give you this question, otherwise, just let me know and I'll accept your comment as the answer:

After the reboot it gave me this error in the event log (system) (The temporary server was the DNS server, but obviously it is gone now.  What should I do?):  
Dynamic registration or deregistration of one or more DNS records failed because no DNS servers are available.
0
 
LVL 25

Expert Comment

by:dew_associates
Comment Utility
That's apparently because you were running DNS on the NT4 box and it never migrated to the Win2k box, but since you didn't post an event ID, I'm not certain. Go through and finish setting up the DNS on the new box if you haven't already done so.

In general, these error messages are logged because the Netlogon service does not
receive a "success" message from the DNS server that owns the zones of the
records that are being registered. There are several reasons why the Netlogon
service does not receive a "success" message:
 
 - Domain controller configuration: DNS server entries in the Transmission
  Control Protocol/Internet Protocol (TCP/IP) properties of the domain
  controller are not properly configured.
 
 - Connectivity: This domain controller does not have Internet Protocol (IP), or
  Transmission Control Protocol/User Datagram Protocol (TCP/UDP), connectivity
  to the DNS servers that own the zones to which records need to be registered
  or deregistered.
 
 - DNS server configuration: The DNS server cannot accept dynamic updates or is
  not configured to accept dynamic updates, as described in the Request For
  Comments (RFC) 2136 specification. If the DNS server that is used by the
  domain controller is not authoritative for the zones to which the Netlogon
  service is attempting to register or deregister, the DNS server must be able
  to provide (to this domain controller) the IP address of the DNS servers that
  are authoritative for the affected zones.
 
Netlogon 5774:
 
The Netlogon 5774 error message is logged in the System event log when the
Netlogon service on a domain controller cannot register an individual resource
record. The event description contains the name of this resource record and
other DNS parameters that are used for the registration attempt, for example:
 
   Event Type: error
  Event Source: NETLOGON
  Event Category: None
  Event ID: 5774
  Date: 2/2/2000
  Time: 8:27:03 PM
  User: N/A
  Computer: COMPUTER10
 
   Description:
  Registration of the DNS record 'corp.computer.com. 600 IN A 192.168.4.1'
  failed with the following error:
  DNS server unable to interpret format.
 
   Data:
  0000: 29 23 00 00 )#..
 
Netlogon 5775:
 
The Netlogon 5775 error message is logged in the System event log when the
Netlogon service on a domain controller cannot deregister an individual resource
record. The event description contains the name of this resource record and
other DNS parameters that are used for the deregistration attempt, for example:
 
   Event Type: error
  Event Source: NETLOGON
  Event Category: None
  Event ID: 5775
  Date: 3/2/2000
  Time: 6:13:09 PM
  User: N/A
  Computer: COMPUTER10
 
   Description:
  Deregistration of the DNS record 'gc._msdcs.computer.com. 600 IN A
  192.168.4.1' failed with the following error:
  DNS bad key.
 
   Data:
  0000: 39 23 00 00 9#..
 
Netlogon 5781:
 
The Netlogon 5781 error message is logged in the System Event Log when the
Netlogon service on a domain controller cannot register or deregister several
resource records. The event description does not contain the names of these
resource records. Also, the event description may be "no DNS servers are
available" which can be misleading, for example:
 
   Event Type: Warning
  Event Source: NETLOGON
  Event Category: None
  Event ID: 5781
  Date: 3/2/2000
  Time: 4:29:12 PM
  User: N/A
  Computer: COMPUTER10
 
Description:
Dynamic registration or deregistration of one or more DNS records failed because no DNS servers are available.

===============

This is just a shot without knowing more, but to resolve this, use any of the following methods:
 
- Create a delegation to the new DNS server on the primary DNS server.
 
- Configure the DNS server's primary DNS server address with its IP address, or remove the value for the Primary DNS Server setting so that the computer uses its IP address.
0
 

Author Comment

by:loucks
Comment Utility
It was 5781.  

DNS is set-up on the permanent DC.

I don't know how to create a delegation to the new DNS server on the primary DNS server.  The permanent DC is the primary DNS server and it has it's own ip for the Primary DNS Server setting.
0
Free Trending Threat Insights Every Day

Enhance your security with threat intelligence from the web. Get trending threat insights on hackers, exploits, and suspicious IP addresses delivered to your inbox with our free Cyber Daily.

 
LVL 25

Expert Comment

by:dew_associates
Comment Utility
Okay, I'm confused. Where is DNS being handled, on the server you're working on or another?
0
 

Author Comment

by:loucks
Comment Utility
DNS ***WAS*** being handled on the *TEMPORARY* machine.  But when I took out the temporary machine, I thought I told it go to the PERMANENT machine for all DNS.  But this error is coming on the (PERMANENT) machine where DNS is supposed to be.

Hopefully that will help.. I get confused just thinking about it.
0
 
LVL 25

Expert Comment

by:dew_associates
Comment Utility
Okay, you have to sit down and setup the DNS service on the new box and then the error will go away.
0
 
LVL 25

Expert Comment

by:dew_associates
Comment Utility
This is probably more than you need, but if it helps...


The Domain Name System (DNS) is the Active Directory locator in Windows 2000.
Active Directory clients and client tools use DNS to locate domain controllers
for administration and logon. You must have a DNS server installed and
configured for Active Directory and the associated client software to function
correctly. This article guides you through the required DNS configuration.
 
NetBIOS name resolution (WINS server, LMHosts file, or NetBIOS broadcast) is
still required for earlier versions of Windows to resolve network resources on
an Active Directory domain.
 
NOTE: A Windows 2000 Server CD-ROM is required to complete Setup. Installing the
operating system from a network share does not work in some scenarios.
 
Experienced DNS administrators are encouraged to read the steps involved in
configuration, and modify them to suit different scenarios. The steps in this
article outline a single, simple configuration and do not represent the only
possible configuration.
 
MORE INFORMATION
================
 
DNS Server Requirements
-----------------------
 
Microsoft recommends that you use Microsoft DNS Server as supplied with Windows
2000 Server as your DNS server. However, Microsoft DNS is not required. The DNS
server that you use:
 
 - Must support the SRV RR (RFC 2052).
 
 - Supports the dynamic update protocol (RFC 2136).
 
Version 8.1.2 and later of BIND (a popular DNS server implementation) supports
both the SRV RR and dynamic update. (Version 8.1.1 does support dynamic updates
but it has flaws that were fixed in 8.1.2.) If you are using a version of BIND
that does not support dynamic update, you need to manually add records to the
DNS server.
 
NOTE: Microsoft DNS, as included with Microsoft Windows NT 4.0 Server, does not
support the SRV record. Use DNS Server that is provided with Windows 2000
Server.
 
Starting with a Windows 2000-Based Stand-Alone Server
-----------------------------------------------------
 
This server becomes a DNS server for your network. You can also promote it to the
domain controller role at a later time.
 
In the first step, you assign this server a static Internet Protocol (IP)
configuration. DNS servers should not use dynamically assigned IP addresses,
because a dynamic change of address could cause clients to lose contact with the
DNS server.
 
Configure TCP/IP:
 
1. Click Start, point to Settings and then click Control Panel.
 
2. Double-click "Network and Dial-up Connections".
 
3. Right-click Local Area Connection, and then click Properties.
 
4. Click Internet Protocol (TCP/IP), and then click Properties.
 
5. Assign this server a static IP address, subnet mask, and gateway address.
 
6. Click Advanced.
 
7. Click the DNS Tab.
 
8. Select "Append primary and connection specific DNS suffixes"
  Check "Append parent suffixes of the primary DNS suffix"
  Check "Register this connection's addresses in DNS"
 
   If this Windows 2000-based DNS server is on an intranet, it should only point
  to its own IP address for DNS; do not enter IP addresses for other DNS
  servers here. If this server needs to resolve names on the Internet, it
  should have a forwarder configured.
 
9. Click OK to close the Advanced TCP/IP Settings properties.
 
10. Click OK to accept the changes to your TCP/IP configuration.
 
11. Click OK to close the Local Area Connections properties.
 
   NOTE: If you receive a warning from the DNS Caching Resolver service, click
  OK to dismiss the warning. The caching resolver is trying to contact the DNS
  server, but you have not finished configuring the server.
 
12. Continue to the next step to install Microsoft DNS Server.
 
Install Microsoft DNS Server:
 
1. Click Start, point to Settings, and then click Control Panel.
 
2. Double-click Add/Remove Programs.
 
3. Click "Add and Remove Windows Components".
 
4. The Windows Components Wizard starts. Click Next.
 
5. Click Networking Services, and then click Details.
 
6. Click to select the Domain Name System (DNS) check box, and then click OK.
 
7. Click OK to start server Setup. The DNS server and tool files are copied to
  your computer.
 
8. Continue to the next step to configure the DNS server.
 
Configure the DNS Server Using DNS Manager:
 
These steps guide you through configuring DNS by using the DNS Manager snap-in in
Microsoft Management Console (MMC).
 
1. Click Start, point to Programs, point to Administrative Tools, and then click
  DNS Manager. You see two zones under your computer name: Forward Lookup Zone
  and Reverse Lookup Zone.
 
2. The DNS Server Configuration Wizard starts. Click Next.
 
3. Right-click Forward Lookup Zone, and then click Properties.
 
4. Choose your DNS server to be a root server. Click Next.
 
5. Choose to add a forward lookup zone. Click Next.
 
6. The new forward lookup zone must be a primary zone so that it can accept
  dynamic updates. Click Primary, and then click Next.
 
7. The new zone contains the locator records for this Active Directory domain.
  The name of the zone must be the same as the name of the Active Directory
  domain, or be a logical DNS container for that name.
 
   For example, if the Active Directory domain is named "support.microsoft.com",
  legal zone names are "support.microsoft.com", "microsoft.com", or "com". Type
  the name of the zone, and then click Next.
 
   NOTE: If you name the zone "com" we will believe that we are authoritative for
  the "com" domain and never forward any requests that we can not answer out to
  the real "com" domain servers. The same would be true if you named it
  "microsoft.com", you would never use your forwarder to resolve requests from
  the real "microsoft.com" servers.
 
8. Accept the default name for the new zone file. Click Next.
 
9. Choose not to add a reverse lookup zone now. Click Next.
 
   NOTE: Experienced DNS administrators may want to create a reverse lookup zone,
  and are encouraged to explore this branch of the wizard.
 
10. Click Finish to complete the Server Configuration Wizard.
 
11. After the Server Configuration Wizard is finished, DNS Manager starts.
  Proceed to the next step to enable dynamic update on the zone you just
  added.
 
Enable Dynamic Update on the Forward Lookup Zone:
 
1. In DNS Manager, expand the DNS Server object. Expand the Forward Lookup Zones
  folder.
 
2. Right-click the zone you created, and then click Properties.
 
3. On the General tab, click to select the Allow Dynamic Update check box, and
  then click OK to accept the change.
 
4. DNS server configuration is finished. Proceed to the next step if you want to
  promote this DNS server to be the first domain controller in the enterprise.
  This is the recommended path.
 
5. If you decide to use a different computer as your first domain controller,
  the configuration instructions in the "DNS Setup for Replica and Child Domain
  Controllers" section apply to that domain controller after you have installed
  Windows 2000.
 
Promote This Server to Domain Controller (Optional--Recommended):
 
Promote this server to the domain controller role by using the Dcpromo.exe
utility.
 
For additional information about promoting and demoting domain controllers, click
the article number below to view the article in the Microsoft Knowledge Base:
 
   Q238369 How to Promote and Demote Domain Controllers in Windows 2000
 
After the server has been promoted to the domain controller role, the DNS server
can use the Active Directory Storage Integration feature (this is the
recommended path). Proceed to the next step if you want to use Active Directory
Storage Integration for DNS.
 
Enable Active Directory Integrated DNS (Optional--Recommended):
 
Active Directory Integrated DNS uses the directory for the storage and
replication of DNS zone databases. If you decide to use Active Directory
Integrated DNS, DNS runs on one or more domain controllers and you do not need
to set up a separate DNS replication topology.
 
1. In DNS Manager, expand the DNS Server object.
 
2. Expand the Forward Lookup Zones folder.
 
3. Right-click the zone you created, and then click Properties.
 
4. On the General tab, the Zone Type value is set to Primary. Click Change to
  change the zone type.
 
5. In the Change Zone Type dialog box, click DS Integrated Primary, and then
  click OK.
 
6. The DNS server writes the zone database into Active Directory.
 
7. Right-click the zone named ".", and then click Properties.
 
8. On the General tab, the Zone Type value is set to Primary. Click Change to
  change the zone type.
 
9. In the Change Zone Type dialog box, DS Integrated Primary, and then click OK.
0

Featured Post

How to run any project with ease

Manage projects of all sizes how you want. Great for personal to-do lists, project milestones, team priorities and launch plans.
- Combine task lists, docs, spreadsheets, and chat in one
- View and edit from mobile/offline
- Cut down on emails

Join & Write a Comment

Suggested Solutions

NTFS file system has been developed by Microsoft that is widely used by Windows NT operating system and its advanced versions. It is the mostly used over FAT file system as it provides superior features like reliability, security, storage, efficienc…
In this step by step tutorial with screenshots, we will show you HOW TO: Enable SSH Remote Access on a VMware vSphere Hypervisor 6.5 (ESXi 6.5). This is important if you need to enable SSH remote access for additional troubleshooting of the ESXi hos…
Access reports are powerful and flexible. Learn how to create a query and then a grouped report using the wizard. Modify the report design after the wizard is done to make it look better. There will be another video to explain how to put the final p…
You have products, that come in variants and want to set different prices for them? Watch this micro tutorial that describes how to configure prices for Magento super attributes. Assigning simple products to configurable: We assigned simple products…

762 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

6 Experts available now in Live!

Get 1:1 Help Now