[opensuse] Leap 42.2 → 42.3, Samba stops working for Windows XP client
Hi people,
I'm managing a Samba server for a pretty small place. And for reasons outside
of my control, there's a single computer there that runs Windows XP. It is
not connected to the WAN, only to the LAN. That computer regularly needs
files from the Samba server.
A few days after Leap 42.3 came out, I upgraded the server. Everything was
smooth sailing, except the Windows XP computer could no longer connect to the
Samba share. Every other computer could, except that one. Is there a known
incompatibility introduced in the upgrade from Samba 4.4 to 4.6? I've looked
around, but I wasn't able to find anything.
I rolled the server back to 42.2 using Snapper (which was also smooth sailing,
thankfully), but I have to finish the upgrade within four-ish weeks.
Any help would be very much appreciated.
Best regards,
Carmen
--
Carmen Bianca Bakker
On 29 July 2017 at 09:52, Carmen Bianca Bakker
Hi people,
I'm managing a Samba server for a pretty small place. And for reasons outside of my control, there's a single computer there that runs Windows XP. It is not connected to the WAN, only to the LAN. That computer regularly needs files from the Samba server.
A few days after Leap 42.3 came out, I upgraded the server. Everything was smooth sailing, except the Windows XP computer could no longer connect to the Samba share. Every other computer could, except that one. Is there a known incompatibility introduced in the upgrade from Samba 4.4 to 4.6? I've looked around, but I wasn't able to find anything.
I rolled the server back to 42.2 using Snapper (which was also smooth sailing, thankfully), but I have to finish the upgrade within four-ish weeks.
Any help would be very much appreciated.
Best regards, Carmen
My guess (note...GUESS..there is no way in a million years I will ever put a Windows XP machine near a network in 2017 to test this for anyone) is that the problem could be the changes introduced in 4.5 https://www.samba.org/samba/history/samba-4.5.0.html Maybe the windows XP machine is using NTLMv1 by default and that is (for VERY good reasons) disabled in Samba now. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Saturday, 29 July 2017 11:34:22 CEST Richard Brown wrote:
My guess (note...GUESS..there is no way in a million years I will ever put a Windows XP machine near a network in 2017 to test this for
Honestly, if it were up to me, I wouldn't put an ethernet cable in _any_ Windows machine. But it's volunteer work and I don't own the place, so yeah...
https://www.samba.org/samba/history/samba-4.5.0.html
Maybe the windows XP machine is using NTLMv1 by default and that is (for VERY good reasons) disabled in Samba now.
Thank you very much! I'll look into that.
--
Carmen Bianca Bakker
participants (2)
-
Carmen Bianca Bakker -
Richard Brown