New
#220
Install Everything search, let it run once it's installed so it can build it's index, takes 10-15 seconds.
Enter downloads in the search field. It will show you every occurrence of downloads on your computer.
Not sure if this is an issue or not !
Noticed once again that build 1813 update breaks SMB 1.0/CIFS Client support.
There are many forums and threads about SMB requirement for file network browsing, but what do we actually need for network browsing if updates are going to keep disabling this feature.
If we dont need SMB1 and it has security issues, why is it still available?
Do we need to install SMB2/3? if so, why has the option for SMB 2/3 been removed from the "Turn windows features on or off" and we can only turn on by Powershell "Set-SmbServerConfiguration –EnableSMB2Protocol $true"
Or how do we enable network browsing without any of the SMB features?
can the experts in this forum clear this up?
Thanks
Hi there
There's a whole load of legacy stuff out there (win 7 / 8 and earlier) plus all sorts of older NAS systems, Linux servers, music servers etc etc which still use the older SMB1 protocol. Actually I think for 90% of home users and networking the whole security issue is vastly overblown anyway. For commercial streaming / networking yes it's important but IMO that's it.
Cheers
jimbo
ok, think I sort of answered my own question here.
Having enabled SMB 1.0/CIFS Client I turned on SMB 2/3 support with Powershell Admin "Set-SmbServerConfiguration –EnableSMB2Protocol $true"
Then disabled all SMB 1.0 support and SMB Direct
restarted and everything shows on network browsing as required. This is except for a NAS drive which I think has SMB 1.0/ CIFS Legacy requirements to be shown on the network.
Tried this on 4 seperate PCs and Laptops and works fine.
There are some older PCs out there though, that will not support SMB 2/3 and therefore SMB 1.0 will still be needed for Network browsing.
To identify if your system is capable of supporting SMB 2/3 use the powershell admin command "Get-SmbServerConfiguration | Select EnableSMB2Protocol" this will produce "True" or "False"
If it is true, use the "Set-SmbServerConfiguration –EnableSMB2Protocol $true" if its false, then enable SMB 1.0/CIFS support
Hope this helps anyone with network browsing issues.
Hi Jimbo
Agreed on all points and as you say, it is overblown for most but for users not on a server environment and using NAS as document server, it is very important that we resolve SMB network browsing and ensuring it is secure.
I think I have resolved my issue in the post above
Cheers
John
Kado,
You are correct, SMB 1.0 for the legacy devices as I could not see my NAS without it either.
I wonder if newer NAS devices are SMB 2/3 compliant?
Although my NAS is a WD My Cloud 8tb and is only 2 years old !