[prev in list] [next in list] [prev in thread] [next in thread] 

List:       samba
Subject:    Re: [Samba] Legacy samba 3.x connecting to server 2022
From:       Rowland Penny via samba <samba () lists ! samba ! org>
Date:       2024-02-29 19:10:59
Message-ID: 20240229191059.2900f0c1 () devstation ! samdom ! example ! com
[Download RAW message or body]

On Wed, 28 Feb 2024 17:09:44 -0500
Greg Dickie via samba <samba@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
[prev in list] [next in list] [prev in thread] [next in thread]