similar to: ad dc demotion fails trying to use non-existent dc as 'partner server for the4 demontion'

Displaying 20 results from an estimated 1000 matches similar to: "ad dc demotion fails trying to use non-existent dc as 'partner server for the4 demontion'"

2014 Sep 11
1
Need help: Impossible to demote/remove a Secondary Windows DC from my Samba 4 AD DC domain
Guys, I have a up and running Samba4 as an AD DC, along side with 3 Domain Controllers, like like: 1- Master - ubuntu-ad-1.sambadom.company.com - Ubuntu Trusty + Samba 4.1.11 + Bind9 2- Slave - ubuntu-ad-2.sambadom.company.com - Ubuntu Trusty + Samba 4.1.11 + Bind9 3- Slave - ubuntu-ad-3.sambadom.company.com - Ubuntu Trusty + Samba 4.1.11 + Bind9 4- Slave - pdwad-1.sambadom.company.com -
2015 Feb 25
2
replication problems in samba4 ad domain
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
2013 Jul 23
1
Win 2003 DC Demotion
All, I've posted a few times about this but without response so it seems that not many folks are trying to do this. So, before I spend many more hours on this trying to make it work, a simple yes or no question: Has anyone successfully demoted a Win 2003 PDC without error after joining a Samba 4.x DC to it? That's it. I'm primarily interested in "yes" responses but
2017 Jul 03
3
demoted DC's still arround
I have been replacing some "old" hardware and have demoted two DC's with 'samba-tool' as per the Samba wiki demotion page. When running Louis' "samba-info.sh" script, that script still finds the presence of the old, now demoted DC hostnames. Further investigation thru RSAT (W10) found the demoted both DC's still listed under the ADUC>Computers (along
2008 Apr 15
1
how to make 'winbind nss info = sfu' work in v >= 3.0.26a
There is an instance of Ms.Active Directory that has had the 'Services For Unix' applied. I use winbind v3.0.24 to get user/group info from that Ms.Active directory instance like so: -------- begin smb.conf snippet: ------------ security = ADS realm = mydomain.com workgroup = MYDOMAIN winbind enum groups = yes winbind enum users = yes winbind nested groups = yes winbind nss info = sfu
2006 Aug 10
1
winbind: group name doesn't map to a SID, but gid does
I'm using winbind v3.0.22 on Debian Linux as a source for nss info. I have a group that was once known by winbind, but is no more: ------ beging shell except ------ # ls -ld ./ drwxrws--- 10 root $MND000-TT227MV5K24I 4096 2006-05-10 15:41 ./ # ------ end shell except ------ It must have been known, as I was the one who chgrp'ed the dir originally. I know what the group name is
2020 Feb 28
2
Demotion of shared symbols resolved from the dynamic linker.
On PowerPC we have a failing address sanitizer test when linking with LLD. The issue is that the symbol '__libc_stack_end' is resolved to an undefined weak symbol when linking with LLD but not when linking (with the exact same command/input) with other linkers. Tracing the symbol I see it is resolved to a definition in the dynamic linker as expected:
2006 Apr 27
2
winbind nss info = sfu is not so much working
with samba 3.0.22, I'm trying to integrate a linux box with Microsoft AD by using winbind for authentication as well as for the source of nss info. When winbind is configured to use its own local id maps, everything works fine. But when i configure winbind to use 'ad' as the source of nss info, authentication fails, 'getent' commands return no results, and 'wbinfo -r
2001 Apr 23
1
win2k domain-less client failing to authenticate when securit y=domain
Hi Jonathan, Yep, samba sends the domain name as well as the username to the domain controller, and what I think happens is the NT controller sees that the domainname passed is NOT his domain, checks his list of trusted domains, doesn't find it, and says sayonara buddy... I am assuming that 'SATURN' is the netbios name of the win2k client machine? I'm not real clear on how this
2018 May 25
5
Demoting troublesome DC
Hello, I am running in a duplicate test environment of my work domain. I have 2 x 4.1 DCs and 2 x 4.7 DCs. I have transferred FSMO role to #3 and it is replicating to #4 fine. I have demoted #1 which appeared to go fine and have turned it off. When I try to demote #2 it fails with the error... Using dc3.domain.com as partner server for the demotion Password for [DOMAIN\administrator]:
2006 Aug 22
1
Total (un)standardized effects in SEM?
Hi there, as a student sociology, I'm starting to learn about SEM. The course I follow is based on LISREL, but I want to use the SEM-package on R parallel to it. Using LISREL, I found it to be very usable to be able to see the total direct and total indirect effects (standardized and unstandardized) in the output. Can I create these effects using R? I know how to calculate them
2016 Mar 31
2
Demote a working DC fails with uncaught exception
Thanks Rowland. Have submitted a bug report (No 11818). spindles7 On Thu, 31 Mar 2016 09:38:02 +0100, Rowland penny <rpenny at samba.org> wrote: >On 30/03/16 23:26, spindles7 wrote: >> Hi all, >> I am consistently getting the error: >> >> root at dc2:~# samba-tool domain demote -Uadministrator >> Using dc1.microlynx.com as partner server for the demotion
2012 Aug 15
2
how best to rollback from a yum update?
Suppose I want to upgrade a bunch of packages on a system, but in case the upgrade produces unexpected, undesired results, I want to be able to rollback the system to its original state. What is the best way to do that? Often, I won't have, or be able to find, packages for the current installed versions. I.e. If I haven't upgraded postgres for 2 years, it may be that I can no longer
2011 Sep 20
3
selinux policy remnant according to /bin/ls on CentOS 6.0 box
I installed CentOS 6.0 on 2 different x86_64 boxen. Both originally had selinux installed and enabled. I never touched selinux other than to remove as much of it as I could via rpm -e. As far as I can tell, here are the remaining packages that have something to do with it: # rpm -qa | grep -iE 'sel|pol' checkpolicy-2.0.22-1.el6.x86_64 libselinux-2.0.94-2.el6.x86_64
2019 Feb 15
6
Demoted/removed a DC, and the NS records?
Following: https://wiki.samba.org/index.php/Demoting_a_Samba_AD_DC i've demoted and removed a DC. Seems all went as expected: root at vdcud1:~# samba-tool domain demote --server=vdcsv1.ad.fvg.lnf.it -U gaio Using vdcsv1.ad.fvg.lnf.it as partner server for the demotion Password for [LNFFVG\gaio]: Deactivating inbound replication Asking partner server vdcsv1.ad.fvg.lnf.it to synchronize
2006 Jan 31
1
windbind, 'template homedir', and macros
I am currently using Mssfu, nss_ldap, and pam_ldap to enable my linux boxes to auth against MsA.D. and get all their user info from MsA.D. I recently discovered that winbind can accomplish the same without Mssfu, as long as I'm content to be limitted by the winbind config directives 'template shell' and 'template homedir'. I'd like to drop sfu if I can. The 'template
2016 Oct 14
2
not quite demoted, yet
A few days ago I demoted my first DC (a v4.2.14, I think) and thought the demote had gone well. Now, when I run "samba-tool dnsupdate --verbose" I can see references to the first DC that remain. Unfortunately, that DC no longer exists so I simply cannot demote it again. Following the instructions on the "Demote a Samba AD DC" page "Verifying The Demotion" section, I
2012 May 10
2
when is the o.s. considered to be at a certain minor version? Or, is it safe to apply only certain package updates from the next release version?
Two related questions about the minor release numbers (e.g. the 'x' in 5.x or 6.x) : 1) What constitutes the o.s. being at a particluar minor release? Typically, when you install you are getting a package set available from a specific minor release number. But what minor release is the o.s. at if I just update the centos-release package, and no other package? Typically, a 'yum
2016 Apr 02
1
Demote a working DC fails with uncaught exception
On 01/04/16 22:38, spindles7 wrote: > Hi Rowland, > Have tried your patch, and now the Demote succeeds: > > root at dc3:~# samba-tool domain demote -Uadministrator > Using dc1.microlynx.com as partner server for the demotion > Password for [MICROLYNX\administrator]: > Deactivating inbound replication > Asking partner server dc1.microlynx.com to synchronize from us >
2017 Jun 26
3
Remove stale DRS replication partner
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