[Samba] Samba trying to connect to a non-existant DC for NTP?

[Rowland Penny]

On Wed, 14 Feb 2024 14:35:38 -0500
"James B. Byrne via samba" <samba at lists.samba.org> wrote:

> At about every 4 seconds the following messages are being created in
> /var/log/messages
> 
> Feb 14 14:05:25 smb4-2 samba[21026]: [2024/02/14 14:05:25.466141,  0]
> ../../source4/librpc/rpc/dcerpc_sock.c:63(continue_socket_connect)
> Feb 14 14:05:25 smb4-2 samba[21026]:   Failed to connect host
> 192.168.18.161 on port 135 - NT_STATUS_UNSUCCESSFUL
> Feb 14 14:05:25 smb4-2 samba[21026]: [2024/02/14 14:05:25.466529,  0]
> ../../source4/librpc/rpc/dcerpc_sock.c:245(continue_ip_open_socket)
> Feb 14 14:05:25 smb4-2 samba[21026]:   Failed to connect host
> 192.168.18.161
> (aac648b2-aac8-411d-afe0-7cbd5455841c._msdcs.brockley.harte-lyne.ca)
> on port 135 - NT_STATUS_UNSUCCESSFUL.

Port 135 is not NTP, it is the End Point Mapper port

> 
> The address 192.168.18.161 was/is assigned to a samba DC (smb4-1)
> which is not online and has not been for quite some time.

Is there anything left in AD that refers to your removed DC ? 
If the removed DC was the holder of the PDC_Emulator FSMO role, that is
one place I would check.

Rowland