Windows cannot access the file gpt.ini for GPO...

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Gabor Hudak (hudak.gabor_at_universalleaf.hu)
Date: 02/20/04 

Date: Fri, 20 Feb 2004 10:41:13 +0100

Hi!

My domain contains a Win 2000 PDC and a Win2003 DC.
When I log on to Win 2003 interactively or try to connect with the terminal
client to Win2003 server I got the same 1058 1030 event and the connecting
fails (client independent).
I can open the gpt.ini file on both server via SYSVOL share with notepad.

Remote Registry and TCP/IP NetBIOS Helper services aren't running but their
startup is automatic and log on are as local service.
When I try start them I got an error:
Services
---------------------------
Could not start the TCP/IP NetBIOS Helper service on Local Computer.Error 5:
Access is denied.
---------------------------
OK
--------------------------

I can edit loggin on the servers the default domain policy in the Group
policy management on Win 2000 server but on the Win2003 server I got an
error:
Group Policy error
failed to open the group policy object
you may not have appropriate rights

datails:
---------------------------
The network path was not found.

Any idea to solve the problem?
Thanks!

Relevant Pages

  • Re: GPO error no appropriate rights
    ... Thank you for posting in the SBS newsgroup. ... Install the Windows Small Business Server 2003 Update for Windows XP ... go to Group Policy Management -> ... DomainName.local -> Small Business Server Client Computer ...
    (microsoft.public.windows.server.sbs)
  • Re: "Windows cannot access the file gpt.ini for GPO" - Events 1058 and 1030 on XP client o
    ... fails (client independent). ... I can open the gpt.ini file on both server via SYSVOL share with notepad. ... Remote Registry and TCP/IP NetBIOS Helper services aren't running but their ... failed to open the group policy object ...
    (microsoft.public.windows.group_policy)
  • RE: My documents synchronization. How to stop?
    ... a new domain on the full server2003, some of the old client machines still ... try to synchronize with the SBS server. ... 2.Restart the problematic client computer to take the group policy effect. ... 6.Make sure that folder redirection group policy have listed in applied ...
    (microsoft.public.windows.server.sbs)
  • Re: Client Synchronization errors after new install of server
    ... The clients will have to regenerate SID's, as the reloaded server is considered to be a different domain. ... The second error is with the Group Policy. ... The client workstations seems to still have some of the old policy. ... USERENV07:26:06:354 UnloadUserProfileP: Didn't unload user profile ...
    (microsoft.public.windows.server.sbs)
  • RE: GP in Terminal server
    ... If the client uses Windows XP, please run Regedit to change the permissions ... >correct DNS server address. ... >Resource Kit) to troubleshoot group policy issues. ...
    (microsoft.public.windows.group_policy)