I have several Windows 7 x64 Enterprise workstations that are not processing GPO's at boot up. In the event log we get an error saying: The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: a) Name Resolution failure on the current domain controller. b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller). Log Name: System Source: Group Policy EventID: 1055 Level: Error User: System This computer account has been around for a long time and you get this message on newly created computer accounts as well. The account name is in DNS and is resolvable using nslookup and ping. I have enabled DHCP-Client logging and you'll see this message: "Your computer was successfully assigned an address from the network, and it can now connect to other computers" a few milliseconds AFTER you get the GPO error above. I have done packet captures and you can see where the network adapter has assigned itself a 169.254.x.x address before the DHCP request happens. I have always wait for network at computer startup and logon enabled, I have disabled IPv6, I have set the connection speed, disabled DHCP broadcast flags, turned off media sensing, and turned off APIPA all in an effort to get GPO's to process at startup. The network is always there when I login though I have had issues of putting in my username and password hitting enter and being returned to the Press Clt+Alt+Delet to Login screen. The error goes away when you statically assign an IP address. All the computers are using a Broadcom NetXtreme 57XX Gigabit Controller with the most up-to-date drivers. Any Ideas? Thanks

I have seen this as well - we have over 600 laptops running windows 7. It does not really seem to cause any issues thought - computer GPO will still get on the machines after 2 or so reboots. After talking to Microsoft support it seems that this is a "known" issue, and hopefully will be resolved in SP1. In our event log we will see a 1055 then it will be followed by a success code... so it fails then succeeds... We have increased the days our DHCP addresses are allocated to 6 days, and this seems to help. -Dan

Hi, Does the problem with other versions of Operating System? It seems that the client can’t connect to DC and get GPO applied at startup, thus the error message pops up. As I understand that you can get the IP address later from DHCP, please run the following command to force the update of the GPO applied on the client computer and restart the machine to see if the problem persists: Gpupdate /force To solid troubleshoot this kind of problem, I kindly recommend you to post in Windows Server forums for a better assistance. Best Regards Dale Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

We are currently only seeing this problem on Windows 7 machines. I have tried running gpupdate /force and no success.

We are currently only seeing this problem on Windows 7 machines. I have tried running gpupdate /force and no success. I am also seeing a similar problem with machines that are running Windows 7 Enterprise. The machines will try to access network drives, before they receive an ip address. Explorer shows the network drives as disconnected. Once the machine has got an IP address(takes about 10-15 secs after desktop is displayed) the drives can be accessed no problem; however until the user clicks on them, or otherwise accesses them, it shows the drives as disconnected. This causes issues with users new to Windows 7, so I get called. To their amazement I fix the problem with out doing anything. This only happens when the computer is put to sleep or shut down. When I lock the computer or log out, the machine retains its' lease and everything works fine. These computers are using the Intel 82567LM-3 Gigabit NIC. Thanks!

I have serval machines that have the exact same issue with the 82567LM-3 Gigabit NIC. I have updated to SP1 and I still have the same issue. Have you had any luck fixing the issue? Thanks

Figured it out had to turn off Spanning Tree on my switches.

I would have never guessed spanning tree was the issue, but it fixed it. Instead of turning spanning tree off for the whole switch you can "spanning-tree portfast" for each port that has a windows 7 computer attached. You can do it for the whole switch but you risk creating a loop.