similar to: User names not replicating to secondary DC

Displaying 20 results from an estimated 3000 matches similar to: "User names not replicating to secondary DC"

2020 Mar 02
0
User names not replicating to secondary DC
> Can you run this script on both DC's. > > https://github.com/thctlo/samba4/raw/master/samba-collect-debug-info.sh === BEGIN dc0 === Collected config --- 2020-02-28-08:30 ----------- Hostname: dc0 DNS Domain: msi.mydomain.com FQDN: dc0.msi.mydomain.com ipaddress: 172.23.93.25 ----------- Kerberos SRV _kerberos._tcp.msi.mydomain.com record verified ok, sample output:
2020 Feb 28
3
User names not replicating to secondary DC
Can you run this script on both DC's. https://github.com/thctlo/samba4/raw/master/samba-collect-debug-info.sh Anonimize where needed but keep thing like. You.dom.tld like that, dont change that to example.tld. Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > Durwin via samba > Verzonden: vrijdag 28 februari
2020 Feb 28
1
User names not replicating to secondary DC
> > > > > Why are you using the internal dns server on one DC and Bind9 on the > > other ? > > I am very familiar with configuring Named on Fedora. I thought it > > would be > > just as easy on Ubuntu. After discovering the files were in different > > places > > and so many more being 'included', I decided to use internal on the
2020 Feb 27
3
User names not replicating to secondary DC
> > DC1 smb.conf > > winbind use default domain = true > > winbind offline logon = false > > winbind nss info = rfc2307 > > winbind enum users = yes > > winbind enum groups = yes > > The above lines have no place in a DC smb.conf or are defaults Commented them out. > > Change the following files as shown:
2020 Feb 28
1
User names not replicating to secondary DC
Your setup is in consistant. > 127.0.0.1 localhost.localdomain localhost > 127.0.0.1 localhost I suggest run my debugscript, make sure the servers there base setup is the same. + set both DC's there /etc/resolv.conf search msi.mydomain.com mydomain.com # IF THIS IS DC1 nameserver 172.23.93.26 nameserver 172.23.93.25 nameserver 172.23.93.3 # and for DC0
2020 Feb 27
2
User names not replicating to secondary DC
Two attachments are not being sent. Pasting contents. DC0 smb.conf # Global parameters [global] netbios name = DC0 realm = MSI.MYDOMAIN.COM server role = active directory domain controller server services = s3fs, rpc, nbt, wrepl, ldap, cldap, kdc, drepl, winbindd, ntp_signd, kcc, dnsupdate workgroup = MSI # This line was added 190710 (DFD)
2014 Jul 21
1
samba-tool domain demote - current DC is still the owner of 2 role(s)
Hey guys, I had recently setup a new DC (called dc0) (in accordance with the wiki) and now I would like to demote the old DC (called pdc0 :)). I followed the wiki again, but I ran into the following issue. When trying to demote the old DC, I get this error message: pdc0 # samba-tool domain demote ERROR: Current DC is still the owner of 2 role(s), use the role command to transfer roles to another
2020 Mar 02
2
User names not replicating to secondary DC
On 02/03/2020 18:59, Durwin via samba wrote: >> Can you run this script on both DC's. OK, dc0 seems to have the ipaddress: 172.23.93.25 ?????? dc1 seems to have the ipaddress: 172.23.93.26 So why does dc1 use 172.23.93.3 as its nameserver ? and what is 172.23.93.3 ? The /etc/krb5.conf files should be the same on both machines, I prefer this format: [libdefaults] ???????
2012 Sep 25
1
DRS replication fails with Windows 2003 R2
Hello. We're trying to integrate Samba 4 as a DC in production. We aim to replace our only Windows 2003 Enterprise R2 Russian DC with 2 Samba DCs. However, we've got a replication problem, we aren't shure is it a bug or misconfiguration. Both Windows and Samba DCs are virtual amd64 machines, running under the control of Xen (so, at least the time is the same). Windows VM has GPLPV
2020 May 18
4
Intermittent permission denied when accessing share
> trying again. here's the output. thanks! Config collected --- 2020-05-18-23:08 ----------- Hostname: fileserver DNS Domain: wdc.mydomain.it Realm: WDC.MYDOMAIN.IT FQDN: fileserver.wdc.mydomain.it ipaddress: 10.0.0.3 ----------- This computer is running Ubuntu 18.04.4 LTS x86_64 ----------- running command : ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc
2019 May 15
0
Workstations cannot update DNS
On 15/05/2019 21:43, durwin at mgtsciences.com wrote: > > > *named.conf.options* > > > options { > > >         directory "/var/cache/bind"; > > > > > >         // If there is a firewall between you and nameservers you want > > >         // to talk to, you may need to fix the firewall to allow > multiple > > >         //
2020 Sep 01
0
Changing IP Scope on a Samba DC
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. We do use .local because Microsoft small business server, which we were playing with before we started down this route automatically suggested we use the
2020 Feb 27
5
User names not replicating to secondary DC
I have 2 Ububtu DCs. One acting as a secondary/failover. At one point the users were replicated from primary to secondary. But now they are not replicating. The output from samba-tool drs showrepl is attached. What else may I provide to aid diagnostics? I know Samba does not replicate sysvol 'yet', so rsync is needed, but that does not seem to contain the users. Thank you,
2019 May 15
2
Workstations cannot update DNS
> > *named.conf.options* > > options { > > directory "/var/cache/bind"; > > > > // If there is a firewall between you and nameservers you want > > // to talk to, you may need to fix the firewall to allow multiple > > // ports to talk. See http://www.kb.cert.org/vuls/id/800113 > > > > // If
2019 May 15
1
Workstations cannot update DNS
> > > > *named.conf.options* > > > > options { > > > > directory "/var/cache/bind"; > > > > > > > > // If there is a firewall between you and nameservers you want > > > > // to talk to, you may need to fix the firewall to allow > > multiple > > > > // ports to talk.
2019 Apr 30
0
Group policies are not applied
Hai, Why would you ever add Domain users to Local Admins? Thas really a very big NO NO, dont do that, really.. Dont.. If you want to be an victum of online crime, that thats the way to allow it to happen. Now your GPO. Its a new setup, correct? If so. Login on the AD and kinit Administrator Run : samba-tool ntacl sysvolreset -k Now, goto the Default Domain policy, is
2019 Apr 29
0
Group policies are not applied
I looked into Windows EventViewer and I found 'Invalid Credentials'. But I do not know how to deal with it. I have authenticated with Domain Controller, why is it saying 'Invalid Credentials'? - System - Provider [ Name] Microsoft-Windows-GroupPolicy [ Guid] {aea1b4fa-97d1-45f2-a64c-4d69fffd92c9} EventID 1006 Version 0 Level 2 Task 0 Opcode 1
2019 Apr 29
2
Group policies are not applied
I have hollowed these instructions. https://github.com/thctlo/samba4/blob/master/full-howto-Ubuntu18.04-samba-AD_DC.txt My normal domain is company.com. For the Samba domain it is msi.company.com. DNS is working. I ran these commands. host -t SRV _ldap._tcp.msi.company.com. _ldap._tcp.msi.company.com has SRV record 0 100 389 dc0.msi.company.com. host -t SRV _kerberos._udp.msi.company.com.
2020 Jun 03
3
get_ea_dos_attribute: Cannot get attribute from EA on file .: Error = No data available
I'm pasting below the output of the debug script you sent me some time ago. Other than this Samba has been compiled with standard options, just ./configure, following the wiki guide with the offered bootstrap file for ubuntu18.04. root at fileserver:~# smbd -b Paths: SBINDIR: /usr/local/samba/sbin BINDIR: /usr/local/samba/bin CONFIGFILE: /usr/local/samba/etc/smb.conf
2019 May 02
4
Group policies are not applied
Hai,   That -k  should use the kerberos auth. we should think about a bit better description here.   When your root/Administrator then it works ok also. Wel, you found the problem and you where able to fix it, so im happy.   and good to see that you did not have any errors running: samba-tool ntacl sysvolreset   Thanks for the notice back.   Greetz,   Louis       Van: durwin at