access violation / group policy problem

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I am running windows 2000 server with service pack 4. I just had a server
crash but was able to restore the system from a Norton Ghost image I had
taken earlier. Everything seemed to work perfectly as the server rebooted and
all users were able to log back in. The problems started when they tried to
access any files on the server. All files would give a sharing violation or
would be read only. Even if I changed the permissions on all the files to
everyone full control the problem still persists.

If I try and change security policy setting in the AD group policy snap in I
get a “Failed to save \cal\sysvol\domain.local\policies\{large
number}\machine\microsoft\windows nt\secedit\gpttmpl.inf†If I move this file
to another location and reset its permission I am unable to edit it in
notepad or even delete it..

Any help would be much appreciated.

Regards

Mark
 
If I try and change security policy setting in the AD group policy
snap in I get a “Failed to save
calsysvoldomain.localpolicies{large
number}machinemicrosoftwindows ntseceditgpttmpl.inf†If I move
this file to another location and reset its permission I am unable to
edit it in notepad or even delete it..
Click to expand...

Hi,

These sound like two different issues. I would run a chkdsk scheduled
on your drive. It should check the acl’s and reset them to the
default if they are corrupted

The second is a group policy issue. That file you are refering to is a
Group Policy. That {large number} is pretty important if you can type
it here that would be great. If it is your Default Domain Policy or
your Default Domain Controller Group Policy then that is a bigger
problem than if it is just a Group Policy you created.

What caused your crash? Was it hardware related? Did you try
everything before restoring from a Ghost image? Is your date/time on
your computer accurate? Make sure the Domain Date/time on all the
computers is the same.

Cheers,

Lara
 
Thanks for your reply:

Just to let you know I have sorted the problem. I may have left out a major
piece of information that was responsible for the problem. I was again able
to restore the ghost image to the drive and then booted up the system, this
time I did not turn the drive from a basic drive under windows to a dynamic
drive so that I could mirror it. I checked everything as far as file
permissions and group policies were concerned and everything worked
perfectly. I then changed the drive to a dynamic drive and everything went
pear-shaped. So for all out there that are interested, do not change your
Basic windows 2000 boot partition to a dynamic drive.
 
Back
Top