similar to: Changing IP Scope on a Samba DC

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

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

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

On Fri, 2020-08-28 at 21:02 -0700, Peter Pollock via samba wrote: > 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

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

Hello Environment: 3 DC. samba Version 4.10.15-Debian I have to change the IP address of one of my DC's. Can I simply: 1. Demote DC 2. Change IP 3. Rejoin with: samba-tool domain join ... or should I do some more things ? Can I keep the old DC name or should I change it? Thanks

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

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

On 03/09/2020 20:18, Peter Pollock wrote: > Hi Rowland, > > The sample files you sent me... in named.conf.options you had the line > listen-on port 53 { 192.168.2.8; 127.0.0.1; }; > > 192.168.2.8 is not used on our network as far as I'm aware. is that > correct? or should I change it to the IP of the server? > > Thanks, Peter > > PS I'm building a new

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

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

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

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

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

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

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

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