Displaying 20 results from an estimated 1000 matches similar to: "Network Time problems with Windows 2k"
2007 Nov 05
0
Samba 3.0.26a, windows 2k3 r2 SFU, problems with auth/nss
Dear samba list,
For some time we've had servers connecting to a w2k3 r2 server via
ADS setup. Wins was working fine and users were able to authenticate.
Recently we've added a GFS like system. This required getting the
UID/GID's unified. Suggestions were made on the samba IRC channel to
install SFU on the PDC. I'm receiving some very strange output.
Usernames/pwd have
2003 Jul 24
0
Password expire problem
In a samba PDC 2.2.8a I've begun to experience a message on wxp sp1.
Whenever a user logs on they recieve a message stating that the password
will expire in 3 days. This message never decreases nor will it go away. I
looked in the archives and found users who have had similar problems but
no solutions. Could anyone comment and offer up a solution? thanks
Ross
[global]
domain master =
2002 Oct 16
0
(fwd from guthrie@counterexample.org) Comment on a web page
----- Forwarded message from "John T. Guthrie" <guthrie@counterexample.org> -----
From: "John T. Guthrie" <guthrie@counterexample.org>
Subject: Comment on a web page
Date: Fri, 23 Aug 2002 19:20:06 -0400
To: webmaster@samba.org
To Whom It May Concern,
I was just looking at your Samba Printing Support Page:
http://us1.samba.org/samba/docs/man/printer_driver2.html
2019 Nov 14
5
I can't get Win10 clients to sync time with the DC
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
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
2024 Jan 17
1
Joining Windows 10 Domain Member to Samba AD/DC
On Wed Jan 17 06:13:56 2024 Luis Peromarta via samba <samba at lists.samba.org>
>
> 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
2018 Nov 22
0
NTP strangeness...
Hi Marco,
As far i can see here.
Are all your ADDC servers set to the same source NTP ( preffered a stratum 1 or 2 ) server. ( and not pool ntp sources )
Because below i see stratum 4 and stratum 3 servers and a timeout on one server.
When i look at this.
> C:\Users\gaio>w32tm /query /peers
> N. peer: 1
2020 Nov 22
0
Time sync not working with Windows 10
From: Mark Foley via samba <samba at lists.samba.org>
To: "samba at lists.samba.org" <samba at lists.samba.org>
Subject: Re: [Samba] Time sync not working with Windows 10
Date: Thu, 19 Nov 2020 22:13:40 +0000
>
> On Wed, 18 Nov 2020 08:41:03 -0500 me at tdiehl.org wrote:
> >
> > On Wed, 18 Nov 2020, Mark Foley via samba wrote:
> >
> > > After
2015 Apr 24
1
Time synchronization issue
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
2017 Jan 31
0
Samba-4.3 AD-DC Win7pro clients not time syncing
On Mon, 30 Jan 2017 12:16:30 -0500 James B. Byrne wrote:
> I set the client's w32tm configuration this way:
>
> w32tm /config /update /manualpeerlist:"time.nrc.ca time.chu.nrc.ca"
> /syncfromflags:ALL
>
> And when I check the status with
>
> w32tm /query /status
>
> then I see this:
>
> Leap Indicator: 0(no warning)
> Stratum: 3 (secondary
2024 Jan 06
0
Joining Windows 10 Domain Member to Samba AD/DC
I think this didn't get sent to the maillist.
--Mark
-----Original Message-----
Date: Fri, 05 Jan 2024 13:58:08 -0500
Organization: Novatec Software Engineering, LLC
To: samba-bounces at lists.samba.org
Subject: Re: [Samba] Joining Windows 10 Domain Member to Samba AD/DC
On Thu Jan 4 22:42:38 2024 Sonic <sonicsmith at gmail.com> wrote:
>
> On Thu, Jan 4, 2024 at 7:46?PM Mark
2018 Nov 22
2
NTP strangeness...
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
2024 Jan 05
1
Joining Windows 10 Domain Member to Samba AD/DC
On Fri Jan 5 03:23:48 2024 Peter Milesson via samba <samba at lists.samba.org> wrote:
>
> 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.
> >
> >
2002 Sep 04
3
RedHat kickstart with PXELINUX
We are attempting to setup an automated system to build some Linux
systems. We have utilised the PXELINUX bootloader after encountering
the PXE 512Kb limit with bootp.
We now have another issue which you may have already run into. In the
DHCP configuration we specify pxelinux.0 as the bootfile, this works
reasonable well, we call the Redhat vmlinuz and initrd.img files
within the
2023 Oct 25
1
DC Time Problems
> 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
>
>
2023 Oct 25
3
DC Time Problems
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
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
2020 Nov 23
0
Time sync not working with Windows 10
On Sun, 22 Nov 2020 09:56:07 Rowland penny <rpenny at samba.org> wrote:
>
> On 22/11/2020 02:04, Mark Foley via samba wrote:
> > From: Mark Foley via samba <samba at lists.samba.org>
> > To: "samba at lists.samba.org" <samba at lists.samba.org>
> > Subject: Re: [Samba] Time sync not working with Windows 10
> > Date: Thu, 19 Nov 2020
2007 Apr 18
2
[Bridge] I want to RTFM -- so where's the FM?
Hi all,
I'm looking for documentation about the internals of the bridging
software. We're putting together a new chip that incorporates, among
other things, a core for a managed switch and a processor that will be
running Linux. I wanted to have the Linux code (among other things)
field SNMP requests and configure the managed switch. I'm hoping that
it's as simple as
2008 Aug 12
2
pdbedit will only add users to the local machine domain, not the global domain
Hello all,
When I try to add a user to my secrets.tdb file on my Samba 3.2.0 PDC, the
users are always added under the local machine domain, not the global domain.
That is, if my PDC machine name is srv1, and it is PDC for the domain DOM1,
then whenever I add a user using "pdbedit -a -u username", then that user
gets placed under the local domain SRV1, not the global domain DOM1. So my