Print

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

[garyhgaryh]

I've been having permissions issues with my DNS-321 box since I got it.  First thing I did when I got the box was to upgrade to 1.01 (need it to support 1.5T drives - works great).  I have two seagate 1.5T drives in a raid 1 configuration.  Once I assign permission to my "volume_1" volume, I can no longer access that volume on my xp laptop so I have to do a factory reset and keep it open to "ALL".

I happen to be playing with the dns-321 on my vista box playing with permissions again.  To my surprise, I can see the dns-321's "volume_1" by typing in the credentials for any user I created on the dns-321.  Remember, I could not get this to work on xp.  Everything works fine in vista! I used a program that required access to the shared drives and it asked me for credentials.  I entered invalid ones and as expected, I couldn't get in.  I entered a valid user, but wrong password, and as expected, I couldn't get in.  I then entered correct credentials for all two of my defined users (that i defined in the dns-321 web interface) and I was able to get in.

I tried the same procedure on the xp laptop and I just can not get it to work.

My thoughts are:  my vista machine is under WORKGROUP and my xp laptop is under my work domain.  However, when I provide credentials, It shouldn't matter because I explicitly am using the same ones by specifying the domain.  Then I realize no matter what I typed on the vista machine for the domain, I can always get in as long as the username and password is correct... so, this works on the vista machine:
user: gary
pass: mypassword

user: inspiron530/gary
pass: mypassword

and surprisingly
user: blah/gary
pass: mypassword

blah is not valid.

None of these work on my xp laptop.  The behavior I want is that of the vista machine.
Can anyone shed some insight on this? The permissions work wonderfully on the vista
machine and not on the XP machine.  XP has service pack 2 installed.  Perhaps I need to
update something? Vista is the home edition (32 bit) with _I think_ service pack 1.

Gary

[jumboframe]

Gary,

I'm using a mixture of OS scenarios for testing the DNS-321, none so far have been with Vista (no computers around with Vista installed).  I've been using Ubuntu 8.10, Windows XP SP3 and Windows Server 2003 SP2.  I'm curious if what you are experiencing has anything to do with this feature:

http://www.microsoft.com/whdc/connect/rally/pnpx-spec.mspx

It may provide an answer as to why Vista behaves in a certain way where as XP does not.

[ECF]

The DNS-321 does not work in a domain network environment.

[garyhgaryh]

Gary,

I'm using a mixture of OS scenarios for testing the DNS-321, none so far have been with Vista (no computers around with Vista installed).  I've been using Ubuntu 8.10, Windows XP SP3 and Windows Server 2003 SP2.  I'm curious if what you are experiencing has anything to do with this feature:

http://www.microsoft.com/whdc/connect/rally/pnpx-spec.mspx

It may provide an answer as to why Vista behaves in a certain way where as XP does not.

Thanks.  I quickly scanned that site but I can't find anything that would help me out.  Perhaps I'm looking in the wrong place.
In anycase, the dns-321 works as expected on my vista box.  I only have one vista machine and the rest of my dozen or so computers are running xp.

Gary

[garyhgaryh]

The DNS-321 does not work in a domain network environment.

What does this mean exactly? If I am outside the workgroup domain, it just won't work? Or do you mean it won't recognize user@domain credentials?

I guess this would explain why the domain part of the component doesn't matter in vista, but what I don't get is why I cannot access the dns-321 on my XP box.  The account I am logged into the xp machine has a password that is 11 characters.  From what I understand, this password must match that of the account password set up on the dns-321.  Is that correct? On vista it doesn't seem to matter.

Thanks for your reply - I appreciate it.
Gary

[jumboframe]

The DNS-331 is still functional in a domain environment even though it does not support domains per se.  I use it in a domain environment where it can be seen by other workstation and can be mapped as a network drive. 

[garyhgaryh]

The DNS-331 is still functional in a domain environment even though it does not support domains per se.  I use it in a domain environment where it can be seen by other workstation and can be mapped as a network drive. 

That's what I thought, but I believe I might be misunderstanding what he's saying when he says "it doesn't work in domain environments".  ECF: Can you clarify?

Thanks,
Gary

[jumboframe]

Yes, please clarify.

[garyhgaryh]

Ah I figured out what the problem is thanks to someone from another forum.  There is a bug in the xp credential routine that will not let you log into the dlink NAS when prompted by XP when you click on a shared or try to go there using \\shared (or whatever you name it).  You have to map the drive and also make sure it's mappable (there is a map setting on the dns-321 UI).

[jumboframe]

You mean addressing the unit by \\192.168.0.32\TEST or \\DNS-321\PRIVATE, etc.  I didn't know that you were addressing the unit by \\TEST or \\PRIVATE.  That makes sense.  Good that we got that clarified.

[garyhgaryh]

Yeah that's exactly how I was accessing it.  I'm not sure why more people haven't ran into this problem as I thought it was common to acccess the shares like this.  But it does seem to work correctly on my Maxtor shared storage II NAS that I have on my xp box so I'm not sure if it's 100% just an XP problem but I'm a happpy camper now.

I'm copying 320GB worth of stuff from my maxtor NASs to my DNS-321.  I hope this is the last issue I have with this 321 box .  I haven't shut down the dns-321 yet and I heard there are problems there and I plan on relocating this NAS in a few days... Keep ya posted if I run into anymore issues.

Gary