SMBv1 is removed in the Windows 10 Insider Preview Build 16226
-
@scottalanmiller said in SMBv1 is removed in the Windows 10 Insider Preview Build 16226:
Not surprising, actually probably a very good thing. Nothing should be using SMB 1 today. SMB 2 and CIFS replaced that a ridiculously long time ago.
The same can be said for 2... 3.x has been out for 5+ years
-
@Dashrender said in SMBv1 is removed in the Windows 10 Insider Preview Build 16226:
@scottalanmiller said in SMBv1 is removed in the Windows 10 Insider Preview Build 16226:
Not surprising, actually probably a very good thing. Nothing should be using SMB 1 today. SMB 2 and CIFS replaced that a ridiculously long time ago.
The same can be said for 2... 3.x has been out for 5+ years
Not the same thing. SMB 3 has different features. SMB 2 / CIFS might be venerable but it is still highly useful and reasonable to use.
Not quite the same as NFS 3 and NFS 4, but we intentionally use NFS 3 much of the time today even though NFS 4 is old.
Also SMB 3 might be "mature" at this point, but it doesn't have broad compatibility yet. So removing SMB 2 from Windows would cripple Windows making it unable to communicate with nearly all NAS and non-Windows native devices.
-
@scottalanmiller That's the sad truth...
-
@scottalanmiller said in SMBv1 is removed in the Windows 10 Insider Preview Build 16226:
Not quite the same as NFS 3 and NFS 4, but we intentionally use NFS 3 much of the time today even though NFS 4 is old.
This may be good for a fork...but why hang on to NFSv3 instead of stepping up to NFSv4??
-
@scottalanmiller said in SMBv1 is removed in the Windows 10 Insider Preview Build 16226:
Not surprising, actually probably a very good thing. Nothing should be using SMB 1 today. SMB 2 and CIFS replaced that a ridiculously long time ago.
Copiers do (scan to folder), unless you pay ridiculous money to upgrade... I'll spare the rant.
-
@Tim_G said in SMBv1 is removed in the Windows 10 Insider Preview Build 16226:
@scottalanmiller said in SMBv1 is removed in the Windows 10 Insider Preview Build 16226:
Not surprising, actually probably a very good thing. Nothing should be using SMB 1 today. SMB 2 and CIFS replaced that a ridiculously long time ago.
Copiers do (scan to folder), unless you pay ridiculous money to upgrade... I'll spare the rant.
But IMO, security trumps functionality. Kill SMB1.0.
-
@dafyre said in SMBv1 is removed in the Windows 10 Insider Preview Build 16226:
@scottalanmiller said in SMBv1 is removed in the Windows 10 Insider Preview Build 16226:
Not quite the same as NFS 3 and NFS 4, but we intentionally use NFS 3 much of the time today even though NFS 4 is old.
This may be good for a fork...but why hang on to NFSv3 instead of stepping up to NFSv4??
Because the work differently and having the overhead of NFSv4 often does not make sense.
-
@scottalanmiller said in SMBv1 is removed in the Windows 10 Insider Preview Build 16226:
@dafyre said in SMBv1 is removed in the Windows 10 Insider Preview Build 16226:
@scottalanmiller said in SMBv1 is removed in the Windows 10 Insider Preview Build 16226:
Not quite the same as NFS 3 and NFS 4, but we intentionally use NFS 3 much of the time today even though NFS 4 is old.
This may be good for a fork...but why hang on to NFSv3 instead of stepping up to NFSv4??
Because the work differently and having the overhead of NFSv4 often does not make sense.
Can you give more detail?
-
@Dashrender said in SMBv1 is removed in the Windows 10 Insider Preview Build 16226:
@scottalanmiller said in SMBv1 is removed in the Windows 10 Insider Preview Build 16226:
@dafyre said in SMBv1 is removed in the Windows 10 Insider Preview Build 16226:
@scottalanmiller said in SMBv1 is removed in the Windows 10 Insider Preview Build 16226:
Not quite the same as NFS 3 and NFS 4, but we intentionally use NFS 3 much of the time today even though NFS 4 is old.
This may be good for a fork...but why hang on to NFSv3 instead of stepping up to NFSv4??
Because the work differently and having the overhead of NFSv4 often does not make sense.
Can you give more detail?
IIRC NFSv4 is a statful protocol. It uses TCP instead of UDP so there is a not insignificant amount of network and processing overhead when moving from NFSv3 to NFSv4.
-
@Dashrender said in SMBv1 is removed in the Windows 10 Insider Preview Build 16226:
@scottalanmiller said in SMBv1 is removed in the Windows 10 Insider Preview Build 16226:
@dafyre said in SMBv1 is removed in the Windows 10 Insider Preview Build 16226:
@scottalanmiller said in SMBv1 is removed in the Windows 10 Insider Preview Build 16226:
Not quite the same as NFS 3 and NFS 4, but we intentionally use NFS 3 much of the time today even though NFS 4 is old.
This may be good for a fork...but why hang on to NFSv3 instead of stepping up to NFSv4??
Because the work differently and having the overhead of NFSv4 often does not make sense.
Can you give more detail?
They are very different protocols with a lot of different features. NFSv3 is much lighter than NFSv4.
