Network Connectivity Monitor Monitor

  • ID:  Microsoft.Windows.GroupPolicy.2008.Runtime.GroupPolicyPreprocessingNetworking.System.Correctnetworkconnectivity.EventBased.UnitMonitor
  • Description:   
  • Target:  Group Policy 2008 Runtime
  • Enabled:  On Essential Monitoring

Operational States

Name State Description
ManualReset Success  
NegativeHealthState Error  

Alert Details

Monitor State Message Priority Severity Auto Resolution
NegativeHealthState (Error) Group Policy Preprocessing (Networking) Alert Medium Match Monitor Health Yes

Run As Profiles

Name
Default

Monitor Knowledgebase

Summary

Network Connectivity

Group Policy processing requires network connectivity to one or more domain controllers. The Group Policy service reads information from Active Directory and the sysvol share located on a domain controller. The absence of network connectivity prevents Group Policy from applying to the user or computer.

Causes
This unit monitor does not contain any causes.
Resolutions

Correct network connectivity

To correct network connectivity:

  • Open a command prompt window on the computer, and then type ipconfig /all.

  • 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).

  • 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.

  • 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.

  • 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.

  • 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.

  • 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.

External References
This monitor does not contain any external references.

See Also for Windows Server 2003/2008 Group Policy Management Pack


Downloads for Windows Server 2003/2008 Group Policy Management Pack

AZURE OPTIMIZATION ASSESSMENT GET STARTED
MIGRATION TO AZURE GET STARTED
SYSTEM CENTER MIGRATION TO AZURE GET STARTED
MIGRATION TO AZURE FOR SQL AND WINDOWS 2008 GET STARTED