similar to: Additional domain controller - not answering the authentication request

2015-11-20 15:11 GMT+01:00 James <lingpanda101 at gmail.com>: > On 11/20/2015 7:40 AM, Ole Traupe wrote: > >> >> >> Am 20.11.2015 um 11:54 schrieb mathias dufresne: >> >>> Hi Ole, >>> >>> I'm still not answering your issue but I come back to speak about TTL. >>> Perhaps someone would be able to bring us some light on

I can prove this within my environment: at the main site: one DC server(samba 4.1.13), one dhcp server, two DNS servers(forward AD query to two AD servers), at the branch site: one DC server(samba 4.1.13), one dhcp server, one DNS server(forward AD query to two AD server), DNSs on client machines point to the DNS servers(not point to the DC). The two DCs are synced and do their work properly

Hai, Ok, i found the problem of first post below. I did a clean install of 4.1.17 (sernet samba) and installed 2 DC's. The sernet package 4.1.17 for debian wheezy has a bug.. maybe others also, beware. When joining as an extra DC, we are (still) missing the rights on /var/lib/samba/private/dns.keytab after joining the domain. /var/lib/samba/private/dns.keytab is set to root:root 600

>> However, my 2nd DC is not that new, I restarted it many times, just >> again (samba service). No DNS records are created anywhere. >> >> If I go through the DNS console, in each and every container there is >> some entry for the 1st DC, but none for the 2nd (except on the top >> levels: FQDN and _msdcs.FQDN). >> >> Could this have to do with...

Am 10.12.2015 um 15:49 schrieb Rowland penny: > On 10/12/15 14:40, Ole Traupe wrote: >> >>>> However, my 2nd DC is not that new, I restarted it many times, just >>>> again (samba service). No DNS records are created anywhere. >>>> >>>> If I go through the DNS console, in each and every container there >>>> is some entry for the

Hmm.. > >>>> Could this have to do with... > >>>> a) I demoted my initial 1st DC (seized FSMO roles) and got rid of > >>>> DNS entries via this script on the wiki? > >>>> b) set up the *new* 2nd DC on the hardware of the prior 1st DC > >>>> (with the same IP address)? This can be a problem yes, depending on the order of

On 10/12/15 15:13, Ole Traupe wrote: > > > Am 10.12.2015 um 15:49 schrieb Rowland penny: >> On 10/12/15 14:40, Ole Traupe wrote: >>> >>>>> However, my 2nd DC is not that new, I restarted it many times, >>>>> just again (samba service). No DNS records are created anywhere. >>>>> >>>>> If I go through the DNS

On 5/5/2017 10:56 PM, Anantha Raghava wrote: > > Hello James, > > To your questions: > > *"Are DC1 and DC2 in the same geographical location?"* > > Yes, they are in same location, & they are in the same subnet as well. > > *"I'm also unclear from your message if you are still having password > issues or not."* > > **It appears

Hi Ole, Using internal DNS samba_dnsupdate does not work correctly, at least not every time. Someone modified this samba_dnsupdate tool commenting this line: os.unlink(tmpfile) which should line 413. Doing that he was able to get files generated by samba_dnsupdate to use them as argument of nsupdate command (without -g switch and with "allow dns updates = nonsecure" in smb.conf). I

Am 2017-12-28 um 15:55 schrieb L.P.H. van Belle via samba: > Hai Stephan, > > You need also this in smb.conf > > # enable offline logins > winbind offline logon = yes On which server(s)? The DCs? the DM? > I did also test my logins with one DC turned off. > And login on the DM is no problem or my pcs, no problem. > > I did not test the AD logins thats

On 5/5/2017 11:08 AM, Anantha Raghava wrote: > > Hello James, > > Even after setting the rfc2307 in smb.conf replication error continues > and password change error continues. Error thrown while forcing > replication is shown below. > > ------------------------------------------------------------------- > Even after setting RFC, DC2 is not getting synced from DC1.

On 11/20/2015 10:17 AM, mathias dufresne wrote: > > > 2015-11-20 15:11 GMT+01:00 James <lingpanda101 at gmail.com > <mailto:lingpanda101 at gmail.com>>: > > On 11/20/2015 7:40 AM, Ole Traupe wrote: > > > > Am 20.11.2015 um 11:54 schrieb mathias dufresne: > > Hi Ole, > > I'm still not answering your issue

On 10/12/15 12:58, James wrote: > On 12/10/2015 6:55 AM, Rowland penny wrote: >> On 10/12/15 10:54, Rowland penny wrote: >>> On 10/12/15 10:44, L.P.H. van Belle wrote: >>>> Hai, >>>> >>>> Ah, ok, wel, yeah, i was missing the NS on the SOA. >>>> >>>> This is imo a bug, i dont know it this is by design for samba,

Hello James, To your questions: *"Are DC1 and DC2 in the same geographical location?"* Yes, they are in same location, & they are in the same subnet as well. *"I'm also unclear from your message if you are still having password issues or not."* **It appears to have been resolved. When we randomly checked, users were able to change their passwords. However

On 11/12/2019 18:10, shacky via samba wrote: > Hi, > I have three Samba Domain Controllers, two in the LAN local network (dc1 > and dc2) and one in a remote network which is accessible from the LAN > through a VPN connection (dc4). > Every domain controller can reach every other domain controllers, and every > type of traffic is permitted by firewalls, they can ping and access to

Hi, I have three Samba Domain Controllers, two in the LAN local network (dc1 and dc2) and one in a remote network which is accessible from the LAN through a VPN connection (dc4). Every domain controller can reach every other domain controllers, and every type of traffic is permitted by firewalls, they can ping and access to every TCP and UDP ports. Checking the Samba replication I see that the

On 10/12/15 13:08, Ole Traupe wrote: > > > Am 09.12.2015 um 17:53 schrieb L.P.H. van Belle: >> Hai Ole, >> >> Can you run on the member where you logged in. >> >> host -t SRV _ldap._tcp.samdom.example.com. >> host -t SRV _kerberos._udp.samdom.example.com. >> >> host -t A dc1.samdom.example.com. >> host -t A dc2.samdom.example.com.

I have installed a secondary DC in my network, following the tutorial: https://wiki.samba.org/index.php/Join_a_domain_as_a_DC#Kerberos I have ran the following command: samba-tool domain join mydomain.com.br DC -Uadministrator --realm = mydomain.com --dns-backend = BIND_INTERNAL It seems that everything is OK. I have ran the following commands in both DC and the result was the same: ldbsearch

Hello Louis, Am 24.04.2015 um 17:16 schrieb L.P.H. van Belle: > Hai.. > > Just tested an upgrade of 4.1.17 to 4.2.1 > result... Fail.. > > setup, > Debian wheezy, sernet samba packages. > 2 clean installed DC's and 1 windows 7 pc joined. > resolv.conf setup > DC1 : namserver DC2 then DC1. > DC2: namserver DC1 then DC2. > > stopped samba on both

Hello James, Even after setting the rfc2307 in smb.conf replication error continues and password change error continues. Error thrown while forcing replication is shown below. ------------------------------------------------------------------- Even after setting RFC, DC2 is not getting synced from DC1. Connection time out error comes. #samba-tool drs replicate DC2.KTKBANKLTD.COM