similar to: Replication error on newly joined DC

I found the answer... I was missing a line from the Global section of smb.conf server services = s3fs, rpc, nbt, wrepl, ldap, cldap, kdc, drepl, winbindd, ntp_signd, kcc, dnsupdate On Sat, Mar 4, 2023 at 1:55?PM Peter Pollock < peter.pollock at kingschristian.org> wrote: > OK. I have been trying to add a DC. I've followed the instructions to > build a DC that are on the Samba

> > > > OK, you are using the winbind 'rid' backend, so it is okay to use > 'Domain Admins', so start again and follow that wikipage: > > Ensure you have the 'acl' & 'attr' packages installed (this is what they > are called on Debian based distros) > They are installed. I built the server using the walk through you gave me. >

Thank you everyone for your help. I corrected my resolv.conf files as Peter Milesson suggested and then had to take a number of extra steps so now things are looking a little better. In case it helps anyone else in the future, here's what I found (plus I am now having problems resolving internal addresses). As far as I can see, the setup on both servers is identical (except they use their own

I have just set up a new AD and am having a little success with it, but DNS resolution is a little slow. I'm looking into why that is and tried an ns lookup for google.com and got the answer SERVFAIL on my AD server. The query was then passed to my next nameserver (google's own dns), which handled the query. Is this correct behaviour? I've not seen SERVFAIL before itadmin at

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

I think it?s the cache. When you where sleeping the cache got updated. But I can be wrong Philip > On 5 Sep 2020, at 12:35, Rowland penny via samba <samba at lists.samba.org> wrote: > > On 05/09/2020 09:53, Peter Pollock via samba wrote: >> I have just set up a new AD and am having a little success with it, but DNS >> resolution is a little slow. >> >>

Thanks! ?"jammy" made it work. ? For some reason, ?lsb_release -cs is returning "victoria" rather than "jammy", and $> sudo apt update Hit:1 http://archive.ubuntu.com/ubuntu jammy InRelease Ign:2 http://packages.linuxmint.com victoria InRelease Get:3 http://archive.ubuntu.com/ubuntu jammy-updates InRelease [119 kB] Hit:4 http://packages.linuxmint.com victoria

On 03/09/2020 20:57, Peter Pollock wrote: > Ubuntu 20.4 and whatever Samba it installs (sorry, I'm not in front?of > the server right now). 4.11. x if I remember correctly, so okay to start with, but can I introduce to Louis Van Belle's repo: http://apt.van-belle.nl/ Once you get up and running, you can use the packages there to keep current. > > Bind 9.16 (although there

On Mon, 04 Dec 2023 13:41:47 -0500 Steve Gutreuter <sgutreuter at gmail.com> wrote: > $> sudo /usr/bin/add-apt-repository "deb > https://cloud.r-project.org/bin/linux/ubuntu $(lsb_release > -cs)-cran40/" Looks like `lsb_release -cs` returns a Mint codename for you. Thankfully, since we know that Linux Mint 21 is based on Ubuntu 22.04 "Jammy Jellyfish", it

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

I just upgraded from Linux Mint 20 to 21 and am no longer able to add the CRAN Ubuntu repository to my list of repositories. ?I am getting: $> sudo /usr/bin/add-apt-repository "deb https://cloud.r-project.org/bin/linux/ubuntu $(lsb_release -cs)-cran40/" $> sudo apt update Hit:1 http://security.ubuntu.com/ubuntu jammy-security InRelease Hit:2 http://archive.ubuntu.com/ubuntu jammy

05.12.2023 17:21, Joachim Lindenberg via samba: > I just upgraded one of my DCs ununtu 20.04 -> 22.04 and samba 4.18 -> 4.19, but the Dc is not yet working again. > > systemctl status samba-ad-dc shows: > > Dec 05 12:48:39 cobra samba[749]: [2023/12/05 12:48:39.562920, 0] ../../source4/samba/service_task.c:36(task_server_terminate) > Dec 05 12:48:39 cobra samba[749]:

I'm having trouble with my new fileserver, I can't make the shares viewable by windows clients. I had the same problems with the first file server I built and cannot remember what I did to "fix" it. I have gone through the page "Setting up a share using Windows ACL's" on the Samba Wiki ( https://wiki.samba.org/index.php/Setting_up_a_Share_Using_Windows_ACLs) but

OK, tried that. Kicked myself for not trying earlier... but it didn't work. In fact, the error has got worse. Now when I try to go from Genesis to Luke I get: sudo samba-tool drs replicate luke genesis DC=kcs,DC=local -Udomainadmin . . ERROR(<class 'samba.drs_utils.drsException'>): DsReplicaSync failed - drsException: DsReplicaSync failed (1359, 'WERR_INTERNAL_ERROR')

Hi, I have been trying for days to solve this to no avail. I have taken over the IT responsibilities at a small school and am trying to get my head around their network and why they are having problems. They have 3 servers, Matthew, Genesis and Luke. Matthew is a Windows 2008 R2 server and holds all the FSMO roles but appears to be screwed up. It won't replicate with anything and randomly

On Fri, 2024-04-05 at 08:04 +0100, Rowland Penny via samba wrote: > On Fri, 05 Apr 2024 08:06:10 +0200 > PaLi via samba <samba at lists.samba.org> wrote: > > > Hello > > > > I have a strange problem on a brand new installation of samba AD > > (samba-4.19.5 on Fedora 39). > > > > Domain controller is dc01.some.domain.org > > Secondary

We have two Samba 4.2.3 servers with FreeRadius to authenticate wireless users against active directory. Using DNS, sometimes both servers end up using the same domain controller to authenticate users. I would like to distribute the load to different DCs. Is there a way to manually point Samba to certain DCs? I tried the following configuration: security = ads password server =

On Fri, 05 Apr 2024 15:38:23 +0200 pavel.lisy at gmail.com wrote: > On Fri, 2024-04-05 at 08:04 +0100, Rowland Penny via samba wrote: > > On Fri, 05 Apr 2024 08:06:10 +0200 > > PaLi via samba <samba at lists.samba.org> wrote: > > > > > Hello > > > > > > I have a strange problem on a brand new installation of samba AD > > >

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

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