similar to: Samba4/AD Replication Issue

Hi, Many of these syncing problems were solved in Samba 4.7 (and probably a few more in 4.8). There were a number of unresolved locking issues that we uncovered as well as some inconsistencies with Windows replication. I would try join a DC with one of the latest Samba versions and see if your problems persist. Cheers, Garming On 21/06/18 21:35, Chris Lewis via samba wrote: > Hello, >

What does the WERR_BAD_NET_RESP means? I'm currently upgrading our DCs to 4.8.3 and I've noticed that the off-site DC has a sync problem of the CN=Configuration NC. The FSMO DC is still in the 4.5.5, but all other DCs, including the off-site are already on 4.8.3. Trying to sync the off-site DC with one of the updated DCs does not work either. The WERR_BAD_NET_RESP message already

Hello, We have a Windows 2008 DC (inview-dc1 and a samba 4.4.16 (inview-dc2) server as a backup DC. The system for the most-part works OK, but occasionally the Samba DC goes wildly out of sync (with respect to group membership), normally after a change to a large group. I have noted previously before the out-of-sync event occurs, this command always fails thus : root at inview-dc2:~#

Thanks Garming. We currently use a standalone bind DNS server. Will the later version of samba work without the integrated DNS backend? Cheers Chris On 21/06/18 23:41, Garming Sam wrote: > Hi, > > Many of these syncing problems were solved in Samba 4.7 (and probably a > few more in 4.8). There were a number of unresolved locking issues that > we uncovered as well as some

On 1/11/2018 1:57 PM, Harsh Kukreja wrote: > Hi > > I have tried  using FQDN for DC1 and DC2 but still it is > failing.Please assist to fix > > samba-tool drs replicate iumdcdp01.iumnet.edu.na > <http://iumdcdp01.iumnet.edu.na> iumsvrpdc DC=iumnet,DC=edu,DC=na > --sync-forced -UAdministrator > INFO: Current debug levels: >   all: 9 >   tdb: 9 >  

Hi James Thanks for your response. hots -t A iumsvrpdc (use it's fqdn as well) I have verified it with the FQDN which says that the record iumsvrpdc.iumnet.edu.na exists Search for 'iumsvrpdc' objectGUID ldbsearch -H /usr/local/samba/private/sam.ldb '(invocationId=*)' --cross-ncs objectguid : it shows 2 records found # record 1 dn: CN=NTDS

I have a Win2k3 server and am trying to manage a Samba4 box (name:UBUNTUSERVER, running Ubuntu 12.04.3 + Samba 4.0.10) as a backup. All seemed well, but after a problem with replication (result 1306 WERR_REVISION_MISMATCH), I couldn't even demote the samba4 DC. So I deleted from SERVERW2K3, deleted /usr/local/samba and re-compiled everything. Also ran make quicktest, all seems OK. Now, this

Hi I have tried using FQDN for DC1 and DC2 but still it is failing.Please assist to fix samba-tool drs replicate iumdcdp01.iumnet.edu.na iumsvrpdc DC=iumnet,DC=edu,DC=na --sync-forced -UAdministrator INFO: Current debug levels: all: 9 tdb: 9 printdrivers: 9 lanman: 9 smb: 9 rpc_parse: 9 rpc_srv: 9 rpc_cli: 9 passdb: 9 sam: 9 auth: 9 winbind: 9 vfs: 9 idmap: 9

On 1/11/2018 10:39 AM, Harsh Kukreja via samba wrote: > Hi > > The DRS sync between two Domain Controllers connected on one network is > failing. I have enabled the log level 9. > > samba-tool drs replicate 172.16.10.5 iumsvrpdc DC=iumnet,DC=edu,DC=na > --full-sync -UAdministrator > INFO: Current debug levels: > all: 9 > tdb: 9 > printdrivers: 9 >

Hi The DRS sync between two Domain Controllers connected on one network is failing. I have enabled the log level 9. samba-tool drs replicate 172.16.10.5 iumsvrpdc DC=iumnet,DC=edu,DC=na --full-sync -UAdministrator INFO: Current debug levels: all: 9 tdb: 9 printdrivers: 9 lanman: 9 smb: 9 rpc_parse: 9 rpc_srv: 9 rpc_cli: 9 passdb: 9 sam: 9 auth: 9 winbind: 9 vfs: 9

Hi, My apologies if this is a FAQ that I missed. This is my first attempt at setting up samba4. Following the howto instructions: kinit administrator seems to work fine. samba is latest git (alpha19). however the join fails (as below): [root at ads bin]# ./samba-tool domain join tribalnova.local DC -Uadministrator --realm=tribalnova.local -d4 GENSEC backend 'gssapi_spnego'

I’m getting errors with replication Samba 4.9.3 on Ubuntu 16.04 6 Samba DC’s at 3 sites I recently joined a Win2k8 R2 server to the domain and promoted it to domain controller. The replication was working before that, and not working after. I didn’t realize the problems and tried to join a Win2012 R2 server and promote to DC as well. That also failed with an error about replication failures.

Am 16.01.23 um 18:31 schrieb Rowland Penny via samba: > > > On 16/01/2023 16:56, Stefan Kania via samba wrote: >> Hi to all, >> Is there a known problem when using Debian 11 together with the samba >> packages from the backports (4.17.4) and the bind9 from the backports >> (9.18). With me it comes on each further Domaincontroller to errors >> with the

On 16/01/2023 18:27, Stefan Kania via samba wrote: > > > Am 16.01.23 um 18:31 schrieb Rowland Penny via samba: >> >> >> On 16/01/2023 16:56, Stefan Kania via samba wrote: >>> Hi to all, >>> Is there a known problem when using Debian 11 together with the samba >>> packages from the backports (4.17.4) and the bind9 from the backports

On 16/01/2023 18:56, Rowland Penny via samba wrote: > > > On 16/01/2023 18:27, Stefan Kania via samba wrote: >> >> >> Am 16.01.23 um 18:31 schrieb Rowland Penny via samba: >>> >>> >>> On 16/01/2023 16:56, Stefan Kania via samba wrote: >>>> Hi to all, >>>> Is there a known problem when using Debian 11 together with the

Hi Stefan, I have exact that running: Samba 4.17.4 and bind 9.18 from the bullseye-backports. I my case "samba_dnsupdate --verbose --all-names" runs without any errors. As like 9.16 I use the "dlz_bind9_18.so" entry in named.conf. If you need further information to compare just ask. Regards Ingo https://github.com/WAdama Rowland Penny via samba schrieb am 16.01.2023 um

Ah, ok, just saw it. Sorry, I missed that. I can only add then, all three DC's in my little net are installed with bind 9.18 and working all the same without errors. Regards Ingo https://github.com/WAdama Stefan Kania via samba schrieb am 16.01.2023 um 20:47: > > > Am 16.01.23 um 20:35 schrieb Ingo Asche via samba: >> Hi Stefan, >> >> I have exact that running:

Am 16.01.23 um 20:35 schrieb Ingo Asche via samba: > Hi Stefan, > > I have exact that running: Samba 4.17.4 and bind 9.18 from the > bullseye-backports. > > I my case "samba_dnsupdate --verbose --all-names" runs without any errors. > On the first DC it's running like I expacted, but on the second one I'm having the provlem. > As like 9.16 I use the

Hi Robb, > We added a DNS entry to Samba via the Windows DNS Manager which apparently > was invalid. Now we can't see the list of forward lookup in the Window DNS > Manager because it immediately errors and we have to restart the Samba > service. > > Running Samba 4.3.11-Ubuntu on Ubuntu 16.04 that's a quite old Samba version and it is EOL'ed. You really should

@Heinz, Thanks for testing also, but what is your samba version, OS and packages samba of compiled samba. To keep info bit more complete @Christian, can you try purge the deleted DNS records. Can you also add the debug 10 log, shown below to this bugreport. https://bugzilla.samba.org/show_bug.cgi?id=14268 I'll retest it here later on today with a few more zones. But i must finish some