Discussion Locked

Windows Server 2003 Autoenrollment

0 helpful
4 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I have a Windows 2003 Server with a mixture of Windows 98 and Windows XP Pro clients. The 98 machines run fine, log on to the domain etc, but evry time I log on from one of the XP machines, I get an Autoenrollment error, I also get the same error every 8 hours thereafter. According to Microsoft, this is caused by incorrect DNS settings. I have checked the DNS settings in all of the XP machines, and as far as I can see they are fine. I have also checked that the DNS server is running on the 2003 server and that lookes fine too. Any ideas what else could cause this?

4 replies

by olivierdon

Found this from Labmice:

CAUSE
This behavior can occur if the Autoenrollment feature cannot reach an Active Directory domain controller. In a Microsoft Windows NT 4.0 domain, Active Directory is not available, so Autoenrollment cannot work. In an Active Directory domain with Microsoft Windows 2000 or later domain controllers, the problem can be caused by a DNS name resolution or network connectivity issue.
RESOLUTION
For a Windows XP-based or a Windows Server 2003-based computer that is joined to a Windows NT 4.0 domain, to disable Autoenrollment in the Local Group Policy, follow these steps on the local workstation:
Click Start, click Run, type gpedit.msc, and then press ENTER.
In the left pane, expand Computer Configuration, expand Windows Settings, expand Security Settings, and then expand Public Key Policies
Double-click Autoenrollment Settings.
Click Do not enroll certificates automatically.
Click OK.
Repeat steps 2 through 5, but in step 2, expand User Configuration, expand Windows Settings, expand Security Settings, and then expand Public Key Policies.
Close the Group Policy window.
For a computer that is a member of a Windows 2000 or later Active Directory domain, make sure that the domain member has network connectivity with at least one domain controller.

After you have determined that you have good Internet Protocol (IP) connectivity between the member and a domain controller, correct the DNS address in the IP properties of the workstation:
Start the Network Connections tool in Control Panel.
Right-click Local Area Connection, and then click Properties.
Click Internet Protocol (TCP/IP), and then click Properties.
Type the correct DNS address in the Preferred DNS server box.
Click OK.

by marc

This is more or less the same answer I got from Microsoft Technet - I have checked the DNS settings on the workstation, the only other thing I can think of is that there is something wrong with the DNS server settings on the server - is there any way to verify this?

This discussion is closed to new replies.