[opensuse] Smb protocol version 1 support with 15.2? Can I use samba packages from 15.1?
On some upgraded 15.1 system to the new 15.2 meanwhile, I have figured that smb protocol version 1 is seemingly gone for good now on the server side.
In this network I have a smb version 1 level client only, and I used to connect to the suse leap 15.1 samba there.
could solve my problem by removing the samba packages from the 15.2 machine and force installing the 15.1 packages from the earlier version?
TY.
On 09/07/2020 11.39, cagsm wrote:
On some upgraded 15.1 system to the new 15.2 meanwhile, I have figured that smb protocol version 1 is seemingly gone for good now on the server side.
Impossible. Leap 15.2 has samba.
samba-4.11.5+git.161.74bc5e6ec8e-lp152.2.12.x86_64.rpm
On Thu, 9 Jul 2020 12:24:07 +0200 "Carlos E. R." robin.listas@telefonica.net wrote:
On 09/07/2020 11.39, cagsm wrote:
On some upgraded 15.1 system to the new 15.2 meanwhile, I have figured that smb protocol version 1 is seemingly gone for good now on the server side.
Impossible. Leap 15.2 has samba.
samba-4.11.5+git.161.74bc5e6ec8e-lp152.2.12.x86_64.rpm
https://wiki.samba.org/index.php/Samba_4.11_Features_added/changed#SMB1_is_d...
On Thu, Jul 9, 2020 at 12:28 PM Carlos E. R. robin.listas@telefonica.net wrote:
On 09/07/2020 11.39, cagsm wrote:
On some upgraded 15.1 system to the new 15.2 meanwhile, I have figured that smb protocol version 1 is seemingly gone for good now on the server side.
Impossible. Leap 15.2 has samba. samba-4.11.5+git.161.74bc5e6ec8e-lp152.2.12.x86_64.rpm
I already researched this, samba 4.11 has smb1 removed even, somewhere I read only with very special commands or parameters the samba client apps can still be made to connect to smb v1 servers, but samba server doesnt have smb v1 protocol any more.
as others in this thread also pointed this out.
So question is, I dont recall the exact version number of samba4 on leap 15.1 any more but that server was still able to serve old smb v1 clients in this network. Can I revert back to those packages?
Even more invasive question: is it possible to revert a zypper dup upgrade or a opensuse upgrade in general to its former state? or can one zypper dup downgrade with the old repos in just the same way or similar? TY
On Thu, 9 Jul 2020 13:09:57 +0200 cagsm cumandgets0mem00f@gmail.com wrote:
On Thu, Jul 9, 2020 at 12:28 PM Carlos E. R. robin.listas@telefonica.net wrote:
On 09/07/2020 11.39, cagsm wrote:
On some upgraded 15.1 system to the new 15.2 meanwhile, I have figured that smb protocol version 1 is seemingly gone for good now on the server side.
Impossible. Leap 15.2 has samba. samba-4.11.5+git.161.74bc5e6ec8e-lp152.2.12.x86_64.rpm
I already researched this, samba 4.11 has smb1 removed even, somewhere I read only with very special commands or parameters the samba client apps can still be made to connect to smb v1 servers, but samba server doesnt have smb v1 protocol any more.
"It's still possible to allow SMB1 dialects, e.g. NT1, LANMAN2 and LANMAN1 for client and server, as well as CORE and COREPLUS on the client"
Note the word 'server'?
as others in this thread also pointed this out.
So question is, I dont recall the exact version number of samba4 on leap 15.1 any more but that server was still able to serve old smb v1 clients in this network. Can I revert back to those packages?
Even more invasive question: is it possible to revert a zypper dup upgrade or a opensuse upgrade in general to its former state? or can one zypper dup downgrade with the old repos in just the same way or similar? TY
On Thu, Jul 9, 2020 at 2:29 PM Dave Howorth dave@howorth.org.uk wrote:
"It's still possible to allow SMB1 dialects, e.g. NT1, LANMAN2 and LANMAN1 for client and server, as well as CORE and COREPLUS on the client" Note the word 'server'?
Some windows XP client can not access the machine any more though, log.smdb output:
[2020/07/08 01:01:11.229780, 3] ../../lib/util/access.c:371(allow_access) Allowed connection from 10.z.x.y (10.z.x.y) [2020/07/08 01:01:11.230157, 3] ../../source3/smbd/oplock.c:1414(init_oplocks) init_oplocks: initializing messages. [2020/07/08 01:01:11.230205, 3] ../../source3/smbd/process.c:1956(process_smb) Transaction 0 of length 137 (0 toread) [2020/07/08 01:01:11.230217, 3] ../../source3/smbd/process.c:1549(switch_message) switch message SMBnegprot (pid 26327) conn 0x0 [2020/07/08 01:01:11.230492, 3] ../../source3/smbd/negprot.c:637(reply_negprot) Requested protocol [PC NETWORK PROGRAM 1.0] [2020/07/08 01:01:11.230510, 3] ../../source3/smbd/negprot.c:637(reply_negprot) Requested protocol [LANMAN1.0] [2020/07/08 01:01:11.230518, 3] ../../source3/smbd/negprot.c:637(reply_negprot) Requested protocol [Windows for Workgroups 3.1a] [2020/07/08 01:01:11.230525, 3] ../../source3/smbd/negprot.c:637(reply_negprot) Requested protocol [LM1.2X002] [2020/07/08 01:01:11.230531, 3] ../../source3/smbd/negprot.c:637(reply_negprot) Requested protocol [LANMAN2.1] [2020/07/08 01:01:11.230537, 3] ../../source3/smbd/negprot.c:637(reply_negprot) Requested protocol [NT LM 0.12] [2020/07/08 01:01:11.230607, 3] ../../source3/smbd/negprot.c:757(reply_negprot) reply_negprot: No protocol supported ! [2020/07/08 01:01:11.230740, 3] ../../source3/smbd/server_exit.c:244(exit_server_common) Server exit (no protocol supported )
-----------
Thought e.g. Windows XP can't talk to samba Version 4.11 any more. How do I make it work again? TY
cagsm wrote:
Thought e.g. Windows XP can't talk to samba Version 4.11 any more. How do I make it work again?
By enabling SMB1 in your Samba server config - I think the option is called "client min protocol".
Note - a little bit of googling would have gotten you the same answer, in seconds. "samba 4.11 smb1".
On Thu, Jul 9, 2020 at 4:22 PM Per Jessen per@computer.org wrote:
cagsm wrote: By enabling SMB1 in your Samba server config - I think the option is called "client min protocol".
thanks for this info but I already had the client min protocol on NT1 setting, but apparently only a server min protocol set to NT1 as well fixed this issue for me always been using the client min/max protocol settings so far.
thanks anyways for making me dig around some more. the windows xp client can now connect again to the samba version which comes with leap 15.2
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
El 2020-07-09 a las 13:09 +0200, cagsm escribió:
On Thu, Jul 9, 2020 at 12:28 PM Carlos E. R. <> wrote:
On 09/07/2020 11.39, cagsm wrote:
On some upgraded 15.1 system to the new 15.2 meanwhile, I have figured that smb protocol version 1 is seemingly gone for good now on the server side.
Impossible. Leap 15.2 has samba. samba-4.11.5+git.161.74bc5e6ec8e-lp152.2.12.x86_64.rpm
I already researched this, samba 4.11 has smb1 removed even, somewhere I read only with very special commands or parameters the samba client apps can still be made to connect to smb v1 servers, but samba server doesnt have smb v1 protocol any more.
Sorry, somehow I missed that it is version one the problem.
as others in this thread also pointed this out.
So question is, I dont recall the exact version number of samba4 on leap 15.1 any more but that server was still able to serve old smb v1 clients in this network. Can I revert back to those packages?
Even more invasive question: is it possible to revert a zypper dup upgrade or a opensuse upgrade in general to its former state? or can one zypper dup downgrade with the old repos in just the same way or similar? TY
Ye.e.e.s... (doubtful of success)
(remember that I recomend a full backup prior to the upgrade?)
- -- Cheers Carlos E. R.
(from openSUSE 15.1 (Legolas))
On Thu, 9 Jul 2020 19:39:36 +0200 (CEST) "Carlos E. R." robin.listas@telefonica.net wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
El 2020-07-09 a las 13:09 +0200, cagsm escribió:
On Thu, Jul 9, 2020 at 12:28 PM Carlos E. R. <> wrote:
On 09/07/2020 11.39, cagsm wrote:
On some upgraded 15.1 system to the new 15.2 meanwhile, I have figured that smb protocol version 1 is seemingly gone for good now on the server side.
Impossible. Leap 15.2 has samba. samba-4.11.5+git.161.74bc5e6ec8e-lp152.2.12.x86_64.rpm
I already researched this, samba 4.11 has smb1 removed even, somewhere I read only with very special commands or parameters the samba client apps can still be made to connect to smb v1 servers, but samba server doesnt have smb v1 protocol any more.
Sorry, somehow I missed that it is version one the problem.
And you somehow missed that he posted two+half hours before you that in fact it does work and he's sorted it?
as others in this thread also pointed this out.
So question is, I dont recall the exact version number of samba4 on leap 15.1 any more but that server was still able to serve old smb v1 clients in this network. Can I revert back to those packages?
Even more invasive question: is it possible to revert a zypper dup upgrade or a opensuse upgrade in general to its former state? or can one zypper dup downgrade with the old repos in just the same way or similar? TY
Ye.e.e.s... (doubtful of success)
(remember that I recomend a full backup prior to the upgrade?)
Cheers Carlos E. R.
(from openSUSE 15.1 (Legolas))-----BEGIN PGP SIGNATURE-----
iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCXwdWWBwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVBsgAoJhCMQ36cbwX0gskoha8 u17sMo5JAJ9yd/H49fSRa63wblnaWXgiy9jPTg== =B6VF -----END PGP SIGNATURE-----
On 09/07/2020 21.02, Dave Howorth wrote:
On Thu, 9 Jul 2020 19:39:36 +0200 (CEST) "Carlos E. R." <> wrote:
El 2020-07-09 a las 13:09 +0200, cagsm escribió:
On Thu, Jul 9, 2020 at 12:28 PM Carlos E. R. <> wrote:
On 09/07/2020 11.39, cagsm wrote:
On some upgraded 15.1 system to the new 15.2 meanwhile, I have figured that smb protocol version 1 is seemingly gone for good now on the server side.
Impossible. Leap 15.2 has samba. samba-4.11.5+git.161.74bc5e6ec8e-lp152.2.12.x86_64.rpm
I already researched this, samba 4.11 has smb1 removed even, somewhere I read only with very special commands or parameters the samba client apps can still be made to connect to smb v1 servers, but samba server doesnt have smb v1 protocol any more.
Sorry, somehow I missed that it is version one the problem.
And you somehow missed that he posted two+half hours before you that in fact it does work and he's sorted it?
Well, I read the mails one by one. I read one, if it is for me, I reply. Then I read the next post. Thus I saw later that he had solved the issue.
Le 09/07/2020 à 21:15, Carlos E. R. a écrit :
Well, I read the mails one by one. I read one, if it is for me, I reply. Then I read the next post. Thus I saw later that he had solved the issue.
best is to read, and let aside if for you, then read ahead :-)
jdd
jdd composed on 2020-07-09 21:53 (UTC+0200):
Carlos E. R. composed:
Well, I read the mails one by one. I read one, if it is for me, I reply. Then I read the next post. Thus I saw later that he had solved the issue.
best is to read, and let aside if for you, then read ahead :-)
Even so, often while composing reply, more shows up that is not seen until after sending.
On 07/09/2020 04:39 AM, cagsm wrote:
On some upgraded 15.1 system to the new 15.2 meanwhile, I have figured that smb protocol version 1 is seemingly gone for good now on the server side.
In this network I have a smb version 1 level client only, and I used to connect to the suse leap 15.1 samba there.
could solve my problem by removing the samba packages from the 15.2 machine and force installing the 15.1 packages from the earlier version?
TY.
Beginning with samba 4.11 smb1 is disabled by default. To enable (if you can't get the client to use smb2 or higher)
Edit /etc/samba/smb.conf and add
client min protocol = NT1 server min protocol = NT1
to the global section to restore workgroups and SMB1
restart samba
On Fri, Jul 10, 2020 at 4:47 AM David C. Rankin drankinatty@suddenlinkmail.com wrote:
On 07/09/2020 04:39 AM, cagsm wrote:
On some upgraded 15.1 system to the new 15.2 meanwhile, I have figured that smb protocol version 1 is seemingly gone for good now on the server side.
Beginning with samba 4.11 smb1 is disabled by default. To enable (if you can't get the client to use smb2 or higher) Edit /etc/samba/smb.conf and add client min protocol = NT1 server min protocol = NT1 to the global section to restore workgroups and SMB1 restart samba
Yes thanks again also to everybody, I ended up doing exactly this. TY.
-
cagsm -
Carlos E. R. -
Dave Howorth -
David C. Rankin -
Felix Miata -
jdd＠dodin.org -
Per Jessen