To troubleshoot the network connectivity or configuration problem, try one or all of the following:
- In Event Viewer, click System, and check for any networking-related messages, such as Netlogon messages, that indicate a network connectivity issue.
- At the command prompt, type netdiag, and note any errors. Those errors usually have to be resolved before Group Policy processing can continue.
- At the command prompt, type gpupdate, and then check Event Viewer to see if the Userenv 1053 event is logged again.
- To verify that the domain controller can be contacted through Domain Name System (DNS), try to access \\mydomain.com\sysvol\mydomain.com, where mydomain.com is the fully qualified DNS name of your domain.
- Verify that you can access the domain controller by using tools such as the Active Directory Users and Computers snap-in.
- Check to see whether other computers on your network are having the same problem.
- If this computer is a part of a cross-forest domain, verify that the forest for the user account is currently available and can be contacted by the computer on which the Group Policy processing failed.
If none of the above actions identified the problem, see the ‘Troubleshooting Group Policy in Windows Server 2003’
white paper at the Microsoft Web site.