Link to home
Start Free TrialLog in
Avatar of rawsharklives
rawsharklivesFlag for United Kingdom of Great Britain and Northern Ireland

asked on

MAC permissions problem with Iomega NAS on Windows Domain

We have a Windows 2003 SBS server and use PCs and MACs. We recently purchased an iomega StorCenter StorCenter ix4-200d to act as our fileserver to take the load off our server.  All seemed fine until the MAC users said they had problems writing to folders, even ones that they had created themselves only minutes before.  After some investigation, it seems that from OS versions 10.6.4 and above, if the MAC is added to the windows domain, the permissions on new folders are set with Read-Only attributes for Everyone, and some of our global User groups.  This can be resolved by logging in to a PC as the MAC user who first created the folder and setting full access again to Everyone and the other groups.  As you can imagine this is painful!  If I remove the MAC from the domain on 10.6.4 upwards, it seems to work fine but I need them on the domain to be able to secure our NAS drive with Active Directory.

Also, I've noticed that below 10.6.4 we can copy files from the MAC's desktop to the NAS by first removing the dotslash files (using Terminal), but on 10.6.4 and upwards, even removing the dotslash files doesn't help and the file copy fails with 'you do not have permission..'

My options seem to be to downgrade all MACs to pre 10.6.4 (not going to go down well) or take them off the Windows domain - not practical.

One more thing - all MACs can copy files absolutely fine to a share on the original Windows 2003 Server.  We are using this as a temporary area for MAC users to get files on to the server.. they copy to the Windows Server and someone on a PC then moves the files on to the NAS for them.

Thanks

Rich Reeves
Jellyfish Creative
01604 233 933
richr@jellyfishcreative.co.uk
Avatar of roylong
roylong
Flag of United Kingdom of Great Britain and Northern Ireland image

I think you have two options:
1: contact Iomega for help sorting out the permissions and privileges.
2: mount the NAS to the windows 2003 server and have your macs continue down this route.
Avatar of rawsharklives

ASKER

Hi,

I will try the iomega route, but as I can get the MACs to work when not on the domain, and PCs work when on the domain, I was assuming they wouldn't get involved.  Worth a shot though.

As to point 2.  Can you clarify what you mean by mounting the NAS to the windows 2003 server?  Do you mean setting up a share on the main server pointing at the NAS?  How would the MACs then access it?

Thanks for your help so far.

Rich
I'm now logging a call with IOMEGA support once I have the serial number of the drive from the office.  I will let you know if they resolve it and pass on points appropriately.

Thanks

Rich
did this get resolved?
ASKER CERTIFIED SOLUTION
Avatar of rawsharklives
rawsharklives
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
I would request closing this question with you solution as the preferred answer.
Could not resolve problem on Windows Domain.  Had to take if off the domain and go about it another way.
I have had a simular problem. I need both MAC and Windows computers to be able to access the NAS device while autenticating to ADS.

After speaking with iomega techs, and having them tell me to only way to have both Windows and MACs access the device was to set it to workgroup modes- not an option for us.

Well, good news!!  --Sort of.  I got to thinking,
While having the NAS setup to access ADS, I enabled the FTP features on the NAS and then installed FTP client applications on the MACS.
Now the Windows and Mac users are albe to authenticate against the Active Directory!

There are just a few minor inconvienences when using this method on a MAC, such as not being able to open a file directly from within an application (perhaps some can recomment a client app that would fix this); and, you need to copy or move the files back and forth.