search for: soldc1

...lete with 'samba-tool drs options --help'. I did run 'samba-tool drs kcc' to force the check and not wait. I see all the automatically generated site links are created as you say they should. I shutdown one of the bridgehead servers in a site (killall samba). In my case it's SOLDC1 in Site B. I ran 'samba-tool drs kcc' on all DC's to see if a new KCC connection would be created on SOLDC2 in site B. It never was. So I restarted SOLDC2 in site B and no connection was ever created. This is all with SOLDC1 in site B still down. This tells me SOLDC2 becomes an isla...

...ool drs options --help'. I did run > 'samba-tool drs kcc' to force the check and not wait. I see all the > automatically generated site links are created as you say they should. > > I shutdown one of the bridgehead servers in a site (killall samba). In > my case it's SOLDC1 in Site B. I ran 'samba-tool drs kcc' on all DC's > to see if a new KCC connection would be created on SOLDC2 in site B. > It never was. So I restarted SOLDC2 in site B and no connection was > ever created. This is all with SOLDC1 in site B still down. This tells > me SOLDC2...

On 9/21/2016 11:32 PM, Garming Sam wrote: > I would have assumed that deleting all the NTDS connections for all the > DCs would have remedied this issue. I'll write a patch to try to avoid > this error in any case. > > Ignoring this error and answering your earlier question, it's often hard > to tell if the KCC is doing what is expected or not. To figure that out, >

...RPC > DSA object GUID: acc2392f-9567-450f-bcb3-4fb1034b8753 > Last attempt @ NTTIME(0) was successful > 0 consecutive failure(s). > Last success @ NTTIME(0) > > DC=ForestDnsZones,DC=domain,DC=local > site-b\SOLDC1 via RPC > DSA object GUID: 55e069f5-4f47-415b-8fa4-a398948235aa > Last attempt @ NTTIME(0) was successful > 0 consecutive failure(s). > Last success @ NTTIME(0) > > DC=ForestDnsZones,DC=domain,DC=local > De...

Hi Garming, ... >> I have what appears to still be a full mesh replication. Shouldn't the >> outbound and inbound neighbors be reflective of the KCC connection >> objects? I would expect to find only inbound and outbound connections >> for SOLDC1. Maybe I'm completely misinterpreting the intended >> behavior. > > There's likely at least some stale entries (repsFrom). The KCC builds > the inbound connections for each DC. Then as a separate step translates > the connections to replication links. The outbound links ar...

...::*??????????????????????????????? 2694/samba: task[dn How do I disable systemd-resolve and ensure only samba is listening on port 53 for DNS requests?? You can see below nslookup succeeds when querying another server in the network but fails on this one. root at soldc4:~# nslookup google.com soldc1 Server:???????? soldc1 Address:??????? 172.16.23.28#53 Non-authoritative answer: Name:?? google.com Address: 172.217.7.238 Name:?? google.com Address: 2607:f8b0:4004:806::200e root at soldc4:~# nslookup google.com soldc4 ;; connection timed out; no servers could be reached Thanks in advance for...

...t; > > How do I disable systemd-resolve and ensure only samba is > listening on > > port 53 for DNS requests?? You can see below nslookup succeeds when > > querying another server in the network but fails on this one. > > > > root at soldc4:~# nslookup google.com soldc1 > > Server:???????? soldc1 > > Address:??????? 172.16.23.28#53 > > > > Non-authoritative answer: > > Name:?? google.com > > Address: 172.217.7.238 > > Name:?? google.com > > Address: 2607:f8b0:4004:806::200e > > > > root at soldc4:~# nsloo...

...kirk,CN=Sites,CN=Configuration,DC=domain,DC=local TransportType: RPC options: 0x00000001 Warning: No NC replicated for Connection! Connection -- Connection name: 6743a36d-2401-4ecb-9f05-565a4528f7c6 Enabled : TRUE Server DNS name : SOLDC1.domain.local Server DN name : CN=NTDS Settings,CN=SOLDC1,CN=Servers,CN=Solomons,CN=Sites,CN=Configuration,DC=domain,DC=local TransportType: RPC options: 0x00000001 Warning: No NC replicated for Connection! Connection -- Connection name: 865908ee...

On Wed, 24 Aug 2016 11:56:06 -0400 lingpanda101--- via samba <samba at lists.samba.org> wrote: > > I know you asked recently but I do have them from a long ago > provisioned DC as reference. > > If you have them, I think you may be the only one who does ;-) A bit of searching doesn't turn up anything about _ldaps records, just _ldap. Rowland

...,DC=domain,DC=local > TransportType: RPC > options: 0x00000001 > Warning: No NC replicated for Connection! > Connection -- > Connection name: 6743a36d-2401-4ecb-9f05-565a4528f7c6 > Enabled : TRUE > Server DNS name : SOLDC1.domain.local > Server DN name : CN=NTDS > Settings,CN=SOLDC1,CN=Servers,CN=Solomons,CN=Sites,CN=Configuration,DC=domain,DC=local > TransportType: RPC > options: 0x00000001 > Warning: No NC replicated for Connection! > Connection -- >...

...= 0 weight = 100 port = 389 svr hostname = pfdc1.domain.local _ldap._tcp.dc._msdcs.domain.local SRV service location: priority = 0 weight = 100 port = 389 svr hostname = soldc1.domain.local _ldap._tcp.dc._msdcs.domain.local SRV service location: priority = 0 weight = 100 port = 389 svr hostname = dundc1.domain.local _ldap._tcp.dc._msdcs.domain.local SRV service location: priority = 0...

...e and ensure only samba is > >> listening on > >>> port 53 for DNS requests?? You can see below nslookup > succeeds when > >>> querying another server in the network but fails on this one. > >>> > >>> root at soldc4:~# nslookup google.com soldc1 > >>> Server:???????? soldc1 > >>> Address:??????? 172.16.23.28#53 > >>> > >>> Non-authoritative answer: > >>> Name:?? google.com > >>> Address: 172.217.7.238 > >>> Name:?? google.com > >>> Address: 2607...

...TransportType: RPC >> options: 0x00000001 >> Warning: No NC replicated for Connection! >> Connection -- >> Connection name: 6743a36d-2401-4ecb-9f05-565a4528f7c6 >> Enabled : TRUE >> Server DNS name : SOLDC1.domain.local >> Server DN name : CN=NTDS >> Settings,CN=SOLDC1,CN=Servers,CN=Solomons,CN=Sites,CN=Configuration,DC=domain,DC=local >> TransportType: RPC >> options: 0x00000001 >> Warning: No NC replicated for Connection! >...