search for: forestdnszoned

Displaying 20 results from an estimated 995 matches for "forestdnszoned".

Did you mean: forestdnszones
2016 Dec 19
2
samba-tool domain ldapcmp compared failed
Hi, Well, I joined a new DC on my domain and when run "ldapcmp" it reported errors. I follow Samba wiki to Joining a Samba to an Existing Active Directory. * Comparing [DNSFOREST] context... * Objects to be compared: 18 Comparing: 'CN=Infrastructure,DC=ForestDnsZones,DC=dom,DC=city10,DC=com,DC=br' [ldap://artemis]
2020 Apr 29
3
samba 4.12.2: WERR_DNS_ERROR_DS_UNAVAILABLE, unable to manage samba DNS
On 29/04/2020 10:58, Olaf Dreyer via samba-technical wrote: > > I run a setup with two Samba DC (currently samba 4.12.2 on debian 10 > VMs). I started with a Windows 2003 DC but the last Windows DC has > been removed a few years ago from this setup. this is really the wrong list for this, so i have CC'ed the samba mailing list, please reply there. You say you started with Win
2016 Dec 19
0
samba-tool domain ldapcmp compared failed
On Mon, 19 Dec 2016 15:44:26 -0200 Vinicius Lehmann via samba <samba at lists.samba.org> wrote: > Hi, > > Well, I joined a new DC on my domain and when run "ldapcmp" it > reported errors. I follow Samba wiki to Joining a Samba to an > Existing Active Directory. > > * Comparing [DNSFOREST] context... > > * Objects to be compared: 18 > >
2020 Apr 29
3
samba 4.12.2: WERR_DNS_ERROR_DS_UNAVAILABLE, unable to manage samba DNS
On 29/04/2020 17:29, Olaf Dreyer wrote: > Hi Rowland, > > this is a good question. Does this listing help or answer? > > root at OMTNDC3:/usr/local/samba/private/sam.ldb.d# ls -al > total 93220 Node,CN=Schema,CN=Configuration,DC=omtn,DC=de > drwxr-x--- 2 root bind????? 4096 Apr 28 16:03 . > drwx------ 7 root root????? 4096 Apr 29 11:25 .. > -rw------- 1 root staff
2020 Apr 29
0
samba 4.12.2: WERR_DNS_ERROR_DS_UNAVAILABLE, unable to manage samba DNS
Well, sometimes I? feel really old..... The last dynamic changes in DNS where made earlier this month, probably before I upgraded from 4.11.5 to newer version. With samba 4.11.5 DNS administration using samba-tool was working fine. Do you think this old setup is the reason for the problems?Any way to fix it? Best regards, Olaf Am 29.04.2020 um 18:35 schrieb Rowland penny via samba: > On
2020 Apr 29
0
samba 4.12.2: WERR_DNS_ERROR_DS_UNAVAILABLE, unable to manage samba DNS
Hi Rowland, this is a good question. Does this listing help or answer? root at OMTNDC3:/usr/local/samba/private/sam.ldb.d# ls -al total 93220 Node,CN=Schema,CN=Configuration,DC=omtn,DC=de drwxr-x--- 2 root bind????? 4096 Apr 28 16:03 . drwx------ 7 root root????? 4096 Apr 29 11:25 .. -rw------- 1 root staff 30384128 Apr 29 12:46 'CN=CONFIGURATION,DC=OMTN,DC=DE.ldb' -rw------- 1 root
2020 Apr 29
2
samba 4.12.2: WERR_DNS_ERROR_DS_UNAVAILABLE, unable to manage samba DNS
G'Day Olaf, If this was working before, then it would be this bug: https://bugzilla.samba.org/show_bug.cgi?id=14310 I'm a bit swamped right now, per Microsoft the correct fix is for our DNS Management server to ignore these values. Can you see if your error looks like this in the server logs? Andrew Bartlett On Wed, 2020-04-29 at 18:53 +0200, Olaf Dreyer via samba wrote: > Well,
2017 Sep 27
2
Samba as AD travails
Many (many) hours later, I'm finally throwing in the towel and seeking help. I have read everything I can find on the internet to no avail to get past my issues. I have to say, I'm very disappointed in the general quality and fragmentation of information on this topic. Samba isn't a turn-key solution as an AD by any stretch of the imagination. I've run the gamut so far with
2020 May 18
2
bogus record in _msdcs zone in samba-dc
On 18/05/2020 18:27, Alex wrote: >>>> 2. Why can't I query and/or delete it using standard means? >>> Probably because it is a wrong record ???? >>> Try running this on a DC: >>> ldbsearch --cross-ncs --show-binary -H /var/lib/samba/private/sam.ldb -b >>> 'DC=_msdcs.domain.com,CN=MicrosoftDNS,DC=ForestDnsZones,DC=domain,DC=com'
2019 Jul 31
2
GPO issues - getting SYSVOL cleaned up again
"--seize" helped: root at pre01svdeb03:~# samba-tool fsmo show SchemaMasterRole owner: CN=NTDS Settings,CN=PRE01SVDEB03,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=pilsbacher,DC=at InfrastructureMasterRole owner: CN=NTDS Settings,CN=PRE01SVDEB03,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=pilsbacher,DC=at RidAllocationMasterRole owner:
2019 Jul 31
3
GPO issues - getting SYSVOL cleaned up again
Progress: no more "dc" in rgrep on both servers PTR for the rejoined pre01svdeb02 is missing, so I assumed we need a dnsupdate: root at pre01svdeb02:~# samba_dnsupdate --verbose IPs: ['192.168.16.205'] need cache add: A pre01svdeb02.pilsbacher.at 192.168.16.205 Looking for DNS entry A pre01svdeb02.pilsbacher.at 192.168.16.205 as pre01svdeb02.pilsbacher.at. need cache add: NS
2020 Feb 16
3
Internal DNS, update of reverse zone fails
Dear list, one more problem. I've setup my host running a samba addc controller. Samba version is samba-4.11.6-r2. I've joined two win10 clients to my domain. One client has a static ip, the other one was configured to ask my dhcpd-daemon for an ip. Following the book from stefan kania, I modified my dhcpd.conf to execute some scripts I've found on ArchWiki to add my
2016 Mar 18
0
missing DomainDnsZones and ForestDnsZones ?
On 18/03/16 19:27, Robert Moulton wrote: > Rowland penny wrote on 3/18/16 11:48 AM: >> On 18/03/16 18:19, Robert Moulton wrote: >>> Greetings - On our samba 4 (4.3.3) AD controller I just noticed >>> something odd. When I run 'samba-tool fsmo show' I get an error: >>> >>> # samba-tool fsmo show >>> ERROR(ldb): uncaught exception - No
2020 Jun 30
3
samab-4.10 nsupdate
I have a dc configured to use the samba internal dns service. The version of samba I am using is 4.10.15 packaged for FreeBSD. Its build options state this: BIND911 : off BIND916 : off , , , GSSAPI_BUILTIN : on GSSAPI_MIT : off LDAP : on . . . NSUPDATE : off My smb4.conf file contains this: [global] bind interfaces only = Yes dns forwarder =
2016 Mar 18
2
missing DomainDnsZones and ForestDnsZones ?
Greetings - On our samba 4 (4.3.3) AD controller I just noticed something odd. When I run 'samba-tool fsmo show' I get an error: # samba-tool fsmo show ERROR(ldb): uncaught exception - No such Base DN: CN=Infrastructure,DC=DomainDnsZones,DC=biostat,DC=washington,DC=edu File "/usr/local/samba/lib64/python2.6/site-packages/samba/netcmd/__init__.py", line 175, in _run
2016 Mar 18
0
missing DomainDnsZones and ForestDnsZones ?
On 18/03/16 18:19, Robert Moulton wrote: > Greetings - On our samba 4 (4.3.3) AD controller I just noticed > something odd. When I run 'samba-tool fsmo show' I get an error: > > # samba-tool fsmo show > ERROR(ldb): uncaught exception - No such Base DN: > CN=Infrastructure,DC=DomainDnsZones,DC=biostat,DC=washington,DC=edu > File >
2020 Apr 30
0
samba 4.12.2: WERR_DNS_ERROR_DS_UNAVAILABLE, unable to manage samba DNS
Hi, I restored the last backup with the 4.11.6 setup. This is working fine and i can confirm that my AD is set up with a single forwarding zone, there is no _msdsc zone. On this 4.11.6 setup also the Windows DNS Tool does not complain. When upgrading to 4.12.2 DNS administration fails again with WERR_DNS_ERROR_DS_UNAVAILABLE. I will try the steps described in the MS document? and come back
2016 Mar 18
2
missing DomainDnsZones and ForestDnsZones ?
Rowland penny wrote on 3/18/16 11:48 AM: > On 18/03/16 18:19, Robert Moulton wrote: >> Greetings - On our samba 4 (4.3.3) AD controller I just noticed >> something odd. When I run 'samba-tool fsmo show' I get an error: >> >> # samba-tool fsmo show >> ERROR(ldb): uncaught exception - No such Base DN: >>
2024 Jan 05
1
Fresh ad installation - Win2022 can't join
Good morning :) Am 04.01.2024 um 20:17 schrieb lists--- via samba: > Am 04.01.2024 um 13:28 schrieb lists--- via samba: >> Am 04.01.2024 um 12:36 schrieb Rowland Penny via samba: >>> On Thu, 4 Jan 2024 12:12:57 +0100 >>> lists--- via samba <samba at lists.samba.org> wrote: >>> >>>> Am 04.01.2024 um 11:55 schrieb Rowland Penny via samba:
2020 May 18
3
bogus record in _msdcs zone in samba-dc
Hello, I've just discovered a bogus record in _msdcs zone which exists on samba-dc (vm-dc4, 4.12.2) only and missing on a PDC (vm-dc1, Windows Server 2008 R2): # samba-tool dns query localhost _msdcs.domain.com @ ALL -U administrator 2>/dev/null Password for [DOMAIN\administrator]: Name=, Records=3, Children=0 NS: vm-dc1.domain.com. (flags=600000f0, serial=181, ttl=3600)