similar to: S4.0.4 Internal DNS problem: WERR_DNS_ERROR_DS_UNAVAILABLE after PDC being offline permanently.....

Am 30.04.2020 um 12:57 schrieb Rowland penny via samba: > On 30/04/2020 11:44, Olaf Dreyer wrote: >> Hi, >> >> I restored the last backup with the 4.11.6 setup. This is working >> fine and i can confirm that my AD is set up with a single forwarding >> zone, there is no _msdsc zone. On this 4.11.6 setup also the Windows >> DNS Tool does not complain. When

On 30/04/2020 11:44, Olaf Dreyer wrote: > Hi, > > I restored the last backup with the 4.11.6 setup. This is working fine > and i can confirm that my AD is set up with a single forwarding zone, > there is no _msdsc zone. On this 4.11.6 setup also the Windows DNS > Tool does not complain. When upgrading to 4.12.2 DNS administration > fails again with

Well, sometimes I? feel really old..... The last dynamic changes in DNS where made earlier this month, probably before I upgraded from 4.11.5 to newer version. With samba 4.11.5 DNS administration using samba-tool was working fine. Do you think this old setup is the reason for the problems?Any way to fix it? Best regards, Olaf Am 29.04.2020 um 18:35 schrieb Rowland penny via samba: > On

Hi Rowland, this is a good question. Does this listing help or answer? root at OMTNDC3:/usr/local/samba/private/sam.ldb.d# ls -al total 93220 Node,CN=Schema,CN=Configuration,DC=omtn,DC=de drwxr-x--- 2 root bind????? 4096 Apr 28 16:03 . drwx------ 7 root root????? 4096 Apr 29 11:25 .. -rw------- 1 root staff 30384128 Apr 29 12:46 'CN=CONFIGURATION,DC=OMTN,DC=DE.ldb' -rw------- 1 root

Hi, I restored the last backup with the 4.11.6 setup. This is working fine and i can confirm that my AD is set up with a single forwarding zone, there is no _msdsc zone. On this 4.11.6 setup also the Windows DNS Tool does not complain. When upgrading to 4.12.2 DNS administration fails again with WERR_DNS_ERROR_DS_UNAVAILABLE. I will try the steps described in the MS document? and come back

G'Day Olaf, If this was working before, then it would be this bug: https://bugzilla.samba.org/show_bug.cgi?id=14310 I'm a bit swamped right now, per Microsoft the correct fix is for our DNS Management server to ignore these values. Can you see if your error looks like this in the server logs? Andrew Bartlett On Wed, 2020-04-29 at 18:53 +0200, Olaf Dreyer via samba wrote: > Well,

On 29/04/2020 10:58, Olaf Dreyer via samba-technical wrote: > > I run a setup with two Samba DC (currently samba 4.12.2 on debian 10 > VMs). I started with a Windows 2003 DC but the last Windows DC has > been removed a few years ago from this setup. this is really the wrong list for this, so i have CC'ed the samba mailing list, please reply there. You say you started with Win

On 29/04/2020 17:29, Olaf Dreyer wrote: > Hi Rowland, > > this is a good question. Does this listing help or answer? > > root at OMTNDC3:/usr/local/samba/private/sam.ldb.d# ls -al > total 93220 Node,CN=Schema,CN=Configuration,DC=omtn,DC=de > drwxr-x--- 2 root bind????? 4096 Apr 28 16:03 . > drwx------ 7 root root????? 4096 Apr 29 11:25 .. > -rw------- 1 root staff

----- "Ben M." <centos at rivint.com> wrote: > Does this appear to be a sound procedure? I have one inline question. I read your version of the procedure and it looks like you want to skip the pvmove. That's fine, but it means more downtime (an unreliable estimate is one minuted per GB). In that case, you don't even need the snapshot. You won't need a point in time

Greetings, I've been having some issues establishing a two way interdomain trust between a samba server and an win2k8 active directory server. I've established a trust password and object and was able to create a trust relationship from the AD server to the samba server but I'm unable to from the Samba server to the AD server. The purpose of this is to enable ADMT to migrate the user

Hi Thanks in advance. I know my question below is not really related with samba but I'm really confused, and you guys are expert on windows authentication, I really hope you have patience to read this and I'll appreciate any of your help. I learned a lot from this post http://lists.samba.org/archive/jcifs/2008-October/008227.html. I know that a "man in the middle" technique,

Hi I've been trying to join a debian6 (IP: 172.16.0.180) box to a win2k8 r2 active directory (ORCHARD, IP: 172.16.0.200), without much success. The settings for samba and kerberos are correct: - and kinit works fine The error string returned is: 'failed to lookup DC info for domain 'ARIAS.INT' over rpc: The network name cannot be found'

Hi, my details: Server: 3.2.3 Client: win2k8 When I try list contents of a shared directory through an ASP script (win2k8 is the client), it's take much time and on samba I saw many times (4 times for each file) the same error: "fill_share_mode_lock failed" I tried "shares mode = No" but no success It's the log: ...:49, 3]

I have a Samba 3.4.0 print server with WinXP, Win2K3, Vista, and Win2K8 clients. The print server functions fine with WinXP and Win2K3. The drivers show up properly and if you look in server properties from those clients you can see the Samba printer port, the drivers, and print forms. However under Vista and Win2K8 server I get nothing. The clients say that the drivers aren't

Would anyone be so kind as to test the performance of TCP streams on Windows 2k8R2 guests of KVM virt servers? virtio-win-1.6.3 was published to address a problem described as "low performance" on Win2k8 guests. Actual performance was not recorded in the bug report. On my KVM servers, Windows 2k8R2 guests are able to send data at less than 4Mbps. I test this by using netcat on

Dear James and Andrew! Thanks much for the help, it seems that viridian=1 solved my problem! I forced a heavy load last night and no reboots were issued! I confirm that I had multiple cpus assigned and dom0 heavy load started the reboot problema, but with viridian=1, everything is OK! Thanks again for everything! Regards, Daniel Message: 3 > Date: Wed, 9 Jun 2010 15:55:13 +0100 >

Good morning. At this moment we run a samba4 domain with five linux DC under 4.1.7 version. However, due to some poor designed apps our LDAP is suffering a lot of querys that raises CPU at 100% for minutes. Performance is poor and we think that a native Windows native DC would not suffer this problem due to a better index management and/or optimization at LDAP service. So, the question is,

On Tue, 22 Jan 2019 14:20:21 -0500 (EST) "Vincent S. Cojot via samba" <samba at lists.samba.org> wrote: > > Hi All, > > On my two-DC setup (dc00 and dc01 - Used to be a 4-Dc setup but 02 > and 03 are gone), I've noticed the following errors which I am unable > to fix.. Any hints? > > * Basic dbcheck is clean. > > [root at dc00 ~]# samba-tool

Hi All, On my two-DC setup (dc00 and dc01 - Used to be a 4-Dc setup but 02 and 03 are gone), I've noticed the following errors which I am unable to fix.. Any hints? * Basic dbcheck is clean. [root at dc00 ~]# samba-tool dbcheck Checking 327 objects Checked 327 objects (0 errors) * Cross-NCS shows two errors related to a de-comissionned DC (dc02) and cannot auto-fix this.. How do I fix

Hello Luc, thanks for your answer. If I understand you correctly than you are using samba4 as windows domaincontroller and you do not have another Windows DC? So after all you have exactly one Kerberos Server that is part of the samba4 server? Thanks Rainer Am 24.03.2015 um 12:41 schrieb Luc Lalonde: > Guten tag Rainer, > > We use our Samba4/Win2k8 AD domain to authenticate all our