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?
Does this help?
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?Does this help?
I have understood that W10 seems to be disabling SMBv1 by default with the latest builds. This should not be happening.
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?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.
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?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.
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_MACHINESOFTWAREMicrosoftWindowsCurrentVersionPoliciesSystem and set it to 1.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.
Access denied to Administrative (Admin) shares in Windows 8 - 4sysops
Nice to see YOU back......If you mean C$ Administrative share then that is because of UAC. You could add a LocalAccountTokenFilterPolicy DWORD in HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionPoliciesSystem and set it to 1.
Access denied to Administrative (Admin) shares in Windows 8 - 4sysops
