Mapped Drive asking for Password

[eric.s]

I'm glad that it works out for you.

There is something I want to add as a side note to those who wants to use this script and want to have the script run when windows start up. I am sure most people in this forum already knew how to do this. But according to my experience, it's not a bad idea to spell it out.

Anyway, if you want to have this script run when windows start up, the easiest way is to just drag and drop the script file into Start --> All Programs --> Start Up. Then it will create a short cut to the script file in the start up and it will call this script to run whenever windows start up.

Have fun everybody

[HarryPotter]

Now its perfect, thank you

OK, "nearly" perfect

Now as I rebootet my PC, the mapped shares are gone. I know there is the possibility of adding your script to the autostart folder.

But shouldnt there also be an option on your script to keep the mappings as windows does?

[eric.s]

You can add a script to create a link that is connected to the actual .vbs file in the start up folder. In other word, the script will basically put the network drive mapping script to the start up item.

Add the following just above "Message Box":

' Create shurtcut
Dim objWSHShell, objSC, tarGetPath
set objWSHShell = CreateObject ("WScript.Shell")

' Create a shot cut in the start menu folder. You need to type in the entire directory where the start up folder is located and then add 'YourscriptFileName.lnk"
' In this example, I will assume "connect_drives.vbs" as the file name
set objSC = objWSHShell.CreateShortCut("C:\Document and Settings\YourName\Start Menu\Programs\Startup\connect_drives.lnk")

' Then give the link to call the actual file. Of course, you need to give the actual path to the script file location
objSC.tarGetPath = "C:\Documents and Settings\YourName\Desktop\connect_drives.vbs"

' Then save the link
objSC.Save

If you want to be sure, check your start up items and see if you can find the newly created link. Since this is the same as dragging and dropping the ".vbs" file to the start up folder, it will connect to the network drive automatically at every windows starts up.

You can make even more fancy scripts if you want. But this is all the time I will spend on this script and it's time for me to enjoy the sun while I can.

[vernavideo]

Greetings to all,

Since quite a few users reported problems with DS asking the password for mapped drives, I would like to share my experience and how I got round this problem with my brand new DS 107+

As stated elsewhere, if you have an xp log-in and create a user on the ds with the same name and password, XP can reconnet all shares without asking for the password each time you boot the xp machine.
What I found out, however, is that even if you do not have an XP log-in (ie. you do not see a log-in screen when you boot your PC or you do not need to type a password) you can still access the shares without being prompted for a password (and without using a script).

all you have to do is find out your user name (as explained elsewhere, in xp, click start, run and type 'cmd'; in the terminal window type set and hit return; the user name is what is displayed after USER:)

In the DS create a user with the same username, leave the password field blank and assign permission on the shares, and voila', no more annoyng password to type when accessing a share...

In addition, if you set the DS to join a workgroup and you did not assigned a fix IP for the workstation, I recomend to not use the Synology Assistant to map shares.
Thi becase the Assistant uses the IP address and not the workgroup machine name.
What this mean, is that if you turn off and on again the DS, chances are that your DCHP server (usually the router) will not give the DS the same ip, therefore you will have to map the share again.
to map a share within a worgroup, simply open xp explorer and locate the shares browsing the 'My Network Places'/Workgroup/your DS name.

Being very unexperienced, I hope I did not say something silly, expecially security wise. If I did, please do not hesitate to correct me.

Regards,
Stefano

[bouncemeister]

In the DS create a user with the same username, leave the password field blank and assign permission on the shares, and voila', no more annoyng password to type when accessing a share...

And also "voila" free access to your DS for everybody!
I really don't recommend leaving the password blank.

[vernavideo]

Hi bouncemeister,

And also "voila" free access to your DS for everybody!

True, everybody inside the LAN can switch on a PC and get access to the shares in the DS for which the admin has granted access to, which is what people without an XP log in are after anyway.

And you can still have shares for which you will have to provide log-in credential.
In any case you do need to log in for admin rights on the DS itself.

If people are concerned about security, they should have set up their OS to prompt for a user and password in first place. Setting up users without a password in the DS for the shares they are going to use for themselves doesn't make things any worse.

Ciao,
Stefano

[Broosha]

.

[Hector]

I just set up a new DS108j and had a similar experience --- Windows was sending a message that not all my network drives would connect, and when I clicked on my "public" folder it asked for a password. I don't have a Windows logon password as I am usually the only user unless my wife decides to not use her PC. So, all I did was delete the "admin" user in the box, leave the password line blank and click "enter". That took me right into an OK status and ever since, my network folders appear when I boot up, no problem. Maybe this will solve your problem.

[Dex]

Maybe this question is answered elsewhere already, but some laptops are equipped with a fingerprint protection.

Will this act the same as typing in the password (ie: they are somehow related or so) and will grant me acces to all the shared maps, or is it a MUST to use the password box in order to get things working ok?

Old post but.... The fingerprint protection only replace the password input so act as same as typing password, as soon as XP is launched and you have used the fingerprint it is working exactly in the same way.
For user which don't have XP password, my case btw, please note that if you enable FileStation and allow an internet access to your Syno, users from the web will be able to log in without entering any password !, they just have to find your username...
For FTP the password is mandatory so it is not an issue, you won't be able to use a "no password" user for FTP.

I've seen that we'll be able to allow FileStation access by user in the next release. This will solve the issue assuming that the correct setup is done (no access to FileStation for user with no pwd).

Waiting for it, I've not allowed internet access to FileStation on my router leaving only the FTP open.

[chdig]

Hi,

I've got the problem of mapped drives unable to connect to my DS207+ upon reboot of Vista.

The problem is that I have a share that I'd like to give access to individuals who enter the office with their laptops on a recurring basis. For privacy reasons, I cannot ask them to give me their laptop master login and password, so I create a new account on the DS207, and give that account access to the share. Next, I give the username/password to the individual, who uses it with the Synology assistant to set up the drive share.

No problems to this point. These people can connect, access the new drive share on their computers. Problem is that when they reboot/come in another day, the share appears in their Window's explorer as connected, but with the 'x' saying it's unaccessible. This user must disconnect, open up the synology assistant, and re-enter all the user/pass info every time they want to access the share.

One more point: if I give access to two or more drive shares to this user, only one of those shares will be unaccessible after reboot, while the others connect without problems using their synology-specific user/pass(!). Still, to use the one that doesn't connect, all must be disconnected and reconnected in order that they all become usable again.

--

My question: Given that I can add a share to a machine using a user/pass that is not its Windows login, why can it not reconnect properly? The general "solution" does not work at all, as I do not have access to the client machine's master login/password. Since when more than one share is present, all but one will reconnect without problems, this seems to be a fine-tuning issue, either on Synology (much, much preferred -- it's difficult to get users to implement VB/bat scripts on their own), or on Windows.

Thanks for your help

[pilotm]

Yes, chdig, this same problem is driving me crazy. I have followed all the FAQs, suggestions to align usernames, flushed credentials, tried 3rd party utilities, and yet after 10+ configs and reboots I don't feel I am any closer to solving this.

Like you I am using Vista (64). I haven't found a log that explicitly provides an error message that drives the system tray message "could not reconnect network drives on login" - perhaps this might help.

Suggestions?

[CronoS]

I am an owner of the DS-106E for 3 years now... I also had this problem with my Vista computer, I only did the following things:

1. Make a Net use (A windows command to create mapped network drives connections) connection with the /persistent option. But don't connect by the Devicename, but with the IP Adress of the NAS device. Change the mapped connection name in Windows explorer with a friendly name in stead of the ugly IP Adress. Now communication is done by IP Adress and DNS/Netbios translation is not necessary. I did this step, because Windows didn't wan't to connect right a way to the share when the computer is just booted. For Example, When I start Winamp after booting the computer, to play a MP3 on the NAS Share, then Windows didn't want to find that file. First thing I needed to do then, was to go to Windows explorer to click on the NAS device share. I believe that this had something to do with DNS or Netbios translation and the combination with applications. When seting up the Mapped network drives with an IP Adress in stead of names, you don't have this problem..

2. I made sure that my windows Logon name is the same as on the NAS device.. If this is the same and the net use is set with the /persistent option, then you don't have the problem that the system is asking you for a password...... When these accounts are different and you make a mapped network connection to you're NAS, then after reboot it will ask you again for the password, because the accounts are different.. If this is exactly the same, you don't have a problem. So I have used this method on several different user accounts, all are working fine..

Good luck

[XplosiV]

Im not sure if this will help anyone, but this is how i have managed to get my drives to map properly.

First, let me lay down some facts/specs,

Laptop, vista 32bit. Admin account / User account - different names/passwords.
DS409+ totally different login name/password to windows accounts - DynDNS mapped. RAID 5.
Mapped to five shared folders on the DS409+ volume


I tried the synology assistant utility to map the drives, but I got the "unable to reconnect mapped drives" balloon on startup.
So, i goto "computer" see the unmapped drives, open one, get password login (with no options to save password) Enter DS login and done, can view that folder. However, I can now view all folders (the remaining 4) so once each folder has been opened once they show up properly in "computer" (without the big red X)

So, this wasn't quite what I wanted. My solution was the following.

Deleting all mapped folders pointing to the DS409+.

Going to "computer"

Clicking "Map Network Drives" You get this.


Choose your drive, as per normal, upon clicking the browse button to locate your DS, you will need to enter your login creds for your DS, make sure "reconnect at logon" is ticked. Then click on "connect using different username" Here enter the DS login creds that you want to use to connect to the DS with. (can be admin or user or any other group as long as the account is held on the DS)

click "finish" and your done, continue to map as many drives as you need.

[jsklone]

Hello everyone,

try to add this in your registry then windows will keep the passwords, this is due to a functionality which is only activated on corporate networks ( Active Directory and so on... ).

Code: Select all

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System]
"LocalAccountTokenFilterPolicy"=dword:00000001
"EnableLinkedConnections"=dword:00000001


Cheers,

John

[bidibulo]

a bit late to give an answer, but i've been fighting with this issue many times and noticed that it happened when you had changed the username on the client computer.

example : you buy a new laptop, boot it, choose "john" as a username during setup
6 months later, you buy a NAS and setup a "johndoe" account on the NAS. So you rename the windows user to match this setting, but it won't help : windows displays "johndoe" when you log in locally, but keeps using the first username "john" when trying to access a shared folder.

I've tried many tricks to change this username and found some workarounds :

- try to rename the user "john" by the userpasswords2 panel : start / run / control userpasswords2 (works on some PCs)
- use the "connect a shared folder" from the explorer and use the "login as a different user" option (maybe this could differ a bit as my Vista is in French)
- use a batch file, but as sais above, passwords are left in clear text, which should be avoided.