D-Link Forums
The Graveyard - Products No Longer Supported => D-Link Storage => DNS-321 => Topic started by: Schlup on September 05, 2009, 02:34:21 AM
-
So my DNS-321 won't reconnect to the mapped network drive after I reboot my computer. I have tried setting it up with Easy Seach, I have also manually mapped the drive in Windows. They both work and I get full access, until I reboot my machine, then the connection is gone again. I see the drive listed with a big red "X" over it. If I double click on that icon like I normally would to access the drive I get the following message...
"An error occurred while reconnecting X: to
\\NAS\Volume_1
Microsoft Windows Network: The account is not authorized to log in from this station
This connection has not been restored."
I have google searched the issue, I have looked through these forums and haven't found a fix yet.
Info:
D-Link DNS-321 with (2) 1TB Seagate drives in it running RAID 0 stripe.
Computer is operating on Windows 7 x64 and connected with a SMC Modem/Router with built in wifi. This used to work correctly on my current setup and would automatically reconnect upon reboot but it hasn't worked for a month or so now. I am at a loss for what to try next. Let me know and I'll post back here quickly.
Thanks in advance!
-
Sounds like a password issue. If you're running Windows 7 Business, Ultimate, or Enterprise, you can do the following.
Hold the Windows key and hit R.
Type control userpasswords2
Select the advanced tab.
You can remove and or add credentials there and correct any bad password or missing password.
-
Yeah, I originally did go in there to disable the sign on screen when I boot my computer up. However, when I noticed that the NAS didn't work anymore I reenabled the sign on screen. I have also checked all the credentials and everything is in there. I also factory reset the DNS-321 and still no help. Any other ideas?
-
I'm not suggesting you disable the login screen, though that won't change the network behavior. However, I'm talking about the Advanced tab on that control and the password management for remote connections.
-
Yeah I get what you're talking about. I'm just talking about what I did previous to all of this which may have caused the initial problem. But yeah, I went there, as I have before and have entered in "Generic Credentials" and they were already listed in there but I double checked by editing and making sure the password was correct.
In other news I manually mapped a new network drive by using the IP address of it and that seems to be working when I restart the computer or log off and log back in it autoreconnects but it only gives me folder access, not drive access so I still can't use it for it's intended purpose which is to do automatic backups using Windows Backup and Restore. Hope this gives you more info...
-
I don't use mapped drivers as a rule, I simply use network paths to access the drive, which works fine. I haven't tried mapping and rebooting, can't say if that would or wouldn't work.
Since Acronis True Image, Beyond Compare, and Cobian Backup all recognize network paths, I never had the need to map drives.
Does Windows backup really need a drive letter? I confess to having never used it.
-
Windows needs an attached storage option to save the backups to...so yes, it needs a drive letter. Besides that, if Windows doesn't see the drive, there is no network path. Besides that, I like to access the drive to put stuff on it and pull stuff off of it. I called tech support today and after a while got transferred to senior tech support and after a while they ran out of options and couldn't figure it out. Told me to call back tomorrow and speak with a product specialist.
My current goal is to be able to use the DLink Easy Search Utility to map the drive without it asking for the username and password. Which I have done for my father's unit but won't work for my unit. I have reset the unit, restored factory defaults, etc. and still it comes up asking for username and password when I go to map the drive. Anybody have any solutions to this?
-
The fact that it asks for a user name and password after a factory reset is odd, it should be in "open" mode at that point. That's how both my DNS-321 and DNS-323 operated before I assigned passwords and permissions.
From the network permissions page:Helpful Hints..
By default, each hard drive or volume will have an open-access rule. These rules must be deleted before user or group specific rules can be created. If you wish to grant access rights to additional users/groups at a later time, please press the "Modify Settings" button (in the Network Access List) in the row of the shared folder you wish to grant access to. Then you can assign access rights to other users/groups. Groups are shown in bold in the Network Access List section.
-
Yeah, it is wierd, I completely agree with you on this. It should be asking for a username and password but it is. Done resets from the back of the unit and factory resets from the configuration page galore but it still asks for a username and password, even though one doesn't exist.
-
Well, it's as strange as it can be. I have two Windows 7 x64 machines here, and they both worked when the DNS-323 had no passwords, and still work with the passwords. I have no problem recognizing them after a reboot. ???
Do you have any other machines that access that NAS? Do they have similar issues?
-
So let me ask you this. If you delete the users and groups and passwords, then delete the paths to the drive on your Windows 7 x64 machine and then restart your machine, map it, then restart your machine again...does it automatically connect to the drive again?
-
Well, I'm a bit lazy, and I'm not willing to do all that. :) I have a dozen users and paths, and I don't want to recreate all of them. I know it worked before I put all the security on, and I was running the 1.02 firmware at the time. It could be that the beta firmware has changed that, I never had the security wide open with the 1.03 beta.
-
I downgraded back to 1.02, I exhaused all tech support avenues and they want to RMA my unit. I'm not sure that is the fix, nor do I really want to pay for shipping just to get a refurb unit. It would be very appreciated if you could help me out here. Wouldn't take too long...
-
Could try this:
For the username put in "EVERYONE" and leave the password blank.
-
You can also use the default which is "dlink" with no password, but Windows still kicks it out upon reboot or log off & log back in. I just don't want to have to remap it every time!
-
Well you might try mapping the drive to a different drive letter.
Do you have the same problem if the drive is mapped to a different letter?
My main system reconnects just fine with both my DNS-321 NAS devices ( drive 'X' and 'Z' ).
Main system is Vista 64. My secondary system is running MCE2005 and no issues with losing drive mapping there as well. My wife's laptop is running Windows XP PRO and no issues with drive mapping there as well. Oh. my other laptop is running Windows Vista Home and it also has no issues with losing drive mappings.
But you said you have Windows 7 64BIT edition.
Well I just booted Windows 7 64BIT and I mapped both NAS devices. Next I rebooted.....
Never prompted for password and both drives are green. Access to the drives is fine as well.
I am not using any group settings and I am running with the latest beta firmware.
I have two 1.5TB Seagate drives on one of the NAS units and two 1TB WD Green drives in the other NAS.
If you right click on the drive and check Properties/Security what do you see?
Mine shows "Everyone, Root(Unix User\Root), Root(Unix Group\root)"
-
You're never going to believe it but I finally found a fix. Windows Live Essentials caused the problem. Uninstalling the "Windows Live ID Login Assistant" fixed the issue. You can find it in your programs list in the control panel.