similar to: old DC showing up

It appears that none of our windows clients are syncing their time with the samba DC.??? From what I can tell they are not able to get a response from the DC.? For example, where the DC is named athena: >w32tm /monitor /computers:athena athena[10.10.1.10:123] ? ICMP: 0ms delay ? NTP: error ERROR_TIMEOUT - no response from server in 1000ms From a Linux machine there is

On Wed, 25 Oct 2023 11:53:07 -0500 Ham via samba <samba at lists.samba.org> wrote: > It appears that none of our windows clients are syncing their time > with the samba DC.??? From what I can tell they are not able to get a > response from the DC.? For example, where the DC is named athena: > > >w32tm /monitor /computers:athena > > athena[10.10.1.10:123]

> On 10/25/2023 9:53 AM PDT Ham via samba <samba at lists.samba.org> wrote: > > > It appears that none of our windows clients are syncing their time with > the samba DC.??? From what I can tell they are not able to get a > response from the DC.? For example, where the DC is named athena: > > >w32tm /monitor /computers:athena > >

> On 10/25/2023 11:16 AM PDT Rowland Penny via samba <samba at lists.samba.org> wrote: > > > On Wed, 25 Oct 2023 11:53:07 -0500 > Ham via samba <samba at lists.samba.org> wrote: > > > It appears that none of our windows clients are syncing their time > > with the samba DC.??? From what I can tell they are not able to get a > > response from the

On 17.11.2019 15:58, Sonic wrote: > On Sun, Nov 17, 2019 at 5:37 AM Viktor Trojanovic <viktor at troja.ch> wrote: >> I'm not sure I understand your setup. It seems like you are running >> Chrony on the host only and you just share the socket with the >> container, no chrony running there. > Yes, you have it correct. That's exactly what I'm doing. >

On Wed, 25 Oct 2023 11:10:57 -0700 (PDT) James Browning via samba <samba at lists.samba.org> wrote: > > On 10/25/2023 9:53 AM PDT Ham via samba <samba at lists.samba.org> > > wrote: > > > > > > It appears that none of our windows clients are syncing their time > > with the samba DC.??? From what I can tell they are not able to get > > a

On Wed, 25 Oct 2023 11:25:14 -0700 (PDT) James Browning via samba <samba at lists.samba.org> wrote: > > On 10/25/2023 11:16 AM PDT Rowland Penny via samba > > <samba at lists.samba.org> wrote: > > > > > > On Wed, 25 Oct 2023 11:53:07 -0500 > > Ham via samba <samba at lists.samba.org> wrote: > > > > > It appears that none of

I'm running a Samba AD DC v4.9.9 with Windows 10 clients connected to it and just noticed that the clients are not synchronizing time with the server. I'm not sure why not. My setup is a bit special in that the DC is running inside a (privileged) linux container. For that reason, it's not possible or necessary for the container to correct the system clock, this is done on the

Hello, I've just discovered a bogus record in _msdcs zone which exists on samba-dc (vm-dc4, 4.12.2) only and missing on a PDC (vm-dc1, Windows Server 2008 R2): # samba-tool dns query localhost _msdcs.domain.com @ ALL -U administrator 2>/dev/null Password for [DOMAIN\administrator]: Name=, Records=3, Children=0 NS: vm-dc1.domain.com. (flags=600000f0, serial=181, ttl=3600)

Hello List, Im running an network with five samba 4 addc, all on debian wheezy with the sernet packages. Recently an replication error showed up for an single Computer (WIN7-M-ADMIN) record. So I unjoined the pc from the domain deleted it's record from dc1 manually on the other dc's it had been removed automaticaly during unjoin. Now I get the following error [2015/07/21

On Sat, 21 Jul 2018 20:57:07 +0200 Kacper Wirski via samba <samba at lists.samba.org> wrote: > Hello, > > I found this bugged record with > > ldbsearch -H > path/to/samba/bind-dns/dns/sam.ldb.d/DC\=DOMAINDNSZONES\,DC\=SUBDOMAIN\,DC\=DOMAIN\,DC\=PL.ldb > '(name=49)' > > So I have a couple of questions - hopefully someone can shed some > light: >

On 05.01.2024 1:28, Mark Foley via samba wrote: > I've added a Windows 10 domain member to my Domain. I'm now following the > procedure in https://wiki.samba.org/index.php/Time_Synchronisation#Configuring_Time_Synchronisation_on_a_Windows_Domain_Member. > > I've created the Group Policy for the "Time Sources". This doesn't seem to be > working. This did

On 04/01/16 17:23, Ole Traupe wrote: > No ideas on that? > > Ole > > > > Am 18.12.2015 um 13:44 schrieb Ole Traupe: >> I accidentally created a SRV record with a false port. I then updated >> the port but was afraid of any consequences. So I deleted that record >> again and wanted to re-create it. But now I can't: "The record >> already

On 08/01/16 10:31, Ole Traupe wrote: > > > Am 04.01.2016 um 19:24 schrieb Rowland penny: >> On 04/01/16 17:23, Ole Traupe wrote: >>> No ideas on that? >>> >>> Ole >>> >>> >>> >>> Am 18.12.2015 um 13:44 schrieb Ole Traupe: >>>> I accidentally created a SRV record with a false port. I then >>>>

On Sat, Jan 18, 2025 at 3:49?AM Programnet via samba <samba at lists.samba.org> wrote: > > I noticed a problem with time synchronization on all Windows endpoints. > I am using Samba 4.21.3 and Chrony 4.3-2. > > When I run the following command in Windows: > > w32tm /monitor > dc1.xxxx.pl *** PDC ***[192.168.45.10:123]: > ICMP: 1ms delay > NTP: +0.0000000s offset

On Mon, 20 Jan 2025 09:38:50 -0500 Jeffrey Walton via samba <samba at lists.samba.org> wrote: > On Sat, Jan 18, 2025 at 3:49?AM Programnet via samba > <samba at lists.samba.org> wrote: > > > > I noticed a problem with time synchronization on all Windows > > endpoints. I am using Samba 4.21.3 and Chrony 4.3-2. > > > > When I run the following command

We have been running Samba v3.0.32 On Red Hat Linux for probably 2 years now (or since it was released). Recently over a three week period, all the Windows clients slowly dropped from the domain one by one and we are unable to get them to re-join the domain. We are still able to map to drives and printers on the Samba server and use them with no problem, but cannot join the domain. We need to

On Thu Jan 18 10:52:55 2024 Sonic <sonicsmith at gmail.com> wrote: > > I'm with Luis in thinking that the fault is with the DC and not the > clients. I recently switched from using a GPO to set the time source to > using the "natural" time sync with the DC at one site due to the fact that > I was running the DC in a container which due to age could not run a

I accidentally created a SRV record with a false port. I then updated the port but was afraid of any consequences. So I deleted that record again and wanted to re-create it. But now I can't: "The record already exists." Observations: 1) I can't see it in the RSAT DNS gui, so I can't delete it there. 2) I also can't delete it via samba-tool (although I could delete

On Fri, Jan 5, 2024 at 2:32?PM Mark Foley via samba <samba at lists.samba.org> wrote: > <snip> I would think the wikis would mention the GPO not being > needed. Did you see the section titles "Default Time Source" in the page you link to that I quoted previously? The wiki clearly spells it out that using a GPO is usually unnecessary. > How do you know you're