Windows file permissions problems

We have an Xserve G5 that was running Server 10.3. I upgraded it directly to Server 10.5. Since then, I am having problems with some of our Windows users.
When they create a new folder, it puts them as the owner, but gives them NO rights. I am using ACLs to give full rights to the group that needs access, and also setting the POSIX group rights to read/write. So once they leave that folder, they can no longer get back in. I have SMB set to inherit rights from the parent, and the ACL is set to inherit as well. Other people in the group can access the folder, just not the owner! I change the owner permissions and all is well (for that folder at least). How do I need to set SMB so it follows the inheritance I set?
Once I have the folder set correctly, any new files created there have the POSIX group set to read only. The ACL inherits properly and still has full control. The owner is set correctly, usually. It is not consistent.
Once someone creates a file in any folder, if a Windows user modifies a file someone else created, it changes the owner name and gives them no rights. It also creates a new ACL record. If the original owner was a Mac user, it creates a new explicit ACL with all rights except execute and delete. If the file has ACL records already, it duplicates them and gives whatever rights it feels like (it seems). One new record may say Allow Delete only, and the next one say Allow Read except for execute. The only thing for certain is it will never match the original ACL. It always adds the new ACLs at the top of the list, and the duplicates are grayed out as if they were actually inherited that way. The most 'popular' file I've found so far had 128 "inherited" ACL records!
It is also denying access to some folders that the user has the correct permissions for. For instance, I can create/modify/delete files logged in on the Mac side, but when I log in on Windows, I have problems accessing files/folders. It shows everything as read only. Even if I change the properties in Windows, it will revert back to read-only when I apply the change.
We have a new Xserve that we will be moving the file services to. At that time, all the Windows users will be moved completely to the Mac side - currently the Windows users are accessing the Xserve and a Novell server.
Thanks in advance for any help.

Hi Thy,
Based on my research, the Trusted Installer is a service, for those resources which only allow Trusted Installer to modify, neither Administrator nor System can modify them.
I am wondering that how secure the network and physical environment is that you need to create a GPO to prevent users making permissions changes on system files. These system files normally only can be modified by Administrators,
System or Trusted Installer, which is secure enough when we don’t add users we don’t trust enough to Administrators group.
>What is the best way to undo this while leaving the audit failures turned on and still retaining the correct permissions on all the files?
As long as administrators on these machines are qualified, you can remove the Group Policy. If not, please don’t make any user you don’t trust as Administrator.
>What happens to the files that aren't owned trustedinstalled than now have the trustedinstaller default permissions under system32 and syswow64 if I were to remove the gpo? What file permissions would be retained?
We should keep the default permissions, if those files weren’t owned by Trusted Installer before, we should change the original owner back, vice versa.
Here are some related articles below I suggest you refer to:
New ACLs Improve Security in Windows Vista
http://technet.microsoft.com/en-us/magazine/2007.06.acl.aspx
SYSK 277: How-To Bring Back the TrustedInstaller
http://blogs.msdn.com/b/irenak/archive/2007/01/30/sysk-277-how-to-bring-back-the-trustedinstaller.aspx
Best Regards,
Amy

Similar Messages

Shared File Permissions Problem

Since upgrading the Mavericks I constantly have file permissions problems when I tranfer files between computer. Let me see if I can clarify the problem procedurally.
1. I have a shared directory that I set to Read&Write privileges for Admin, (me), and Everyone.
2. I clicked the cog to apply the changes to all the enclosed items. Perfect... everything contained within the directory was changed.
3. I went to my other Maverics computer and connected to this shared directory using SMB, AFP, connect to server command-k, and using the shared feature on the finder window, which asked me to authenticate when I make the connection. I logged in with the admin account to make sure I absolutely had full privileges.
4. I transferred a file to the shared directory and it ended up with the privileges of only (me) RW and Everyone as No Access. It dropped every other set of privileges that were in the directory and set Everyone to No Access, which is a major problem since it serves the files to the web server. I checked the Sharing preferences in the System Preferences. Sure enough all groups are set to Read and Write.
The shared directory in Terminal says the privileges are drwxrwxrwx+ so it should retain those privileges for any file I place in that directory, but it doesn't.
This is a new problem to Mavericks. When I used OS 10.7 and 10.8 and chose the get info option to apply the permissions to all enclosed files it stayed that way for any file I inserted into the directory. Now you have to constantly change file permissions even going from Mavericks-to-Mavericks computers.
Does anyone know how to retain the file permissions for a shared directory when new files are placed in the directory?

see Topic: Office (2004 & v.X) can't save to AFP volumes properly
Apple wants you to enable ACLs even if your not using them. See my posting dated April 14

Installed Photoshop cc 2014 asks for serial # - corrupted Windows file permissions

More of a warning / heads up to all than a question - installing Photoshop cc 2014 [via the CC manager app] caused some Windows file (security) permissions to become corrupt corrupt on my system. Symptoms include cc2014 asking for serial number validation on startup (when, as a cloud version, it should not do so), then being unable to connect to the internet when you press the 'validate serial' button so getting that window into infinite loops, and - a real pain in the *** when trying to fix the above - causing abends of some windows shell functions that in turn cause windows explorer to crash and restart.
Anyhow, digging into this (fortunately, I am a long time Windows SysProg) I discovered that for reasons unknown, either the CC master app or the actual Photoshop cc2014 installer (or both) are changing file access control permissions on a number of files, mostly DLL's. Most of the files affected are in the (normally hidden) Program Data directory on the windows root disk, Some of them are in the Adobe subdirectory - so fair enough if they want to fool around with their own program - but others being changed are in the Common Files and Microsoft subdirectories. I cannot for the life of me figure out why this is necessary nor why Adobe feel the need to touch files that 'do not belong' to them - something dangerous in the extreme as an external app such as Windows Update might replace or 'repair' the files so touched, and if Adobe / CC are relying on file permissions on non-Adobe files, such changes could result in all manner of random and spurious problems / error messages occurring.
Anyhow, if, fellow Photoshop cc 2014 user, you get this happen to you then you can fix the file permissions by opening a console window [also called a "DOS box", or "command prompt" depending on your age and knowledge... 8-) ] and run the windows file checker with the command
"sfc /scannow". Make sure that you use 'run as administrator' to open the console window, or you'll get an error about sfc only being available to administrators. Also a very (very) sensible idea to close all non-essential running applications first to prevent any possibility of weird interactions happening.
Finally, check that the 'hosts' file in [root drive]:/Windows/System32/drivers/etc is valid - for some reason, it looks like the install tried to check or update this file (again, I have no idea why) but the result was a corrupted hosts file, which I assume is the root cause of the 'unable to connect to host' type internet error messages. Copy the file, rename it as 'hosts.txt' and edit it with notepad or wordpad. Look for lines containing garbage strings at the bottom of the file (any line that starts with a # ignore, it is a comment, and any line that has IP addresses or host names should be ignored - though if they reference a site such as "someserver.adobe.com" you might want to treat them with suspicion if you continue to get internet 'cant connect to site' type errors.
Anyhow, when I fixed these two sets of problems, Photoshop cc 2014 started 'right first time' without all the BS messages about serial numbers etc.
Hope this helps somebody out there in AdobeLand......
Rick

Update: I tried several times to reproduce the error, actually it dosen't occur. I changed nothing on my system, without reboot it twice. This is what I said in my beginning times: it occurs sometimes but often. I will keep you up to date.

File Permissions Problem - Multiple Network Users

My wife & I have a home office network setup for our business, and are having trouble with shared files over the network. We're both on Macs, and all of our client files reside on an internal hard drive in my Mac Pro. I've set her up as a "Sharing Only" user on my computer (which matches the username & password of her account on her iMac), and have properly setup file sharing in both the System Preferences, and in the directory itself that we want shared. I've also applied the permissions to all files & folders below the main folder, and she can view, open and save whatever she needs and it works great.
*Here's where the problem comes in...* If either of us create a NEW file or folder, the other person doesn't have WRITE access to it (we can browse and open it fine). The second I go to update a file she created, it won't let me over-write it, and I have to go into the permissions for that specific file and give myself Read/Write access. I've experimented with "Groups", and assigned both of us a special group, and applied that group access to that directory, but it doesn't make any difference when a NEW file or folder is created - it doesn't copy the parent directory permissions to itself, it makes one of us the owner, and nobody else has access.
Is there any way around this? We're both constantly creating new files, and it really hampers our workflow to have to keep re-applying file permissions every time one of us creates something new. Ideally, any new files created within that main client folder would automatically have the same permissions as the parent directory. Any help would be greatly appreciated! Thanks!!

you can keep those files on a separate partition on the hard drive and turn off ownership for that partition.
the only other way i know how to deal with this is using inherited ACLs.
run the following terminal command from your account on the mac pro.
chmod -R +a "username allow delete,chown,list,search,add_file,\
addsubdirectory,delete_child,file_inherit,directoryinherit" /path/to/shared/folder
put your short username instead of username in the above. also, instead of /path/to/shared/folder put the unix path to the folder you are sharing. you can get this path by dragging that folder to a terminal window.
repeat the command with your wife's username instead of yours.
warning: this will work with newly created files in the shared folder and with the files you COPY to that folder. it will not work with files that you MOVE to that folder.
Message was edited by: V.K.

Recurring file-permissions problems

A problem has abruptly appeared and keeps (unpredictably) recurring. When I edit a file and then save the modified version of that file, something breaks and when I try to reopen the file, later, I get a "you do not have permission to open this file" message. And the file can't be opened.
If I restart my MacBook Pro, the problem will usually disappear for a while, then begins to pop up again.
I've been running Mountain Lion since shortly after it was introduced. This is a new problem (never encountered it in 25 years with Macs; this began a few days ago) and has me baffled.

Back up all data now.
This procedure will unlock all your user files (not system files) and reset their ownership and access-control lists to the default. If you've set special values for those attributes on any of your files, they will be reverted. In that case, either stop here, or be prepared to recreate the settings if necessary. If none of this is meaningful to you, you don't need to worry about it.
Step 1
Launch the Terminal application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Terminal in the icon grid.
Drag or copy — do not type — the following line into the Terminal window, then press return:
sudo chflags -R nouchg,nouappnd ~ $TMPDIR.. ; sudo chown -R $UID:20 ~ $_ ; chmod -R -N ~ $_ 2> /dev/null
Be sure to select the whole line by triple-clicking anywhere in it. You'll be prompted for your login password, which won't be displayed when you type it. You may get a one-time warning not to screw up. You don't need to post the warning. If you don’t have a login password, you’ll need to set one before you can run the command.
The command will take a noticeable amount of time to run. Wait for a new line ending in a dollar sign (“$”) to appear, then quit Terminal.
Step 2
Boot into Recovery by holding down the key combination command-R at startup. Release the keys when you see a gray screen with a spinning dial.
When the OS X Utilities screen appears, select Utilities ▹ Terminal from the menu bar. A text window opens.
In the Terminal window, type this:
resetpassword
That's one word with no spaces. Then press return. A Reset Password window opens. You’re not going to reset a password.
Select your boot volume ("Macintosh HD," unless you gave it a different name) if not already selected.
Select your username from the menu labeled Select the user account if not already selected.
Under Reset Home Directory Permissions and ACLs, click the Reset button.
When that's done, launch Disk Utility and repair the permissions of the boot volume.
Select  ▹ Restart from the menu bar.

Project 2010 Trial - Enterprise Global File permissions problem

Hi,
I recently installed Project 2010 Server Trial version. The web fronted work but when i try with Project 2010 Profesionnal client, i got this error message :
"No permissions to read Project Server Enterprise Global File.
The Project Server Enterprise Global could not be accessed. Contact your Administrator."
Anyone can help me ?
Regards

i have faced similar issue in Project Server 2013, and while troubleshooting the problem, i have found in the event logs the following error on the application server take place while trying to access the PWA with the Project Pro.
Application log Error with ID 8306 and Task Category Claims Authentication:-
An exception occurred when trying to issue security token: ID 3242: The security token could not be authenticated or authorized..
Resolution at my side:-
while troubleshooting it seems that resting IIS @ the WFE server solved the issue.
wish that it helps.
thx
Karim El Zarka, MCTS Sharepoint 2010 , MCITP SharePoint Administrator 2010 Whenever you see a reply and if you think is helpful, click "Vote As Helpful"! And whenever you see a reply being an answer to the question of the thread, click "Mark
As Answer

Mac to Mac file sharing - file permissions problem upon newly created files

Hi all,
At home I have two iMac's both running Snow Leopard.
iMac A/Users/*1 is sharing his iMac A/Users/*1/Documents folder.
The sharing & permissions - preferences of this folder and the files inside this folder are:
'*1' : (the iMac A's main user account) : Read & Write
'share' : (a Sharing Only account, set up from iMac A) : Read & Write
everyone : : No Access
iMac B/Users/*2 is able to read & write to this folder because he is connected with iMac A as 'share'.
So far so good. iMac A/Users/*1 can read & write to his own Documents folder
and so can iMac B/Users/*2 because he is connected to iMac A as 'share'.
But: this only applies to the folders and files that are _already in_ the iMac A/Users/*1/Documents folder,
because I once changed the sharing & permissions -permissions of iMac A/Users/*1/Documents as mentioned above and executed 'Apply to enclosed Items...'.
So the problem is: when I create a new file or folder on iMac A/Users/*1 or on
iMac B/Users/*2 and put it in iMac A/Users/*1/Documents, this new file or folder will only
have the standard sharing & permissions - preferences of any newly created file or folder
on the iMac X/Users/*Y it was created. The problem is those sharing & permissions - preferences
will not let the other iMac X"/Users/*Y" Read & Write to this new file or folder but only let himself
Read & Write. Following, the other iMac X"/Users/*Y" will only be able to Read the newly created
file or folder, because the standard standard sharing & permissions - preferences on
iMac A/Users/*1 as well as on iMac B/Users/*2 are the following:
'*Y' : (the iMac X's main user account) : Read & Write
staff : (Administrator accounts on iMac X) : Read only
everyone : : Read only
A pretty manual fix to this problem is walking to iMacX" and changing the
sharing & permissions - preferences of the newly created file or folder so that iMacX"
will also be able to Read & Write this newly created file or folder.
Does anyone know a better fix for my problem? Basicly I want to have Read & Write
sharing & permissions on the newly created file or folder for both iMac's,
not only the for the file or folder creator's iMac. And this without having to change
sharing & permissions - preferences of this newly created file or folder manually
each time.
Thanks in advance,
Vincent Verheyen.

Hi all,
I have found a thread wich i think also handles about my problem.
The standard sharing & permissions - preferences or privileges
can be changed apparently, this seems to have got something to do
with umask and changing this umask. The adress is the following:
*http://www.macosxhints.com/article.php?story=20031211073631814*
Other ways to change the above-mentioned umask may be
applications like SharePoints, TinkerTool or BatChMod.
All of them are also mentioned in the above-mentioned thread.
I haven't executed the solution as mentioned in the above-mentioned
thread yet, replies to the thread speak about insecurity and failures.
Further more I haven't found any other solutions to my problem,
so any help is still greatly appreciated.
Thanks in advance,
Vincent Verheyen.

Windows partition permissions problem

i have a fat32 partition that i use to be able to see files whenever i'm on windows or linux. my fstab is as follow:
/dev/discs/disc0/part4 /mnt/windows vfat rw,user,auto 0 0
but if i do
[nbcjr@universo ~]$ touch /mnt/windows/lin
touch: cannot touch `/mnt/windows/lin': Permission denied
what's going on?? how do i set this partition to be mounted automatically and to permit any user (or at least my main user) to write any file on it???
thanks!

hi!
i also have a ntfs partition that sometimes i want to get something from. i mount it as read only, but only root has permission to acess it. i don't know how to solve this.
fstab
/dev/discs/disc0/part1 /mnt/ntfs ntfs ro,user,noauto,unhide 0 0
windows is my fat partition, ntfs is the ntfs one.
[nbcjr@universo mnt]$ ls -lah
total 42K
drwxr-xr-x 10 root root 248 2005-09-20 02:15 .
drwxr-xr-x 19 root root 464 2005-09-18 23:07 ..
drwxr-xr-x 2 root root 48 2005-06-17 02:43 captive-noname
dr-xr-xr-x 2 root root 2.0K 2005-09-30 12:07 cd
drwxr-xr-x 2 root root 48 2005-08-24 17:58 dvd
drwxr-xr-x 2 root root 48 2005-08-24 17:58 fl
drwxr-xr-x 2 root root 48 2005-06-22 22:00 floppy
dr-x------ 1 root root 8.0K 2005-09-21 23:39 ntfs
drwxr-xr-x 2 root root 48 2005-09-20 02:15 usb
drwxr-xr-x 9 nbcjr root 32K 1969-12-31 21:00 windows
even after
[root@universo nbcjr]# chmod 755 /mnt/ntfs/
chmod: changing permissions of `/mnt/ntfs/': Read-only file system
it stays like that. thanks a lot!

File permissions problem

I'm trying to organise permissions on my server. I have a bunch of .iso files which I mount over nfs but it seems as though no matter what I do, the owner and group permissions are ignored.
Obviously I'm mounting as root. The files are owned by root but I can only mount them when the other permissions are set to rw-. Doesn't seem to matter what the owner and group permissions are set to.
What am I doing wrong?
edit:
I'm guessing root runs mount but mount is actually run as something else?
Last edited by sand_man (2010-01-21 11:28:13)

Hmm it is strange. I can mount an iso locally where root has no permissions at all.
Makes no sense to me. There must be a reason why "other" has to have write permission when mounting over nfs
Is it the network group one needs to be in? I'll give it a try
edit again:
I think I might just mount the iso on the server and export that. Its essentially the same thing and I'm the only one using it so it won't matter anyway.
Last edited by sand_man (2010-01-22 01:44:02)

Oracle Secure Backup on Windows: file permission problem?

Hi all.
I did a new Oracle Secure Backup installation.
I implemented a real simple domain:
a Linux box is the media/administrative server. Then I have some Windows and Linux Client.
On a Windows 2000 server SP4 box I'm experiencing an error.
On certain directories i get the following:
The directory is not a subdirectory of the root directory.
On certain files I get the following instead:
The directory name is invalid.
The OSB service is running under the local system account on the client.
Can you help me trouble this error?
Thanks
Giovanni

Thanks for your reply.
Disks are mounted using CIFS.
we got the fix for this, need to do the following changes.
# Turns off locking
echo 0 > /proc/fs/cifs/OplockEnabled
# Turns off inode caching
echo 0 > /proc/fs/cifs/LookupCacheEnabled
cheers...
Edited by: TJ_DBA on 14/02/2011 16:43

MaxDB 7.6 on Windows 7 - permissions problems

Hi.
I want to install MaxDB on windows 7 so that regular users could control the x_server and issue dbmcli commands.
Currently when I install it, only the administrator can control x_server (start/stop it) - regular users get an access denied error.
In addition, various commands fail with error:
ERR
-24994,ERR_RTE: Runtime environment error
1,could not create comm. shared memory [5]
When trying to run them not as administrator.
So, what are the guidelines for installing maxdb under windows 7 regarding permissions?
How can I let regular users do these actions?
Thanks,
Doron

> You're saying there is no way for my application to do this without having admin privileges?
The required privileges had been available to standard users until Windows 2008/Vista.
And, by the way, MaxDB is not released for Vista!
> Or the dbmcli commands - part of them succeed and part don't. Why is that? I can create a database with regular user privileges but I can't extend it. This does not sound as designed behavior - maybe I'm doing something wrong?
It's just that MaxDB is a server product and is not developed on Windows 7 for end users.
No design bug here, just the standard permissions for end users have changed with Windows 7.
> (the dbmcli behavior looks suspicious to me because on linux/solaris it works without root privileges).
Ok - this is something completely different here.
Even as member of "Administrators" on Windows 7 you don't have all privileges...
Right now, you've to use these tools as administrator on Windows 7.
While we're at it: if there is a chance that this will be changed/adapted I highly doubt that it would happen for an old release as 7.6.
Go for 7.7 or 7.8 instead.
regards,
Lars

CIFS File Permissions Problem

Has anyone else experienced this? I have a remote site setup using a WAAS 574 in inline mode (connected to a 2811 router) and whenever I enable the CIFS Accelerator on the device (and the Central Office WAAS) the remote site end users start gaining access to each other’s files? Not all of them, just files that someone else was accessing recently. It seems like the CIFS Accelerator has recently accessed files cached and doesn’t check the User rights on Active Directory for some reason. I have CIFS disabled for now but I would love to re-enable it. FYI – The File Server being accessed is a MS Windows 2008 R2 will all Service Packs and Updates installed.

Hi William,
Do you know if this is a newly installed server and if Share
configured on this server are ABE (Access-bases Enumeration). If yes then
you would need to configure them as dynamic shares in WAAS. See below link.
http://www.cisco.com/en/US/docs/app_ntwk_services/waas/waas/v431/configurati
on/guide/filesvr.html#wpxref89338
Thanks
Ahsan

10.8.4 (server) and windows file sharing problem

Hello
This is a clean install of 10.8.4 and server apps not and upgrade of 10.5.8
(This server had a working 10.5.8 server install.... sigh!)
AFP, SMB and guest access enabled on all shares
Guest sharing enabled in the User accounts in System prefences.
from any Mac station AFP:// and SMB:// works fine using Guest access or typing in any name.
No Windows station ( Win 7, XP, SRV 2008 ) can connect to the shares successfully.
Tried from stations that are part a local domain and others who are just in a WGRP
When attempting to connect to the Mac server shares the log in window appears and
no matter what is typed in ( Even the Mac server admin account) or guest
the connection fails
Error: is not accessible, you might not have permission to use this network resource
the remote procedure call failed

I'm actually having the same issues as Shawn. No non-Mac computers can connect to the new Mac Pro server (10.8.4) using SMB. Mac users can use SMB or AFP without issue.
Here's a screenshot of the message Windows users are seeing:
Can someone point me in the right direction on how to get this fixed? This is urgent!
Adam

Weird Locked Files/Permissions/Dock/Etc

I have some sort of odd locked file/permissions problem (I think).
About a year ago, I seem to have done something to my permissions or locked files that I can't seem to fix. I have a variety of disparate symptoms, including applications that won't work or can't be installed/deleted because support or preference files are locked or can't be changed, a need to repeatedly reauthenticate with a password just to move files from one folder to the next, an inability to turn off file sync for mobile me, dock item changes that go away whenever I reboot, locked files that continually reopen in Preview, having to manually delete and reinstall apps like Preview apparently because of locked preference files, printers that won't work because of locked files until I delete all and reinstall, software that won't run properly or fails to launch at all on double click, etc.
It is almost like a ghost in the machine problem because the problems are relatively varied.
I've tried disk utility etc to repair permissions and none of the repairs work (I keep getting the same errors, copied below). I've tried a complete reinstall of the OS, repair permissions from the OS X restore disk, etc. and nothing seems to help.
This is happening on a Mac Pro 1,1 (3.0 GHz), running 10.7.4 with all updates through today and with a Radeon 4870 card, and 9 GB of properly matched ram. Everything else works pretty well and I have no similar problems on my wife's 2011 iMac, my MacBookAir i5, etc.
I'm thinking that there is some sort of locked file or permissions problem that is not getting fixed correctly and that there might be some trick to fixing it.
Help!!
Repairing permissions for “Master”
ACL found but not expected on “Library/Printers”
Repaired “Library/Printers”
ACL found but not expected on “private/etc/apache2/users”
Repaired “private/etc/apache2/users”
ACL found but not expected on “Library/Printers/PPDs”
Repaired “Library/Printers/PPDs”
ACL found but not expected on “Library/Printers/PPDs/Contents”
Repaired “Library/Printers/PPDs/Contents”
ACL found but not expected on “Library/Printers/PPDs/Contents/Resources”
Repaired “Library/Printers/PPDs/Contents/Resources”
ACL differs on “Users”
Repaired “Users”
ACL found but not expected on “private/var/root”
Repaired “private/var/root”
ACL found but not expected on “private/var/root/Library”
Repaired “private/var/root/Library”
ACL found but not expected on “private/var/root/Library/Preferences”
Repaired “private/var/root/Library/Preferences”
Permissions repair complete

Repairing the permissions of a home folder in Lion is a complicated procedure. I don’t know of a simpler one that always works.
Back up all data now. Before proceeding, you must be sure you can restore your system to its present state
Launch the Terminal application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Terminal in the page that opens.
Drag or copy — do not type — the following line into the Terminal window, then press return:
chmod -R -N ~
The command will take a noticeable amount of time to run. When a new line ending in a dollar sign ($) appears below what you entered, it’s done. You may see a few error messages about an “invalid argument” while the command is running. You can ignore those. If you get an error message with the words “Permission denied,” enter this:
sudo !!
You'll be prompted for your login password, which won't be displayed when you type it. You may get a one-time warning not to screw up.
Next, boot into Recovery by holding down the key combination command-R at startup. Release the keys when you see a gray screen with a spinning dial.
When the Recovery screen appears, select Utilities ▹ Terminal from the menu bar.
In the Terminal window, enter “resetpassword” (without the quotes) and press return. A Reset Password window opens. You’re not going to reset the password.
Select your boot volume if not already selected.
Select your username from the menu labeled Select the user account if not already selected.
Under Reset Home Directory Permissions and ACLs, click the Reset button.
Select  ▹ Restart from the menu bar.

Problem with file permissions in Windows shares

Due to a company merger we are now supporting a group of Macs in our PC environment. These Macs connect to our Windows shares. This generally works well, however we have discovered a problem. It’s to do with the way our Macs interact with our Windows shares. When they copy a file to a windows share they take the permissions for the file they copy from the route of the share rather than from the subfolder the files are copied to and write the file permissions accordingly.
This only affects admin users who use Macs with the ability to change file permissions. Everyone else inherits the permissions from the subfolder as they should because their account can’t change the permissions. If the route and subfolder permissions are the same then there is no change. If they are different, the Mac will use the share route permissions as preference.
We have shares where users don’t have access to the route folder but do have access to other folders. This is so that they can’t change the top level folder structure. However they are able to create folders and files under the top level folders. If an administrator uses a Mac, no one has access to any files or folders they create because users don’t have access to the route folder and this is copied to the files and folders they create. This doesn’t affect our PC’s only the Macs.
We are using the latest Mac OS fully updated and Windows 2008 server. Is this a normal Mac ‘Feature’? Is there a work around?

I’m a bit disappointed by the lack of response to my problem. As Windows is the predominant file server in business, this problem must have occurred before.
Are Mac people really saying that Macs are not designed to connect to networks? At the moment our Macs are unusable apart from a few isolated tasks. Basically they are used by a few designers who work in isolation. If PC’s had this problem no one would buy them.

Windows file permissions problems

Similar Messages

Maybe you are looking for