Author Topic: Samba Server v4.11.9  (Read 2092 times)

Paul Smedley

  • Hero Member
  • *****
  • Thank You
  • -Given: 22
  • -Receive: 70
  • Posts: 606
    • View Profile
Re: Samba Server v4.11.9
« Reply #15 on: June 25, 2020, 11:17:09 pm »
Hi Mike,

Most useful would be a log.smbd.exe with debuglevel of 3 and an attempt to connect from win10...

Here you are.

Greetings,
Mike

Here's the relevant part:
[2020/06/25 16:11:47.936000,  2] ../../libcli/auth/ntlm_check.c:429(ntlm_password_check)
  ntlm_password_check: NTLMv1 passwords NOT PERMITTED for user Mike
[2020/06/25 16:11:47.936000,  3] ../../libcli/auth/ntlm_check.c:436(ntlm_password_check)
  ntlm_password_check: NEITHER LanMan nor NT password supplied for user Mike
[2020/06/25 16:11:47.936000,  2] ../../source3/auth/auth.c:343(auth_check_ntlm_password)
  check_ntlm_password:  Authentication for user [Mike] -> [Mike] FAILED with error NT_STATUS_WRONG_PASSWORD, authoritative=1

As suspected, it looks like you've downgraded Win10 to use a lower grade authentication scheme to be compatible with older Samba versions...

NTLMv1 was disabled by default a few Samba versions ago. If you want to keep Win10 compatible with Samba 3.6, you can add (I think)
ntlm auth = yes

to the global section of your smb.conf

Of course, the better option for security would be to move 100% to Samba 4.x and fix Win10 :)

Cheers,

Paul

Mike Kölling

  • Jr. Member
  • **
  • Thank You
  • -Given: 0
  • -Receive: 3
  • Posts: 65
    • View Profile
Re: Samba Server v4.11.9
« Reply #16 on: June 26, 2020, 09:21:28 am »

NTLMv1 was disabled by default a few Samba versions ago. If you want to keep Win10 compatible with Samba 3.6, you can add (I think)
ntlm auth = yes
to the global section of your smb.conf


Hi Paul,

That did the trick. I can't go up to the security level of Samba 4 by now, because we still run an old file server (with eCS2.0RC6a) with an old Samba 3.0 server - Never touch a running system :).
And the Win 10 machine must see this old file server.

Thanks for your help to solve the issue.
Wish you a nice weekend.

Greetings from Potsdam / Germany,
Mike
« Last Edit: June 26, 2020, 09:25:03 am by Mike Kölling »

Paul Smedley

  • Hero Member
  • *****
  • Thank You
  • -Given: 22
  • -Receive: 70
  • Posts: 606
    • View Profile
Re: Samba Server v4.11.9
« Reply #17 on: June 26, 2020, 10:44:24 am »
Hi Mike,


NTLMv1 was disabled by default a few Samba versions ago. If you want to keep Win10 compatible with Samba 3.6, you can add (I think)
ntlm auth = yes
to the global section of your smb.conf

That did the trick. I can't go up to the security level of Samba 4 by now, because we still run an old file server (with eCS2.0RC6a) with an old Samba 3.0 server - Never touch a running system :).
And the Win 10 machine must see this old file server.

Thanks for your help to solve the issue.
Wish you a nice weekend.

Glad it helped. Given you run both Samba 3.0 and now 4.11.9 I'm really interested in any comments on performance, stability, etc

Cheers,

Paul

Mike Kölling

  • Jr. Member
  • **
  • Thank You
  • -Given: 0
  • -Receive: 3
  • Posts: 65
    • View Profile
Re: Samba Server v4.11.9
« Reply #18 on: June 26, 2020, 01:23:28 pm »
Glad it helped. Given you run both Samba 3.0 and now 4.11.9 I'm really interested in any comments on performance, stability, etc

Hi Paul,

The old Samba server is restarted once every week automatically to avoid problems with the Samba server. The computer by itself needs to be restarted every second month usually. We needed some time debug the script files coming with the 3.0 but now it is stable enough for us. The biggest issue we have with the older Samba server are the remains of temporary files like "~name.docx" or ".~lock.name.odt" once we open files lets say in MS-Word or OpenOffice. After closing the files the temporary files still exists. We have to clean it manually from time to time. I never saw such a problem using the 3.6 or now with your 4.11 version. Another issue with the older Samba server is the rights management. Not sure if it is better now with the newer version, because testing has taken place mainly by my person with no access from other accounts.

Greetings,
Mike

Dariusz Piatkowski

  • Hero Member
  • *****
  • Thank You
  • -Given: 14
  • -Receive: 17
  • Posts: 728
    • View Profile
Re: Samba Server v4.11.9
« Reply #19 on: July 05, 2020, 05:29:21 pm »
Hi Paul,

Hi All,

I'm now at a point in Samba Server development where i'm prepared to publicly share some binaries based on Samba v4.11.9

Client tools/DLLs:
http://smedley.id.au/tmp/smbcl411-4.11.9-20200621.zip...

Yikes, I'm badly behind on this...

OK, Q re: the Samba client...any chance you can release the NetDrive plug-in as well to match the upgraded client?

I am going to give just the client a try, I think it's safe to toss everything into the \usr\local\... path, that way no impact on the RPM official releases.

Thanks!

Dariusz Piatkowski

  • Hero Member
  • *****
  • Thank You
  • -Given: 14
  • -Receive: 17
  • Posts: 728
    • View Profile
Re: Samba Server v4.11.9
« Reply #20 on: July 06, 2020, 09:41:05 pm »
Paul!

Hi Paul,

Hi All,

I'm now at a point in Samba Server development where i'm prepared to publicly share some binaries based on Samba v4.11.9

Client tools/DLLs:
http://smedley.id.au/tmp/smbcl411-4.11.9-20200621.zip...

Yikes, I'm badly behind on this...

OK, Q re: the Samba client...any chance you can release the NetDrive plug-in as well to match the upgraded client?

I am going to give just the client a try, I think it's safe to toss everything into the \usr\local\... path, that way no impact on the RPM official releases.

Thanks!

So I'm talking the Samba client only here, CLI test: the stuff works but it's reporting itself as a 4.11.5, so is this the right stuff you wanted tested?

I put all the EXEs into \usr\local\bin and DLLs into \usr\local\lib, both are present in the right places in CONFIG.SYS, and running specifically from the CLI with a FULL PATH to the EXE itself still produces a 4.11.5 output from '--version'.

For what it's worth, I have the following currently present:

1) samba-client-4.11.5-0.oc00.i686
Code: [Select]
Directory of G:\usr\bin

 1-25-20  6:46p        13,729    124 a---  smbcacls.exe
 1-25-20  6:46p     1,072,315    124 a---  smbclient.exe
 1-25-20  6:46p       153,715    124 a---  smbclient.map
 1-25-20  6:46p       138,390    124 a---  smbspool.exe
 1-25-20  6:46p         3,984    124 a---  smbtree.exe
        5 file(s)   1,382,133 bytes used

2) your test release
Code: [Select]
Directory of G:\usr\local\bin

 6-20-20  8:14p        18,971      0 a---  smbcacls.exe
 6-20-20  8:13p     1,087,293      0 a---  smbclient.exe
 6-20-20  8:13p       158,022      0 a---  smbclient.map
 6-20-20  8:13p       143,544      0 a---  smbspool.exe
 6-20-20  8:13p         9,022      0 a---  smbtree.exe
        5 file(s)   1,416,852 bytes used

Paul Smedley

  • Hero Member
  • *****
  • Thank You
  • -Given: 22
  • -Receive: 70
  • Posts: 606
    • View Profile
Re: Samba Server v4.11.9
« Reply #21 on: July 08, 2020, 08:22:48 am »
Hi Dariusz,

Sorry for the delayed response. For the Netdrive client, you need an updated smbcl411.dll - I'll try package one up soon.

Cheers,

Paul

Dariusz Piatkowski

  • Hero Member
  • *****
  • Thank You
  • -Given: 14
  • -Receive: 17
  • Posts: 728
    • View Profile
Re: Samba Server v4.11.9
« Reply #22 on: July 08, 2020, 07:47:44 pm »
Hey Paul,

...Sorry for the delayed response. For the Netdrive client, you need an updated smbcl411.dll - I'll try package one up soon...

No worries, but please take a look at the previous post of mine where I reported that the client EXEs are reporting as the prior version, that being: 4.11.5 instead of 4.11.9.

Thanks again,
-Dariusz