similar to: Replication issues samba 4.10.11-SerNet-Debian-10.buster

Displaying 20 results from an estimated 500 matches similar to: "Replication issues samba 4.10.11-SerNet-Debian-10.buster"

2023 Apr 02
1
Inconsistent SYSVOL ACLs
I have two domain controller servers, with samba in version 4.18 On both DCs both the Sysvol share and the subdirectories (including GPOs) have the same permission: getfacl /usr/local/samba/var/lib/samba/sysvol # file: usr/local/samba/var/lib/samba/sysvol # owner: root # group: 3000000 user::rwx user:root:rwx user:3000000:rwx user:3000001:r-x user:3000002:rwx user:3000003:r-x group::rwx
2016 Nov 16
2
Error on demote dead server
Hi I have a DC server (named dc-server1) with corrupted database. I transferred all FSMO to dc-server2 and now I'm trying to demote dc-server1 running "samba-tool domain demote --verbose --remove-other-dead-server=dc-server1" on dc-server2, but the following error occurred. The problem continues even after running "samba-tool dbcheck --cross-ncs --fix --yes". Samba
2016 Feb 10
0
4.4.0rc2 demote and --remove-other-dead-server
Hi all, We were trying the new --remove-other-dead-server coming with the 4.4.0rc. The domain is a brand new one with several DC added and two Windows clients, no user yet. Here is the smb.conf: [global] workgroup = SAMBA realm = SAMBADOMAIN.TLD netbios name = DC200 server role = active directory domain controller server services = -dns
2016 Dec 16
2
remove dead server (samba 4.4.4)
Hi, I'm trying to remove a DC from a site we have shutdown. The demote command is throwing up this message: [root at aragorn ~]# samba-tool domain demote --remove-other-dead-server=pippin Removing nTDSConnection: CN=eca08dbb-1f34-476e-96dd-33ec22b2bc94,CN=NTDS Settings,CN=GANDALF,CN=Servers,CN=SAOPAULO,CN=Sites,CN=Configuration,DC=e-trust,DC=com,DC=br Removing nTDSDSA: CN=NTDS
2020 Jun 10
2
getting no SRV record
I am setting up a newly reloaded Ubuntu 18.04.4LTS Samba 4.12.3 domain controller with BIND9_DLZ. All has gone well until I run: root@[dchost]:~# host -t SRV _ldap._tcp.[domain].work. _ldap._tcp.[domain].work has no SRV record Then I run: root@[dchost]:~# samba-tool dns add [dchost] [domain].work _ldap._tcp SRV '[dchost].[domain].work 8080 0 100' -Uadministrator Password for
2020 Jun 10
2
getting no SRV record
Same result: root@[dchost]:~# host -t SRV _ldap._tcp.$(hostname -d) _ldap._tcp.[domain].work has no SRV record (Sent from home location.) Bob Wooden Donelson Trophy 615.885.2846 On 6/10/20 2:37 PM, Rowland penny via samba wrote: > On 10/06/2020 20:25, Bob Wooden via samba wrote: >> I am setting up a newly reloaded Ubuntu 18.04.4LTS Samba 4.12.3 >> domain controller with
2020 Jun 11
0
getting no SRV record
(Sent from home location.) Bob Wooden On 6/10/20 7:51 PM, Bob Wooden via samba wrote: > > (Sent from home location.) > > Bob Wooden > > > root@[[dchost]:~# cat /etc/hosts > 127.0.0.1??? localhost > 192.168.16.50??? [dchost].[domain].work??? [dchost] > > root@[dchost]:~# systemctl status bind9 > ? bind9.service - BIND Domain Name Server > ?? Loaded: loaded
2020 Jun 11
2
getting no SRV record
(Sent from home location.) Bob Wooden On 6/10/20 4:16 PM, Rowland penny via samba wrote: > Try checking /etc/resolv.conf, it should be: > > search [domain].work > > nameserver <the DC's ipaddress> > > I seem to remember Bind9 being mentioned, is it running ? > > Is /etc/hosts set up correctly ? > > Rowland And here ya go. root@[[dchost]:~# cat
2016 Oct 20
2
Correcting "incorrect userParameters value on object...." ???
sernet-samba-4.2.14-23.el6.x86_64 Errors [on all DCs] related to incorrect userParameters values - on user's that are working. How does one go about rebuilding/correcting this value? [root at larkin28 ~]# samba-tool dbcheck --reset-well-known-acls --fix - -yes Checking 1743 objects ERROR: incorrect userParameters value on object CN=darrell,OU=Industries Users,DC=example,DC=com. If you have
2020 Jun 10
2
getting no SRV record
Here's what happened: root@[dchost]:~# samba_dnsupdate --use-samba-tool Failed to get Kerberos credentials, falling back to samba-tool: kinit for [dchost]$@[domain].WORK failed (Cannot contact any KDC for requested realm) ERROR(runtime): uncaught exception - (9711, 'WERR_DNS_ERROR_RECORD_ALREADY_EXISTS') >>>>>>>> snipped for brevity
2019 Dec 18
3
DNS replication issue
Hi Rowland, Thank you for replying. Please find the output here below. Just a possible tip: _kerberos._tcp.example.com??? service = 0 100 88 addc-new.example.com. output is present on the new machine but if we issue a host -t SRV _kerberos._tcp.example.com on addc2 it does not appear in the list. Kind regards. Collected config? --- 2019-12-18-20:30 ----------- Hostname: addc-new DNS Domain:
2019 Aug 20
0
Problems with NIS Server on Samba 4
On 20/08/2019 02:59, Marcio Demetrio Bacci wrote: > Hi, > > I performed the procedures below on Samba4-DC1 (Master) and apparently > everything went fine. > > /etc/init.d/samba-ad-dc stop > > sed -i -e 's/${DOMAINDN}/DC=empresa,DC=com,DC=br/g' \ > ? ? ? ? ?-e 's/${NETBIOSNAME}/SAMBA4-DC1/g' \ > ? ? ? ? ?-e 's/${NISDOMAIN}/empresa/g' \ > ? ?
2020 Jun 10
0
getting no SRV record
On 10/06/2020 21:58, Bob Wooden via samba wrote: > Here's what happened: > > root@[dchost]:~# samba_dnsupdate --use-samba-tool > Failed to get Kerberos credentials, falling back to samba-tool: kinit > for [dchost]$@[domain].WORK failed (Cannot contact any KDC for > requested realm) > > ERROR(runtime): uncaught exception - (9711, >
2016 Sep 02
1
Segmentation fault in samba_upgradedns - Samba 4.4.5
On 2 September 2016 at 14:51, Rowland Penny via samba <samba at lists.samba.org > wrote: > > > As I said, I know very little about freebsd, but you should be aware > that Samba only supports the last three major versions i.e. at the > moment 4.2.X, 4.3.x and 4.4.x > They are supported in three ways, the oldest version (now 4.2.x) only > gets security fixes, the middle
2020 Jun 10
2
getting no SRV record
It is the first DC in a new domain. Nothing is "joined" to it. (Sent from home location.) Bob Wooden Donelson Trophy 615.885.2846 On 6/10/20 3:04 PM, Rowland penny via samba wrote: > On 10/06/2020 20:51, Bob Wooden via samba wrote: >> Same result: >> >> root@[dchost]:~# host -t SRV _ldap._tcp.$(hostname -d) >> _ldap._tcp.[domain].work has no SRV record >
2020 Jun 11
2
getting no SRV record
On 11/06/2020 12:16, Bob Wooden via samba wrote: > When I "nslookup". I get: > > root@[dchost]:~# nslookup [dchost].[domain].work > Server:??? ??? 192.168.116.50 > Address:??? 192.168.116.50#53 > > Non-authoritative answer: > Name:??? [dchost].[domain].work > Address: xx.198.245.139 > > This local active directory is the first I have ever setup with a
2019 Oct 11
1
dns replication error due to deleted records
El 11/10/19 a les 17:29, Rowland penny via samba ha escrit: > On 11/10/2019 16:02, Luca Olivetti via samba wrote: >> El 11/10/19 a les 16:59, Luca Olivetti via samba ha escrit: >>> El 11/10/19 a les 16:12, Rowland penny via samba ha escrit: >>>> Try running this on a DC: >>>> >>>> samba-tool ldapcmp ldap://DC1 ldap://DC2 >>>>
2019 Dec 18
2
DNS replication issue
Hello, We are setting up 2 AD machines: New machine with subnet 192.168.1.21: Version 4.10.11-SerNet-Debian-10.buster Bind version 9.11.5 Existing machine 1 with subnet 192.168.2.21 Version 4.10.11-SerNet-Debian-10.stretch Bind version 9.10.3 Existing machine 2 with subnet 192.168.3.21? Version 4.10.11-SerNet-Debian-10.stretch Bind version 9.10.3 All with BIND_DLZ backend, same
2019 Aug 29
0
Permission Issue
Hi, this configuration doesn't make any differenc in daily life. So perhaps an ID-Mapping problem? an ldbsearch --url=/var/lib/samba/private/sam.ldb shows dn: CN=Team IT and facilities,OU=HO,OU=example,DC=com,DC=de objectClass: top objectClass: group cn: Team instanceType: 4 whenCreated: 20180731103742.0Z uSNCreated: 3631 name: Team objectGUID: 7a27f859-97dc-4cf8-b4b1-c7b7cfe0f585
2020 Jun 10
0
getting no SRV record
On 10/06/2020 20:51, Bob Wooden via samba wrote: > Same result: > > root@[dchost]:~# host -t SRV _ldap._tcp.$(hostname -d) > _ldap._tcp.[domain].work has no SRV record Is this the first DC in a new domain, or a new DC joined to an existing domain ? If it is the latter, then it might be a samba_dnsupdate problem, try looking in syslog. You could try adding 'dns update command =