NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
sudden permissions problem - You need permission to perform this action
I have samba (SMB) share called "pictures" which I map to my Windows 7 machine as drive Y:. I used Windows Explorer to move some pictures to my Y: drive today (as I've done hundreds of times before) ...
If you haven't set up a Windows credential for the NAS (either via the Windows Credential manager, or by entering the user/password for the NAS when you access the share), then Windows will automatically use your windows username and password when it connects to the NAS.
Also, you can change file attributes from windows by right-clicking on the files or folders from file explorer.
Overall, Microsoft has made some changes to they way they handle guest access - and they might be getting your way.
What I recommend is setting up a user account on the NAS. You could call it ken, and match the password to your Windows password. Or you could use the NAS admin account if you want to map the entire data volume instead of a share.
Then you can reset the file permissions on the NAS using the settings wheel for the share. Maybe also change the share owner/group to match the NAS user account you are using.
I actually have a "Home Folder" for my "ken" user on the NAS. Additionally, I have several "guest shares" called "music, pictures, and videos" (The ReadyNAS sets these up by default). I am attaching to the NAS from Windows 7 Ultimate. I mapped my Z: drive to my "ken" folder (//10.0.0.11/ken; which is /home/ken on the NAS ). I mapped my Y: drive to my "pictures" share (//10.0.0.11/pictures; which is /data/pictures on the NAS). I log into Windows as "ken" (no password). I am pretty sure that the order in which I logged into the shares didn't matter (it does now, per below). I can't put my finger on anything that has changed in years. I would boot up my Windows box and log into my Z: drive and it would ask for my credentials and I would type in the NAS username/password for my "ken" home folder and then I would have access to it until rebooting my Windows box. After this I could click on the Y: drive and it would not NOT ask for any credentials; it would simply give me guest access. Files I saved to Z: have a username.group of ken.users and files I saved on Y: have a username.group of guest.guest.
NOW what I'm finding is that if I log into the Z: drive first I get access to the Z drive (ken.users) and I have access to Y:. However, the Y: share now sees me as "ken.users" rather than "guest.guest" and I am unable to write to anything but the root directory in Y:. If I log into the Y: drive before logging into the Z: drive I am able to write to the Y: drive as guest.guest, just like before, but when I then try to access the Z: drive and I am prompted for my username and password, it refuses to let me log in as ken. Instead I get the following error, ""\\10.0.0.11\ken Microsoft Windows Network: Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed. Disconnect all previous connections to th eserver or shared resource and try again."
So, it does seem SOMETHING has changed with the way Windows is passing credentials to the NAS. I'd still like to access my home directory using my username and password and I'd like access to my several shared directories as guest.guest. However, Windows doesn't seem to like maintaining multiple connections to the same IP address any longer when I log into Y first. If I log into Z first then Y: see me as ken instead of guest. This used to work just fine until something mysterious changed. I am not very familiar with Credentials Manager as I've never had to use it in the past 10 years for this purpose. I did experiemnt with about five different forms of credentials (adding and deleting via Credentials Manager) but I couldn't get anything to work.
I am hoping that above sheds some light on this and that you could provide more direction. I'm stuck again. Thank you.
kenalker wrote:
However, Windows doesn't seem to like maintaining multiple connections to the same IP address any longer when I log into Y first.
It can maintain multiple connections, but they must use the same credentials. Windows has always worked that way, it is nothing new.
Microsoft has made some other changes on guest access, and my guess is that they will lock it down further over time. While you could simply try to track those changes as they unfold, in my opinion you are better off just setting up the NAS so you don't routinely use guest access.
How you handle this depends on what access restrictions you want to apply. If you want full access to all shares from all devices on your home network, then what you want to do is
- add credentials in the windows credential manager (for "ken" in your case, with the NAS password for ken)
- change the file access settings for the public shares so that ken has full read/write permission. You can also set the owner of the shares to ken/users
Thanks for the quick response. I do recall and have experienced what you say, that "It can maintain multiple connections, but they must use the same credentials." But I can tell you with all certainly that I've been logging into Z: and saving files that end up owned by ken.users and logging into Y: and saving files that end up owned by guest.guest (all from one computer). Not sure how I managed for years or why it suddenly stopped (maybe that is different than what you are saying).
For option one this means adding my credentials to machines that belong to other people, which would give them access to my home share, right (not good, if so)?
For the second option, this means having to add a new user to the access settings every time a new device is added to the network that needs guest access, true? I think it would also mean creating a user on the NAS for that person (which, perhaps, means they'd end up with a home share even if they don't need one). Not ideal, especially for guests visiting for a day, but would work.
I would normally experiemnt with these before writing back but must leave town shortly, so will probably have more questions once I try it out. Thanks!
kenalker wrote:
For option one this means adding my credentials to machines that belong to other people, which would give them access to my home share, right (not good, if so)?...
But I can tell you with all certainly that I've been logging into Z: and saving files that end up owned by ken.users and logging into Y: and saving files that end up owned by guest.guest (all from one computer). Not sure how I managed for years or why it suddenly stopped (maybe that is different than what you are saying).
Whether it's "good" or not depends on what data you put in the home share. Personally I don't use the home shares at all. As far as the past goes, the rules here are changing. WannaCry is one reason, as it exposed the dangers of allowing open access to network shares.
That said, it is certainly possible to reset the file access rights on the public shares to allow both guest and "ken" to write to the share. You could start with using the reset control on the file access page, and see if that solves it.
Also, one way to "fake" multiple credentials is to use the NAS IP address when mapping Z and the NAS name when mapping Y. Windows treates the IP address and the hostname as two different devices. Then you can just create a NAS credential for ken on the machines that access the ken home share, and always use guest for public shares.
You could also create a second account, and use its credentials on the other PCs to access the public shares (avoiding guest, and allowing you to be selective on whom you let access the public shares).
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
