On Thu, 12 Sep 2019, John Hodrien wrote:

On Thu, 12 Sep 2019, qw wrote:

...

Hi,

I can access centos's samba via windows 7, but fail via windows 10. Why?

I'm pretty sure this is because the default Samba config doesn't enable SMB2.

Make sure this is set in your smb.conf and I think you should be good:

[global] max protocol = SMB2

Why? This is NOT necessary for win 10 to work. I do not even know if it will work with win 10 but for sure it is not necessary. You are actually suggesting going backwards.

From the smb.conf man page:

Default: server max protocol = SMB3

By default SMB3 selects the SMB3_11 variant.

SMB3_11: Windows 10 technical preview SMB3 version (maybe final).

I have a half dozen or so samba file servers that have a combination of win7 and win10 versions running and none of the config files contain anything that changes the SMB version.

I would suspect if you have to mess with the SMB protocols to get win 10 to talk, you are doing something else wrong.

Regards,

Hi,

windows 7 supports smb3. If centos's samba server suport smb3, how to make windows 10 support smb3 too?

Thanks!

Regards

Andrew

At 2019-09-13 15:47:34, "John Hodrien" J.H.Hodrien@leeds.ac.uk wrote:

On Thu, 12 Sep 2019, me@tdiehl.org wrote:

...

Why? This is NOT necessary for win 10 to work. I do not even know if it will work with win 10 but for sure it is not necessary. You are actually suggesting going backwards.

You're spot on, sorry. This was CentOS 6 samba3 advice, carelessly thrown out for C7.

jh _______________________________________________ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos

On Fri, 13 Sep 2019, John Pierce wrote:

On Fri, Sep 13, 2019 at 8:42 AM qw applemax82@163.com wrote:

...

windows 7 supports smb3. If centos's samba server suport smb3, how to make windows 10 support smb3 too?

with min_protocol=SMB3, windows 7 will use SMB3_00, while windows 10 will use SMB3_11 and everyone should be happy.

Setting min_protocol is not necessary centos 7 for win7 or win 10 to work.

The defaults work just fine. If they didn't I would have 300 or so unhappy users. :-)

Regards,

I update centos's samba to 4.8.3-6. My windows 10 is professional, whose version is 1803. I still can't access samba. Do I need update my windows 10 to 1903?

andrew

At 2019-09-12 17:45:10, "anax" anax@ayni.com wrote:

On 12/09/2019 11.09, qw wrote:

...

Hi,

I can access centos's samba via windows 7, but fail via windows 10. Why?

Thanks!

Regards

Andrew _______________________________________________ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos

Hi Andrew

No problem here with:

Centos:

CentOS Linux release 7.6.1810 (Core)

and Samba:

samba-client-libs-4.8.3-6.el7_6.x86_64 samba-4.8.3-6.el7_6.x86_64 samba-common-4.8.3-6.el7_6.noarch samba-libs-4.8.3-6.el7_6.x86_64 samba-client-4.8.3-6.el7_6.x86_64 samba-common-libs-4.8.3-6.el7_6.x86_64 samba-common-tools-4.8.3-6.el7_6.x86_64

Windows 10:

Windows 10 Home, Version 1903

suomi _______________________________________________ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos

Hello, Anax

My shared drives were inaccessible after updating my windows 10 to the latest “Windows 10 Fall Creators Update”.

Within the latest “Windows 10 Fall Creators Update” the Guest access in SMB2 is disabled by default.

You can change this setting within your group policy settings.

Right click the Windows Icon at the bottom left of the task bar, or select the windows key + r

Within the run box, type “gpedit.msc”

Within the local Group Policy Editor, select “Administrative Templates”

Select “Network”

Select ”Lanman Workstation”

Double click “Enable Insecure guest logons” option

Tick the “Enable” option

Select OK

On 12.9.2019 г. 14:43, anax wrote:

Regards

On 9/12/19 2:14 PM, Fred Smith wrote:

On Thu, Sep 12, 2019 at 02:02:20PM +0200, Michael Schumacher wrote:

...

Thursday, September 12, 2019, 11:09:36 AM, you wrote:

q> I can access centos's samba via windows 7, but fail via windows 10. Why?

You might want to provide your /etc/samba/smb.conf so that we can take a look. There are so many ways to operate Samba that it is impossible to help without.

when I ran into the same issue, adding the following lines to the global section of "smb.conf" made things ok: client min protocol = SMB2 client max protocol = SMB3

SMB version 1 should not be used in any case and MS deprecated its use in W10 AIUI HTH

You should also ensure you're not suffering a selinux blockage. I've had that happen with Samba.

Fred