search for: last

...3fe6bc7c-1116-4344-96a6-c58c43bc217f DSA invocationId: 89351eec-7207-45f5-b6b9-cebfcacfd0e3 ==== INBOUND NEIGHBORS ==== DC=ForestDnsZones,DC=simalaya-group,DC=com Default-First-Site-Name\ADCAD01 via RPC DSA object GUID: 1e3dc50c-5138-4760-bdd7-69fdf8ab2335 Last attempt @ Tue Feb 10 17:48:43 2015 CET was successful 0 consecutive failure(s). Last success @ Tue Feb 10 17:48:43 2015 CET DC=ForestDnsZones,DC=simalaya-group,DC=com Default-First-Site-Name\ADCAD02 via RPC DSA object GUID: 97b81951-bdf8-47bd...

...x00000001 DSA object GUID: fe066b13-6f9e-4f3c-beb4-37df1292b8cb DSA invocationId: 8a2b1405-07b1-4d92-89dd-1d993e59e378 ==== INBOUND NEIGHBORS ==== DC=DomainDnsZones,DC=mediture,DC=dom vsc\DC01 via RPC DSA object GUID: da9bb168-47a0-4368-aff3-bf06d1b869d2 Last attempt @ Tue Mar 14 09:26:12 2017 CDT was successful 0 consecutive failure(s). Last success @ Tue Mar 14 09:26:12 2017 CDT DC=DomainDnsZones,DC=mediture,DC=dom aws\AWS-DC01 via RPC DSA object GUID: 8b750a53-3d39-4bc0-8fe9-9bffa9e413aa...

I believe the problem is a lack of outbound replication for non PDC emulator DCs. You'll notice isn't even trying because last successful was 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...

...01 DSA object GUID: ef37f4de-a03c-493c-96f6-e521a5415d81 DSA invocationId: b0bc10b9-a67f-4550-8fbf-3dc9fbe6fecc ==== INBOUND NEIGHBORS ==== DC=samdom,DC=loc Standardname-des-ersten-Standorts\dc01 via RPC DSA object GUID: c60bca82-df6e-409e-85c5-e2cc733691da Last attempt @ Thu May 8 14:49:28 2014 CEST was successful 0 consecutive failure(s). Last success @ Thu May 8 14:49:28 2014 CEST DC=samdom,DC=loc Standardname-des-ersten-Standorts\dc03 via RPC DSA object GUID: 94534f65-5d06-41f5-844d-a58a0bc03c9...

...; replicate. If I create it on vsc-dc01 (PDC emulator) then it does > replicate. > > On 03/13/2017 12:13 PM, Arthur Ramsey wrote: >> >> I believe the problem is a lack of outbound replication for non PDC >> emulator DCs. You'll notice isn't even trying because last >> successful was 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\A...

...>> other. That is correct. This isn't a huge issue for me. I can continue >> using the old KCC for now. The full mesh isn't detrimental to my >> network. Don't want to take up too much of your time. Thanks >> >> > The KCC has been my pet project for the last little bit, so I am very > interested in how it functions in general. But as far as I can tell, the > KCC is doing what is expected of it. What should happen, and I say > should, is that if the bridgehead server dies, the bridgehead server > role will transfer to the other DC. There mig...

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

...e-8786-474d-97e9-73d016cbfabe DSA invocationId: 5b85ee7e-afb5-4ea7-b507-84559aa9ca8b ==== INBOUND NEIGHBORS ==== CN=Schema,CN=Configuration,DC=SAMDOM,DC=LOCAL         Default-First-Site-Name\SRVSAMBA2 via RPC                 DSA object GUID: a21f165c-9fc8-4024-83e9-89f182f05077                 Last attempt @ Fri Jul 13 14:53:02 2018 CEST was successful                 0 consecutive failure(s).                 Last success @ Fri Jul 13 14:53:02 2018 CEST CN=Schema,CN=Configuration,DC=SAMDOM,DC=LOCAL         Default-First-Site-Name\SRVWIN via RPC                 DSA object GUID: 237cdbec-2...

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

Hi, I removed the last server (samba4-dc-old listed below) from the domain, but information related to that server remained. Is there any way to remove this registry from Samba 4? samba-tool drs showrepl Default-First-Site-Name\SAMBA4-DC DSA Options: 0x00000001 DSA object GUID: a1ab021c-0ef7-4fd3-a69d-28afc7c1260a DSA i...

...-6f9e-4f3c-beb4-37df1292b8cb > DSA invocationId: 8a2b1405-07b1-4d92-89dd-1d993e59e378 > > ==== INBOUND NEIGHBORS ==== > > DC=DomainDnsZones,DC=mediture,DC=dom > vsc\DC01 via RPC > DSA object GUID: da9bb168-47a0-4368-aff3-bf06d1b869d2 > Last attempt @ Tue Mar 14 09:26:12 2017 CDT was > successful > 0 consecutive failure(s). > Last success @ Tue Mar 14 09:26:12 2017 CDT > > DC=DomainDnsZones,DC=mediture,DC=dom > aws\AWS-DC01 via RPC > DSA object GUID: 8b750a53...

...DSA Options: 0x00000001 DSA object GUID: a1ab021c-0ef7-4fd3-a69d-28afc7c1260a DSA invocationId: a20c8ed0-c72a-4e57-9e59-2236f127d0b8 ==== INBOUND NEIGHBORS ==== DC=ForestDnsZones,DC=empresa,DC=com,DC=br Default-First-Site-Name\WIN-DC1 via RPC DSA object GUID: d580939f-a8b9-43ea-84e9-be0f9bd29468 Last attempt @ Tue Jul 30 09:14:11 2019 -03 was successful 0 consecutive failure(s). Last success @ Tue Jul 30 09:14:11 2019 -03 DC=ForestDnsZones,DC=empresa,DC=com,DC=br Default-First-Site-Name\WIN-DC2 via RPC DSA object GUID: 3b894dae-0497-43ae-b69a-e31750112321 Last attempt @ Tue Jul 30 09:14:12 201...

...is isn't a huge issue for me. I can >>> continue >>> using the old KCC for now. The full mesh isn't detrimental to my >>> network. Don't want to take up too much of your time. Thanks >>> >>> >> The KCC has been my pet project for the last little bit, so I am very >> interested in how it functions in general. But as far as I can tell, >> the >> KCC is doing what is expected of it. What should happen, and I say >> should, is that if the bridgehead server dies, the bridgehead server >> role will transfer...

I recently reported order() to ignore decreasing=TRUE with na.last=NA. Now I discovered two other problems and send corrected code. Best regards Jens Oehlschlägel # PROBLEM 1 see PR#1906 # PROBLEM 2 > order(1, na.last=NA) Error in apply(sapply(z, is.na), 1, any) : dim(X) must have a positive length # clearly wrong as > order(1) [1] 1 # is def...

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

HI, i just played around with Windows 2008 R2 as ADS Server and two SAMBA 4 as additional DCs. Setting up the Samba 4 DCs works fine. Now I wanted to remove the last Windows DC with dcpromo. It fails with the following statement: Der Vorgang konnte nicht durchgef?hrt werden. Fehler: Active Directory konnte keinen anderen Dom?nencontroller f?r die ?bertragung der verbleibenden Daten in Verzeichnispartition DC=ForestDnsZones,DC=local,DC=laurenz,DC=ws fi...

...c7c1260a >> DSA invocationId: a20c8ed0-c72a-4e57-9e59-2236f127d0b8 >> >> ==== INBOUND NEIGHBORS ==== >> >> DC=ForestDnsZones,DC=empresa,DC=com,DC=br >> Default-First-Site-Name\WIN-DC1 via RPC >> DSA object GUID: d580939f-a8b9-43ea-84e9-be0f9bd29468 >> Last attempt @ Tue Jul 30 09:14:11 2019 -03 was successful >> 0 consecutive failure(s). >> Last success @ Tue Jul 30 09:14:11 2019 -03 >> >> DC=ForestDnsZones,DC=empresa,DC=com,DC=br >> Default-First-Site-Name\WIN-DC2 via RPC >> DSA object GUID: 3b894dae-0497-43ae-b69...

Hello List. Last month i started to face a strange issue on an asterisk server 1.8.9.3 built on Centos 5.3 x86_64 dedicated server. out of the blue UDP stops responding .. and keep getting the following output: ---------------------------------- Opening message for the problem -------------------------------------...

I repeat my emails of 11/15/01 and 2/26/02, since it looks like this ESS bug is still not fixed in ESS 5.1.23, and I think some resolution is needed. When help() is invoked, ESS makes a copy of .Last.value in the .GlobalEnv, which is *not* where R normally stores it (R stores it in package:base). When this copy becomes stale it leads to wrong answers. The bug is in essd-r.el, lines 63-64: (ess-retr-lastvalue-command . ".Last.value <- get(\".ess.lvsave\",inherits=TRU...

...-bbda-4d0d9bc31caa DSA invocationId: d7f3c683-fcf2-473c-be01-a6f58af6cb88 ==== INBOUND NEIGHBORS ==== DC=DomainDnsZones,DC=pukey ?????????????? Default-First-Site-Name\KEFKA via RPC ?????????????????????????????? DSA object GUID: a35b2245-3340-4182-aaf8-dd344725805e ?????????????????????????????? Last attempt @ Mon Oct 28 20:25:21 2019 EDT failed, result 2 (WERR_FILE_NOT_FOUND) ?????????????????????????????? 21813 consecutive failure(s). ?????????????????????????????? Last success @ Wed Aug 14 01:19:23 2019 EDT DC=pukey ?????????????? Default-First-Site-Name\KEFKA via RPC ??????????????????????...