Windows 10: Windows 10 uses SMB1, 2 or 3?

Hi, everyone is reporting SMB issues with sharing.

I wanted to know what exactly is SMB and which one is Windows 10 using which is causing such problems?

:)

 

Windows 10 November Update - cannot see other network devices

I found the easiest solution for me.

Enable both SMB1 and SMB2 using Powershell ISE, which is installed with Windows 10 Pro by default.

Note my PC had 2 versions of Powershell. Powershell and Powershell ISE. The applet required is in Powershell ISE.

Instructions in this KB https://support.microsoft.com/en-us/kb/2696547

Follow this KB and enable both SMB1 and SMB2. No restart required. Just refresh the "Network" page after running the applet.

I would guess by the settings when using Get-SmbServerConfiguration that SMB1 is being disabled by default, maybe for security reasons. You do not need to disable the newer versions of SMB, just make sure all versions are enabled unless you have specific
reasons for not wanting SMB1 enabled at all due to security.

It survived a full reboot for me and seems to show all my Linux and other Windows devices normally now.

Let me know if this helps anyone else.

 

Windows 10 November Update - cannot see other network devices

This did not work for me. I tried the Get first and got "Get-SmbServerConfiguration is not recognized as an internal or external command, operable program or batch file"

 

Does this help? https://support.microsoft.com/en-gb/kb/2696547

I have understood that W10 seems to be disabling SMBv1 by default with the latest builds. This should not be happening.

 

And what does SMB have to do with the router?
Some users reported problems with network file sharing after changing their router.

 

It is for computer to computer. But also controls how Windows knows where and how to find the other machines on the network.

SMB is short for Samba. Microsoft neutered their version, so that it is not fully capable of connecting to anything running Linux, which is every Router, NAS, Printer embedded software, etc.

 

But why did they make such a move?
Or no one has any idea?

 

Because they believed that there was a security issue with SMB 1 & 2, which there is not.

SMB 3 is not backwards compatible with Samba 4.x, along with they did not carefully think this out too well.

Why do they do half of the stuff that they do, to frustrate end users.

 

Any idea if RedStone fixes this?

If not, I will have to manually enable SMB1 and 2 on all my devices.
Will this break anything such as slow speed issues or certain other devices not showing up?

 

Hi there

One problem I notice with SAMBA to W10 is that the Linux boxes while seeing W10 seem to get a strange message when you try and access the Windows C drive -- no problem with any other Windows share or the "Users" directory on the C drive.

Cheers
jimbo

 

If you mean C$ Administrative share then that is because of UAC. You could add a LocalAccountTokenFilterPolicy DWORD in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System and set it to 1.

Access denied to Administrative (Admin) shares in Windows 8 - 4sysops

 

Nice to see YOU back......*Smile

 

Hi there

No it's not the C$ stuff -- browsing through C you get messages file does not exist -- it's all ok once you get to users and browse from there.

Absolutely no probs with any other Windows shared drives.

Cheeers
jimbo

 

Not that I have heard. The only thing about Redstone that I have heard is around 1200 changes, with a lot in a bad way.

After the last rollout which broke stuff on my test box, 10 got yanked and the discs destroyed. I am done playing with Microsoft and being their Beta tester.

From this point on, it is purely Linux in my house.

 

I saw that also, until I disabled SMB 1 & 2 on my test box with 10. Once I did, all shares showed up on the 10 box and Linux boxes.