search for: lasted

Hi, I have replications problems on one of my server. Replication was working since month and yet stopped working. on the remote server: islad01:~ # samba-tool drs showrepl | more Default-First-Site-Name\ISLAD01 DSA Options: 0x00000001 DSA object GUID: 3fe6bc7c-1116-4344-96a6-c58c43bc217f DSA invocationId: 89351eec-7207-45f5-b6b9-cebfcacfd0e3 ==== INBOUND NEIGHBORS ====

Changes replicate to it, but not from it. vsc\VSC-DC02 DSA Options: 0x00000001 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

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:

Hi all, I am currently struggling to remove one of our Samba4 DC from the domain. Some time ago, adding a new Samba DC to our AD did not succeed and I had to demote the new server again. After removal, replication on one of the old/existing DCs got weird. /usr/local/samba/bin/samba-tool drs showrepl gives the following: Standardname-des-ersten-Standorts\dc02 DSA Options: 0x00000001 DSA object

On 3/13/2017 2:15 PM, Arthur Ramsey via samba wrote: > Upgraded to 4.6.0 on all nodes. Still seeing the same issue. > > If I create an object on vsc-dc02, epo-dc01 or aws-dc01 DCs it doesn't > 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

On 9/22/2016 6:31 PM, Garming Sam wrote: > On 23/09/16 00:59, lingpanda101 at gmail.com wrote: >> For clarification I'll add a few things. >> >> I initially deleted all the NTDS site links for each site and allowed >> the new KCC to create them. However it did not create them I believe >> correctly. By that I mean it defined what appeared to be a bridgehead

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

I'm having a strange"samba-tool drs showrepl" output and I don't know where to start to fix it. My environment: - SRVWIN: Win2008R2 DC server - SRVSAMBA: Samba 4.7.6 DC on Ubuntu 18.04 Server - SRVSAMBA2: Samba 4.7.6 DC on Ubuntu 18.04 Server To test AD replication I've created an user object on SRVWIN and it appears on both SRVSAMBA and SRVSAMBA2 (checked with ADUC from

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 invocationId: a20c8ed0-c72a-4e57-9e59-2236f127d0b8 ==== INBOUND NEIGHBORS

On 3/14/2017 10:29 AM, Arthur Ramsey wrote: > Changes replicate to it, but not from it. > > vsc\VSC-DC02 > DSA Options: 0x00000001 > 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 >

hmm, ? Well based on what i see, that error comes at the end of this process, so strange it errors out. Beside that your output looks good. ? You can try to install these, if its python problem Run samba-toold drs showrepl? after every install, that helps in detecting which package you might miss. ? apt install python-dnspython ? apt install python-iso8601 ? apt install python-crypto ? apt

On 2016-09-24 06:53, lingpanda101 at gmail.com wrote: > On 9/22/2016 6:31 PM, Garming Sam wrote: >> On 23/09/16 00:59, lingpanda101 at gmail.com wrote: >>> For clarification I'll add a few things. >>> >>> I initially deleted all the NTDS site links for each site and allowed >>> the new KCC to create them. However it did not create them I believe

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 defined # PROBLEM 3 >

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

Hi, Is the problem because of the Samba version? Since my Windows server is 2008 and was having trouble joining the Samba 4.10 on domain , I chose to install Samba from the very old Debian 9 repository (apt-get). Now that Samba is in the domain I want to upgrade to 4.10. Is there a problem updating Debian 4-5-16 from the Van Belle repository ( http://apt.van-belle.nl/)? I believe this may

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 -------------------------------------------------- [Mar 21 09:57:04] ERROR[6748] netsock2.c:

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:

I am having issues with Samba DC replication between two directly connected DCs. I don't understand what is wrong or how to fix it. Can someone advise? $ sudo samba-tool drs showrepl Default-First-Site-Name\OLYMPIA DSA Options: 0x00000001 DSA object GUID: 50507d18-c8ee-4ef4-bbda-4d0d9bc31caa DSA invocationId: d7f3c683-fcf2-473c-be01-a6f58af6cb88 ==== INBOUND NEIGHBORS ====