We NEED a Windows Registry expert!

[fred.w....@gmail.com]

Background

Some Forum members are having (or have had) difficulties getting Windows 10 to recognize the NAS that the B2 publishes on a house LAN. 

The current member suffering is here 

https://groups.google.com/g/brennanb2/c/Ltl0QkOPqXk

I also had this problem and here was my Final resolution

================================================

I have finally resolved this issue: My B2's NAS is back!

This has been ALLOT of pain for me - to eliminate, narrow down the issue I have

1) Checked I could see the B2 Nas on an Android device (I could)

2) Replaced my router (it needed replacing anyway) (No Change)

3) Did all that was recommended by the kind people on this thread (No Change)

4) Upgraded my Windows 10 to Pro (ouch!) (No Change)

5) began researching and testing on and off for weeks until I go a fix that worked. The fix is (apart form all the option in the thread above)

a) Open the "Group Policy Editor" from an Windows Admin account

b) go to the "Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options" path

c) find the entry "Network security: Restrict NTLM: Outgoing NTLM traffic to remote servers"

d) change its value to "Allow all" from the options.

e) save

f) exit the utility

g) reboot

====================================================

I think it is a bit unreasonable to have to purchase a Windows 10 Pro licence to 

solve the problem and I am sure that if one knows what registry value is set by

"Network security: Restrict NTLM: Outgoing NTLM traffic to remote servers"

I am sure a Reg edit would resolve the issue. 

Is there such an expert on the forum?? If so PLEASE HELP.

Fred

[Daniel Taylor]

Hey Fred,

I hear you. (But no I'm not such an expert.)  Whenever I've had to go into the Registry over the years, I always get nervous.  One wrong move and you have a new problem with something you have no idea about and, unless you know exactly what you did wrong, no way to figure it out. We have a lot of users who should not be confident to go messing about in the Registry.

All that being said, in the case you outlined above, I realize that all your work could have been easily short cut by one (or two?) simple tweaks to the Registry.

It seems that someone with sufficient knowledge of Windows 10 and the Registry could whip up a specialized program that would set those specific values to what they need to be, without risking having to go into the Registry manually.  Or, more generally, display the current settings of everything that has anything to do with allowing NAS to work, and then allowing you to change only those items.  I haven't written a program for Windows since way before Win10 came out, so I'm feeling my age.

[fred.w....@gmail.com]

Hi Daniel

You are sharing my thinking :)

Yes I was thinking a "Regedit" macro to change what I think is probably one Registry setting may be a possibility. (I have seen the like!)

But I do agree we should not be encouraging people to edit the Registry by hand themselves - it could be catastrophic even with a backup made first!

Hope someone on the forum has the skills though - you never know who is out there!

Fred

[Mark Fishman]

I searched for 'registry key for "Network Security" Outgoing' and found

https://www.windows-security.org/c526612a90004088b250158bc5e7dc2d/network-security-restrict-ntlm-outgoing-ntlm-traffic-to-remote

Is that what you are looking for?

[fred.w....@gmail.com]

Hi Mark

Yes that look to be the one.

We need a Regedit macro that set the value to "Allow all". 

I could do it from an Admin account using the Group Policy editor that you get "turned on" with a Windows Pro licence.

When I made that change my B2's NAS reappeared :))

Fred

[fred.w....@gmail.com]

Dear Reader,

With the help of Mark Fishman,  I have constructed the attached file, which if downloaded on to a Windows 10 system, and saved as a file,

will if the user's account has Admin privileges and when the file is double clicked on, effect the registry change that brought my B2's NAS back to being visible.

The file contains this text

-----------------------------------------------

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0]

"RestrictSendingNTLMTraffic"=dword:00000000

-------------------------------------------------

and makes a single change to the Windows 10 registry and

Thanks Mark.

Fred.

[Daniel Taylor]

Bravo to both of you.  I look forward to reading that this has solved the problem for various users.

[fred.w....@gmail.com]

Hi Daniel,

Well the first test user is potentially "Frenchie" on this thread https://groups.google.com/g/brennanb2/c/Ltl0QkOPqXk

Fred

[John Johnstone]

Hi guys,

New here, first post. I just bought a B2 2T and like a few people, couldn't get access to the B2 NAS from my Windows 10 PC. The Network search never picked the B2 at all. After a bit of reading through the forums and a few frustrations, I managed to get a result. I took the following steps:

- turned NAS on at the B2

- turned the SMB1.0/CIFS Client on in Windows and rebooted the PC 

- added a network location \\BRENNANB2\music and entered the credentials root, password brennan. It took a while for the PC to set this up

Voila ... the network location was created. I was able to then map the location as a network drive

Hope this helps

John

[fred.w....@gmail.com]

Thanks john,

Glad you got your NAS working with Windows. 

This thread was trying to deal with the few instances in which the steps you document do not work.

Fred