search for: noqueri

On my member server, running 'ntpq -p' yields: ntpq -p localhost: timed out, nothing received ***Request timed out The ntp.conf file is trying to use the DC's hostnames addresses: user at DC01:~# cat /etc/ntp.conf # /etc/ntp.conf, configuration for ntpd; see ntp.conf(5) for help driftfile /var/lib/ntp/ntp.drift # Enable this if you want statistics to be logged. #statsdir

On Tue, 12 Sep 2017 14:41:42 -0300 Flávio Silveira via samba <samba at lists.samba.org> wrote: > > Ok, I understand now, one question though: if realm is > AD.TECNOPON.COM.BR, does domain need to be AD? No, you can use anything you like, provided it is one word, 15 characters or less, without punctuation. > If I understand > correctly, realm is "full domain with

Em 13/09/2017 10:36, L.P.H. van Belle via samba escreveu: > Hai, Flavio, > > Yes, it looks good, but i suggest, if you setting up a new DC on debian.. > Go here: https://github.com/thctlo/samba4/tree/master/howtos > And read the file: stretch-base-2-samba-minimal-ad.txt > > This should works also for debian Jessie, if it errors only remove the words " limited" from

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

Hai, Flavio, Yes, it looks good, but i suggest, if you setting up a new DC on debian.. Go here: https://github.com/thctlo/samba4/tree/master/howtos And read the file: stretch-base-2-samba-minimal-ad.txt This should works also for debian Jessie, if it errors only remove the words " limited" from the line restrict. Now, review the code below, you need to make a few small changes.

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

| My DC is a samba4.3 over Ubuntu 16.04. | I've configured ntp in the same server. | However > when I join a windows 10 client to my domain, this one doesn't | update its datetime. | Once I logging in, I am able to set any datetime. | And more > No matter the windows 10 client' s datetime, I can logging in with | any user of the Active Directory. | I need a proper time sync in

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

Hai, Copy the code and Set these variable Run the script, restart samba and login again with an pc. Should work now, your missing something and. Your not using good ntp servers. #!/bin/bash ########## NTP Settings needed for a correct funtioning samba AD DC server ## Set to 1 installs the ntp server. (default is ok ) ## (default is ok ) NTPD_INSTALL="1" # if you run the server on a

Hi, I'm currently sinking my teeth into NTP, to build a local time server. So far, configuring a local NTP server and getting the clients to connect to it works well. Now, I'm thinking about securing the whole thing. BTW, I made a copy of the original ntp.conf file and started my own from scratch. Right now, I have five printed books opened on the corresponding chapters (Carla

Copied Roweland's DC ntp.conf file into my two DC's. Restarted (all) ntp. Member still timing out! (I am starting to think that there is 'something' about the sernet packages that "they" do differently.) Rowland, Could I ask you to copy the ntp.conf from your client (appears to be your laptop) so I could review it's contents? --- ------------------------- Bob

Thank you, Rowland. Copied your simpler ntp.conf file into my member server. Made the appropriate changes. Restarted all the ntp service on all machines (just in case.) Ran 'ntpq -p' (on member server) and got the correct answer. Proper connection to DC's. --- ------------------------- Bob Wooden of Donelson Trophy 615.885.2846 (main) www.donelsontrophy.com [1] "Everyone

I have two DC's running Version 4.1.16-SerNet-Debian-9.wheezy and a member server running Version 4.1.11-Debian. When I 'ntpq -p' from the member server I get: localhost: timed out, nothing received ***Request timed out Member server ntp.conf file: cat /etc/ntp.conf # Local clock (this is not the localhost address!) server 127.127.1.0 fudge 127.127.1.0 stratum 10 # The source,

Hai Flavio, > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > Flávio Silveira via samba > Verzonden: woensdag 13 september 2017 16:19 > Aan: samba at lists.samba.org > Onderwerp: Re: [Samba] File server questions > > > > Em 13/09/2017 10:36, L.P.H. van Belle via samba escreveu: > > Hai, Flavio, > >

I’m currently trying to install a new (primary) AD DC in a Linux container. It seems to me that being in a container, the DC is easier to maintain and backup than on bare metal, and I prefer a container over a VM for performance reasons. If the container setup will prove to be too much of hassle, I’ll switch to a VM, though. The first issue I’m facing is time synchronization. An container cannot

Made the suggested adjustments (4 locations in the member server ntp.conf file) and restarted ntp. Still (member server) timing out. Not sure what you mean about removing "server 0.debian.pool.ntp.org iburst" lines. Those on the DC's. Aren't they necessary? Running 'ntpq -p' on DC's results in correct response. --- ------------------------- Bob Wooden of

Hai Guy, Yes, it make a backup of your previous version so you can revert if needed. And review your config after your run it, you micht see a these line : restrict > -4 default kod notrap nomodify nopeer noquery mssntp mssntp ( check if you dont see mssntp 2 x, if so, remove 1 of them ) This is because normaly this is run against a "default" ntp.conf And change the variables

On 13/02/15 17:26, Bob of Donelson Trophy wrote: > > > Copied Roweland's DC ntp.conf file into my two DC's. Restarted (all) > ntp. Member still timing out! > > (I am starting to think that there is 'something' about the sernet > packages that "they" do differently.) > > Rowland, Could I ask you to copy the ntp.conf from your client (appears