Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 688
  • Last Modified:

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

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!!

0
jgantes
Asked:
jgantes
  • 2
1 Solution
 
AdamRobinsonCommented:
Can you post the results of your GPRESULT on the client(s)?

0
 
jgantesAuthor Commented:
GPRESULT

INFO: The Policy object does not exist.



Jim
0
 
jgantesAuthor Commented:
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.
0
 
DarthModCommented:
PAQd, 250 points refunded.

DarthMod
CS Moderator
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now