D-Link Forums

The Graveyard - Products No Longer Supported => D-Link Storage => DNS-323 => Topic started by: jkdham on January 26, 2009, 04:27:04 PM

Title: unable to map drives
Post by: jkdham on January 26, 2009, 04:27:04 PM
We just bought the dns, and put in 2 1tb seagate ST31000333AS
 
I am trying to map the drives, but it keeps telling me that it failed.  I have called the dlink tech support line, and neither of the two techs could help me.  I am waiting for a product specialist to call.

can anyone help?
Title: Re: unable to map drives
Post by: ttmcmurry on January 26, 2009, 06:07:25 PM
What OS are you running?  Do you have any security products installed (e.g. Norton, Trend, McAfee..)?
Title: Re: unable to map drives
Post by: jkdham on January 26, 2009, 06:16:01 PM
Panda Security is turned off, so is windows firewall.  Out of our 4 computers (2 xp and 2 vista), I have only had success with the 2 xp machines.  We think that there is something in Vista that is blocking it.  It has asked to install drivers, but cannot find the appropriate drivers either from the disk or online.

what on vista could be interfering with mapping the drives?   

Thanks
Title: Re: unable to map drives
Post by: ttmcmurry on January 26, 2009, 08:01:23 PM
The drivers are the PNP-X drivers from the Support Page.  They aren't necessary for the 323 to work properly.  Have you tried to set up a user for yourself on the 323? 

I had some early trouble with Vista (and to a greater extent with Windows Seven) and the 323 with mapping drives.   What I did was create an administrators group and a user & password for myself and adding myself to the administrators group.  Then I went to Network Access and modified the share and replaced the ALL group with the administrators group.  Going back to Computer, I was able to map a drive with the username and password I created on the 323.  This solution worked on Vista, Seven, and XP for me.

The problem I had was with Vista and Seven not accepting a blank user & password.  Windows was requiring a username and a password - nothing worked if either was blank.  XP never had that issue for me, guest/anonymous access worked perfectly.