search for: soldc2

...t. 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 island without anyway to replicate. One strange thing is 'samba-tool drs showrepl' begs to differ. root at soldc2:~...

...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 island without anyway to replicate. > > One strange thing is 'samba-tool drs showrepl' begs to dif...

...Name,CN=Sites,CN=Configuration,DC=domain,DC=local TransportType: RPC options: 0x00000001 Warning: No NC replicated for Connection! Connection -- Connection name: 26508262-933f-4fd3-bc2c-c236e050bfb0 Enabled : TRUE Server DNS name : SOLDC2.domain.local Server DN name : CN=NTDS Settings,CN=SOLDC2,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: 5ef1d75c...

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

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

...,DC=domain,DC=local > TransportType: RPC > options: 0x00000001 > Warning: No NC replicated for Connection! > Connection -- > Connection name: 26508262-933f-4fd3-bc2c-c236e050bfb0 > Enabled : TRUE > Server DNS name : SOLDC2.domain.local > Server DN name : CN=NTDS > Settings,CN=SOLDC2,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 = dundc1.domain.local _ldap._tcp.dc._msdcs.domain.local SRV service location: priority = 0 weight = 100 port = 389 svr hostname = soldc2.domain.local _ldap._tcp.dc._msdcs.domain.local SRV service location: priority = 0 weight = 100 port = 389 svr hostname = dundc2.domain.local _ldap._tcp.dc._msdcs.domain.local SRV service location: priority = 0...

...TransportType: RPC >> options: 0x00000001 >> Warning: No NC replicated for Connection! >> Connection -- >> Connection name: 26508262-933f-4fd3-bc2c-c236e050bfb0 >> Enabled : TRUE >> Server DNS name : SOLDC2.domain.local >> Server DN name : CN=NTDS >> Settings,CN=SOLDC2,CN=Servers,CN=Solomons,CN=Sites,CN=Configuration,DC=domain,DC=local >> TransportType: RPC >> options: 0x00000001 >> Warning: No NC replicated for Connection! >...