none
Windows Could not connect to the group policy client service.

    Question

  • Hello Experts....One of our client is facing this issue on Windows 10 & 8 client machines. They can not login, it gives an error "Windows Could not connect to the group policy client service".There are multiple users who are facing this issue. 

    Can you please help me what could be the problem. I am unable to resolve this. DC is running on Windows Server 2012 R2.

    Thanks,

    Sim

    Wednesday, January 4, 2017 3:59 AM

All replies

  • Greetings,

                    The error, Windows Could not connect to the group policy client service indicates that the issue could be local to the client, in which you can check for the GROUP POLICY Client Service in the workstation. If the service is started, we can go ahead and start the normal troubleshooting like name resolution of the domain FQDN and the DNS configuration.

    Regards

    Eric


    Microsoft Forum Update

    Wednesday, January 4, 2017 6:14 AM
  • Hi... The services does not starts..I have to reboot multiple times to get this service working. It is not one client more than 200 users are affeceted from this.

    Also, these clients are connecting to Azure DC and they cant update their GPO policies. It says computer policy update failed. Access is denied.

    Any help is appreciated.

    Wednesday, January 4, 2017 7:35 AM
  • Hi Sim,
    Please take a look at the following article as below and try the suggested method in it to see if it helps:
    BEST FIX: Failed to connect to Windows service
    https://appuals.com/best-fix-failed-to-connect-to-windows-service/

    Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.
    Best regards,
    Wendy


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com


    Wednesday, January 4, 2017 8:47 AM
    Moderator
  • Greetings,

                     If the issue is global involving 200 users and clients, then please check whether any group policy has been rolled out recently. you can also verify the policies effect using group policy results in the Domain controller.

    Regards

    Eric


    Microsoft Forum Update

    Wednesday, January 4, 2017 8:53 AM
  • Is the machine are from the same OU or of different ou? If same OU then check the security setting and check authenticated users group ,system, self is there or not.

    Also check the firewall setting as a precaution :

    • UDP 88 - Kerberos Authentication
    • UDP and TCP 135 - Client to domain controller operations (RPC)
    • UDP 389 - LDAP queries
    • TCP and UDP 464 - Kerberos Password Change
    • TCP 3268 and 3269 - Global Catalog client to domain controller
    • TCP and UDP 53 - DNS (assuming your DC is also acting as DNS, otherwise you need to open to your DNS server and point to it).
    • TCP 1031  Transmission Control Protocol

    Wednesday, January 4, 2017 10:16 AM
  • Hi,

    I am checking how the issue going, if you still have any questions, please feel free to contact us.

    And if the replies as above are helpful, we would appreciate you to mark them as answers, and if you resolve it using your own solution, please share your experience and solution here. It will be greatly helpful to others who have the same question.

    Appreciate for your feedback.

    Best regards,

    Wendy


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

    Tuesday, January 10, 2017 7:40 AM
    Moderator