similar to: Unauthorized 401

Dear list, After (almost) successfully removing a dead DC from my domain I am left with only one visible symptom: samba-tool drs showrepl shows two stale outbound link for one of the remaining 2 DCs: DC=DomainDnsZones,DC=subdom,DC=mydom,DC=com NTDS DN: CN=NTDS

I am trying to add a (CentOS4.4) Samba-3.0.23d server to a AD Win2K3 domain and the following error occurs # /usr/kerberos/bin/kinit administrator@SUBDOM.DOMAIN # net join Using short domain name -- SUBDOM Failed to set servicePrincipalNames. Please ensure that the DNS domain of this server matches the AD domain, Or rejoin with using Domain Admin credentials. Disabled account for

Hi all, I'd like to get added to the EditGroup for wiki.centos.org and perhaps projects.centos.org. I'm interested in adding content periodically throughout wiki.centos; most likely in the HOWTO areas, but am happy to do reorganization and cleanup as-needed. On the projects side I'd like to create a project for the i586 on CentOS 5 section. Thanks, Ray -- Ray Van Dolson <rayvd

On 6/26/2017 2:43 PM, Johannes Engel via samba wrote: > Dear list, > > After (almost) successfully removing a dead DC from my domain I am left > with only one visible symptom: > samba-tool drs showrepl shows two stale outbound link for one of the > remaining 2 DCs: > DC=DomainDnsZones,DC=subdom,DC=mydom,DC=com > NTDS DN: CN=NTDS >

Hi James, thanks a lot for your hint. However, I seem to be unable to find it there. Can you please be a little more specific? I tried to check the replication topology, but no success. Thanks a lot! Best regards Johannes lingpanda101 via samba <samba at lists.samba.org> schrieb am Mo., 26. Juni 2017 um 20:52 Uhr: > On 6/26/2017 2:43 PM, Johannes Engel via samba wrote: > > Dear

Hello, We have recently joined a Windows Server 2008 R1 on our samba domain as a domain member. The samba domain controller runs Samba version 3.4.9 on FreeBSD 8.2. We use the Windows Server as a terminal server for our domain users who need an accounting application called Acomba. Therefore we have added TS User CALs to the server in question. The TS Licensing Server was activated and the

Hi James, thanks a lot. However, in the Windows Sites & Services application the connection in question does not show up at all. It is only visible in the samba-tool output and only for the objects DomainDnsZones and ForestDnsZones... Best regards Johannes Am 27.06.2017 um 17:16 schrieb Johannes Engel: > > Hi James, > > thanks a lot. However, in the Windows Sites &

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

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

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 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

Hi Karthik, thanks for taking a look at this. I'm not working with gluster long enough to make heads or tails out of the logs. The logs are attached to this mail and here is the other information: # gluster volume info home Volume Name: home Type: Replicate Volume ID: fe6218ae-f46b-42b3-a467-5fc6a36ad48a Status: Started Snapshot Count: 1 Number of Bricks: 1 x 3 = 3 Transport-type: tcp

Hey Richard, Could you share the following informations please? 1. gluster volume info <volname> 2. getfattr output of that file from all the bricks getfattr -d -e hex -m . <brickpath/filepath> 3. glustershd & glfsheal logs Regards, Karthik On Thu, Oct 26, 2017 at 10:21 AM, Amar Tumballi <atumball at redhat.com> wrote: > On a side note, try recently released health

On a side note, try recently released health report tool, and see if it does diagnose any issues in setup. Currently you may have to run it in all the three machines. On 26-Oct-2017 6:50 AM, "Amar Tumballi" <atumball at redhat.com> wrote: > Thanks for this report. This week many of the developers are at Gluster > Summit in Prague, will be checking this and respond next