[Samba] Laptops unable to access Windows SMB share
Rowland Penny
rpenny at samba.org
Fri Jan 24 09:18:56 UTC 2025
On Thu, 23 Jan 2025 20:12:54 +0000
Stephen Brandli <steve at brandli.com> wrote:
> Thanks for the reply. I agree it's reasonable to expect me to update
> to see if that fixes the problem. I have started that very long
> process. I would not have bothered you all except, in the meantime,
> we have a real problem with the laptops. Also, since the fixed
> machines do not have the problem, I can see only two reasons for it:
> (1) The laptops are relying on broadcast, which isn't getting
> transmitted from Unsecure 2 (which has no domain controllers) to
> Secure 2, or there is something about moving the laptops around with
> the associated changes in IPs. I was hoping that someone knew what
> was happening.
>
> To answer your questions: I did put in my admittedly long description
> that these are Samba domain controllers (4.13.13). They are on
> Bullseye. The Samba fileserver that works with the laptops is on
> Buster. The laptops are Windows 10 fully updated as is the Windows
> file server that isn't working with the laptops.
>
I wonder if SMBv1 has anything to do with your problem ?
I ask this because Samba changed the default to a minimum of SMBv2 at
4.11.0.
You may be hitting a bug and if you are and it has been fixed in a
later version, then you have no chance of getting it fixed in versions
of Samba that you are using now, they are all EOL from the Samba point
of view. The fix is to upgrade, if at that point, you still are having
problems, then you at least stand a chance of getting it fixed. Can I
suggest you upgrade everything to Debian 12 and use Samba from
bookworm-backports, this will get you the very latest version of Samba.
Rowland
More information about the samba
mailing list