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...
No need to be sorry, as you can see I have been busy and sphardy, ewok and others have been helping me out.
I looked into the batch file method while you were gone and didn't explore it much further. Call me stubborn but when mapping a drive (which should be an easy and straightforward process does not work, I want to know why. What makes me different than the millions of other windows users out there that I can't map a drive? Then I want to fix whatever it is that is preventing me from doing that. Working around the problem by creating a batch file wasn't the solution that I wanted to jump to right away. I do really appreciate your in depth explanation though.
After you left I started talking about UNC with sphardy which actually serves my purpose just as well. I am not even really sure what the main advantage/disadvantages using a mapped drive vs a UNC path are but they seem to serve the same purpose and work just fine for me. So I am using UNC now which is great.
One of the other problems I was having was with permissions which I finally had to resort to making my NAS users login/pass the same as my Windows logon/pass. This wasn't what I really wanted to do since my Windows logons don't have passwords but it works as a small security measure to prevent guest access I guess. I also had to copy all of my files from the first share I setup to a new share which seemed to fix any access problems I was also having.
The last problem was the access speed which was cause by a bug in the 4.1.7 firmware and I got the workaround from this thread viewtopic.php?f=21&t=48120
So in the end, I setup a new share, accessed with a UNC path (created a shortcut) and used the info in the linked thread to fix the speed issue. So far so good. :D
I looked into the batch file method while you were gone and didn't explore it much further. Call me stubborn but when mapping a drive (which should be an easy and straightforward process does not work, I want to know why. What makes me different than the millions of other windows users out there that I can't map a drive? Then I want to fix whatever it is that is preventing me from doing that. Working around the problem by creating a batch file wasn't the solution that I wanted to jump to right away. I do really appreciate your in depth explanation though.
After you left I started talking about UNC with sphardy which actually serves my purpose just as well. I am not even really sure what the main advantage/disadvantages using a mapped drive vs a UNC path are but they seem to serve the same purpose and work just fine for me. So I am using UNC now which is great.
One of the other problems I was having was with permissions which I finally had to resort to making my NAS users login/pass the same as my Windows logon/pass. This wasn't what I really wanted to do since my Windows logons don't have passwords but it works as a small security measure to prevent guest access I guess. I also had to copy all of my files from the first share I setup to a new share which seemed to fix any access problems I was also having.
The last problem was the access speed which was cause by a bug in the 4.1.7 firmware and I got the workaround from this thread viewtopic.php?f=21&t=48120
So in the end, I setup a new share, accessed with a UNC path (created a shortcut) and used the info in the linked thread to fix the speed issue. So far so good. :D
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
