NTFS Permissions problem - can't delete files.

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

Guest

When setting-up my laptop to supply files from a share I (foolishly) set
filesystem-permissions on the folder and contents as well as share
permisisons. These permisisons limited access to system, Administrators and
one specific user, which account is solely for network access.

-If only I'd heeded my own advice to others not to use filesystem
permissions.. but I thought I knew better on my own computer :-/

Anyway, Now have a weird situation where some files and folders in the share
cannot be deleted (either locally or via the share) and also I cannot take
ownership of these files and folders locally.

This despite the local user being a member of the Administrators group, and
the Administrators group having inheritable rights to the toplevel folder. As
I cannot view the permissions of the files in-question I cannot tell what
their ownership is.

I suspect this came-about as a result of files being moved into the folder
from other areas, and bringing their permissions with them. I might be wrong
though, it's just a guess.

Any suggestions for a fix?
 
Ian said:
When setting-up my laptop to supply files from a share I (foolishly) set
filesystem-permissions on the folder and contents as well as share
permisisons. These permisisons limited access to system, Administrators
and
one specific user, which account is solely for network access.

-If only I'd heeded my own advice to others not to use filesystem
permissions.. but I thought I knew better on my own computer :-/

Anyway, Now have a weird situation where some files and folders in the
share
cannot be deleted (either locally or via the share) and also I cannot take
ownership of these files and folders locally.

This despite the local user being a member of the Administrators group,
and
the Administrators group having inheritable rights to the toplevel folder.
As
I cannot view the permissions of the files in-question I cannot tell what
their ownership is.
Click to expand...
Have you disabled simple file sharing?
I suspect this came-about as a result of files being moved into the folder
from other areas, and bringing their permissions with them. I might be
wrong
though, it's just a guess.
Click to expand...
No, it is more like grasping for straws.
Any suggestions for a fix?
Click to expand...
Enable simple file sharing.
Access the security tab.
You can now inspect and set file permissions. Be sware though that you must
go to the root of the permissions tree because permissions may be inherited
from the top down. Hence, it is rather easy to make mistakes, and I
certainly have found to be the case by experience.
Jim
 
I don't generally see a problem with configuring both share and NTFS
permissions but maybe I am missing something in your configuration.

What happens when you try to take ownership? Is the administrators group
listed as a potential owner?? It should be by default as long as
administrators have the user right in Local Security Policy [assuming XP
Pro?] for take ownership of files and objects. You could also go to a parent
folder and in the ownership tab make sure that change owner on subcontainers
and objects is selected and then try again. Sometimes security descriptors
become corrupted and running Check Disk selecting the option to
automatically fix file errors is selected. Another trick to try could be to
use ntbackup to backup and restore that folder but select the option to not
include security settings in the backup. If all that fails a couple of
command line tools such as xcacls.vbs or fileacl can be used to change
ownership and permissions. Fileacl has a /force switch that can be used to
try and change ownership as long as your account has backup and restore user
rights. Another trick is to open a command window as system if all else
fails. Use the AT command to do that while logged on as an administrator as
in AT 22:02 /interactive cmd.exe and then use that command window to use the
file utilities.You would want to set the time to be a few minutes in the
future. Booting into Safe Mode may also be worthwhile. There was a very
similar post in this newsgroup a few days ago and a reboot resolved the
problem and showed the folder to be empty for that user. Good luck! --
Steve

http://support.microsoft.com/default.aspx?scid=kb;en-us;825751 ---
xcacls.vbs
http://www.gbordier.com/gbtools/fileacl.htm --- fileacl
 
Back
Top