Hi guys, I have been trying to troubleshoot for hours, searching Google, YouTube, etc. but I can’t get it to work. I have my share in unraid set to private and my user has read/write permissions, then I go to file explorer and see my unraid server called “Hemmaserver“ but when I click on it this error message pops up:

 

“\\HEMMASERVER is not available. Maybe you don’t have permissions to use this resource. Ask the server’s administrator for help. Multiple simultaneous server connections or resources that are shared by the same user that uses more than one username are not allowed. Disconnect all previous connections to the server or the shared resources and try again.“

-Directly translated from Swedish to English as best I could.

 

I am using the tailscale plugin in case that is important and I am using the latest windows 11 version and unraid version 6.12.9

Did  you set up a Windows credential for your Unraid Share Access user in Windows Credential Manager?    (Windows can do some strange things about logging into servers at times.  It is often best to force Windows into using the login that you want it to use.   Credential Manager can do that.  You should reboot the Windows computer after you make the change.) 

Another thing to try:

13 minutes ago, Frank1940 said:

Did  you set up a Windows credential for your Unraid Share Access user in Windows Credential Manager?    (Windows can do some strange things about logging into servers at times.  It is often best to force Windows into using the login that you want it to use.   Credential Manager can do that.  You should reboot the Windows computer after you make the change.) 

 @Frank1940 I did that and then I got it to work for a day (I hadn't rebooted the first time). But now when I shut the pc down during the night and started it the next day, the private share is inaccessible again. I'm going to try removing the credentials again and then re-enter them again and then reboot to see if it fixes it again. But I doubt it's going to be a long-term fix.

 

6 minutes ago, Frank1940 said:

Another thing to try:

Thx, i'm going to try this too

Windows will allow only one connection from a Windows client computer to any server.  (As I understand it,this is strictly a Windows policy!)  There was a backdoor where you could use the IP-Address of a server and the server's Network name to set up two connections.  BUT I have not been able to get that to work for some time. 

 

Windows also has recently implemented a policy that guest/anonymous connections to servers are not allowed.

 

Window networking error messages are confusing and often misleading. 

 

Many folks try to get around Windows security policies and sometimes, they are successful.  But, essentially, they are just hacking Windows security and MS may plug these hacks at any time in the future.  I feel that it best to just set things up the way MS wants them to be.    Here is a link to a couple of PDF files that will help you do this:

 

     https://forums.unraid.net/topic/110580-security-is-not-a-dirty-word-unraid-windows-10-smb-setup/

 

@Frank1940 Do you mean that I have to re-enter the credentials into credential manager every time I reboot my PC? Or what do you mean with "Windows will allow only one connection from a Windows client computer to any server"? I only have one PC connected to 1 user on my unraid server so I can't have exceeded some sort of limit

10 minutes ago, Thedinotamer said:

I only have one PC connected to 1 user on my unraid server so I can't have exceeded some sort of limit

 

That PC is only allowed one login/connection to any Server.  (That restriction is enforced by the client PC.)   That means if that client PC establishes a login to your Unraid server silently, any attempt to login with another set of login credentials will fail!

 

Here is an old post that describes what happens behind the sceans:

 

    https://forums.unraid.net/topic/25064-user-share-problem?tab=comments#comment-228392

 

 

23 minutes ago, Thedinotamer said:

Do you mean that I have to re-enter the credentials into credential manager every time I reboot my PC?

No.  I should be a one time deal to add them and Windows should continue to use them forever.  Note that every user on that client has their own environment...

16 minutes ago, Frank1940 said:

PC establishes a login to your Unraid server silently

When would it have done this? As I said before I have only tried to login into one user.

 

17 minutes ago, Frank1940 said:

No.  It should be a one time deal to add them and Windows should continue to use them forever.  Note that every user on that client has their own environment...

What do you think made Windows to break the connection to the shares if this is the case?

2 hours ago, Thedinotamer said:

What do you think made Windows to break the connection to the shares if this is the case?

The connection is 'broken' is always broken when the client is shutdown. 

 

3 hours ago, Thedinotamer said:

When would it have done this? As I said before I have only tried to login into one user.

As I understand, the client and the server do a handshake operation the first time that the client tries to connect to the server.  (Note that this first contact could be setting up a 'mapped' Windows drive...)  Be sure that you read that post from LimeTech back on 2013 about the login handshaking that goes on. 

 

SMB has its roots back in Windows for Workgroups which was introduced back in the early 1990's.   At that time, SMB was intended to link together a few computers in small engineering groups who wanted to share data without restrictions among their group.  (My first experience using it was with 10 base 2 cards and RG-58 cabling.)  It has evolved over the last thirty years into the basic standard networking protocol for the Governments and businesses.  And this has resulted in it becoming a prime target for every hacker in the world.  So security is now the watchword for SMB.  The goal of SMB is now to ensure that only verified authorized users ever gain access to a SMB server.  If you as a user don't qualify in even the smallest detail, SMB is going to deny you access. 

i did find this on windows home page and help me

 

Select Start, type gpedit.msc, and select Edit group policy.

 

In the left pane under Local Computer Policy, navigate to Computer Configuration\Administrative Templates\Network\Lanman Workstation.

 

"my edit find the SMB over QUIC and enable it"

 

Open Enable insecure guest logons, select Enabled, then select OK.

 

this did work for me

found if you are using a local account and not a Microsoft account then maybe you need this instead i used like 4 hrs to find a fix

a. On the Start Menu search, type gpedit and start the Edit Group Policy app (i.e. Local Group Policy Editor). If you are using Home edition, skip to step 8.

b. In the console tree, select Computer Configuration > Windows Settings > Security Settings> Local Policies > Security Options.

c. Double-click Microsoft network client: Digitally sign communications (always).

d. Select Disabled > OK.

 

 

Edited May 27, 20251 yr by OlsenTF
a new fix for local account on windows

After many attempts i have found this solution.

 

Run Powershell as administrator and type this:

Set-SmbClientConfiguration -EnableInsecureGuestLogons $true -Force

this will allow insecure guest logins which were deactivated with the past windows updates

 

https://learn.microsoft.com/de-de/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3?tabs=powershell

On 4/15/2024 at 2:17 PM, Frank1940 said:

Did  you set up a Windows credential for your Unraid Share Access user in Windows Credential Manager?    (Windows can do some strange things about logging into servers at times.  It is often best to force Windows into using the login that you want it to use.   Credential Manager can do that.  You should reboot the Windows computer after you make the change.) 

Thanks Franck, my new computer was not able to connect. Then I added both the IP and the name of my server in the credential manager and after a reboot it finally worked.  

On 1/16/2025 at 12:40 PM, SLoeffler said:

After many attempts i have found this solution.

 

Run Powershell as administrator and type this:

Set-SmbClientConfiguration -EnableInsecureGuestLogons $true -Force

this will allow insecure guest logins which were deactivated with the past windows updates

 

https://learn.microsoft.com/de-de/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3?tabs=powershell

this doesn't work i came here cuz it said there was a fix but like always been happening for 10 years plus and still no fix wow 

On 4/20/2025 at 4:41 PM, Shady420 said:

this doesn't work i came here cuz it said there was a fix but like always been happening for 10 years plus and still no fix wow 

It's not specific to unraid, it's a Windows problem. Same thing happens in ZimaOS as well.

I never had problems to connect from windows to unraid... the firewall must be off or at least some rules implemented.

Thats it.

And all shares should be done over folders with network adresses under windows - so you dont need the Network environment view under windows...

And unraid should have a user which is identical to the windows-user (same name, same password).

This is a weird one. In the last three days, I started having access problems to Unraid public shares on one Windows 11 machine only; Unraid 7.2.2. It works fine on the other two. I did have allow insecure logins enabled (It still is), but I decided I would try the Unraid user/password route.

• In File Explorer, I can no longer consistently access the server either by server name or IP address

• I have created a user/password in Unraid and given the user read/write access to all public shares

• I deleted all references to the server name and IP address in Windows Credential Manager and created new entries with the Unraid user name and password

• Server name no longer appears in Network section of File Explorer

• Every once in a while, I can get the shares to show up when I enter the server name or IP address in File Explorer, but, after a reboot (or even sometimes before if I navigate away) it no longer works

• If I delete the credentials from Credential Manager, attempting to access the server sometimes brings up a user name and password prompt. I enter these and, maybe, 25% of the time, the connection works and the shares show up (until they suddenly don't any more)

• Often, entering the credentials again when prompted just results in an error that the network path is not found

• I can also no longer access the Unraid server by server name in the browser address bar. Only IP address works

Below is a screen shot in my dual pane file explorer of it failing by server name and succeeding by IP address; sometimes, even IP address will not work. Clicking on Connect results in nothing unless I delete the MEDIANAS credentials from Credential Manager. It then prompts for user name and password and, far more often that not, still fails to connect. All these shares are Public.

Here is what smbstatus shows for the above. I am not sure where the locked files come from and if they are causing problems as I have no shares open at the moment.

The 100.98.17.2 IP address is the Tailsclale IP of the Windows 11 machine from which I am having the problems and Tailscale is currently turned off. 192.168.1.115 is the DHCP assigned address for the PC.

I have never seen this problem before in 12+ years of using Unraid, especially since two other PC are unaffected. It is obviously a problem on this PC only; however, I'm having a hard time tracking it down. WIndows sucks. :)

Edited December 18, 2025Dec 18 by Hoopster

10 hours ago, Hoopster said:

This is a weird one. In the last three days, I started having access problems to Unraid public shares on one Windows 11 machine only; Unraid 7.2.2. It works fine on the other two.

Start here and make sure that the network type is Private:

https://forums.unraid.net/topic/191221-some-musings-on-smb-and-samba-and-unraid-and-windows/#findComment-1561581

If you still have problems let's go on....

What version and release of Windows are you using on this PC? (Example answer--- Windows 10 PRO 25H2)

10 hours ago, Hoopster said:

In File Explorer, I can no longer consistently access the server either by server name or IP address

This one is harder to resolve as it is a networking problem. Begin by reboot the all routers and switches. Setup Windows credentials for both the server name and the server's IP address. Now let's use Windows File Explorer rather than a third party File Manager for testing purposes.

1--- Am I correct in assuming that you are are typing in \\server_name and \\server_IP_address on the File explorer title bar and not getting to the server?

2--- Or you you looking for it under "Network" in the left Panel. And it does not appear or appears only inconsistently.

Number 2 is easy. As Far as I am consider, Network Discovery is basically broke since SMBv1 was turned off. Use this method and ignore "Network" completely!

https://forums.unraid.net/topic/191221-some-musings-on-smb-and-samba-and-unraid-and-windows/#findComment-1561585

Number 1 is a bigger problem to resolve if my earlier suggestions did not fix it. So let's leave it for your next post.

Added before posting:

11 hours ago, Hoopster said:

This is showing that computer 192.168.1.115 is actually connected to this server. And it currently looking at the 'Pictures' share. (I believe Samba always uses the IP address rather than the server_name. It is the job of the router to resolve the server_name to the IP address.)

From the Pid, it i s actually your Tailscale connection looking at the Pictures share.

Edited December 18, 2025Dec 18 by Frank1940
to strike out sentence...

12 hours ago, Hoopster said:

Server name no longer appears in Network section of File Explorer

Thats the Windows Firewall - deactivate it or implement a propper rule.

Strange: On your screenshot, smbstatus shows under Username the term "shares"...

In my case, i get the "username" i use under Win 11 and unraid (same user, same password) - Is the user really called "shares"?

Edited December 18, 2025Dec 18 by Zonediver

2 hours ago, Frank1940 said:

Start here and make sure that the network type is Private:

Yes, I have Network discovery and File and printer sharing turned on under the Private network. They are off on Public networks. Double checked that yesterday.

2 hours ago, Frank1940 said:

What version and release of Windows are you using on this PC?

Windows 11 Pro 25H2

2 hours ago, Frank1940 said:

Am I correct in assuming that you are are typing in \\server_name and \\server_IP_address on the File explorer title bar and not getting to the server?

Correct. However, it works far more often with IP Address and rarely with server name.

2 hours ago, Frank1940 said:

Or you you looking for it under "Network" in the left Panel. And it does not appear or appears only inconsistently.

On the rare occasion that server name actually connects, the server name then appears in Network in the left panel. Otherwise, it is not there.

Credentials for both server name and server IP Address exist in Credential Manager.

Until four days ago, none of this was a problem on this PC. Some Windows update must have broken things. It does work fine on other PCs.

2 hours ago, Frank1940 said:

Number 2 is easy. As Far as I am consider, Network Discovery is basically broke since SMBv1 was turned off. Use this method and ignore "Network" completely!

https://forums.unraid.net/topic/191221-some-musings-on-smb-and-samba-and-unraid-and-windows/#findComment-1561585

I have the same problems in Windows File Explorer. In fact, neither server name or IP address works there.

In my third party File Explorer (Directory Opus), I did pin MEDIANAS (on one of the rare occasions when server name worked) to its Quick Access list. It does not work there either.

Of course, mapping network drives does not work either.

Edited December 18, 2025Dec 18 by Hoopster

2 hours ago, Zonediver said:

Strange: On your screenshot, smbstatus shows under Username the term "shares"...

In my case, i get the "username" i use under Win 11 and unraid (same user, same password) - Is the user really called "shares"?

Yes. In my testing, I created an Unraid user called shares. It is connecting with the proper user name. I can see how that might be confusing, but, since I was testing access to Unraid shares, that is the user name I created for my tests.

Here is a cleaner smbstatus screen with connection to Unraid via IP address (it survived a reboot) and with the Backups share open in File Explorer. Unraid user name is "shares" so it is connecting via the correct credentials in Credential Manager.

Edited December 18, 2025Dec 18 by Hoopster

9 minutes ago, Hoopster said:

Here is a cleaner smbstatus screen with connection to Unraid via IP address (it survived a reboot) and with the Backups share open in File Explorer.

This looks like everything is normal from a Samba standpoint. You can see the connection from your Windows computer and the user_name is correct.

I am only mentioning this next part because of something I remember from a while back. Someone had a similiar problem and resolved it by doing a Windows reinstall using the method that preserves the installed user programs and data. (Problem is that I am getting older and my memory is not as good as it was five-to-ten years ago and I can't remember the more pertinent details.) IF you decide on this approach, do some research first as the Windows install program has several avenues that you can use when running it. Look for advice from the Microsoft site as there is a lot of Windows 'help info' that is pure crapola!

An other option is to roll back the most recent Windows updates on this computer and see if that fixes it. (In fact, I would try this first before I did a reinstall.)

28 minutes ago, Frank1940 said:

An other option is to roll back the most recent Windows updates on this computer and see if that fixes it. (In fact, I would try this first before I did a reinstall.

I just rolled back the Windows Security update install on December 15. It seemed like a likely culprit and was about the time the problems started. One of the PCs that works fine has that update installed, the other one does not.

No joy. Still cannot connect by server name, but, once again, the connection to Unraid shares via IP address survived the reboot. At least that seems to be consistent now and is what I will have to use until I can get this figured out.

Edited December 18, 2025Dec 18 by Hoopster

In my experience, when a Windows PC has those kinds of issues, best bet is to reformat. It's a pain, but I've spent hours trying to resolve issues like that, and in the end still had to format.

41 minutes ago, JorgeB said:

In my experience, when a Windows PC has those kinds of issues, best bet is to reformat. It's a pain, but I've spent hours trying to resolve issues like that, and in the end still had to format.

An "Inplace Upgrade" is faster and do the job as well...