NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Mapping A Share Fails to Connect At Startup
I am using Windows 7
I access my ReadyNAS Duo via Frontview
I created one user: user1
and one group: users
I have one share: files
The share has been set with the following permissions:
CIFS:
Default Access: Disabled
Write Enabled Users: user1
Enable Oplocks for this Share: Checked
All other options unchecked
Advanced Options:
Share folder owner: user1
Share folder group: users
All rights: read/write
Grant rename and delete privileges to non-owner of files: checked
All other options: unchecked
I have done a one time reset of the owner and group by checking "Set ownership and permission...." on the Advanced tab and applying so all files and folders are owned by user1.
Now for the problem. When I try to map the drive on my windows 7 computer so that it connects at startup it fails each time I reboot. To map the drive I click "Computer" in the start menu and choose "Map network drive" from the bar at the top of the window. I choose the Z: and browse for the folder I want to map. As soon as I click on the NAS I am prompted to Enter "Network Password". I assume I am supposed to enter the username and password for the share that I created and to check "Remember my credentials". The only unchangeable choice that seems out of place is that the "Domain: RAVEN" is chosen. RAVEN is the name of my computer but not the name of the domain that I setup on my network. Regardless of that anomaly I input my username and password and I connect to the NAS and choose the share to map.
Now I am back at the Map Network drive window and I have selected "Reconnect at logon". There is also a checkbox for "Connect using different credentials". I am not sure if I should check this box or not??? If I do check it and press finish I am prompted to enter a network password. I can either use my existing user that I created in Windows 7 or I have the choice to use another account. At this point I am thoroughly confused and not sure which to choose or if I even needed to connect using different credentials at all. Needless to say my connection fails upon restart, though it seems to connect fine when I complete the drive mapping as I can access the share without any problem.
If someone could clear up the correct way for me to connect I would really appreciate it.
Thanks
I access my ReadyNAS Duo via Frontview
I created one user: user1
and one group: users
I have one share: files
The share has been set with the following permissions:
CIFS:
Default Access: Disabled
Write Enabled Users: user1
Enable Oplocks for this Share: Checked
All other options unchecked
Advanced Options:
Share folder owner: user1
Share folder group: users
All rights: read/write
Grant rename and delete privileges to non-owner of files: checked
All other options: unchecked
I have done a one time reset of the owner and group by checking "Set ownership and permission...." on the Advanced tab and applying so all files and folders are owned by user1.
Now for the problem. When I try to map the drive on my windows 7 computer so that it connects at startup it fails each time I reboot. To map the drive I click "Computer" in the start menu and choose "Map network drive" from the bar at the top of the window. I choose the Z: and browse for the folder I want to map. As soon as I click on the NAS I am prompted to Enter "Network Password". I assume I am supposed to enter the username and password for the share that I created and to check "Remember my credentials". The only unchangeable choice that seems out of place is that the "Domain: RAVEN" is chosen. RAVEN is the name of my computer but not the name of the domain that I setup on my network. Regardless of that anomaly I input my username and password and I connect to the NAS and choose the share to map.
Now I am back at the Map Network drive window and I have selected "Reconnect at logon". There is also a checkbox for "Connect using different credentials". I am not sure if I should check this box or not??? If I do check it and press finish I am prompted to enter a network password. I can either use my existing user that I created in Windows 7 or I have the choice to use another account. At this point I am thoroughly confused and not sure which to choose or if I even needed to connect using different credentials at all. Needless to say my connection fails upon restart, though it seems to connect fine when I complete the drive mapping as I can access the share without any problem.
If someone could clear up the correct way for me to connect I would really appreciate it.
Thanks
30 Replies
Replies have been turned off for this discussion
- Hmm.
The option to connect using different credentials is because by default, it will connect with your Windows logon details. So yes, you should do that when you first set up a mapped drive. The way I do it is to check both of those boxes before even browsing for the folder I want to map. Once I enter my Nas Admin creds (I use absolute paths ie: \\192.168.1.x\home\<user>\folder1) it immediately opens this new resource/drive in a new window. (I guess to confirm that's what I wanted)
I have no problems with reconnecting at logon.
Have you tried the command line batch (manual) reconnect at logon approach? (found in the wiki under "shares") - Hi Panda,
Thanks for the response. Could you please review my steps and tell me what I am doing wrong?
1. Choose Map network drive and check both checkboxes for "Reconnect at logon" and "connect using different credentials".
2. press the browse button and choose my NAS drive.
3. I am prompted for my login/pass. I enter my NAS admin login/pass (the same one I use for Frontview) and not my Username that I have setup to access the share.
4. instead of choosing the share named "files" I browse through the c folder to the folder named "files" and press ok giving me a path of \\NAS-01-F0-3F\c\files
5. Press Finish at which point I am presented with another window asking for a network password and giving me the choices to connect as RAVEN\admin (and enter a password) or to "Use another account".
6. I choose "use another account" and enter in the username I have setup as a user on my NAS with access to the share files, named "user1" and input user1's password and check the box "Remember my credentials" and press OK.
I tried these steps and I get an error saying I am already mapping the drive as another user and cannot choose to map it as user1. I assume this is because I initially used the login/pass of my admin account during the steps above. Should I use the admin login/pass (the same one I use for Frontview) for both steps 3 and 6? If I do that will the files that I create be set to the owner "admin" or the owner "user1"?
Thanks - Well, sometimes Win7 just wants a confirmation of your logon. Use the same Nas root admin account info. You might want to hold off on checking the "remember login" box until you know it's working for sure.
Another reason could be that your actual windows logon has no password assigned to it currently.
For me, my Win7 doesn't even show my Nas in the list. (something to do with a network discovery problem) So, I have to type it in manually. And I don't use any masks. I am using the IP address. So, I type in \\192.168.1.2\c\<user> and go from there. Of course, my router has assigned the ip subnet to *.*.*.2 and that is what I am using.
If you can't make it work from the GUI, try the DOS approach. Get to a command shell and type the following:
net use $resource \\$host\$sharename /persistent:no
$resource = desired mapped drive letter, with a colon [F:]
$host = your nas name or IP {READYNAS | 192.168.1.# }
$sharename = path to folder you wish to map {folder | home\folder}
On my computer, since I already have a Nas-Root access mapped, I didn't need to enter a password or user.
ie: NET USE m: \\readynas\Mom /persistent:no
Once you can get this to work from the command line, then you can include this command in a batch file that you can set up to run every time you boot your machine.
NOTE: Extensive help on the "net use" command can be found at microsoft. - So here is the wrinkle to what you have been suggesting.
I have two computers for me and my wife. Both of them use a different Windows 7 username and no password and both need access to the files on the NAS using the same NAS user account that I created (user1). I used to have the NAS setup with open access and it worked fine. However I do not want anyone clever enough to hack into my wifi to be able to access my NAS so I needed to add the layer of security by making the share password protected and adding a NAS user (user1) with access to the NAS shares.
That may help you better understand what I am trying to accomplish as far as the goal.
Before your reply I read all about net use and tried it with the same result. My command line looked like this "net use z: \\NAS-01-F0-3F\files /user:user1 MY_PASSWORD_WAS_HERE"
I then added the command "NET USE /Persistent:Yes" to set it to reconnect at startup
The drive mapped fine and I was able to open it up and see all the files, create files with the correct ownership rights, everything is perfect except when I restart it fails to reconnect.
Any new suggestions? Thanks for sticking with me. - Try
net use z: \\nas_name\share /user:username password /persistent:yes /savecred
- I will give it a shot sphardy! Crossing my fingers....
- Couple of notes regarding this attempt.
This code gives a switch error.
net use z: \\nas_name\share /user:username password /persistent:yes /savecred
I had to use this:
net use z: \\nas_name\share /persistent:yes /savecred
and then it prompts me for the user and password
The share is then mapped per the norm and I can access it. Upon restart I still get the "Failed to reconnect error", but if I click on the mapped share it "thinks" for a few seconds and then opens the drive as if it has no problem connecting. If I look in the Credential Manager the credentials are saved under the Windows Credentials area.
So basically what this is telling me is that Windows remembers my credentials but it doesn't use them when the computer reboots only when I double click on the share manually....???
Pulling out my hair. - Try using the ip address instead of NAS name - maybe there's some name resolution issue preventing the initial connection
- I was just able to experiment a little with my Win 7 Ultimate installation - and got that old familiar feeling of windows-induced-frustration.
When mapping the share to a drive letter via the "net use" command, my symptoms are identical to those of @sulu. On every reboot the share was remembered due to the /persistent option, but failed to mount fully giving the familiar "failed to connect" error, but I click on the mapped drive the share opens without issue. One small difference however, no amount of playing with the /savecred option would get my credentials into the Credential Manager
I then completely deleted the drive mapping and recreated it via the Windows GUI (Open "Computer" in Explorer and select the "map network drive" option from the top of the window). Credentials were immediately saved and visible in credential manager. And so far, after 3 reboots, the drive is mapped without issue.
I have no explanation, and 3 reboots is hardly a definitive test but something is definitely wrong when using the "net" command
Afraid that's my weekly struggle-with-windows limit far exceeded - sphardy, I tried your suggestions and it still fails to reconnect for me. I tried using a windows xp computer to map the drive and I get the same problems. Maps fine, but fails to reconnect upon reboot.
I am so frustrated. I need to work off of my NAS and I have been trying to get this resolved for 2 weeks plus now. It is seriously a thorn in my side. Should I remove all security from the NAS and try to map the drive without any user/pass and see if it can connect on reboot? I am running out of options. Maybe I can't have a secure NAS device and just need to leave it open to the world...
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
