similar to: Network rebuild advice needed

Thank you for your assistance. Turns out everything is really really screwed up and I can't even add a DC right now. I thought I had added a third and it seemed to be replicating but now the other two won't recognize it as a DC. I'm so deep in this hole right now I'm considering nuking the whole thing, quitting my job and moving to a desert island. It seriously couldn't make

Of course, it seems we are running Samba 4.7.6-Ubuntu. Great. The biggest regret of my last few years is that we are also running Zentyal, which I am desperate to get rid of. I'm trying to build a new server with the latest Samba and join that to the domain to see if I can get a good copy of the database, then wipe the other servers and rebuild them from scratch On Sat, Aug 29, 2020 at

Tried the join. Failed to find a writeable DC Tried with --server and gave it the name of one of the servers. No luck Tried a different server and.... itadmin at dc2020:/run/samba$ samba-tool domain join kcs.local DC -U"KCS\domainadmin" --dns-backend=SAMBA_INTE RNAL --server "luke.kcs.local" Password for [KCS\domainadmin]: INFO 2020-08-30 00:37:08,420 pid:175166

On 17/08/2020 04:21, Peter Pollock via samba wrote: > So I screwed up my AD. > > At some point a Windows 2019 server was attempted to be added and it messed > the schema up. > > That server was removed and ceremonially burned in the fire pit but I > couldn't fix the issues that had arisen, so I restored both of the original > Samba DC's from backups That is

Given the situation in the world today, I would agree a desert island sounds ideal. However I think there is hope for your network, so you can run away in peace. First, you have not said which Samba versions you are using, so the advise below is a bit generic. If my network was behaving like this I would use Samba's backup tools to make a backup, and start again with the restored domain,

A join might be all your need, but given the source version you can't do an offline backup, so I would then see if you can use our online backup tool, then restore from there. Andrew Bartlett On Sat, 2020-08-29 at 17:02 -0700, Peter Pollock wrote: > Of course, it seems we are running Samba 4.7.6-Ubuntu. > > Great. > > The biggest regret of my last few years is that we are

Yeah, I already tried that, to no avail. I finally had some modicum of success. Switched everything off except one server, then restored that from June and was able to then build a new server and join it to the domain. And everything was peachy. Except the original server has some stupid zentyal issues which no one on the zentyal boards can help me fix and when I then demoted the original

You have a duplicate RID pool, so the RIDs that it thinks it can allocate are already allocated. dbcheck on Samba 4.5 and later (so should work for your 4.7) can fix that. Run that on the source server locally. Andrew Bartlett On Sat, 2020-08-29 at 17:42 -0700, Peter Pollock wrote: > Tried the join. Failed to find a writeable DC > Tried with --server and gave it the name of one of the

Hi all, I know this isn't strictly Samba related, but I have a fileserver and want to install some VM software on it so I can build a new Samba DC on there and still keep the fileserver running. In your experience, what's the best VM to install? Are there any which wok better or worse with Samba? Does it make any difference? I'm running Ubuntu 20.04.1 Thanks!

Andrew, I very much appreciate your swift reply and your expertise. I readily admit I'm a little out of my depth here. I'm sitting here in California at almost midnight with just the weekend to get done all I need to do on the network and I fear this may be derailing my plans. This article on the Samba Wiki https://wiki.samba.org/index.php/Changing_the_IP_Address_of_a_Samba_AD_DC seems to

Please forgive me, I'm not sure what terminology to use here so this question may sound wrong. I have built two servers samba servers with a new domain. They replicate happily and I can seem to do everything I could ever want on them. DC01 holds all the FSMO roles and, as the first one built, acts as the "master" for DNS. Nothing works well on either server if DC01 is not at the

To save the whole back story, I borked everything and had to restore from backups. DC1 and DC2 (Samba DC's) came back fine DC3 (Windows 2008 DC) did not come back. Which is fine, I wanted to decommission it anyway. I have seized all the FSMO roles (because DC3 previously held them all) and replication SEEMS to be OK (users created on each machine replicate across instantly, although

Thanks Rowland. Have submitted a bug report (No 11818). spindles7 On Thu, 31 Mar 2016 09:38:02 +0100, Rowland penny <rpenny at samba.org> wrote: >On 30/03/16 23:26, spindles7 wrote: >> Hi all, >> I am consistently getting the error: >> >> root at dc2:~# samba-tool domain demote -Uadministrator >> Using dc1.microlynx.com as partner server for the demotion

Am 12.08.19 um 17:07 schrieb L.P.H. van Belle via samba: > Hai Stefan, > > Why make DC2 a member?? > Leave it as is, setup a new member, much better, and i'll bet less work/stress. In fact it's even DC1 but anyway: because of the hardware. Specific RAID arrays etc needed for backups and snapshots.

On 01/04/16 22:38, spindles7 wrote: > Hi Rowland, > Have tried your patch, and now the Demote succeeds: > > root at dc3:~# samba-tool domain demote -Uadministrator > Using dc1.microlynx.com as partner server for the demotion > Password for [MICROLYNX\administrator]: > Deactivating inbound replication > Asking partner server dc1.microlynx.com to synchronize from us >

Hi! i have 3 dcs with samba i demote bdc and replace it with dc2 with de same ip the replicate with dc1 is ok, and the replicate of dc3 with dc1 is ok, the problem is in dc2 with dc3 i found the problem, but i dont known how fixes when i do samba-tools drs showrepl in dc3 i see in connection appears the old dc named bdc and dont appears the new, dc2 i try with samba-tool drs replicate but

I have a domain with two Samba DC's I don't want to use either of them as a fileserver, so I want to build a separate file server which is not a DC, which will deliver all the files to the lovely little windows users (including their roaming profiles). I've been looking online and there seems to be a thousand different ways to "join" my fileserver to the domain, but most of

Checking the databases against each other throws up pages and pages of errors. The two are completely out of sync now. What I have seen is that for no apparent reason, one of the servers suddenly decided it would sync with the Windows server, which appears to have updated the schema. Yesterday when I compared the databases on the two linux servers they only had a couple of errors, today, many

Apparently I missed a step somewhere! On DC01 /etc/systemd/resolved.conf says [Resolve] #DNS= #FallbackDNS= #Domains= #LLMNR=no #MulticastDNS=no #DNSSEC=no #DNSOverTLS=no #Cache=yes #DNSStubListener=yes #ReadEtcHosts=yes On DC02 it reads [Resolve] DNS=8.8.8.8 FallbackDNS=8.8.4.4 #Domains= #LLMNR=no #MulticastDNS=no DNSSEC=no #DNSOverTLS=no #Cache=yes #DNSStubListener=yes #ReadEtcHosts=yes So

To get the question of why new servers, this one I'm using has hardware whose remaining life is measured in days. The elastic bands and sticky tape it is held together with won't hold for much longer. I'm using it to build and test a new environment, but then I need to migrate that onto something with a little more vitality before bringing it into production (in the next 56 hours). As