Hi,

 

I used to be able to access the \\TOWER smb shares from my w10 vm (16273 build) but it doesn't work anymore.

 

I've tried to put shares on 'secure' but the same error appears. 

 

I've tried various solutions such as https://serverfault.com/questions/720332/cannot-connect-to-linux-samba-share-from-windows-10 and http://getadmx.com/?Category=Windows_10_2016&Policy=Microsoft.Policies.LanmanWorkstation%3A%3APol_EnableInsecureGuestLogons to no avail.

 

Any ideas ?

 

Thanks,

M.

Edited August 25, 20178 yr by mathieuNls

If you set a valid username and password for these shares I expect you can map the shares directly while supplying the username and password.

 

Try My Computer > Map Network Drive.

\\tower\media

 

And supply a username and password.

Here is the quick fix:

Configure the following Group Policy settings:

Computer configuration\administrative templates\network\Lanman Workstation

"Enable insecure guest logons"

 

To know more:

https://support.microsoft.com/en-us/help/4046019/guest-access-smb2-disabled-by-default-in-windows-10-server-2016

This is helpful. Put it in wiki.

12 hours ago, publicENEMY said:

This is helpful. Put it in wiki.

If this proves to be the solution to the OP's problem, could you add a post to this thread:

 

      https://forums.lime-technology.com/topic/53172-windows-issues-with-unraid/

 

 

And include links to this thread and to the entry in the WIKI.  I have a feeling this will be the first of many posts about this type of problem as MS tightens overall security on Win10. 

Indeed, you need to enable guest access. But, if you cannot or do not want, with Windows 10, you need to have the same username and password created on unraid. That shouldn't be a problem if you are using a local account, but given how Microsoft has been forcefully pushing their Microsoft accounts, if you made the mistake of going with a Microsoft account for login in to Windows, you can also simply create on Unraid a user with your MS email and password. That works too.

 

for those who have enabled guest access, the very first time you will try to access Unraid shares after that, enter ".\Guest" as username and leave the password field blank. Check the "Remember credentials" option if wanted.

 

Shahin,

 

Thank you for this solution. Only thing that worked for me and I've spent about a week fighting with this so I can simply connect to shared drives in the office. Created an account just to thank you.

 

Well done sir,

Bobvorn

Just wanted to add that Windows 10 Update Version 2004 broke access for both computers I applied the update to.

While the GPO showed Lanman Workstation allowing insecure guest logons, it wasn't working.

When investigating the Registry, it showed a value of 0, so it was not active, and the GPO was not being applied.

 

Had to perform registry edit as show in previous link to once again make active and restore connectivity.

Regedit Path: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters

SHOW LESS

Edited June 11, 20206 yr by ScytheNoire

Thank you, ScytheNoire, for posting this solution.  I had the same problem after updating to Version 2004.

On 6/11/2020 at 9:07 AM, ScytheNoire said:

Had to perform registry edit as show in previous link to once again make active and restore connectivity.

Regedit Path: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters

SHOW LESS

This needs to be pinned. Save my butt. Same issue. Upgraded today to 2004 and the registry did not match the group policy.

 

Thank you!

On 9/26/2019 at 4:39 AM, fnfsms said:

You can follow this video link

 

On 6/11/2020 at 9:07 AM, ScytheNoire said:

Just wanted to add that Windows 10 Update Version 2004 broke access for both computers I applied the update to.

While the GPO showed Lanman Workstation allowing insecure guest logons, it wasn't working.

When investigating the Registry, it showed a value of 0, so it was not active, and the GPO was not being applied.

 

Had to perform registry edit as show in previous link to once again make active and restore connectivity.

Regedit Path: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters

SHOW LESS

 

Regedit Path: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters

Double-click AllowInsecureGuestAuth and change "Value data" from 0 to 1

 

This worked for me after updating Windows 10 Education to 2004, thank you!

good post - many thanks.

Wow!! After months of head scratching why I couldnt access the shares on a new Win 10 laptop from my Win 10 PC (but I could the other way round), this was the reason!!  It was enabled in the GPO on my PC but yes, the reg key above was 0!  As soon as I changed it to 1, it worked a treat!! Thank you so much!

 

Jimbo

Thank you very much. It has been driving me nuts for many days. After 20h2 windows update.

Can't believe registry was not changing when setting changed through local policy editor.

All my network now working again wow! No thanks to microflopt. Thanks again Clive

Edited March 10, 20215 yr by Clivoss
Added detail about my windows version.

I don't believe that the two are logically connected together (setting one changes the other to conform). If you notice they have two different names for the parameter being set.  Ideally, only one of these parameters exists on a system but if they are both there, they do interact.  Not sure which one might have precedence.  Safest bet to check to make sure both (if both exist) are set to a 1.

I'm trying to create an account using my email and password in unraid that ties to my azure account (which is how my laptop is logged into it), but it doesn't like the @ symbol -_-

Hey there, very new to Unraid and setting up a VM with acces to my unraid server.
I have enable "Allow insecure guest logon" in the group policy editor after it couldnt see my server.

Everything is working now. Is this still a good fix in 2026 or is there another preferred method?

I am wondering if there are any security risks by enabling this .

48 minutes ago, Bobjonko said:

Hey there, very new to Unraid and setting up a VM with acces to my unraid server.
I have enable "Allow insecure guest logon" in the group policy editor after it couldnt see my server.

Everything is working now. Is this still a good fix in 2026 or is there another preferred method?

I am wondering if there are any security risks by enabling this .

MS added this requirement to help secure the computers that are running Windows. You can read about the problem of security for both Windows and Unraid starting here (and for the next several posts which will help you set up a secure environment for your data):

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

Your needing to "Allow insecure guest logon" implies that you are allowing 'Public' access to the data on your Unraid server. Do you need to secure the data on your Unraid server? I quote from this thread:

(With everyone having a smart device these days, many folks give visitors WiFi login credentials. Having your shares secure from easy access will give you peace of mind--- Do you really want your shady brother-in-law to have free-and-easy access to the backups of your financial records?)

22 hours ago, Frank1940 said:

MS added this requirement to help secure the computers that are running Windows. You can read about the problem of security for both Windows and Unraid starting here (and for the next several posts which will help you set up a secure environment for your data):

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

Your needing to "Allow insecure guest logon" implies that you are allowing 'Public' access to the data on your Unraid server. Do you need to secure the data on your Unraid server? I quote from this thread:

Thank you for your reply Frank! I guess I have some reading to do :)

In regards to the "public" access; on the "shares" page in Unraid it states that all my shares are set to "Private". It will probably become clearer when I read trough the thread you posted.