loosing connection to shares on server

[Guest]

I am running 2000 server, sp4 and xp pro, sp2 workstations. At least a couple
times a week all workstations loose the abillity to open shares from the
server, also can't open them by running \\server\share. The error says
"\\server\share is inaccessible, you might have permission to access this
resource, contact administrator. Windows cannot find the network path. Verify
the network path is correct and the destination computer is not busy or
turned off"

All users have permissions to the shares, the server is not off or running
high cpu. There are several events logged in the event viewer when this
occurs. They are:
Event 1000, source Userenv: Windows cannot query for the list of group
policy objects. A message that describes the reason for this was previously
logged.
Event 1000, source Userenv: Windows cannot access the file gpt.ini for GPO.
The file must be present at location <>. Group policy processing aborted.
Please help (these errors are generated any time someone tries to access a
share. A reboot of the server temporarily resolves the problem.

 

[Guest]

Are the workstations pointing to the windows 2000 server for DNS resolution??
This is a critical part of Group Policy propogation and AD in general.

 

[Guest]

Also, try:

http://www.eventid.net/display.asp?eventid=1000&eventno=6866&source=Userenv&phase=1

 

[Guest]

thanks for the post. I tried editing the gpt.ini files, we'll see if that
helps. The errors also occur when I try to access group policy when users
also can't access shares as described in my first post.
When you attempt to open or edit a domain Group Policy Object (GPO) on a
computer running Windows 2000 Server, you may receive the following error
message:
The domain controller for Group Policy operations is not available. You may
cancel this operation for this session or retry using one of the following
domain controller choices:
The one with the Operations Master token for the PDC emulator

The one used by the Active Directory Snap-ins

Use any available domain controller

again, I reboot fixes the problem for a few days.