Displaying 20 results from an estimated 3000 matches similar to: "using w32tm (WinXP) w/samba3 as DC: can't get DC List"
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.
>
>
2018 Nov 07
0
Time server on AD DC in an LXD container.
You might find a solution here:
https://serverfault.com/questions/879164/using-host-as-ntp-client-and-lxc-router-as-ntp-server
On Tue, Nov 6, 2018 at 5:59 PM Jonathan Kreider via samba
<samba at lists.samba.org> wrote:
>
> Further investigations reveal:
> ---
> C:\WINDOWS\system32> w32tm /monitor
> GetDcList failed with error code: 0x800706BA.
> Exiting with error
2013 Jul 25
0
DsGetDomainControllerInfoW fails with level 2008+, works with 2003
Hello,
I stumbled on this problem while troubleshooting a time synchronization
problem. The Windows commands "w32tm /monitor" and "nltest /dclist:domain"
appear to both use the same call to query the domain for a list of domain
controllers. When the DC is Samba4 (2003 domain & forest level) these
commands complete successfully. After raising the levels to 2008 or 2008_R2
2009 Mar 10
0
WinXP3: NBNS query: non-exist; Wireshark: "'NB ?'<00>" & "'NB ?'<20>"
I'm getting some odd queries from a WinXPSP3 client to an older samba
(3.2.0-24) Domain & File server running on linux kernel (2.6.27.19).
The client seems to be querying for a netbios name <literal-question mark>
followed by binary 0 (<00>) to the DomainServer, or Broadcasting the query
with the '?' followed by a space <20>.
This is from conversation over wire
2010 May 04
0
How to net group add 'group' (I scrod myself...can't figure out how descrod)
I have:
interfaces = lo0, eth2
and:
socket address = 192.168.3.1
socket address = 127.0.0.l
in my smb.conf, but when I try to
"net group add anything" (on server running samba 3.5.2, as a DC):
<asks for current log'ed in users's password> mypwd
Could not connect to server 127.0.0.1
Connection failed: NT_STATUS_CONNECTION_REFUSED
So what am I missing?
Shouldn't
2003 Feb 04
0
FW: [despammed] Samba - winXP lookup
> Might not be it...but the '30 second lockup' triggered a memory...
>
> Could this be the 'looking for scheduled tasks' problem?
> Here's a blurb from the
> windows-net-mag site
> (http://www.win2000mag.net/Articles/Index.cfm?ArticleID=24546)
.
Like Windows 2000, XP suffers from a little-documented browse delay. When you browse to a Windows 9x computer
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
2011 Jun 28
2
cygwin 'QueryUserInfo' fails dueto samba error. Wazup?
I made progress in tracking down a problem on cygwin that's been bothering
me for a while since Win7 and domain.
when I do:
> mkpasswd -D
mkpasswd (434): [31] A device attached to the system is not functioning.
A network trace shows that it's trying to get the home dir
information from my main user. Wwhen it queries the info
Samba returns STATUS UNSUCCESSFUL (indicated in network
2007 Jun 16
1
had 3 kernel panics since upgrade from 3.0.21a to 3.0.25 and 3.0.25a on CentOS 4.4
Does anybody have any ideas on this? On our server that has been running
'rock-solid' with no crashes we have now had 3 kernel panics that each
appear to have been triggered by the newly upgraded samba daemon.
We used to run samba 3.0.21a for 'years' with no crashes.
On May 26 we upgraded to 3.0.25
June 9 10:58:28 first crash kernel panic
process involved according to log
2015 Dec 22
0
The number of maximum ticket referrals has been exceeded
Hi,
I have a AD domain based on 2 Ubuntu servers running Samba 4.1.17
I've successfully added a number of windows and linux clients to the domain.
I now tried adding an extra Linux printer server. When I try to access the
server from a Windows client, I am asked to enter a username and password
(altough I am already logged in to the domain). Whatever username and
password I enter access is
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
2007 Dec 06
7
time server = yes
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?
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
2010 Jan 14
1
0 length domain name & SCHANNEL can't be used to fetch trust account password?
I have a few errors I'm trying to chase down in an effort to get a
Win7 client in my domain. WinXP works -- tested unjoining and
rejoining today, and it can still join.
I have the registry adds for DNSNameResolutionRequired=0 under
LanmanServer&Client/Params (put it in both places in attempt to get
things working), as well as a DomainCompatibilityMode=1
I've tried moving to winbind
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.
> >
> >
2011 Dec 27
1
Practicality of fixing samba's case mangling problems?
Samba has multiple areas of case mangling problems that cause
incompatibilities
when used with windows or linux clients.
How viable is the idea of fixing the problems? Would the sky fall in if
it preserved case, but
either 'ignored it', or gave preference to matches that included the
case as typed (vs. alternate case
matches).
The first would be fairly compatible with current Win