similar to: samba Digest, Vol 208, Issue 5

Thanks for your advice, Rowland > > Yes, I am setting up a new Samba-based AD DC. > If you are joining? to an existing domain, then you cannot be setting up > a new domain ;-) Yes - joining a new DC to an existing domain. > > Should I install BIND9 and DHCP first, then install Samba and do the join? > > I personally would do it in stages, set up the Rpi, add

On 05/04/2020 17:34, Rick Hollinbeck via samba wrote: > Yes, I am setting up a new Samba-based AD DC. If you are joining? to an existing domain, then you cannot be setting up a new domain ;-) > The goal is to eventually transfer the FSMO roles to the Pi and remove my current Windows > 2008 servers. Shouldn't be a problem. > > Should I install BIND9 and DHCP first, then install

Greetings all; Does nut build on an r-pi4b? I have an r-pi4b running one of my cnc machines and the power bump performance due to the size of its psu and the fairly rapid start time of my standby generator, does not allow a full powerdown restart to take place, leaving the pi in a crashed state. I've purchased a factory refurbed cyberpower ups rated at 650 WA which I intend to figure

On 04/05/2020 12:59, Jelle de Jong via samba wrote: > > root at samba01:~# cat /etc/nsswitch.conf? | grep winbind > passwd:???????? files systemd winbind > group:????????? files systemd winbind OK, the only computer I have that runs systemd, is my Rpi4 running Raspbian, which is basically Buster compiled for ARM. I have in /etc/nsswitch.conf: passwd:???????? files winbind

On 06/04/2020 19:53, Rick Hollinbeck wrote: > My dhcpcd.conf specifies a fixed ip for eth0, but I don't really know how well it will play with > bind9 and samba. > I think I'll take your advice here. I understand why Raspbian uses dhcpcd, it makes it easier for them, but I see no good reason to use it on something that should have a fixed ipaddress. > > I'm also

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 >

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

I'm looking for some general advice. I'm beginning to set up a Raspberry Pi 4 as a SOHO server with Samba on Raspbian Buster. I will be running as a member of an existing Windows AD (JOIN), then allow logging in from Windows and Linux clients. (I previously got Samba 4.11 to join my domain successfully using a Ubuntu VM.) I am also planning to install BIND9 DNS with dynamic updates

But runs normally if started. On a rpi4 running an uptodate raspbian buster, how do I set it to auto start at boot time? Thanks. Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) If we desire respect for the law, we must first make the law respectable. - Louis D.

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.]

On 2020-09-05 05:23, Roger Price wrote: > On Sat, 5 Sep 2020, Gene Heskett wrote: > >> But runs normally if started. On a rpi4 running an uptodate raspbian >> buster, how do I set it to auto start at boot time? > > Hello Gene, By "auto start" I assume you mean the automatic power on of a box > when wall power returns after a power failure. For this to

Hi, I'm not sure if it is a bug or a feature. I'm running Ubuntu 20.04 on my RPi4 which connects to the UPS over USB. I have noticed whenever I reboot my RPi4. It resets the UPS ( I can hear the relay) -- Powerloss. Any pointers to disable this annoying bug / feature. ups.conf: --8<---- [tripp] driver = usbhid-ups port = auto vendorid = 09ae productid = 2009 bus

On 05/02/2020 10:33, L.P.H. van Belle via samba wrote: > >> I didn't bother checking, I can cause the panic just by editing >> smb.conf, adding the two lines in question and then >> restarting Samba. I >> do this over SSH, so presumably the network is up on eth0 ;-) > Ah, ok, so we clearly have bug in samba??? > But i dont see this one on Debian Buster

Louis, et al. Hi! So, I'm working on a 20.04 setup. I think I'll still use the distro version and not Louis' packages. [No offense Louis - I just need to be sure if (forbid) anything happens to Louis, his packages aren't going to be supported any more, and I'll be on my own for security updates etc. The 20.04 versions are pretty current, and I think will meet my needs for the

On Sep 5, 2020, at 5:23 AM, Roger Price wrote: > > On Sat, 5 Sep 2020, Gene Heskett wrote: > >> But runs normally if started. On a rpi4 running an uptodate raspbian buster, how do I set it to auto start at boot time? > > Hello Gene, By "auto start" I assume you mean the automatic power on of a box when wall power returns after a power failure. For this to work,

Hai marco, Well, "My" preffered for now is systemd-networkd. Current debian still used /etc/network/ but next will be systemd as default. Ubuntu uses : /etc/netplan/ Howto configure it. wget https://raw.githubusercontent.com/thctlo/debian-scripts/master/setup-systemd-networkd.sh bash setup-systemd-networkd.sh member Nothing will be changed on the system but you end up with a

Hi, I have set up a fresh DC from scratch using samba 4.5.1 with Bind9, added another DC, all strictly following the instructions in the samba wiki. Samba was built from the source tarball on debian/raspbian 8u8 (Jessie), Bind9 is 9.9.5-9 coming with the OS. Everything appears to be in a working order: I can join Windows workstations, add Users with RSAT, etc. Only when comparing the

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/>

Hello Rowland,     thank you for advice. I reconfigure both AC-DCs again with new data and send updated data. Unfortunately, the result is the same. I'm also sending a listing from samba-setup-checkup.sh.  * Linux: Raspbian, debian stretch lite  * Samba version 4.5.12-Debian  * DNS: BIND9_DLZ 9.10.x  * Installed packages: ntp ntpdate samba smbclient winbind libcups2 samba-common

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