GPO Not Working - Got it to WORK!!!

GPO Not Working

I’ve created a DOMAIN name GreatBay.local. I’ve created an Organization Unit (OU) called Restricted Group. I’ve created two new users named test and test1 directly into the Restricted Group OU.

However, it’s not working.

I did the following to create the GPO.
- Opened Active Directory
- Under the domain name (GreatBay.local) I created an OU called Restricted Group
- I right click on the Restricted Group OU and click Properties
- Clicked on Group Policy tab
- Created a new GPO called Restricted Group Policy Object
- I restricted Internet access using a fake windows proxy setting.

The users I entered in the Restricted Group OU are still getting internet access.

Server: Windows 2003 running Exchange 2003 SP2
Domain name (Pre-Windows 2000): GREATBAY
Domain functional Level: Windows 2000 mixed
Forest functional Level: Windows 2000

I ran on the server:
C:\>gpupdate /force
Refreshing Policy...
User Policy Refresh has completed.
Computer Policy Refresh has completed.
To check for errors in policy processing, review the event log.

Then I ran gpresult on both machines

From the Windows 2003 Server:
C:\>gpresult /s spare11 >gp-spare11.txt
ERROR: The RPC server is unavailable.

From the PC itself:
C:\>gpresult
INFO: The policy object does not exist.

Any help would be appreciated.

I GOT IT TO WORK!

I found it was a DNS issue.

Although, I had setup the Exchange 2003 server, I never setup the DNS in the Windows 2003 server. Since I’m building our first Domain infrastructure I needed to do the DNS. Over the past three years our peer-to-peer network has grown from one subnet of 80 devices to 3 subnets and 400 devices. A centralized network is needed… a domain.

On the server-side PC (GBSERVER5) I removed the external DNS IP address and entered it in DNSmgmt MMC, in GBSERVER server properties, under the forwarders tab I entered the external IP (14.22.22.12).

On the client-side (SPARE11 - XP sp2) I entered the server-side (GBSERVER5) IP address as the DNS (192.168.1.14). The Windows server picked up the client-side PC. And POW it worked!!!