Posted on 2013-01-19
Last Modified: 2013-01-20
I have on a Qnap a shared volume, my active directory users on a Exchange server 2003,   now a user sees all subdirectories , how to set per user only specific directories to see and edit
Question by:BIAPRO
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
1 Comment
LVL 18

Accepted Solution

Andrej Pirman earned 500 total points
ID: 38796211
QNAP uses Samba user authentication on Linux (QNAP) system, so you must edit user by user separately on QNAP, and users will need to login separately into QNAP.

Another option is that you join QNAP to your local domain, so users from AD domain will be synced with users on QNAP Samba and you can then perform some limiting actions on directories.

Probably the most elegant option is to use QNAP as iSCSI attached storage and attach it to your Exchange server. Create some iSCSI target on QNAP, then install iSCSI initiator to your Server 2003 (here: ) and connect it with QNAP created iSCSI target.
Doing so, Server 2003 will see iSCSI target dedicated space as unformated disk drive, so you format it with NTFS filesystem, set drive letter, and use it as normal disk drive, with all permissions and properties as existing filesystem on Exchange.

If you go with iSCSI, you will find it very usefull, but keep in mind:
- iSCSI target reserves space all at once, so if you set on QNAP that iSCSI target will have 500 GB of space, it gets reserver right now
- for added security, you may configure CHAP password on QNAP, and use the same password in Server's iSCSI initiator under ADVANCED settings before you connect to iSCSI target.
- iSCSI target and initiator communicate via TCP/IP, so both must be in the same IP subnet. I use simple trick to protect it a bit more. I configure additional IP address on Esxchange server, for example with subnet mask so only 2 IP addresses are available. Then I'd use:
- for iSCSI target (QNAP) IP address, subnet (/30)
- for iSCSI initiator (Server 2003) IP address, subnet
- do NOT put Gateway address, as it is not needed, nor DNS

Doing so, you will hide local IP of QNAP from LAN users.

Featured Post

Want Experts Exchange at your fingertips?

With Experts Exchange’s latest app release, you can now experience our most recent features, updates, and the same community interface while on-the-go. Download our latest app release at the Android or Apple stores today!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Many admins will agree: WSUS is is a nice invention but using it on the client side when updating a newly installed computer is still time consuming as you have to do several reboots and furthermore, the procedure of installing updates, rebooting an…
Learn about cloud computing and its benefits for small business owners.
Windows 8 comes with a dramatically different user interface known as Metro. Notably missing from the new interface is a Start button and Start Menu. Many users do not like it, much preferring the interface of earlier versions — Windows 7, Windows X…
With the advent of Windows 10, Microsoft is pushing a Get Windows 10 icon into the notification area (system tray) of qualifying computers. There are many reasons for wanting to remove this icon. This two-part Experts Exchange video Micro Tutorial s…
Suggested Courses

615 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question