That frequently occurs when the network is not entirely "ready" at startup when the system is starting up all its services for a variety of different reasons. What does the userenv.log say? Are normal background refresh cycles successful?
From: David Lum [mailto:[email protected]] Sent: Wednesday, March 11, 2009 7:33 AM To: NT System Admin Issues Subject: Error in event log I have a recently virtualized DC with the following entries in the Application Event log (entries did not appear before VM-ing to Hyper-V): Event Type: Error Event Source: Userenv Event Category: None Event ID: 1054 Date: 3/11/2009 Time: 6:37:02 AM User: NT AUTHORITY\SYSTEM Computer: COC-SBS1 Description: Windows cannot obtain the domain controller name for your computer network. (An unexpected network error occurred. ). Group Policy processing aborted. What I have already tried: DCDIAG: Comes up clean NETDIAG: passes all test Replication with another DC works This DC is also a DNS server, and for DNS it points to itself No related errors in this servers System Event log When logged in, \\mydomain.com\sysvol\mydomain.com <file:///\\mydomain.com\sysvol\mydomain.com> works I can get to the DC with ADUC snap in, etc EventID.NET has an entry about an AMD processor driver, which I haven't tried yet but the VM's DC is on an quad-core AMD Opteron system David Lum // SYSTEMS ENGINEER NORTHWEST EVALUATION ASSOCIATION (Desk) 971.222.1025 // (Cell) 503.267.9764 ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
