Windows Forum

Ask something
Discussion Locked

Share and NTFS Permissions

0 helpful
9 replies

by sharphillips

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I am setting up file and share permissions on a new server and something very strange is happening. I can set up the permissions and apply them, but as soon as I click OK and go back in and look at them, they are all changed to "Unknown User", withthe exception of Administrators. I have had nothing but trouble since promoting this server to PDC, and demoting the old one. I wondered if the SAM came across corrupted from the old PDC, but I can set permissions on that one and they stick. Hasanyone ever seen this happen and know how to fix it?

9 replies

by hasse mcse/brainbench

Hi!

I have never come across and error like this one and I think only way you might fix it is by promoting the OLD PDC again and reinstalling the new server since it seems like the new one has a coruppted sam for some strange reason.

/Hasse

by kieron

Not SAM but SID!!!
Use the Getsid utility to obtain the SIDs for the old and the new local groups, and redirect the output to a text file as in the following example:
Getsid \\oldserver localgroup \\newserver localgroup>sid.txt
The output looks like this:

The SID for account SERVER1\mygroup does not match account SERVER2\mygroup
The SID for account SERVER1\mygroup is S-1-5-21-275538420-358423036-7473742-1001
The SID for account SERVER2\mygroup is S-1-5-21-763131457-352918740-1170935872-1007
Copy the files from the old server to the new server, using the Scopy utility.

After you copy the files, file permissions on the new server list the local group as Unknown.

NOTE: Before performing this step, make sure your user account belongs to at least one domain global group that has Full Control permissions and is listed on the file ACE. Otherwise you will lose access to these files on the new server when you replace the local group SID with a local group SID fromthe destination serv

by veetel

I had a similar problem with users connecting to a share across a WAN link from a trusted domain. Their accounts would go to unknown. A reboot restored the users but didn't explain why. This couldn't possibly be the best resolution for a fix. Found an article in TR that the problem was actually caused by the RPC service and the fix was to change that service startup parameter to manual. Haven't had any problems since.

This discussion is closed to new replies.