Re: Windows 2003 File Server Access
- From: Bryce Alan Katz <morganesumon@xxxxxxxxx>
- Date: Fri, 07 Apr 2006 12:28:48 -0400
bdexter@xxxxxxxxx wrote:
Thanks for your post. I couldn't get to the second link even when IDirect link to Access Based Enumeration whitepaper:
combined both lines. I know how to connect to a Windows share but what
I'm not sure about is how to set up the permissions to accomplish in
Windows, the same look I have in Netware. From what I can tell, in
order for someone to see a complete path from the shared "parent
folder" to the folder I actually want them to have full rights to, a
few levels down, I will have to give them read rights to every folder
in between and make sure inherited rights is turn off, which sounds
like a lot of work. It seems like a possible security risk though, to
let Everyone have read rights from the top level down, which would let
them view every folder as well as see files they can't. Even if they
can't open the file, they would still be able to read the name.
Please let me know if I am still not being clear.
Thanks,
Brian
http://www.microsoft.com/windowsserver2003/techinfo/overview/abe.mspx
I've not taken the time to read it. However, what you're describing has been an issue with Novel to Windows migrations for years. Historically I've dealt with it by reconfiguring the shared folder structure and connecting drive letters as necessary using various tools.
.
- Follow-Ups:
- Re: Windows 2003 File Server Access
- From: bdexter
- Re: Windows 2003 File Server Access
- References:
- Windows 2003 File Server Access
- From: bdexter
- Re: Windows 2003 File Server Access
- From: Doug Sherman [MVP]
- Re: Windows 2003 File Server Access
- From: bdexter
- Windows 2003 File Server Access
- Prev by Date: Domain Issues
- Next by Date: Re: Chaning name of Administrator user
- Previous by thread: Re: Windows 2003 File Server Access
- Next by thread: Re: Windows 2003 File Server Access
- Index(es):
Relevant Pages
|