| Event Id | 1129 |
| Source | Microsoft-Windows-GroupPolicy |
| Description | The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has succesfully processed. If you do not see a success message for several hours, then contact your administrator. |
| Event Information | According to Microsoft : Cause This event is logged when the processing of Group Policy failed because of lack of network connectivity to a domain controller. Resolution Correct network connectivity To correct network connectivity: 1.Open a command prompt window on the computer, and then type ipconfig /all. 2.Make sure that the computer has an IP address in the correct IP address range and does not have an Automatic Private IP Addressing (APIPA) address (an IP address in the 169.254.x.x range). 3.Ping the loopback address of 127.0.0.1 to verify that TCP/IP is installed and correctly configured on the local computer. If the ping is unsuccessful, this may indicate a corrupt TCP/IP stack or a problem with the network adapter. 4.Test whether you can ping the local IP address. If you can ping the loopback address but not the local IP address, there may be an issue with the routing table or with the network adapter driver. 5.Ping the IP address of a domain controller in the users' and computers' domain. Failing to ping the these domain controllers indicates a potential problem with the network in between the computer and the domain controllers. Diagnose the problem further using Network troubleshooting procedures. 6.Ping the fully qualified name of a domain controller in the users' and computers' domain. Failing to ping the name of these domain controllers indicates a potential problem with name resolution between the computer and the domain controllers. 7.Follow Network troubleshooting procedures to diagnose the problem further Note:The steps listed above may have varying results if your network constrains or blocks ICMP packets. Verify Group Policy applies during computer startup and user logon. Afterward, Group Policy applies every 90 to 120 minutes. Events appearing in the event log may not reflect the most current state of Group Policy. Therefore, you should always refresh Group Policy to determine if Group Policy is working correctly. To refresh Group Policy on a specific computer: 1.Open the Start menu. Click All Programs and then click Accessories. 2.Click Command Prompt. 3.In the command prompt window, type gpupdate and then press ENTER. 4.When the gpupdate command completes, open the Event Viewer. Group Policy is working correctly if the last Group Policy event to appear in the System event log has one of the following event IDs: 1500 1501 1502 1503 |
| Reference Links | Event ID 1129 from Microsoft-Windows-GroupPolicy |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.