disturbedone
Vendor
I don't believe this is a Windows issue but as it's on W2K8R2 AD I wanted to put it to others here to see if they've encountered this before.
The issues with OSX Lion & AD are well known ie the issue with .local domains. We have got a workaround and the Macs now join the domain and can logon.
We have AD accounts with a Home Folder set to \\c2cifs\filestore0\sharename\%username% which is a CIFS share on a NetApp FAS SAN. Permissions are set so users can only get access to their own folder. Prior to moving to CIFS the shares were on W2K3R2 and worked on Leopard. As a test I mapped the Home Folder back to the W2K3R2 server and I get the same thing so it's not an issue with the CIFS share on the SAN.
They also have mappings to \\c2cifs\filestore1\sharename
There are 2 issues:
1. The user cannot access their Home Folder and are presented with the error 'The folder "filestore0" cannot be accessed because you don't have permissions to see its contents'
2. The Home Folder and the other shares simply show "filestore0" or "filestore1" in Finder. They do not show "sharename". The other shares can be accessed fine but they just don't show the share name they show the root.
The naming issue must be a OSX issue. Maybe they'll fix it one day.
I found now allows access to the folder. However it still maps the Home Folder to \\c2cifs\filestore0\ and doesn't go to \\c2cifs\filestore0\folder1\userfolder where the AD Home Directory points it to. There's a ? in the Dock and hovering over it says 'Username's Network Home'
Any ideas on the subfolder permissions thing?
The issues with OSX Lion & AD are well known ie the issue with .local domains. We have got a workaround and the Macs now join the domain and can logon.
We have AD accounts with a Home Folder set to \\c2cifs\filestore0\sharename\%username% which is a CIFS share on a NetApp FAS SAN. Permissions are set so users can only get access to their own folder. Prior to moving to CIFS the shares were on W2K3R2 and worked on Leopard. As a test I mapped the Home Folder back to the W2K3R2 server and I get the same thing so it's not an issue with the CIFS share on the SAN.
They also have mappings to \\c2cifs\filestore1\sharename
There are 2 issues:
1. The user cannot access their Home Folder and are presented with the error 'The folder "filestore0" cannot be accessed because you don't have permissions to see its contents'
2. The Home Folder and the other shares simply show "filestore0" or "filestore1" in Finder. They do not show "sharename". The other shares can be accessed fine but they just don't show the share name they show the root.
The naming issue must be a OSX issue. Maybe they'll fix it one day.
I found now allows access to the folder. However it still maps the Home Folder to \\c2cifs\filestore0\ and doesn't go to \\c2cifs\filestore0\folder1\userfolder where the AD Home Directory points it to. There's a ? in the Dock and hovering over it says 'Username's Network Home'
Any ideas on the subfolder permissions thing?
