Just today my windows 10 computer is asking me to enter a password when i try to browse over the network to one of my shares?    All of my shares are set to SMB Public NFS - and AFP -

 

what gives all of a sudden?

My Win10 laptop started doing this a lot more recently.  I am assuming some Windows update has prompted the change.

 

I can resolve it by telling windows to log into the share with username of "\" and leave the password box blank.  I hope that works for you.

I had the same issue some weeks backs and what I do was repair permissions.

That solved it.

 

Hope it helps

Gus

 

Just a note, sometimes in Windows 10 you need to enter the hostname in the username box when you login to a share

 

ex:

 

tower/username

password

I get the following message from Windows

 

"The remote device or resource won't accept the connection"

 

I've reset permissions, shutdown windows firewall and disabled AV.  Any other ideas?  I can access it via FTP though so its on the network just not file sharing.

Even after creating a new share with security and assigning a user to it I cant access that share 

 

\\unraid\test

 

user: unraid\winuser

pass: passwd

 

Something has changed in the way windows does network shares and its broken my ability to use my unraid server.

I get the following message from Windows

 

"The remote device or resource won't accept the connection"

 

I've reset permissions, shutdown windows firewall and disabled AV.  Any other ideas?  I can access it via FTP though so its on the network just not file sharing.

 

I get the same thing. It is a Windows thing. I work with multiple domains and networks at work and can usually wiggle my way through and around the network.....but this one I've tried everything and it seems I'm just locked out.

 

Delete any unRAID credentials in Control Panel - Credential Manager so they can be renegotiated.

 

Windows will only allow one login per remote computer so if you need to connect to a share under a different user you will have to delete credentials again.

Seems this may be an issue with my unraid box.  I cant get into it using a windows 7 computer either.  I can get into my old 4.7 unraid server but not my newer 6.1.9.. 

I would check all your SMB settings and share permissions.

I have had same issue and on Windows 10 2004

On 9/23/2016 at 11:36 PM, auujay said:

I can resolve it by telling windows to log into the share with username of "\" and leave the password box blank.

 

Oh my God, that worked!!!  lol  How weird is that!?  Hahaha

For problems with access using Guest account privileges, see here:

 

    https://docs.microsoft.com/en-us/troubleshoot/windows-server/networking/guest-access-in-smb2-is-disabled-by-default

 

Read the entire article as they have done more than just restrict SMB2 and SMB3 protocols.  They also disabled SMB1 and a few other things.   This is all been done because of real existing security issues!

 

This is going to be an ongoing issue for anyone who is trying to run Unraid trying to use an unrestricted Guest access mode using a Windows 10 or Windows 11 computer.  (MS is going to be doing their best to prevent it!)  To prevent these type of issues, setup a login for your Windows users and require them to log in.  (You can use the Credential Manager to log them in automatically in the background!)  If after doing that you want to allow unrestricted access, you can do it with the Unraid SMB security settings.  (Not really recommended.  Once you have your users set up, it is a couple of small steps to restrict the access to your Unraid SMB shares to just those users!)  By requiring a login, you will at least keep out undesirable (and, perhaps, malicious) clients who do not have login credentials.

On 9/23/2016 at 11:36 PM, auujay said:

My Win10 laptop started doing this a lot more recently.  I am assuming some Windows update has prompted the change.

 

I can resolve it by telling windows to log into the share with username of "\" and leave the password box blank.  I hope that works for you.

 

This worked for me as well.  Thanks. Using Windows 11 and UnRaid 6.11.1

To get this to work on my Windows 10 (Enterprise) I had to set AllowInsecureGuestAuth to 1 in [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters] in the Registry Editor.

 

Then I had to login with username "\" and no password.

 

Edited May 29, 20233 yr by frakman1