<div>
Can you post the results of your GPRESULT on the client(s)?<br />
<br />

</div>


Can you post the results of your GPRESULT on the client(s)?



<div>
GPRESULT<br />
<br />
INFO: The Policy object does not exist.<br />
<br />
<br />
<br />
Jim
</div>


GPRESULT

INFO: The Policy object does not exist.



Jim

<div>
Spoke to soon... found a KB on MS website that describes adding registry keys to set a static range for the RPC ports. &nbsp;One we did this we were good to go.
</div>


Spoke to soon... found a KB on MS website that describes adding registry keys to set a static range for the RPC ports.  One we did this we were good to go.

<div>
<div class="content wysiwyg-content">
We have all the necessary ports/services forwarding through our firewall (this is not on a public internet, but segmented internal network) and can login fine.<br />
<br />
HOWEVER, evern though mapped drives work, login, joining to domain, etc. all work -- Group Policy isn't applying itself.<br />
<br />
GPUPDATE says &quot;success&quot; but none of our policies are enforcing. &nbsp;HERe are our open ports<br />
<br />
• &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Kerberos (88/tcp, 88udp)<br />
• &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;LDAP (389/udp, 389/tcp and/or 636/tcp if using LDAP over SSL)<br />
• &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;SMB over IP traffic (445/tcp, 445/udp)<br />
• &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;DNS ports (53/tcp, 53/udp) used for name lookups<br />
• &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;135 DCE Enpoint<br />
• &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;1000-5000 (For testing of RPC)<br />
<br />
Shouldn't it be working w/ Group Policy too!?<br />
<br />
<br />
Thanks!!<br />
<br />

</div>
</div>


We have all the necessary ports/services forwarding through our firewall (this is not on a public internet, but segmented internal network) and can login fine.

HOWEVER, evern though mapped drives work, login, joining to domain, etc. all work -- Group Policy isn't applying itself.

GPUPDATE says "success" but none of our policies are enforcing.  HERe are our open ports

•	Kerberos (88/tcp, 88udp)
•	LDAP (389/udp, 389/tcp and/or 636/tcp if using LDAP over SSL)
•	SMB over IP traffic (445/tcp, 445/udp)
•	DNS ports (53/tcp, 53/udp) used for name lookups
•	135 DCE Enpoint
•	1000-5000 (For testing of RPC)

Shouldn't it be working w/ Group Policy too!?


Thanks!!



Does Group Policy require RPC?  Our DC is behind a firewall an Group Policy won't apply

Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).