Hello Everyone,

 

I have a the same issue, I have setup a Unraid Server setup a Share as Pulblic and exported it. But i can not connect to the NAS over the network. I have windows 10 home, but have enabled SMB via the control panel, i dont have any A/V running. i can ping the server, and i can connect via a browser but cant see it in the network option or map a network drive. Please help! I have attached some pics.

@mattiscg  just to check the obvious, have you actually set any shares to be visible on the network (by default none of them are)?   You did not post your system’s diagnostics zip file so we cannot look there to see.

Uploaded System Dignostics, and i have set the SMB Security Setting - i set the Share to Pulbic. is that what you are talking about?

tower-diagnostics-20240425-0735.zip

Dont know what i did but after a reboot, i was able to access the shares. Thanks everyone.

@mattiscg, you are looking for this  share:

 

When the Share name is actually!

Edited May 4, 20242 yr by Frank1940

I made the mistake of patching and rebooting.

 

No access to shares as usual.

 

Same error. 

 

NFS running, SMB running. Tried creating a new user and share but no access. 

 

Attempt connect to an existing share returns:

"The mapped network drive could not be created because the following error has occurred:

An unexpected error occurred."

And yes, I've tried every thing in this thread multiple times.

 

tower-diagnostics-20240507-0518.zip

5 minutes ago, lonebear said:

I made the mistake of patching and rebooting.

 

No access to shares as usual.

 

Same error. 

 

NFS running, SMB running. Tried creating a new user and share but no access. 

 

Attempt connect to an existing share returns:

"The mapped network drive could not be created because the following error has occurred:

An unexpected error occurred."

And yes, I've tried every thing in this thread multiple times.

 

tower-diagnostics-20240507-0518.zip 204.64 kB · 0 downloads

to clear _other_ issues I have removed the drives I was attempting to add. this is a diag with them removed and off.

tower-diagnostics-20240507-0527.zip

 

Under windows 11. Unraid 6.10.12.

 

I had my drive mappings loose all connections every time I restarted my file server for what ever reason.

 

I needed to remove all mappings and then remap everything

 

I have found now that adding a network location works better and I do not loose the mappings on a restart

 

The only problem or inconvenience is that that my network locations no longer have a drive letter attached to them

You have to add the windows user in to unraid. Then enable that on the share. Click on users then click on the windows user that you added then you see all the shares, set read write. then in windows map a drive to the \\ipaddress\share name using the windows user account. 

I know this is old, but it just worked for me after a major Windows 11 update,

Thank you!

This originally worked for me but I upgraded the CPU in my server the other day and have been having issues accessing and adding the server as a network drive since.

I ended up resetting windows (needed to be done anyway), enabled smb1 to be sure, enabled insecure connections via gpedit, and I can now see the server in my network, but I can only see an empty folder when I know my data is still intact as I can still access it via streaming apps, etc.

 

If I try to map the server as a network drive, I get a connection failure.

 

Images and diagnostics attached.

homeserver-diagnostics-20240605-2213.zip

I know this is over a year old. But for other users who search this and land on this page. I fixed this problem by adding my server name and IP to my Windows host file in C:Windows/System32/drivers/etc/hosts. 

 

The problem is not Unraid, it's Windows.

I found the answer that worked for me on reddit:
 

Go to the credentials manager in Windows and add the server and your credentials there. Then logout of windows and back in and it should work.

 

I know.... I'm responding to an old post, but its good to document things somewhere.

Keeping this thread relevant.. just fixed me up on my WIndows Server 2022 install!

Clear install of win11 also couldn't map unraid shares.
Deleting everything in Credential Manager in windows worked again but if you have root share set per spaceinvader video you need to use username set there, not just a root.



This solution is still relevant

 

 

Edited October 8, 20241 yr by BeersTeddy

Thanks, this simple fix cured my ills.

https://techcommunity.microsoft.com/blog/filecab/accessing-a-third-party-nas-with-smb-in-windows-11-24h2-may-fail/4154300

If you are on Win11 pro 24h2 check the article above, there's even more policies you will have to turn off or you won't be able to access your SMB share.

 

• On the Start Menu search, type gpedit and start the Edit Group Policy app (i.e. Local Group Policy Editor).
• In the console tree, select Computer Configuration > Windows Settings > Security Settings> Local Policies > Security Options.
• Double-click Microsoft network client: Digitally sign communications (always).
• Select Disabled > OK.

45 minutes ago, cprn.1337 said:

https://techcommunity.microsoft.com/blog/filecab/accessing-a-third-party-nas-with-smb-in-windows-11-24h2-may-fail/4154300

If you are on Win11 pro 24h2 check the article above, there's even more policies you will have to turn off or you won't be able to access your SMB share.

 

• On the Start Menu search, type gpedit and start the Edit Group Policy app (i.e. Local Group Policy Editor).
• In the console tree, select Computer Configuration > Windows Settings > Security Settings> Local Policies > Security Options.
• Double-click Microsoft network client: Digitally sign communications (always).
• Select Disabled > OK.

Version 7 will have a fix for this problem.  Earlier Unraid versions can be 'fixed' by adding the following lines to the SMB Extras section of   SETTINGS   >>>   Network Services   >>>  SMB

 

[global]
server signing = auto

 

(If the [global] header already exists, you need only to enter the second line under it.)

 

This solution is a one time fix as it allows your Unraid server to do the proper SMB signing with your Windows client..  (The problem with your solution is that you have to do it for every Windows computer that will attach to your Unraid server.  And it does allow an identified security issue to exist.  Granted the risk is small for most most people,,,)

 

 

32 minutes ago, Frank1940 said:

Version 7 will have a fix for this problem.  Earlier Unraid versions can be 'fixed' by adding the following lines to the SMB Extras section of   SETTINGS   >>>   Network Services   >>>  SMB

 

[global]
server signing = auto

 

(If the [global] header already exists, you need only to enter the second line under it.)

 

This solution is a one time fix as it allows your Unraid server to do the proper SMB signing with your Windows client..  (The problem with your solution is that you have to do it for every Windows computer that will attach to your Unraid server.  And it does allow an identified security issue to exist.  Granted the risk is small for most most people,,,)

 

 

I am on 7.0.0-beta.4 and this parameter isn't added by default.

2 minutes ago, cprn.1337 said:

I am on 7.0.0-beta.4 and this parameter isn't added by default.

That is not needed, see here:

https://forums.unraid.net/topic/177975-formatted-my-pc-and-installed-fresh-windows-11-now-cant-access-smb-shares/?do=findComment&comment=1478526

 

6 hours ago, cprn.1337 said:

I am on 7.0.0-beta.4 and this parameter isn't added by default.

 

I would not expect it to be added as an SMB Extra.  Run the following command:

testparm

And look in the output for the following SMB parameter and see what its setting is:

server signing = if_required

      {parameter}        =  {Setting}

 

IF it does not show up, use this command:

testparm -v

 

This list seems to contain the setting of every possible SMB parameter and its setting so it is very, very long.   (The short list appears to the the ones which have modified from the default settings.)

 

Edited November 9, 20241 yr by Frank1940

13 hours ago, cprn.1337 said:

https://techcommunity.microsoft.com/blog/filecab/accessing-a-third-party-nas-with-smb-in-windows-11-24h2-may-fail/4154300

If you are on Win11 pro 24h2 check the article above, there's even more policies you will have to turn off or you won't be able to access your SMB share.

 

• On the Start Menu search, type gpedit and start the Edit Group Policy app (i.e. Local Group Policy Editor).
• In the console tree, select Computer Configuration > Windows Settings > Security Settings> Local Policies > Security Options.
• Double-click Microsoft network client: Digitally sign communications (always).
• Select Disabled > OK.

I upgraded to Win 24H2 yesterday and just noticed I cannot access my Shares on this computer (access is fine on others).  However, this policy you mention was already disabled.  I had to also complete the other step mention in the article:

 

Disable the guest fallback protection:

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 e.

b. In the console tree, select Computer Configuration > Administrative Templates> Network > Lanman Workstation.

c. Double-click Enable insecure guest logons

d. Select Enabled > OK.

Edited November 10, 20241 yr by zero_koop

Had this issue when upgrading to Win11 24H2. Looks like SMB Signing is enabled by default now.

Use the following in PowerShell cmd to disable it. Haven't found a way to enable it Unraid side yet.

Check Status: 
Get-SmbClientConfiguration | FL requiresecuritysignature

 

Disable:
Set-SmbClientConfiguration -RequireSecuritySignature $false
 

On 11/9/2024 at 11:37 PM, bluxxy said:

Use the following in PowerShell cmd to disable it. Haven't found a way to enable it Unraid side yet.

You should be able to do by adding the following to the    Samba Extras   section of the SETTINGS >>>  SMB

[global]
server signing = auto

 

(If there already is a [global] section heading, just add the second line.)   I test this by upgrading a WIN11 Pro  mini computer to 24H2 and verifying that SecuritySigniture was required.  (I had to turn it on-- not sure why??)   And everything worked.  

 

Note that there are TWO major security changes in 24H2 update.  The  second one is that guest logins from Windows clients are no longer permitted on WIN11 PRO (and probably the Enterprise and other specialty versions).   You can get around this by adding a Share Access User to Unraid and setting a Windows Credential (type that phase in the taskbar search box) for your Unraid server and the Share access user that you set up.  (P.S.  You do not need a separate credential for each Windows client computer if they all have the same Share access privileges on the server.  If you are coming from using Public access mode on your Unraid server that is what you had anyway!)   That Share Access user is basically just a set of rules and any client computer can use that set of rules.  SMB and Samba prefix the Share Access user with the Device Name for that computer.  You can find that in the Settings app as shown here:

 

Because of this combination of the Device/Computer name and the Share Access user, each login from separate client computers becomes unique and everything just works.

 

If you look at the devices on your router, you will find it there.  (By the way, that name should be unique or things don't work right...)  

 

On 12/3/2024 at 1:17 PM, Frank1940 said:

Note that there are TWO major security changes in 24H2 update.  The  second one is that guest logins from Windows clients are no longer permitted on WIN11 PRO (and probably the Enterprise and other specialty versions).   You can get around this by adding a Share Access User to Unraid and setting a Windows Credential (type that phase in the taskbar search box) for your Unraid server and the Share access user that you set up.  (P.S.  You do not need a separate credential for each Windows client computer if they all have the same Share access privileges on the server.  If you are coming from using Public access mode on your Unraid server that is what you had anyway!)   That Share Access user is basically just a set of rules and any client computer can use that set of rules.  SMB and Samba prefix the Share Access user with the Device Name for that computer.  

 

 

Hi Frank,

I did this as it was recommended on one of the posts to prepare for the future but now I can't delete stuff on the share. How do I fix this? do I need to upgrade the permission on my user?