Article ID: 935918 - View products that this article applies to.
In a domain environment, when you try to apply a Group Policy setting to Microsoft Windows Server 2003-based domain controllers and to other domain clients, the policy setting is not applied. When you try to access the Sysvol folder on a domain controller by using its fully qualified domain name (FQDN) in the form \\contoso.com\Sysvol, you may receive the following error message:
Note you can access the Sysvol folder by using the domain controller's IP address or the domain controller's NetBIOS name.
"Configuration information could not be read from the domain controller, either because the machine is unavailable, or access has been denied."
When this issue occurs, the following event messages may be logged every five minutes in the domain controllers' Application logs.
Event Type: Error
Event Type: Error
Microsoft(R) Windows(TM) Dfs Utility Version 4.0 Copyright (C) Microsoft Corporation 1991-2001. All Rights Reserved. --mup.sys-- 1 entries... Entry: \contoso.com\sysvol ShortEntry: \contoso.com\sysvol Expires in 300 seconds UseCount: 0 Type:0x11 ( OUTSIDE_MY_DOM DFS ) 0:[\dc1.contoso.com\sysvol] State:0x21 ( ) 1:[\dc2.contoso.com\sysvol] State:0x21 ( ) DfsUtil command completed successfully.
This issue may occur if you have used the FQDNs of the domain controllers of the domain forest to create trust relationships between domain controllers in Active Directory Domains and Trusts.
To resolve this issue, remove the domain controller entries from Active Directory Domains and Trusts. To do this, follow these steps:
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/888943/ )Event 1030 and event 1058 may be logged, and you may not be able to start the Group Policy snap-in on your Windows Small Business Server 2003 computer
Article ID: 935918 - Last Review: May 10, 2007 - Revision: 2.1