Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Der Alte]

I have my DNS320 set up in two volumes, the first volume is RAID1, the second is JBOD.  The first volume is intended to be private and the second to share files with the outside world.

Windows 7 does not react well with different permissions for each volume.  It only seems to comprehend one log in for the machine that can access everything.  When I try to identify a different user, it restricts me to just one user ID and locks me out of whatever that user name cannot access. 

I can only get complete access when I set the shares to wide open.  Anytime I create a user, things start to go wrong.  Windows 7 does not seem to comprehend that I can log in as admin and control everything, then log on as another user to test whether I got the access, etc... set up correctly.  What I input in Windows 7 (in terms of user and password) does not seem to correlate properly with the DNS 320.

The DNS320 works great until you get into different users and permissions and then try to access with Windows 7.  There is precious little compatibility except when everything is wide open.

Does anyone have any work arounds?  The ability to open up part of the NAS to the internet is rather pointless if I can secure part of it.  I realize that this may very well be a Windows rather than a D-Link problem....but I just want an answer and I could die a thousand deaths trolling Windows support forums for the answer and am hoping for some answers here.

FYI, I've cleared out Credential Manager to no avail.  The problem seems isolated to whenever I set up different users with restricted access on the NAS.

[colinkhalid]

Does this post help ?

http://forum.dsmg600.info/viewtopic.php?id=6593

[Der Alte]

It did not answer the question head on, but it left me a bread crumb where I eventually figured out what was going wrong.

The trick is that the "wide open" setting on the DNS 320 where any user on the network can read/write is only valid so long as there are no Users designated.  Once a single user goes in, everyone (at least in the Windows world), has to log in as that user.

If you are creating a restrictive user, then you must create another account (besides admin or administrator) that has global read/write permissions.  Log in as that new user who has permissions to everything on on the DNS and you are fine. 

If you are going to set up Users, the Admin account on the DNS 320 is really only good for administering accounts.  You need to set up a separate user for Windows that can read/write to everything.  Once you have that you can set up more restrictive users to limit access.

This may be elementary to some, but for somebody like me with only basic computer training who learns most things through trial and error, it was a revelation.    Thanks for the pointer.