similar to: Fwd: Re: Problem with Samba4 DB

hi mathias let me confirm your statement so.. you think if we demote those 2 DC server that already offline, the DNS will be running well well if this is one of option we have, i will consider to upgrade our FSMO DC from samba 4.1.X to 4.4.x , by the way, are there any consideration if we update samba directly from 4.1 to 4.4 ? let me answer some of your question *1 - what command are you

dear all i have problem with my samba4 installation currently we still using samba 4.1.11 we have many about 30 site office who is connected to the head office by Vpn with 1 mbps i have 2 DC in head office and have oen DC in every Site office since yesterday i found out in my one off my DC in head office, the Main DC (the DC that we make as first DNS in other DC in head office of site

dear roland and mathias i already upgrade samba server version to 4.4.4 i have domote 3 of 4 offline dc successfully one dc that i cant demote shown this error message /**//*[root at pdc ~]# samba-tool domain demote --remove-other-dead-server=dc25*//* *//*ERROR: Demote failed: DemoteException: dc25 is not an AD DC in domain.co.id*//* *//*A transaction is still active in ldb context

Oki Doki. First the fact you can't add new DNS entry in your DNS zones is not a blocking point to remove a DC. It's a blcoking point to add new entries. Now you are the one deciding if you would remove it or not, but seriously, for me that's not a reason to keep up it running: you can replace it by another DC which will do exactly the same job and if you are lucky enough you would be

2016-04-04 14:20 GMT+02:00 Rowland penny <rpenny at samba.org>: > On 04/04/16 10:23, mathias dufresne wrote: > >> SOA means "this DNS se'rver can modify the zone". >> > > No it doesn't, it stands for 'Start Of Authority' and contains who to > contact for the domain records. > Rowland... thank you again Captain Obvious. Yes SOA means

SOA means "this DNS se'rver can modify the zone". Using Bind-DLZ all DNS servers can modify the AD zones, they all reply "I am the SOA" when you ask them about SOA for AD zones. Using Internal DNS I expect all DNS servers can modify the AD zones also (that's internal stuff) but even if they can modify the AD zone locally that's is not the process chosen by Samba

hi guys i need some advice for my case that i faced here.. i have Two AD with two different domain, platform and network : i expect all user in different domain can resolve the other domain dns let say 1. domainwin.com >> windows 2008 AD >> 172.16.1.2 2. domainnux.com >> Samba 4 AD >> 172.16.2.2 is it possible if i create 1 new BIND DNS Server in 172.16.3.2

hi all i have problem with my multi-site AD-DC installation, one of my DC, suddently cant start well, i think problem(corrupt) with the LDAP database then i try to re join it, but every time i try to join it i always has issue like this /Finding a writeable DC for domain 'domain.co.id' Found DC pdc.domain.co.id Password for [domain\administrator]: workgroup is domain realm is

On Mon, Aug 8, 2016 at 5:49 AM, Stefan Kania <stefan at kania-online.de> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > you should set up a dns-proxy and use this proxy as forwarder in your > domains Really, really not the same thing as a DNS slave. If your DNS master, such as your Samba or AD server, goes toes up for whatever reason, the DNS slave can continue

On 15/06/16 10:14, bentunx wrote: > hi mathias > > let me confirm your statement > so.. you think if we demote those 2 DC server that already offline, > the DNS will be running well > well if this is one of option we have, i will consider to upgrade our > FSMO DC from samba 4.1.X to 4.4.x , by the way, are there any > consideration if we update samba directly from 4.1

On Mon, 21 Aug 2017 22:15:58 +0700 zhia chandra <bentunx at gmail.com> wrote: > hi rowland > > > *OK, you were asked 'Was this pc a member of any NT4 Domain in the > past?'You replied with:'nope ..'* > > well all the pc who had trust relationship problem is new PC with > windows 7 or earlier .. they never connected to PDC in clear OS > > i

On Tue, 15 Aug 2017 20:52:12 +0700 zhia chandra via samba <samba at lists.samba.org> wrote: > hai belle > > Was this pc a member of any NT4 Domain in the past? nope .. > > but actually our samba4 server was upgrated from samba3 base on > clearOS 5 .. > > and actually i still running samba3 in stand alone mode for netbios > only, incase some PC cannot map /

Hi all, Thank you Mark for these precisions. I did switch a DC to --dns-backend=NONE using samba-tool domain join. This removed dns-<DCname> user for this DC and associated keytab. We changed /etc/resolv.conf to use another DC - one with Bind running - as nameserver. Stopping there, running samba_dnsupdate gave error "NOTAUTH". As we want our DC being able to push into DNS

For me: - SOA means where updates can be sent. - SOA can be one or several. - NS is a record to help non-authoritative name servers to find a valid name server for the zone they receive a request and they don't know anything about that zone. - SOA is often declared as NS, I agree. I explained this is not mandatory. There is no link between these two notions except they share a zone. You are

Hi, I just solved this problem for myself: # samba-tool user add my-username-here User 'my-username-here' added successfully # samba-tool group addmembers 'Domain Admins' my-username-here Added members to group Domain Admins # samba-tool dns add localhost example.com testname A 10.0.0.2 -U my-username-here --password="my-password-here" Record added successfully >

Hi Rowland, I had run those queries during troubleshooting last night as well, apologies if I get ahead of myself, here are all of my missing roles, they only have dn entries, the second line containing fsmoowner is blank: itwerks at cbadc01:~$ sudo /usr/local/samba/bin/ldbsearch -H /usr/local/samba/private/sam.ldb -b 'CN=System,DC=cb,DC=cliffbells,DC=com' -s sub

Hello, i have two samba 4 domain controllers v4.1.0, with bind_dlz running so far without problems, but now i have some problems with dns. Running samba-tool dns query dc1 samdom.example.com @ ALL returns this error: ERROR(runtime): uncaught exception - (1383, 'WERR_INTERNAL_DB_ERROR') File "/usr/local/samba/lib64/python2.6/site-packages/samba/netcmd/__init__.py", line 175,

Attempting to move FSMO roles from one SerNET Samba 4.5.4 DC to another, all roles transfered except the DNS related ones - those fail with an LDAP_INSUFFICIENT_ACCESS_RIGHTS [root at larkin28 ~]# samba-tool fsmo show SchemaMasterRole owner: CN=NTDS Settings,CN=LARKIN28,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=micore,DC=us InfrastructureMasterRole owner: CN=NTDS

Aaaaaaand more problems... Welcome to the continuing saga of FILER. It appears that neither SOA or NS records were updated during the process of moving fsmo roles to CBADC01. SOA entries on all three active DCs point to FILER. There aren't any NS records for any of the new DCs, only FILER. In RSAT each DNS server's properties show filer.cb.cliffbells.com is the primary server. This

Hey, Thank you Louis for this script, I didn't yet took time to dig in but I'll do. I didn't took time neither to perform another test. That should be done today. Anyway I waited for DC synchronisation before posting. I joined my DC and removed the old ones almost at same time then I gave more than 12 hours to my DC to synchronize. Then I tried to understand what happened, I wrote