similar to: Samba DNS fails when queried with nslookup commands

Hai James, Thanks, thats exactly what we needed. I'll comment below. > -----Oorspronkelijk bericht----- > Van: James Atwell [mailto:james.atwell365 at gmail.com] > Verzonden: donderdag 13 augustus 2020 14:46 > Aan: samba at lists.samba.org > CC: L.P.H. van Belle > Onderwerp: Re: [Samba] Samba DNS fails when queried with > nslookup commands > > Hi Louis and

Hai, Only the forwarder is running in this systemd setup. This : 127.0.0.53:53 does NOT conflict with normaly resolv.conf setting Because samba or any dns server does not run on 127.0.0.53 Dont make the mistake to see this for : 127.0.0.1 Please show : /etc/hosts /etc/resolv.conf Depending on which one your using: /etc/network/interfaces and/or /etc/netplan/01-netcfg.yaml

> -----Oorspronkelijk bericht----- > Van: James Atwell [mailto:james.atwell365 at gmail.com] > Verzonden: donderdag 13 augustus 2020 16:48 > Aan: samba at lists.samba.org > CC: L.P.H. van Belle > Onderwerp: Re: [Samba] Samba DNS fails when queried with > nslookup commands > > > On 8/13/2020 9:57 AM, L.P.H. van Belle via samba wrote: > > Hai James, > >

Hai, @Rowland. Yes yes, you did say you hate systemd. :-) I had a hard(er)time on this one also but i got passed it. ;-) But you and everybody else on the list, please review this setup. And a very big thank you Rowland for the start of it. This should be a good base to start with as howto for ubuntu 18.04 systemd based. Any suggestion additions please add them, below is also the order

Following the guidance here, https://wiki.samba.org/index.php/Idmap_config_ad, I added idmap lines to my smb.conf file on my Samba 4.7 AD-DC server on Ubuntu 18.04. Samba no longer starts and testparm reports that the idmap ranges for the default * domain and the AD domain are overlapping. Here's my smb.conf file (FWIW, if I don't comment security = ADS, server role is set to Member

Hi, I hope someone can help me with the following problem. I followed the following guides to setup samba as an additional active directory server to my windows server with bind9 dns: https://www.tecmint.com/join-additio...r-replication/<https://www.tecmint.com/join-additional-ubuntu-dc-to-samba4-ad-dc-failover-replication/>

Hai, I had a quick look. Barry, can you get this script and run it. https://raw.githubusercontent.com/thctlo/samba4/master/samba-collect-debug-info.sh Then post the results to the list. It collects all info i need to have a better look. I have a few ideas, this might be a resolving order problem, i've based on the errors below. Can you also post the output of bind from the point its

Hi, After installing samba on ubuntu 18.04 following the guide at https://wiki.samba.org/index.php/Setting_up_Samba_as_an_Active_Directory_Domain_Controller  can't do anything with it. # smbclient -L localhost -N Connection to localhost failed (Error NT_STATUS_CONNECTION_REFUSED) looks like its not even running... ps ax | egrep "samba|smbd|nmbd|winbindd"  1965 pts/0    S+     0:00

Hi Rowland, Thats not the point here, if this is a AD-DC or not.. ;-) I'll explain. This is about, how DNS requests are done on the system and accepted by the "dns service" You can install unlimited DNS servers on the AD-DC and chain them, but wize.. No offcourse not. :-) Turning off systemd-resolved is probably a good idea, yes, it is. But it does not harm if its on as long

On Wed, 24 Aug 2016 11:56:06 -0400 lingpanda101--- via samba <samba at lists.samba.org> wrote: > > I know you asked recently but I do have them from a long ago > provisioned DC as reference. > > If you have them, I think you may be the only one who does ;-) A bit of searching doesn't turn up anything about _ldaps records, just _ldap. Rowland

So, I'm curious about the contrast between modifying netplan vs simply disabling systemd.resolved Is there some advantage to the gyrations to make netplan work, vs simply disabling resolved and manually defining the IP and DNS server? [I'm not complaining, I'm thankful for all the options - just wanting to have the best handle possible on the reasoning behind one method vs the other.]

Here are the ouputs of the previous diagnostics you asked for: :~$ nslookup sambaDC Server: 127.0.0.53 Address: 127.0.0.53#53 Non-authoritative answer: Name: sambaDC.domain.com Address: 131.192.176.40 :~$ nslookup sambaDC.domain.com Server: 127.0.0.53 Address: 127.0.0.53#53 Non-authoritative answer: Name: sambaDC.domain.com Address: 131.192.176.40 :~$ host

Hai Barry, We know about exchange might be a problem, the others i dont know.. Check the windows schema levels. https://wiki.samba.org/index.php/AD_Schema_Version_Support You could try a clean setup as shown by my howto. Before you install setup ip and hostname in the windows DNS for the linux server. Make sure you use a name thats never used before, just to be sure of no side effects.

Hi, I am configuring file servers with AD integration with referring below link. I am able to get AD user name and group by running this command wbinfo -u and wbinfo -g but when I run getent passwd and getent group I am unable to see in the list. Please help me to understand where I am doing wrong. https://www.teknophiles.com/2016/11/14/linux-file-servers-in-a-windows-domain/ Environment

On Sun, 9 Jun 2024 13:18:10 +0200 Ronny Preiss via samba <samba at lists.samba.org> wrote: > > No need to build Samba yourself, you can find packages here: > > > > http://www.corpit.ru/mjt/packages/samba/ > How can I install these files? Try reading the 'README' file from the link I posted. > > Here are the requested files from both servers. > >

On 02/03/2020 11:51, Paul Littlefield via samba wrote: > On 02/03/2020 10:49, Rowland penny via samba wrote: >> Does your DC have a fixed IP and if not, why not ? > > Yes, using netplan in Ubuntu 18.04... > > network: > ? ethernets: > ??? ens18: > ????? addresses: > ????? - 130.130.0.218/16 > ????? gateway4: 130.130.0.1 > ????? nameservers: > ???????

On 9/22/2016 6:31 PM, Garming Sam wrote: > On 23/09/16 00:59, lingpanda101 at gmail.com wrote: >> For clarification I'll add a few things. >> >> I initially deleted all the NTDS site links for each site and allowed >> the new KCC to create them. However it did not create them I believe >> correctly. By that I mean it defined what appeared to be a bridgehead

See below, basicly what now happend is. This one line : > 127.0.1.1 gaia.rompen.local gaia <<<< CHANGE THIS Is what is your problem. Read throught the settings, you need a few changes. Its mostly good. After the changes, reboot the AD-DC. Then after its rebooted and after the changes for the member, reboot that also. Then is should be ok. Greetz, Louis >

On 9/21/2016 11:32 PM, Garming Sam wrote: > I would have assumed that deleting all the NTDS connections for all the > DCs would have remedied this issue. I'll write a patch to try to avoid > this error in any case. > > Ignoring this error and answering your earlier question, it's often hard > to tell if the KCC is doing what is expected or not. To figure that out, >

On Sat, 8 Jun 2024 17:05:25 +0200 Ronny Preiss via samba <samba at lists.samba.org> wrote: > Hi, > > I have two problems with my 2 Samba AD-DC. I don't know if the two > problems are related. > Both domain controllers show the same error pattern for problem 1.The > second problem only occurs with the second domain controller. > The domain itself seems to work and