Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello NetApp experts
Our mutual customer has a NetApp FAS3050 NAS filer
They set the root shares (CIFS) with the following NTFS permissions
Everyone - List Folder/Read Data
and then set explicit permissions on folders below there
(this is their corporate standard)
This works fine for XP and Server 2003 clients -- they can browse the folder and access sub folders (sub folders that they have rights to)
But is not working with Vista clients
Vista Explorer gets access denied on the root share
But Vista cmd prompt can read the root share ok !
Anyone come accross this before ?
Setting Traverse Folder permissions on the root share reportedly overcomes the issue
(even though the users should already have the bypass traverse checking right
Thanks for any thoughts
6 REPLIES 6
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
What version of OnTap is being used?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
OnTap version is NetApp Release 7.2.6.1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The OnTap version is fine, interesting that the CMD prompt can gain access with no probs. If I get chance I'll try and re-produce on our kit but we're running OnTap 7.3.1 so this might be misleading...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks, if you have a chance to try Vista Exploerer and cmd prompt against any OnTap version, that would be much appreciated.
Not sure what the recommended root share permissions are, and how it compares to
Everyone - Special - List Folder/Read Data
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The end customer (our mutual customer) has heard from NetApp and they have confirmed it is a NetApp 'issue' in this particular way it is all configured and have recommended some work around
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
