Topic: Windows 10 remove SMB 1 - SMBServer share no longer accessible

[Stefano]

@Stefano - 1803 arrived completely automatically - just happened (honestly). Not forgetting that this (SME-to-MSW alleged connectivity WITHOUT SMBv1) hasn't worked for me ever - going back to at least SME7 if not before - memory blurred back then.

I know what I mean.. and we're testing w10 1803 'cause it seems to be able to break working machines (strange enough, isn't it?)
my feeling is that we're all beta testers here (and unfortunately not for SME)

[piran]

Hasn't broken anything on three of my machines. The Autumn version was unattainable by two of those three machines and could NOT be forced, eventually had to do bare metal rebuilds - including for a MS Surface Book! This time everything progressed ...as if by clockwork.

SMB Direct
https://en.wikipedia.org/wiki/Server_Message_Block
https://en.wikipedia.org/wiki/Remote_direct_memory_access

Now awaiting a "In Your Dreams" retort from one CB:-)

[Brenno]

what is the output of :

Code: [Select]

config show smb

Here's the output:

Code: [Select]

[root@webserv ~]# config show smb
smb=service
    DeadTime=10080
    KeepVersions=disabled
    OpLocks=enabled
    OsLevel=35
    RecycleBin=disabled
    RoamingProfiles=no
    ServerMaxProtocol=SMB2
    ServerName=webserv
    ServerRole=WS
    ShadowCount=10
    ShadowDir=/home/e-smith/files/.shadow
    UnixCharSet=UTF8
    UseClientDriver=yes
    Workgroup=sme-server
    status=enabled
[root@webserv ~]#

if you set config setprop smb ServerMinProtocol SMB2; then having SMB1 not working is the intended behaviour.

I did not set the ServerMinProtocol property.

What are the windows version trying to connect to the SME ?Do they have SMB2 enabled.

Windows 7 Professional, Windows 2012r2 and Windows 10.  All have SMB2 enabled because we have SMB1 disabled on all.

Sounds like we're out of luck on this for a while, which is a shame.  It's really only me that needs periodic access and I can likely do what I need with WinSCP (or even FTP), so I can live with it.

[bas60]

Just checking..

No solution for 9.2 without enabling SMB1.0 ?

[Jean-Philippe Pialasse]

We are investigating if if can upgrade to samba 4 using the centos samba4 rpms, it seems hazardous as the implementation is not complete, and some rpm like libsmbclient are missing.

Without thos possibility, yes only SMB1 protocol is compatible between samba 3, inlcuded in SME9,  and Win 10.

[tdbsoft]

Hi Everyone,

has there been any update about Samba on SME 9.2 fix for Windows 10 domain login and SMB 2 or 3 share access.

Windows 7 support deadline is 14 Jan 2020. and windows 10 computers are becoming more common and currently can't logon to the domain at all for windows 10 1809 or newer and SMB V1 has be to readded for share use. It could be entirely possible that Microsoft could remove the ability to add SMB V1 at any point in the next feature update. which break existing fixes and render them unusable.

Can anyone advise?

[ReetP]

Hi Everyone,

has there been any update about Samba on SME 9.2 fix for Windows 10 domain login and SMB 2 or 3 share access.

No because Samba 3.x can't do SMB v3. The only long term solution for SMBv3 is Samba 4, and that isn't going to happen on SME v9. There isn't enough time to be worthwhile, and we don't have the manpower to try and implement it - it is a huge amount of work. Lots of people 'want' but no one is prepared to actually get their hands dirty and do some work.

Windows 7 support deadline is 14 Jan 2020. and windows 10 computers are becoming more common and currently can't logon to the domain at all for windows 10 1809 or newer and SMB V1 has be to readded for share use. It could be entirely possible that Microsoft could remove the ability to add SMB V1 at any point in the next feature update. which break existing fixes and render them unusable.

No, as far as I am aware Windows 10 can do domain logons since M$ re enabled it, and allows install of SMBv1 and SMBv2 for network browsing. Please see the various threads, bugs, and M$ documentation on this on this.

Note that I believe there were two actually slightly different issues at the same time - removal of SMBv1 which disabled share browsing, and something else that disabled domain logons. They appeared to be one and the same but were not.

If you actually searched the bugs you would also find things like this:

https://bugs.contribs.org/show_bug.cgi?id=10575

So you can enable max protocol SMB2 for network browsing but I am not sure you can still use domain logons with this if you set min protocol SMB2 as well - I think Samba has to be able to handle the NT protocol as well for 'legacy' domain logons (but you need to test - I have no Windows machines at all to test with)

Yes, they could remove it or break it again. My suspicion is they will keep it there until RHEL/CentOS6 goes EOL.

If you are worried about it then the best thing you can do is stop using Windows, or help us get SME v10 out of the door. It won't happen by itself. And yes, we all have families, kids and jobs too.

[ReetP]

As an addendum I think the following is true but E&OE.....

SMBv1 uses the NETBIOS protocol which enables the old style windows network browsing.

SMBv2 does not. I believe you can still connect using a direct URL or mapped drive, but you cannot use network browsing.

I cannot confirm which protocol you need to install to restore Domain logon functionality as we have no 'Pro' machines to test with (it's the sort of thing we need a hand with)

[Milliron]

Just out of curiosity, what would be a 'pro' machine, ReetP?

[janet]

Just out of curiosity, what would be a 'pro' machine, ReetP?

He is referring to Windows 10 Professional which supports DOMAIN login, as compared to Windows 10 Home (which does not support DOMAIN login).

[ReetP]

He is referring to Windows 10 Professional which supports DOMAIN login, as compared to Windows 10 Home (which does not support DOMAIN login).

:thumbsup:

Beat me to it thanks !!