Hey Rowland,
Thanks for the reply. It was indeed SMB1 that was missing. It had been
installed but not rebooted so of course was not working. I know we have a
mix of versions but some 3.6 which should be able to do SMB2 so I'll
definitely try that out. It was just kind of a surprise that they updated.
Of course they also had issues with old Windows 2003 servers that also need
SMB1.
Appreciate the help,
thanks,
Greg
On Thu, Feb 29, 2024 at 2:11?PM Rowland Penny via samba <
samba at lists.samba.org> wrote:
> On Wed, 28 Feb 2024 17:09:44 -0500
> Greg Dickie via samba <samba at lists.samba.org> wrote:
>
> > Hi,
> >
> > Stupid question. Legacy installation as far as linux servers goes
> > but the windows admins have just got rid of all the DCS less than
> > server 2022 and suddenly all the samba 3.x machines cannot talk to
> > the DCs or rejoin the domain.
> >
> > net ads join -d 10 showed port 445 was not responding so I enabled
> > SMB1 but I'm guessing there are some ciphers at least that are not
> > compatible. Some of these are RH5 machines and cannot be upgraded so
> > is there anyway to coax server 2022 to let them in?
> >
>
> I think you need to talk to the Windows admins to find out just what
> the new DCs are capable of, they should be using port 445 as that is
> the SMB TCP port, have they turned off NTLM ???
>
> I think it is highly likely that SMBv1 is turned off, Microsoft now
> does this by default.
>
> You refer to Samba 3.x , but what versions ? It has been a long time
> since I used any Samba 3 version, but I think you need 3.5.x at least
> for SMBv2 and I also seem to remember that RHEL5 was capable of 3.6.x
>
> Once you do get things working again, can I suggest you then start
> making plans to upgrade everything.
>
> Rowland
>
>
> --
> To unsubscribe from this list go to the following URL and read the
> instructions: https://lists.samba.org/mailman/options/samba
>
--
Greg Dickie
just a guy
514-983-5400