Windows cannot access the file gpt.ini

[Gabor Hudak]

In the event log: 1058:

Windows cannot access the file gpt.ini for GPO
CN={31B2F340-016D-11D2-945F-00C04FB984F9},CN=Policies,CN=System,DC=ULT,DC=lo
cal. The file must be present at the location
<\\ULT.local\sysvol\ULT.local\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9
}\gpt.ini>. (The network path was not found. ). Group Policy processing
aborted.

First I tried to apply the KB294257 article for the guid above to reset
permissions, but it has had no effect.

The I follewed the KB221833 article to debug the userenvironment but I
can't determine what shuold I do.
Here is the log:
USERENV(208.dc8) 13:21:59:011 ProcessGPO: Found file system path of:
<\\ULT.local\sysvol\ULT.local\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9
}>
USERENV(208.dc8) 13:22:01:261 ProcessGPO: Couldn't find the group policy
template file
<\\ULT.local\sysvol\ULT.local\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9
}\gpt.ini>, error = 0x35.
USERENV(208.dc8) 13:22:01:261 ProcessGPO: ==============================
USERENV(208.dc8) 13:22:01:261 EvalList: ProcessGPO failed
USERENV(208.dc8) 13:22:01:261 GetGPOInfo: EvaluateDeferredGPOs failed.
Exiting
USERENV(208.dc8) 13:22:01:261 GetGPOInfo: Leaving with 0
USERENV(208.dc8) 13:22:01:261 GetGPOInfo: ********************************
USERENV(208.dc8) 13:22:01:261 ProcessGPOs: GetGPOInfo failed.
USERENV(208.dc8) 13:22:01:261 ProcessGPOs: No WMI logging done in this
policy cycle.
USERENV(208.dc8) 13:22:01:261 ProcessGPOs: Processing failed with error 53.

[Tim Springston (MSFT)]

Hi Gabor-

What happens if you try to access this path below by pasting it into the Run
option from the Start Menu and pressing enter?

\\ULT.local\sysvol\ULT.local\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9

--
Tim Springston
Microsoft Corporation

This posting is provided "AS IS" with no warranties, and confers no rights.
"Gabor Hudak" <hudak...@universalleaf.hu> wrote in message
news:e%237l3XT$DHA....@TK2MSFTNGP10.phx.gbl...

[anon...@discussions.microsoft.com]

The problem is DNS. I was having the same problem and
found the solution(workaround)on a newsgroup.

The solution as listed on only one reference on the web:

Edit the hosts file on EACH domain controller. Put in the
IP address for your domain controller (the local IP
address should be first in the list) -- and then next to
the IP address do NOT put the host name, but put the name
of the domain. Then list the IP address for EACH domain
controller in your domain on that same hosts file (with
the domain name next to it). In other words, your hosts
file should look like this (if you have just two domain
controllers):

121.121.121.121 yourdomainname.com

121.121.121.122 yourdomainname.com

Where 121.121.121.121 = the ip address of the local domain
controller for THIS hosts file.

Where 121.121.121.122 = the ip address of your OTHER
domain controller

yourdomainname.com = the name of your domain

The list would be reversed (as far as IP address) on the
hosts file on the other domain controller. Yes, you need
a hosts file on EACH domain controller.

>.
>