similar to: Replication problems

Am 23.08.2016 um 15:36 wrote Heinz Allerberger via samba: > Hello there, > > I have a problem with replication between two domain controllers, dc1 > and dc2. > Distribution: Debian 8.5 > Samba-Distribution: sernet-samba 4.3.11-14 > > The replication on dc2 working fine without any failures. > But the synchronization on dc1 gives the failure "WERR_BAD_NETPATH".

Hello, I am changing 2 x Gentoo/Samba 4.1 AD DCs for 2 x Ubuntu/Samba 4.7 AD DCs. I have joined the 2 new DCs and transferred the role to #3. I am performing sysvol replication from #3 to #4 quite happily with no errors. I have left them for 2 weeks. Windows desktops, etc. appear fine with no problems. I now want to demote and remove #1 and #2 from the domain and network. In preparation, I

On Fri, 25 May 2018 13:33:19 +0000 Paul Littlefield via samba <samba at lists.samba.org> wrote: > Hello, > > I am changing 2 x Gentoo/Samba 4.1 AD DCs for 2 x Ubuntu/Samba 4.7 AD > DCs. > > I have joined the 2 new DCs and transferred the role to #3. > > I am performing sysvol replication from #3 to #4 quite happily with > no errors. > > I have left them

I had a AD with 4 Win2003 DC. Now I use a samba4 server as a additional DC. Samba4 server system version: ubuntu 15.04 Samba version: samba 4.3.0 The replication from win2003 DC to samba4 DC was success. But have some problem from samba4 DC to win2003 DC. I can run "samba-tool drs showrepl" without error. But in log.samba it can found many message like: [2015/10/09 12:53:11.562088, 0]

Hello everyone. After all the problems I had demoting my DC and managed it to work again, it was working for only a week. Now i am getting this messages on the log: [2014/07/22 16:13:11.745783, 0] .../source4/librpc/rpc/dcerpc_util.c:681(dcerpc_pipe_auth_recv) Failed to bind to uuid e3514235-4b06-11d1-ab04-00c04fc2dcd2 for e3514235-4b06-11d1-ab04-00c04fc2dcd2 at

On 1/2/2018 4:05 PM, Rowland Penny wrote: > On Tue, 2 Jan 2018 15:52:57 -0500 > lingpanda101 <lingpanda101 at gmail.com> wrote: > >> On 1/2/2018 3:37 PM, Rowland Penny wrote: >>> On Tue, 2 Jan 2018 15:23:18 -0500 >>> lingpanda101 <lingpanda101 at gmail.com> wrote: >>> >>> >>>> Actually it looks as if Bind isn't running.

Hi. For a long time I am puzzled why, when internet connection is gone (beyond first router, outside of subnet) SSH (and telnet?) connection is drastically slowed. Same behavior, but less impacted is observed when system boots without working internet connection, and I am not sure, but I think even access to SAMBA fileshares can be/is affected. Affected systems are mostly production

Hello there, I have a problem with replication between two domain controllers, dc1 and dc2. Distribution: Debian 8.5 Samba-Distribution: sernet-samba 4.3.11-14 The replication on dc2 working fine without any failures. But the synchronization on dc1 gives the failure "WERR_BAD_NETPATH". Because the message "BAD_NETPATH" I checked the DNS-resolution:

Hello again, Samba experts, sorry for being such a pain in your necks, but I really need to get a recent Samba version to compile, and it looks like I definitely need your help with this. In the meantime, I have found that the huge number of "conflicting types" errors for rpc_*_init(...) is due to the fact that the Samba 4.6.4 codebase seems to have for all RPC modules: NTSTATUS

Hi llvm users & developers! Attached patches: 1) rewrite previous patch, now for darwin platform applied old mechanism 2) patch added processing .rept directive 3) patch added processing .irp directive 4) patch added processing .irpc directive -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hello Samba experts, due to the "SambaCry" issue (CVE-2017-7494), I am trying to update the Samba server installation on my Thecus NAS (dating back to 2011) from version 3.5.16 to the current 4.6.4. So far, I have successfully * created a cross-compiling toolchain for the NAS (i686-nptl-linux-gnu) based on gcc-5.2 * compiled Python and Samba library dependencies for my

I've been grappling with a recurring set of errors for quite some time now: - UpdateRefs failed with NT_STATUS_IO_TIMEOUT - Failed samba_kcc - NT_STATUS_IO_TIMEOUT - IRPC callback failed for DsReplicaSync - NT_STATUS_IO_TIMEOUT Despite cranking up the log level to 10, the returned information remains frustratingly cryptic and hard to decipher. This error, being overly generic, continues to

Hello Andrew, 1. What is the explanation for the fact that when the log level is set to 5 or 7, the NT_STATUS_IO_TIMEOUT error does not appear, but when it is at the default log level, it does? Another point I've noticed before is that when I run the command "samba-tool dbcheck --cross-ncs --reset-well-known-acls --fix --yes" (*Checked 15337 objects (0 errors)*), and in another

These are the errors I'm receiving on the latest git build of samba 4. I'm using SuSE 12.1 and compiled with: ./configure --enable-fhs --prefix=/usr --sysconfdir=/etc --localstatedir=/var /home/jason/Downloads/samba-master/librpc/idl/eventlog.idl:108: error: Unable to determine origin of type `struct dom_sid0' /home/jason/Downloads/samba-master/librpc/idl/eventlog.idl:108: error:

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

Hello samba team, Ive Samba 4.19.1 join to Windows 2022 AD the replication works only from Windowd DC to Samba DC but not in the other direction. DC1: windows server 2022 , schema version 69 DC2: Samba version 4.19.1, schema version 69 Domain and forest functional level in 2008_R2 (two environments) When i check the replication status from Samba the error is: [.................] [root at

On Thu, 2024-04-11 at 14:21 -0300, Elias Pereira wrote: > Hello?Andrew, > > 1. What is the explanation for the fact that when the log level is > set to 5 or 7, the NT_STATUS_IO_TIMEOUT error does not appear, but > when it is at the default log level, it does? I don't have an explanation for this, sorry. ?Have you looked into the 1.5 second queries, what is sending them and

Either the local server is busy, or possibly (but it would not explain the samba_kcc) Samba's drepl process is stuck talking to a remote server. Is the drepl local processes very busy doing inbound replication? My instinct is either the server is very busy (and this should show up in CPU use) or a transaction is being held open excessively. Andrew Bartlett On Sat, 2024-03-09 at 19:11 -0300,

I am trying to connect a KVM-QEMU VM to OVS-DPDK vhostuser port. But, I am encountering a few errors. Since I am very new to libvrt and Linux I am not able to sort them out. Any guidance in this regard would be a great help. These are my System Logs: Mar 28 18:03:04 dpdk-OptiPlex-5040 libvirtd.service: 1529: debug : virCommandRunAsync:2429 : About to run LIBVIRT_LOG_OUTPUTS=3:stderr

> > Is the drepl local processes very busy doing inbound replication? How can I check this? My instinct is either the server is very busy (and this should show up in > CPU use) or a transaction is being held open excessively. I use VMs on Proxmox. In DC1, I installed the Proxmox agent, and CPU usage via the dashboard is very low. However, when I checked using 'top,' the LDAP