search for: nttime

...s epoch (never) yet there are no errors. Inbound replication for this DC seems fine. [root at vsc-dc02 ~]# samba-tool drs showrepl [...]==== OUTBOUND NEIGHBORS ==== DC=DomainDnsZones,DC=mediture,DC=dom aws\AWS-DC01 via RPC DSA object GUID: 8b750a53-3d39-4bc0-8fe9-9bffa9e413aa Last attempt@ NTTIME(0) was successful 0 consecutive failure(s). Last success @ NTTIME(0) DC=DomainDnsZones,DC=mediture,DC=dom epo\EPO-DC01 via RPC DSA object GUID: 28f7281f-3955-4885-8a7d-42a36ee87590 Last attempt@ NTTIME(0) was successful 0 consecutive failure(s). Last success @ NTTIME(0) DC=DomainDn...

.... >> >> [root at vsc-dc02 ~]# samba-tool drs showrepl >> [...]==== OUTBOUND NEIGHBORS ==== >> >> DC=DomainDnsZones,DC=mediture,DC=dom >> aws\AWS-DC01 via RPC >> DSA object GUID: 8b750a53-3d39-4bc0-8fe9-9bffa9e413aa >> Last attempt@ NTTIME(0) was successful >> 0 consecutive failure(s). >> Last success @ NTTIME(0) >> >> DC=DomainDnsZones,DC=mediture,DC=dom >> epo\EPO-DC01 via RPC >> DSA object GUID: 28f7281f-3955-4885-8a7d-42a36ee87590 >> Last attempt@ NTTI...

...0 consecutive failure(s). Last success @ Fri Sep 23 14:40:18 2016 EDT ==== OUTBOUND NEIGHBORS ==== CN=Configuration,DC=domain,DC=local site-c\DUNDC2 via RPC DSA object GUID: 3c08db42-9416-40df-99ad-6d0c0ec554a6 Last attempt @ NTTIME(0) was successful 0 consecutive failure(s). Last success @ NTTIME(0) CN=Configuration,DC=domain,DC=local Default-First-Site-Name\PFDC1 via RPC DSA object GUID: acc2392f-9567-450f-bcb3-4fb1034b8753 Last attempt @ NTTIME(0)...

...t at vsc-dc02 ~]# samba-tool drs showrepl >>> [...]==== OUTBOUND NEIGHBORS ==== >>> >>> DC=DomainDnsZones,DC=mediture,DC=dom >>> aws\AWS-DC01 via RPC >>> DSA object GUID: 8b750a53-3d39-4bc0-8fe9-9bffa9e413aa >>> Last attempt@ NTTIME(0) was successful >>> 0 consecutive failure(s). >>> Last success @ NTTIME(0) >>> >>> DC=DomainDnsZones,DC=mediture,DC=dom >>> epo\EPO-DC01 via RPC >>> DSA object GUID: 28f7281f-3955-4885-8a7d-42a36ee87590 >>&gt...

...nbound replication for > this DC seems fine. > > [root at vsc-dc02 ~]# samba-tool drs showrepl > [...]==== OUTBOUND NEIGHBORS ==== > > DC=DomainDnsZones,DC=mediture,DC=dom > aws\AWS-DC01 via RPC > DSA object GUID: 8b750a53-3d39-4bc0-8fe9-9bffa9e413aa > Last attempt@ NTTIME(0) was successful > 0 consecutive failure(s). > Last success @ NTTIME(0) > > DC=DomainDnsZones,DC=mediture,DC=dom > epo\EPO-DC01 via RPC > DSA object GUID: 28f7281f-3955-4885-8a7d-42a36ee87590 > Last attempt@ NTTIME(0) was successful > 0 consecutive failure(s)....

.... > Last success @ Fri Sep 23 14:40:18 2016 EDT > > ==== OUTBOUND NEIGHBORS ==== > > CN=Configuration,DC=domain,DC=local > site-c\DUNDC2 via RPC > DSA object GUID: 3c08db42-9416-40df-99ad-6d0c0ec554a6 > Last attempt @ NTTIME(0) was successful > 0 consecutive failure(s). > Last success @ NTTIME(0) > > CN=Configuration,DC=domain,DC=local > Default-First-Site-Name\PFDC1 via RPC > DSA object GUID: acc2392f-9567-450f-bcb3-4fb1034b8753 >...

...0 consecutive failure(s). Last success @ Tue Mar 14 09:24:45 2017 CDT ==== OUTBOUND NEIGHBORS ==== DC=DomainDnsZones,DC=mediture,DC=dom vsc\DC01 via RPC DSA object GUID: da9bb168-47a0-4368-aff3-bf06d1b869d2 Last attempt @ NTTIME(0) was successful 0 consecutive failure(s). Last success @ NTTIME(0) DC=DomainDnsZones,DC=mediture,DC=dom aws\AWS-DC01 via RPC DSA object GUID: 8b750a53-3d39-4bc0-8fe9-9bffa9e413aa Last attempt @ NTTIME(0) was successful...

On Mon, 2019-08-26 at 23:10 +0200, gizmo via samba wrote: > Ok, I understood, I should join with a new name. > But what's the difference between my plans and the docu "Rejoining the upgraded DC" ? > There is nothing mentioned, that a new name is necessary. > Is it because I install a new OS and so I start from scratch ? A new name is not necessary, which is why this

On 2017-04-20 18:38, Rowland Penny wrote: > On Thu, 20 Apr 2017 18:00:24 +0200 > Sven Schwedas via samba <samba at lists.samba.org> wrote: > >> On 2017-04-07 13:44, Sven Schwedas via samba wrote: >>> In the end I just upgraded all DCs to 4.5 and remote-deleted the >>> broken ones. Seemed to work without a hitch, manual removal was >>> only necessary

...ure(s). > Last success @ Tue Mar 14 09:24:45 2017 CDT > > ==== OUTBOUND NEIGHBORS ==== > > DC=DomainDnsZones,DC=mediture,DC=dom > vsc\DC01 via RPC > DSA object GUID: da9bb168-47a0-4368-aff3-bf06d1b869d2 > Last attempt @ NTTIME(0) was successful > 0 consecutive failure(s). > Last success @ NTTIME(0) > > DC=DomainDnsZones,DC=mediture,DC=dom > aws\AWS-DC01 via RPC > DSA object GUID: 8b750a53-3d39-4bc0-8fe9-9bffa9e413aa > Last attemp...

...simalaya-group,DC=com Simalaya\SIMAD01 via RPC DSA object GUID: 62d8e484-19cb-4e15-b741-88b5c54dc3f5 Last attempt @ Tue Feb 10 17:49:43 2015 CET failed, result 121 (WERR_SEM_TIMEOUT) 78908 consecutive failure(s). Last success @ NTTIME(0) CN=Schema,CN=Configuration,DC=simalaya-group,DC=com Default-First-Site-Name\ADCAD01 via RPC DSA object GUID: 1e3dc50c-5138-4760-bdd7-69fdf8ab2335 Last attempt @ Wed Feb 4 15:50:14 2015 CET was successful 0 consecutive failure(s)....

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

...sten-Standorts,CN=Sites,CN=Configuration,DC=samdom,DC=loc DSA object GUID: 1a890c41-4326-47c1-90c0-28f8e70801a7 Last attempt @ Thu May 8 14:51:59 2014 CEST failed, result 2 (WERR_BADFILE) 1005465 consecutive failure(s). Last success @ NTTIME(0) DC=samdom,DC=loc NTDS DN: CN=NTDS Settings\0ADEL:8c0461e2-6f72-42be-98ab-ce175fc84653,CN=dc03\0ADEL:619df70c-abc9-4644-bff6-35809664bbd9,CN=Servers,CN=Standardname-des-ersten-Standorts,CN=Sites,CN=Configuration,DC=samdom,DC=loc DSA object GUID: 8c0461e2-6f72-42be-98ab-ce...

Hello Christian, Ive had a quick look at you output, that looks pretty normal. I'll have a good look Friday, tomorrow day off. So my suggestion is post the output to the list but -d10 is not needed. The regular output should be sufficiant. Im wondering why there is no dc3 in kcc also but why i see over 15 RPC sessions. Maybe normal maybe not, this i dont know. Greetz, Louis >

...ive failure(s). Last success @ Wed May 10 19:18:30 2017 CEST ==== OUTBOUND NEIGHBORS ==== DC=DomainDnsZones,DC=hq,DC=brain-biotech,DC=de Default-First-Site-Name\DC4 via RPC DSA object GUID: 5edfa50e-bcbf-4f1e-9a2f-35ee2fb0fe9c Last attempt @ NTTIME(0) was successful 0 consecutive failure(s). Last success @ NTTIME(0) DC=DomainDnsZones,DC=hq,DC=brain-biotech,DC=de Default-First-Site-Name\DC3 via RPC DSA object GUID: d4b82a24-f75e-4b47-920f-92e7bc8bd03c Last attempt @ NTTIM...

Situation: Trying to upgrade Samba from 4.1 to 4.5 without disruption too much by adding new DCs and demoting old ones. After bringing online the first 4.5 DC, I ran `demote --remove-other-dead-server=` on that DC to remove one of the old 4.1 DCs (held no FSMO roles). That seemed to run fine (the DC had been offline for a few weeks at that point and I didn't want to restore it just for

I forgot to associate inter-site links (all using default), which fixed a lot though I'm still having an issue. * vsc site o vsc-dc01 o vsc-dc02 * aws site o aws-dc01 * epo site o epo-dc01 * vsc-dc01 => anywhere: OK * vsc-dc02 => anywhere: not replicating * aws-dc01 => anywhere: OK * epo-dc01 => anywhere: OK I've tried with samba_kcc =

...a06c4c Last attempt @ Fri Sep 12 11:53:49 2014 CDT was successful 0 consecutive failure(s). Last success @ Fri Sep 12 11:53:49 2014 CDT ==== OUTBOUND NEIGHBORS ==== DC=DomainDnsZones,DC=mediture,DC=dom EP\DC02 via RPC DSA object GUID: 9febf392-a39d-4d92-b4d3-4d818a1ce807 Last attempt @ NTTIME(0) was successful 0 consecutive failure(s). Last success @ NTTIME(0) DC=DomainDnsZones,DC=mediture,DC=dom Default\DC03 via RPC DSA object GUID: 248a73b1-ffa5-46dd-bc4d-c468bf6bfead Last attempt @ NTTIME(0) was successful 0 consecutive failure(s). Last success @ NTTIME(0) DC=DomainDns...

...up. I am looking at a potential replication issue and want to know if the message from 'samba-tool drs showrepl' is indicative of trouble. The 'Inbound neighbors' list looks correct on both CH and NY DCs. The 'Outbound neighbors' list on both DCs shows 'Last attempt @ NTTIME(0) was successful'. I listed the full output at the bottom of this post. The logs don't have overt error messages, although I admit I don't understand everything that gets logged. I looked at levels 3, 5, and 10. I tested replication by adding a DNS entry, adding an account, then dele...

...ng at a potential replication issue and want to know if the message from 'samba-tool drs showrepl' is indicative of trouble. > > The 'Inbound neighbors' list looks correct on both CH and NY DCs. The 'Outbound neighbors' list on both DCs shows 'Last attempt @ NTTIME(0) was successful'. I listed the full output at the bottom of this post. > > The logs don't have overt error messages, although I admit I don't understand everything that gets logged. I looked at levels 3, 5, and 10. > > I tested replication by adding a DNS entry, a...