SMB is Dead, Long Live SMB

Hi folks again

Here's the W2K22 server with SMB1 option.



I've been a bit "Naughty" here as as I've played around with this to make it operate as a "Desktop Workstation" --these Windows servers are so much less bloated than the standard W10 retail offerings and run really well as a desktop -- bit of work though to get rid of all the "Server nag things" of course. The add features / turn windows features on / off totally unmodified - just standard and SMB1 was still an available option.

Hint - if you want to have a go with this type of stuff install initially as a VM.


Cheers
jimbo

Yep
I just got SMB1 re-enabled on both computers and now the master can see both the master and the slave, but the slave still only sees itself. Before, the master only saw itself as well. Now I have to find where I wrote down the registry hack for forcing which computer would be the master browser and which wouldn't, and I might be back up and running. I can tell that the LAN is partially running now, since if I have a full name for a file (computer/path), then the slave can access the file. I just cant browse to the master computer to find a file anymore. Wish me luck.
Tim

I have it saved. In the thread it also points to handy tool

Registry Hack to DISABLE Master Browser

Tim Ryan said:

Yep
I just got SMB1 re-enabled on both computers and now the master can see both the master and the slave, but the slave still only sees itself. Before, the master only saw itself as well. Now I have to find where I wrote down the registry hack for forcing which computer would be the master browser and which wouldn't, and I might be back up and running. I can tell that the LAN is partially running now, since if I have a full name for a file (computer/path), then the slave can access the file. I just cant browse to the master computer to find a file anymore. Wish me luck.
Tim

Out of curiosity: why would anybody re-enable SMB1? I mean, after reading the article, it doesn't just seem to be a security vulnerability. It's a wide-open landing pad for hackers!

I even question Windows 10's pseudo-replies that was added to prevent SMB1 clients from freezing upon receiving invalid replies... it should not be replying at all.

I remember SMB from the early/mid 90's with Token Ring LANs. We (My LAN/WAN Network Management site) had early versions of IBM LAN Manager and later LAN Network Manager.

ish4d0w said:

Out of curiosity: why would anybody re-enable SMB1? I mean, after reading the article, it doesn't just seem to be a security vulnerability. It's a wide-open landing pad for hackers!

I even question Windows 10's pseudo-replies that was added to prevent SMB1 clients from freezing upon receiving invalid replies... it should not be replying at all.

Hi there
If you've been following the thread you can see there's still a huge need for SMB1 - until you get rid of loads of old W7 and earlier computers, loads of "smart TV's" and other types of things that connect to TV's e.g some types of firestick boxes, and even a load of old NAS systems still currently in use.

As far as problems of security on home LAN's is concerned - this is a topic hugely over estimated these days - Windows WD is fine and it's SCAMMING rather than any sort of "Ransomware" and malicious hacking that is a problem - and that's usually the fault of users themselves giving out too much information on social media sites or opening email attachments from person / persons unknown.

Cheers
jimbo

jimbo45 said:

Hi there
If you've been following the thread you can see there's still a huge need for SMB1 - until you get rid of loads of old W7 and earlier computers, loads of "smart TV's" and other types of things that connect to TV's e.g some types of firestick boxes, and even a load of old NAS systems still currently in use.

As far as problems of security on home LAN's is concerned - this is a topic hugely over estimated these days - Windows WD is fine and it's SCAMMING rather than any sort of "Ransomware" and malicious hacking that is a problem - and that's usually the fault of users themselves giving out too much information on social media sites or opening email attachments from person / persons unknown.

Cheers
jimbo

Ohh, that makes sense. Thank you!

TV2 said:

Yes, this issue reared it's ugly head for me this weekend.
I have Kodi installed on my Nvidia Shield for streaming content from a W10 PC. Sometime on Saturday Kodi upgraded itself (without asking) to v19 Matrix. We sat down to watch a movie and while browsing to my files I got the "Operation Not Permitted" error. It quickly dawned on me what that was all about and with the ice in my drink melting I went into the Kodi settings and changed all SMB Client settings to SMBv1 and turned off all security settings.
Good movie.

Kodi defaults to SMBv3 on install. I can set up Windows and Kodi to work together on SMBv3, but then my 4 home networked W10 PC's can't see each other. That's the annoying thing - I don't have mixed OS here. Why won't it just work?

Until there is an easy, reliable way to set up a private home network that just works (like a 6 step tutorial) then people like me are just going to take the small risk (as Jimbo45 has been saying) to get things working - now.

Is there a tutorial somewhere that takes you step by step to set up a secure network that just works?

Hi there
current release (Kodi 19) allows you to set "Min protocol" but I still need SMB1 to access my NAS from amazon firestick to play multi-media into a smart TV using the firestick.

I'm still on Kodi 17.x as the Video seems infinitely better than with the latest versions runs more smoothly -- could be because I haven't got all the settings correct - but if it works why bother. I skipped all the kodi V18 versions.

Cheers
jimbo