similar to: Time synchronization issue

but It does work out of the box.. If al was setup ok.. It the time server also the DC with FSMO role PDC ? if not, then thats your error. this is a good read. https://technet.microsoft.com/en-us/library/cc773013(v=ws.10).aspx Greetz, Louis >-----Oorspronkelijk bericht----- >Van: william.epci at gmail.com >[mailto:samba-bounces at lists.samba.org] Namens William LIM

Hello Andrey Thanks for the trick. I'll try it. But it's a pity it doesn't work natively, right ? 2015-04-22 14:08 GMT+02:00 Andrey Repin <anrdaemon at yandex.ru>: > Greetings, William LIM! > > > Hi, > > > I have set a Samba AD DC on my network. Version is 4.1.17 on a Debian > > Wheezy. > > > I have an issue on my Windows XP SP3 clients :

Hi ! Actually, problem was located on client side, not samba side. w32time has "disappeared" from services list (!) the w32tm /unregister and w32tm /register solve the problem My clients seem to be correctly synchronised with my AD DC now. If i find out why w32time has disappeared, I'll post a message here. Thank you for your help ! 2015-04-22 16:02 GMT+02:00 Andrey Repin

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

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

We have a Samba-4.3 AD-DC hosted on a FreeBSD-10.3 system. We have just discovered that for some reason our domain workstations are not synchronising their time with the AD-DC. We have not altered the default GPO nor have we created a special GPO to handle time services. I have been working on several of the domain clients and I cannot seem to get them to source from the Samba server. I have

I have the impression your DC?s ntp server is not working properly for whatever reason. Your windows machines try to grab time for them, can?t, and then default to local coms clock or some other time source. From a windows member machine, can you try : w32tm /stripchart /computer:us.pool.ntp.org /dataonly /samples:5 That should work. Then try: w32tm /stripchart /computer:your.dc.address

Hi, The Windows and Linux workstations are not synchronizing the time with the Samba 4 DC. I have verified that the problem is permission. I'm using Samba 4.6.3 on Debian 8. In this way the stations are with different schedules from the DC. Do I need to configure any GPOs? What is the maximum time the computer clock can differ from DC ? Regards, Márcio

Ok, good it works now.. ? Yes, clients should be synced with the DC.. i can only think of?3 reasons why it didnt work or stopped working. ? 1)?If the pc time gets out of sync (+5min) ?for some reason, then the client wil try 8 more times and then it marks the source as unusable.. ??? ( if a pc is never rebooted, this can happen also?) ? 2) u used w32time to set time, and if you run than from

Greetings, William LIM! > Hi, > I have set a Samba AD DC on my network. Version is 4.1.17 on a Debian > Wheezy. > I have an issue on my Windows XP SP3 clients : the time on these computers > is not synchronized with my Domain Controler. > Big problem is, if time difference is considerable (more or less 5 > minutes), users can not log in. > On the other hand, my server

Greetings, William LIM! >> > I have set a Samba AD DC on my network. Version is 4.1.17 on a Debian >> > Wheezy. >> >> > I have an issue on my Windows XP SP3 clients : the time on these >> computers >> > is not synchronized with my Domain Controler. >> >> > Big problem is, if time difference is considerable (more or less 5 >>

Hello James I read this article, it's not working on Windows clients. ----- Original Message ----- From: lingpanda101 at gmail.com To: samba at lists.samba.org Sent: Monday, August 1, 2016 2:05:09 PM Subject: Re: [Samba] Samba 4 ad client not syncing time On 8/1/2016 12:56 PM, Dante F. B. Colò wrote: > Hello folks > > I've deployed Samba 4.0.26 using Sernet binary packages

I've been using bind9 and DHCP on Samba 4.1.0 thru 4.1.17 and Slackware 64 14.1 for many months now in a production environment and it works just fine. There are a few tweaks here and there to get bind/dhcp to play nicely with Samba ... Note, conf file locations are Slackware, but you'll know where the same thing goes in your distro. In the examples below, my Domain IP range is

I just realized that some of my Windows 10 clients do not appear to be syncing the time correctly. I setup NTP to run on my Netgate PFSense server. It is using pfsense.pool.ntp.org Time Servers. I configured NTP on my Samba servers to point to back to the PFSense Server. NTP on the samba servers have the following ntp.conf files: # /etc/ntp.conf, configuration for ntpd; see ntp.conf(5) for

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

In our network we found some client with clock differences. Some machine have effectively some troubles, eg have NO 'Windows Time' service defined, probably some glitches happened when moving from our old NT-like domain. Anyway, catching for that, we have found some other strangeness. Windows time service run: C:\Users\gaio>sc query w32time NOME_SERVIZIO: w32time TIPO

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

Hai, i had this also .. First set the xp machines within 5 min time difference compaired to the server, then time should be in sync because time is passed by AD. If you already had 8 failures of time sync then the sources is excluded.. please read : https://support.microsoft.com/en-us/kb/314054 for more info. Greetz, Louis >-----Oorspronkelijk bericht----- >Van: william.epci at

"Ah, but what if you have Unix clients" I do have Unix clients. They work just fine. The Samba AD/DC is the DHCP server. The Windows and Linux clients get their IP addresses and everyone can see all the hosts on the domain. for example: >From the domain controller (host name MAIL) $ host mark # mark is a Windows 7 workstation MARK.hprs.local has address 192.168.0.55 $ host

I want my XP clients to update their clocks from my samba server. I have time server = yes in smb.conf, and running ntpd on the server, but my clients aren't updating their clocks. I tried running the command manually logged in as a domain user: net time /setsntp:10.8.2.3 but it just says "System error 5 has occurred. Access is denied". Any ideas?