similar to: Changing IP Scope on a Samba DC

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 31/08/2020 19:59, Peter Pollock wrote: > Yes, it is 192.168.2.0/24 <http://192.168.2.0/24> > > Thank you. OK, try these files: /etc/bind/named.conf -----------start--------------- // This is the primary configuration file for the BIND DNS server named. // // Please read /usr/share/doc/bind9/README.Debian.gz for information on the // structure of BIND configuration files in

Ubuntu 20.4 and whatever Samba it installs (sorry, I'm not in front of the server right now). Bind 9.16 (although there is no AD DNS Zone file for that version of Bind so I'm using the version 9.12 file (database "dlopen /usr/local/samba/lib/bind9/dlz_bind9_12.so") The provision did not go well. I'm not sure why. I'm learning though. slowly but, well, slowly. On Thu,

On 05/09/2020 07:46, Peter Pollock wrote: > I FINALLY DID IT!!!!! > > After following Louis van Belle's walk-through to create a new DC, and > having problems at the end, I realized there was nothing in the walk > through about modifying?/var/lib/samba/bind-dns/named.conf to let > Samba know the Bind version so I did that and Voila! > > We have name resolution, can

OK.. after school ended today, I poked around and found nothing so I started all over again. Followed Louis' instructions at https://github.com/thctlo/samba4/blob/master/full-howto-Ubuntu18.04-samba-AD_DC.txt all the way through but at the end, the resolver is not working - and kinit cannot find a KDC (I'm guessing because the resolver is not working!) This is the only server on the

Thank you for your help Rowland. I have done as Andrew suggested with mixed success. The biggest problem I've found is that the internal DNS is seriously screwy. There are no zone files for the domain that I can find and no server suggests it's the master - yet when dc1 falls over they all fall down. I'm going to find somewhere else to seek assistance with that because it's a bind

Samba seems to have provisioned OK, but kinit cannot find the realm and I have some records missing that I don't know how to fix: itadmin at dc01:~$ kinit administrator at INTERNAL.KCS kinit: Cannot find KDC for realm "INTERNAL.KCS" while getting initial credentials itadmin at dc01:~$ host -t SRV _ldap._tcp.internal.kcs Host _ldap._tcp.internal.kcs not found: 3(NXDOMAIN) itadmin at

I just ran samba_dnsupdate --all-names and got this: itadmin at genesis:~$ sudo samba_dnsupdate --all-names add_interface: not adding duplicate interface 192.168.1.11 ldb_wrap open of secrets.ldb GENSEC backend 'gssapi_spnego' registered GENSEC backend 'gssapi_krb5' registered GENSEC backend 'gssapi_krb5_sasl' registered GENSEC backend 'spnego' registered GENSEC

On 05/09/2020 09:12, Peter Pollock wrote: > I just found the /etc/hosts thing two seconds before reading your email. > > A couple of questions: > > 1) The install also did nothing to krb5.conf - do I need to merge it > with the file that the install generated? No, the one the distro created is enough. > 2) When adding a DC to this domain, do I follow the same walk-through

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

I just found the /etc/hosts thing two seconds before reading your email. A couple of questions: 1) The install also did nothing to krb5.conf - do I need to merge it with the file that the install generated? 2) When adding a DC to this domain, do I follow the same walk-through but just use samba-tool domain join instead of domain provision? 3) What tests should I run? I can join a computer to the

On 01/09/2020 20:17, Peter Pollock wrote: > Thanks Rowland. > > I'll try out those changes tonight. > > The two cards are necessary because I this is my gateway machine. One > card connects to the internet router on 10.1.10.80 and the other > connect to the local lan. I personally do not think that is a good idea, we do not recommend using a DC as a fileserver, never

On 01/09/2020 18:48, Peter Pollock wrote: > 192.168.1.11 was from a time we tried to increase the number of > available IP's by adding a virtual IP in Zentyal for the server to > listen on. It never worked and now Zentyal won't let me remove it, due > to not being able to save changes. You really need to fix this. You have two ethernet cards, eth0 & eth1, do you really

I FINALLY DID IT!!!!! After following Louis van Belle's walk-through to create a new DC, and having problems at the end, I realized there was nothing in the walk through about modifying /var/lib/samba/bind-dns/named.conf to let Samba know the Bind version so I did that and Voila! We have name resolution, can create kerberos tickets, just successfully connected a windows workstation to the

I would have added an extra DC.. Move FSMO Removed old server from AD, Cleanup AD. Install new server with new ip's. And Add CNAMEs where needed, Move FSMO back. Remove extra DC. ;-) Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > Rowland penny via samba > Verzonden: vrijdag 4 september 2020 10:00 >

On 01/09/2020 00:33, Peter Pollock wrote: > I just ran? samba_dnsupdate --all-names and got this: > > itadmin at genesis:~$ sudo samba_dnsupdate --all-names > add_interface: not adding duplicate interface 192.168.1.11 You said that you were using the 192.168.2.0/24 network, where is that ipaddress coming from ? > ldb_wrap open of secrets.ldb > > update failed: NOTAUTH >

On 29/08/2020 07:54, Peter Pollock via samba wrote: > 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

On 29/08/2020 07:54, Peter Pollock via samba wrote: > > 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

I've asked a couple of other questions on here, which people have kindly answered and I'm waiting for the opportunity to implement what they have suggested. In the meantime: We are running out of IP addresses! We currently use 192.168.2.0/24 and it's proving to not be enough addresses. I'm considering changing to 192.168.4.0/22 to virtually quadruple the number of addresses we

This is brand new. Created following Louis' instructions (although in my install of Ubuntu 20.04, it gets a little tricky with installing packages because it claims one or more don't exist after adding Louis' repository and doing an apt update). Totally separate network from my Zentyal installs, on a ProxMox virtual server, if that makes any difference. I know the admin password, I