similar to: problems after lowering tombstone...

Greetings, I'm currently experiencing an issue with two of my three Samba servers where one Samba process is pegging the CPU usage and eating up a lot of virtual and resident memory. While this is happening I get a "ERROR(runtime): DsReplicaGetInfo of type 0 failed - (-1073610723, 'NT_STATUS_RPC_PROTOCOL_ERROR')" error when I try to run the samba-tool drs showrepl command.

Hi , I 've been trying to get my 2 Samba DCs to replicate between each other but it fails DC1: Freebsd-9.1-Release, Samba 4.02, hostname ldap1, objectGUID: a2454bb4-9f94-4879-a5ff-c1a40537cb5e DC2: Freebsd-9.1-Release, Samba 4.02, hostname ldap2, objectGUID: 0103c98e-0b54-4ca4-a4e5-2259fa6b0563 ===the output showrepl command========== [root at ldap1 ~]# samba-tool drs showrepl

On Thu, Apr 16, 2015 at 02:33:20PM +0000, Donaldson Jeff wrote: > My apologies, went to paste and accidentally sent the message...see below for rest of detail. > > > Greetings, > > > I'm currently experiencing an issue with two of my three Samba servers where one Samba process is pegging the CPU usage and eating up a lot of virtual and resident memory. While this is

I've got a couple of Samba4 DCs running as VMs for testing. The primary AD DC went smoothly. The second VM joined properly and all but it's only when I get to the replication tests that I see errors. This is following the wiki When I run the command "samba-tool drs kcc -Uadministrator windowsdc.mycrap.cnpapers.dom" I get an error indicating that

Hi, I been using samba4 from git15 version of 4.0.0, when samba4 hit stable we made it a main ADDC. Around 4.0.6 or later, I stuck on a DNS problem (which results in stop responding to clients from time to time, channging to BIND didn't help when we tried some time ago. I would like to fix those problem with reinstalling DC, but first I would like to replicate it to other DC so AD trust wont

Dear all, I have joined samba 4.1.18 (FreeBSD 9.1) to an Active Directory domain as an active directory domain controller. The domain has two other Windows Server 2008 R2 DCs. Both windows and samba complain about replication problems. Windows reports that replication from Windows DCs to Samba completes successfully, but replication from Samba to Windows fails with error "The replication

Hi, Samba team! I am trying to install samba4 on FreeBSD 9.2 as a domain DC to join an existing samba4 domain controller on FreeBSD 9.2. I followed the instruction of: Samba4/HOWTO/Join a domain as a DC Everything is OK until I run the following command: root at mtm:/var/named/etc/namedb # samba-tool drs showrepl Default-First-Site-Name\MTM DSA Options: 0x00000001 DSA object GUID:

Hi *running **samba-tool drs showrepl* *and this error, what?* Default-First-Site-Name\SAMBA4 DSA Options: 0x00000001 DSA object GUID: 14af1258-d46c-4fd2-a08f-624d6c162b80 DSA invocationId: e367b956-55c8-4fc2-bb40-38bdfd5f472f ==== INBOUND NEIGHBORS ==== ERROR(runtime): DsReplicaGetInfo of type 0 failed - (-1073610723, 'NT_STATUS_RPC_PROTOCOL_ERROR')

My apologies, went to paste and accidentally sent the message...see below for rest of detail. Greetings, I'm currently experiencing an issue with two of my three Samba servers where one Samba process is pegging the CPU usage and eating up a lot of virtual and resident memory. While this is happening I get a "ERROR(runtime): DsReplicaGetInfo of type 0 failed - (-1073610723,

I did, but I don't know how to decypher it. Here's a 1.5 second snippet of the the strace -p PID command. Jeff Donaldson Technology Director Newark Charter School jeff.donaldson at ncs.k12.de.us (302) 369-2001 ext: 425 ________________________________________ From: Jeremy Allison <jra at samba.org> Sent: Thursday, April 16, 2015 6:49 PM To: Donaldson Jeff Cc: samba at

dear samba community, we have a big problem on joining a Samba 3.5.6 PDC. Hopefully anyone has an idea/suggestion. When trying to join with a Samba 4.2.10 or 4.3.9 we got the following error on client site: Failed to pull dcerpc auth: NT_STATUS_RPC_PROTOCOL_ERROR. cli_rpc_pipe_open_schannel_with_key: rpc_pipe_bind failed with error NT_STATUS_RPC_PROTOCOL_ERROR libnet_join_ok: failed to open

Em 05-05-2016 00:14, Jones Syue escreveu: > > How about add 'server signing = auto', > for example: > > [global] > server signing = auto Hi, Made no difference if set on the member I want to add to domain, but when set to the server I got this on member: mic-158 samba # net rpc join -S PDC -U domadminuser No realm has been specified! Do you really want to join an

Samba4 latest on FreeBSD8.1RC2 built and running as a joined DC: 81rc2# pwd /usr/local/samba/sbin 81rc2# ps -ax | grep samba 92436 ?? Ss 0:00.24 ./samba 92437 ?? S 0:00.01 ./samba 92438 ?? I 0:00.04 ./samba 92439 ?? S 0:00.01 ./samba 92440 ?? S 0:00.00 ./samba 92441 ?? S 0:00.00 ./samba 92442 ?? S 0:00.00 ./samba 92443 ?? S 0:00.01 ./samba

Hi, I have started getting the following error message when I run the repadmin showreps command on the Windows Server 2008 server that is my primary DC: DsReplicaGetInfo() failed with status 8453 (0x2105): Replication access has been denied. DsReplicaGetInfo() failed with status 8453 (0x2105): Replication access has been denied. My scenario has a Windows Server 2008 as the primary DC

Hi I actually have troubles to join a samba4 machine into an old samba3 domain. I know I know most of you will yell reading this, but i have to deal with a customer's very old environment :) They're thinking about migrating fully in samba4, but it will take some times so for now let's focus on the situation we have Configuration: - Samba3 PDC :3.5.18-28 - Samba4 client Debian 8.7

Hi, for a while I am getting the error message Default-First-Site-Name\MACY DSA Options: 0x00000001 DSA object GUID: 0178f264-745f-4478-8858-765947178966 DSA invocationId: f43943f8-11c7-4bd3-8fcc-fa626ff17ff2 ==== INBOUND NEIGHBORS ==== ERROR(runtime): DsReplicaGetInfo of type 0 failed - (-1073610699, 'The operation cannot be performed.') when running samba-tool drs showrepl on one

Hi list, We use samba 4.1.17 (debian's version) on several DCs. I just realized that one of them is desynced and cannot get it to resync. The long story: we got 5 DCs splitted over several sites. Recently we had to replace one of them (let's call him DC5). Since both had to run in parallel for data recovery/users work we decided to join a brand new DC (DC6) and latter demote the

I started with one dc, 'dc1', running samba v4.0.21, in subnet1. I successfully added two more dc's, 'dc2' and 'dc3', both running samba v4.0.24, both in subnet2. There are several firewalls between subnets 1 & 2. I continued to make firewall holes on behalf of msad after I added dc's 2 & 3. I.e. when they were added, there were patterns of communication

On Tue, 2016-12-20 at 16:12 +0100, Ronny Forberger via samba wrote: > > Am 15.12.2016 um 19:08 schrieb Ronny Forberger: > > > > Hi, > > > > for a while I am getting the error message > > > > Default-First-Site-Name\MACY > > DSA Options: 0x00000001 > > DSA object GUID: 0178f264-745f-4478-8858-765947178966 > > DSA invocationId:

Yes they are, see samba-tool drs replicate -h. Am 24.02.2016 um 16:24 schrieb Achim Gottinger: > Have you tried to replicate with the --sync-forced and --full-sync > options? > > Am 24.02.2016 um 14:31 schrieb Sébastien Le Ray: >> Hi list, >> >> We use samba 4.1.17 (debian's version) on several DCs. I just >> realized that one of them is desynced and