Fixing Group Policy networking issues

Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2

This topic includes a procedure you can use to verify your network configuration and addresses other network connectivity issues.

From the following list, choose the problem that best describes your situation, and then step through the suggested fix:

• Group Policy does not apply when connecting remotely over a slow link

• Unable to access domain controller

• Group Policy does not replicate

Network Connectivity and Configuration

For Group Policy to be received at the client, there must be network connectivity between the client and the domain controller. This section includes information about troubleshooting network connectivity.

To test for network connectivity problems, check system event logs on the client computer (that is, look for failed access attempts). You can also use the ping or netdiag commands to test network connectivity.

To verify a properly configured connection:

1. Type the following command at the command prompt:

   netsh interface ip show config

2. If you get an error, open Network Connections, and then resolve the problem by enabling or repairing the connection.

   • To enable the connection, right-click the connection and select Enable.

   • To repair the connection, right-click the connection and select Repair.

3. If the network connection is enabled, you should see a list showing values for IP address, subnet mask, default gateway, and so on.

4. If necessary, check each network setting to verify that it is configured properly.