Displaying 20 results from an estimated 6000 matches similar to: "I can't get Win10 clients to sync time with the DC"
2019 Nov 16
2
I can't get Win10 clients to sync time with the DC
On 16.11.2019 15:17, Sonic wrote:
> On Thu, Nov 14, 2019 at 1:56 PM Viktor Trojanovic via samba
> <samba at lists.samba.org> wrote:
>> 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
2018 Nov 05
4
Time server on AD DC in an LXD container.
After reading the instructions at
https://wiki.samba.org/index.php/Time_Synchronisation, I still have
questions about how samba interacts with nptd.
The issue is that LXD doesn't want containers setting the time and so won't
start ntpd at container startup even though it's enabled in systemd. The
host does sync it's time with a national time server, so we can assume that
the
2019 Oct 24
2
chronyd vs ntpd on SambaAD ?
Hi,
As Centos 7 and Fedora defaults to chronyd [2] , should I use ntpd for
some reason [3] ? I based my configurations on [1] which use ntpd ...
but I thinking change for chronyd , change ntp deamons could outage the
samba service and client computers ?
Thanks
[1]
https://negativo17.org/samba-4-active-directory-with-bind-dlz-zones-dynamic-dns-updates-windows-static-rpc-2/
[2]
2006 Oct 11
9
time synchronization problem (using NTP)
Hi,
using SLES10 I''m unable to synchronize the time of DomU with that of Dom0. There
is a persistent offset of about 3 seconds!
Here''s a small history (not actual output):
remote refid st t when poll reach delay offset jitter
rkdvmso1.dvm.kl 192.168.0.11 5 u - 64 1 0.136 -2977.1 0.099
*rkdvmso1.dvm.kl 192.168.0.11 5 u 2 64
2019 Oct 27
1
chronyd vs ntpd on SambaAD ?
On Thu, 2019-10-24 at 16:27 +0100, Rowland penny via samba wrote:
> On 24/10/2019 16:10, S?rgio Basto via samba wrote:
> > Hi,
> > As Centos 7 and Fedora defaults to chronyd [2] , should I use ntpd
> > for
> > some reason [3] ? I based my configurations on [1] which use ntpd
> > ...
> > but I thinking change for chronyd , change ntp deamons could outage
>
2018 Nov 06
2
Time server on AD DC in an LXD container.
Further investigations reveal:
---
C:\WINDOWS\system32> w32tm /monitor
GetDcList failed with error code: 0x800706BA.
Exiting with error 0x800706BA
---
error 0x800706BA indicates that the RPC server is unavailable.
Any ideas?
Thanks,
Jonathan Kreider
On Tue, Nov 6, 2018 at 5:48 PM Jonathan Kreider <jonathan.kreider at gmail.com>
wrote:
>
> Thanks Robert & Marco.
>
>
2024 Feb 26
1
samba 4.19 Windows 11 clients Time sync problem
Hello,
It is debian 11, and it is ntp, as you can see below my ntp.conf.
Ntp service is running fine . Some , not all, W10/11 clients do not sync with the dc (samba 4.19).
What i did on the clients:
net stop w32time
w32tm /unregister
w32tm /register
net start w32time
But after some time the wrong time shows up again?
Greetings
Daniel
-----Urspr?ngliche Nachricht-----
Von: Luis Peromarta
2019 Nov 17
4
I can't get Win10 clients to sync time with the DC
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.
>
2019 Jan 08
1
AD DC in a container: NTP
Hi Louis,
In general, this sounds like the solution I was looking for. But I’m still a bit unclear about the practical implementation.
So, the DC can be setup without ntpd as it will work based on the system clock which, in turn, is actually being updated by the container host using NTP. Which means we’ve got the DC itself covered. But if ntpd is not installed, then how can the DC serve time
2020 Nov 18
6
Time sync not working with Windows 10
After our office upgraded to Windows 10, time sync stopped working with the Windows
workstations. This used to work fine with Windows 7 and still works with linux domain members
(although that's not surprising).
The Windows 10 workstations ended up operating off the CMOS clock. We didn't notice this for a long
time since the CMOS clock drift is slow, but after several months users started
2019 Nov 17
2
I can't get Win10 clients to sync time with the DC
On 16.11.2019 23:37, Sonic wrote:
> On Sat, Nov 16, 2019 at 10:34 AM Viktor Trojanovic <viktor at troja.ch> wrote:
>> I think you may be confusing privileged with unprivileged containers,
>> what you describe is perfectly possible with a privileged container but
>> would be a bit more complicated to set up with an unprivileged one
>> (since the user id's in the
2015 May 24
4
Systemd
On 5/24/2015 12:22 PM, Gordon Messmer wrote:
> On 05/24/2015 11:41 AM, Kirk Bocek wrote:
>> to activate your selected daemon. I just used the new systemd commands,
>> thinking that would be enough. So I tried that and rebooted. Nope, same
>> problem:
>
> chronyd and ntpd both use UDP port 123, so each will terminate the
> other when it starts. If both are enabled,
2015 May 24
3
Systemd
On 5/23/2015 11:22 PM, Luigi Rosa wrote:
> Kirk Bocek wrote on 24/05/2015 04:37:
>> So I've built my first CentOS 7 host and am learning all the new ways
>> of doing
>> things. I setup and enabled ntpd but after a reboot I get:
>
> In CentOS 7 is bettere to use chrony, here's an howto
>
> http://linoxide.com/linux-command/chrony-time-sync/
>
So
2024 Feb 16
1
samba 4.19 Windows 11 clients Time sync problem
Hi there.
A few NTP experts around here lately.
We need more info. Distro, and wether your are using NTP (nrpsec) or Chrony.
Regards.
LP
On 16 Feb 2024 at 14:37 +0100, Daniel M?ller via samba <samba at lists.samba.org>, wrote:
> Dear all,
>
> We just have a samba 4.19 domain running. And what i recognized ist hat some
> windows 10/11 clients does not sync time with the dc.
2018 Jun 03
3
chrony configuration for secondary samba DC
How you so sure about it?
Even at https://packages.ubuntu.com/bionic/samba chrony mentioned as
suggested related package
.
On Sun, Jun 3, 2018 at 6:13 PM Rowland Penny via samba
<samba at lists.samba.org> wrote:
>
> On Sun, 3 Jun 2018 16:59:38 +0200
> Reindl Harald via samba <samba at lists.samba.org> wrote:
>
> >
> >
> > Am 03.06.2018 um 16:48 schrieb
2016 Jan 27
4
NTP Service Running on Local Host does not Sync System Time
Hi List
I have ntp running as a service on a PC, with the expectation that it
would keep time in synch to my ntp server.
However, while I can manually update the time using "ntpdate -u ...",
I find that if I manually force the wrong time, the ntpd service does
not automatically re-synch the system time with the ntp server:
- Current time:
[admin at lol ~]# date
Wed Jan 27 10:54:21
2024 Jan 18
1
Joining Windows 10 Domain Member to Samba AD/DC
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
2019 Apr 25
3
Windows clients require reboot once a day in order to access mapped drives
>
>
> Forgot to mention, are sure your time sync over AD is working correctly.
> One to add to you list, check times of server and clients, (* yes again,
> if needed just to be sure).
>
Yes, I have double check that time is correctly being synced.
FYI, Rowland, the process outlined in the wiki for using chronyd does not
work on Ubuntu 18.04 (my AD DC is on Ubuntu, but my file
2025 Jan 18
3
Time synchronization problem. Chrony, ntp
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 from dc1.xxxx.pl
RefID: time.cloudflare.com [162.159.200.123]
Stratum: 4
dc2.xxxx.pl[192.168.45.9:123]:
ICMP: 1ms delay
NTP: -0.0001207s
2024 Feb 16
2
samba 4.19 Windows 11 clients Time sync problem
Dear all,
We just have a samba 4.19 domain running. And what i recognized ist hat some
windows 10/11 clients does not sync time with the dc. The time is not the
real time as on the dc, about 10 minutes back or several minutes in the
future.
Is this a bug or did spmething chance in the behaviour of samba?
My ntp.conf/ Debian11:
driftfile /var/lib/ntp/ntp.drift
server 127.127.1.0
fudge