IT Employment

Ask something
Discussion Locked

Active Directory-related Error

0 helpful
3 replies

by bobby gillette

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I receive the following error in my event log on a remote dc...

Security policy cannot be propagated. Cannot access the template. Error code = 3.
\\smc.ad\sysvol\smc.ad\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\Machine\Microsoft\Windows NT\SecEdit\GptTmpl.inf.

Funny thing is, I can access the above file, open the policy (which by the way is the Default Domain Controller GPO) via the SYSVOL share. Has anyone else experienced this problem?

3 replies

by timwalsh

Funny things can happen with AD sometimes. It doesn't matter if you can access the template. It's the system that needs to use it.

Try the following NS Knowledge Base articles to see if they fit your situation.

Cannot Access Group Policy Objects--Event ID 1000 and Event ID 1001 Logged Q258296

Error Messages Every 5 Minutes Report Events 1000, 1001, and 13508, Citing Replication Trouble Q285923

by abrass

If your DNS address is not configured properly in TCP/IP properties, it can prevent computers from applying policies... even on themselves!! This may not be your problem, but it was mine just a couple of days ago. Workstations were configured to an external DNS server on the internet rather than the DNS server in their own domain, causing them to be confused as to their own identities and group policies were not being applied.

by bobby gillette

I think I finally locked it down... the server (my remote dc/gc) has a second NIC installed (gig fiber to be exact), which it uses as its network connection. The internal NIC is disabled, but still had its original bindings. One of the TechNet articles dealt with AD having problems if the NIC at the top of the Connections list doesn't have File and Printer Sharing enabled. Funny thing was, the gig card DID indeed have it bound and enabled. I took a chance and unbound File and Printer Sharing onthe disabled internal NIC, and haven't gotten any further messages. Hopefully that fixed the problem ;)

Word to the wise, use that internal NIC as your primary network connection, or, if you choose to install another adapter, disable the internal one in BIOS and remove it from Windows Device Manager entirely.

This discussion is closed to new replies.