Windows Server 2008 permissions problems

November 11, 2010 at 19:01:56
Specs: Windows Server 2008 Std, na
Just wondering if any of you might have any idea why I am seeing strange permissions issues on a file server. It is running Windows Server 2008 Std, and is part of a domain.

For example:

I can successfully drill down to the folder \\server\E$\share\Lorem\Ipsum\dolor. I can open most of the folders in here. But there is one ('sit’) that I can’t open:

If I open the Security properties of 'sit', I get the message “you do not have permissions to view or edit this object’s permission settings”. If I go to the Owner tab, it says “Unable to display current owner”. Now I will likely be able to take ownership of this folder as the domain administrator (and then be able to get in), but I am just wondering why this is happening all over the place. And sometimes even if I take ownership, it wont take ownership of the subfolders even though I tell it to do so (thus I need to repeat the same process).

For other folders in that same directory ('dolor'), I can browse their Security settings and open them without a problem. They all are inheriting permissions from \\server\E$\share\Lorem. And the Owner of Lorem is the domain Administrator. Why is it that some folders (e.g. 'sit') are not inheriting these same permissions?

Is there an easy way to make it so that Administrator automatically has permissions to every share/directory/file on the server?

Thanks in advance.

See More: Windows Server 2008 permissions problems

Report •

November 13, 2010 at 21:04:41
Without knowing the entire history, it's hard to say. Was the folder moved there from another folder? If so, it most likely will not inherit the permissions of the parent, depending where it came from.

Is there a way to set it so administrator automatically has permission? It depends what you mean by 'automatically'. And administrator does have access in the sense that he can't be locked out. Otherwise you'd have to edit the permissions of the parent folders or the root of the drive - something I wouldn't recommend.

Report •
Related Solutions

Ask Question