similar to: fsmo _role_seize _issue

Displaying 20 results from an estimated 2000 matches similar to: "fsmo _role_seize _issue"

2014 Nov 05
2
Lost DC with FSMO-Rolls
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I lost my DC with all fsmo-roles. I try to "seize" the roles to another DC. It worked four out of five roles: root at SVL-V-AD1:~# samba-tool fsmo seize --role=rid Attempting transfer... Transfer unsuccessful, seizing... FSMO seize of 'rid' role successful root at SVL-V-AD1:~# samba-tool fsmo seize --role=pdc Attempting
2018 Jun 06
2
Erro Transfer Fsmo(DNS)
So not the problem of using "seize" when both the OLD-FSMO server and NOVO-FSMo are active and on the network? The problem is to use "seize" if OLD-FSMO is not on the network and then come back? If I understood how it would be .... Regards; On 06-06-2018 15:46, Rowland Penny via samba wrote: > On Wed, 6 Jun 2018 15:35:29 -0300 > Carlos via samba <samba at
2013 Mar 08
0
FSMO Roles / DC Deletion Errors
Hi all- I've been polishing my Samba4 AD set-up as we get close to deploying it the office. However, one thing that I'm having issues with is FSMO roles and DCs. The gist of the situation is that I can not demote the original DC. Both DCs are implemented with Samba4, running the same version (4.0.3) and have replication working* Here is a summary of everything I've noticed: ?
2018 Jun 06
4
Erro Transfer Fsmo(DNS)
Hi! In wiki -> https://wiki.samba.org/index.php/Transferring_and_Seizing_FSMO_Roles#Difference_of_Transferring_and_Seizing_FSMO_Roles "If the DC is broken (e. g. hardware defect) and will never come back again, then you can seize the role on a remaining DC. It is very important that the old DC will never be connected to the network again, if it is connected again, this will cause
2019 Aug 04
1
Problems Transferring FSMO Roles
On 04/08/2019 18:17, Marcio Demetrio Bacci wrote: > Hi, > > > Maybe the output of 'samba-tool fsmo transfer --help' should include > the > -U parameter and its purpose in the current context... > > I've done this > > samba-tool fsmo transfer --role=domaindns -Uadministrator > * The 'domaindns' role does not have an FSMO roleowner > That is
2020 Oct 13
2
automatic transfer or seize fsmo roles
Hello list: Sorry for my ignorance but anyone could you tell me if is possible setting automatic transference or seize fsmo roles on samba4, to avoid manual action over server, such as HA, i mean in case that my fsmo role owner crash. Best regard.
2019 Jul 19
1
Failed Xfer of domain and forest fsmo
On 07/19/2019 03:08 PM, Rowland penny via samba wrote: > On 19/07/2019 20:41, Robert A Wooldridge via samba wrote: >> I have transferred all fsmo's except domain and forest.? When I >> attempt either one of these I get this error: >> >> samba-tool fsmo transfer --role=forestdns >> ERROR: Failed to delete role 'forestdns': LDAP error 50 >>
2018 Jun 06
2
Erro Transfer Fsmo(DNS)
But, if you use the "seizi" dc that no longer has the FSMO should be removed from the network, right? Regards; On 06-06-2018 11:36, Rowland Penny via samba wrote: > On Wed, 6 Jun 2018 11:24:33 -0300 > Carlos via samba <samba at lists.samba.org> wrote: > >> Hi! >> >> The problem with this is that both Dcs will continue on the >> network ... I
2009 Jul 07
0
[perf-discuss] help diagnosing system hang
Interresting... I wonder what differs between your system and mine. With my dirt-simple stress-test: server1# zpool create X25E c1t15d0 server1# zfs set sharenfs=rw X25E server1# chmod a+w /X25E server2# cd /net/server1/X25E server2# gtar zxf /var/tmp/emacs-22.3.tar.gz and a fully patched X42420 running Solaris 10 U7 I still see these errors: Jul 7 22:35:04 merope Error for Command:
2019 Aug 04
2
Problems Transferring FSMO Roles
Maybe the output of 'samba-tool fsmo transfer --help' should include the -U parameter... > (...) if you enter 'samba-tool fsmo transfer --help' it prints amongst > the output: > > --role=ROLE?????????? The FSMO role to seize or transfer. > ??????????????????????? ....................... > ??????????????????????? ..................... >
2018 Jun 06
2
Erro Transfer Fsmo(DNS)
Hi! The problem with this is that both Dcs will continue on the network ... I wanted to transfer the FSMOs, because in DC (that has today) I will perform an S.O. upgrade and if something goes wrong, it is already correct !!! Regards; On 06-06-2018 11:05, Rowland Penny via samba wrote: > On Wed, 6 Jun 2018 10:46:48 -0300 > Carlos via samba <samba at lists.samba.org> wrote: >
2018 May 15
1
Transfer FSMO roles [SEC=UNOFFICIAL]
UNOFFICIAL Hi, I am running an old SAMBA DC (Bilbo) that I want to upgrade. I installed the latest version of SAMBA 4 on an old PC (jimbo) and joined the domain. I intend to transfer the FSMO roles, upgrade Bilbo and transfer the roles back. I have transferred all roles except domaindns and forestdns. Jimbo says that these roles have no owner but Bilbo thinks it is the owner. Is there some way
2018 Jun 06
2
Erro Transfer Fsmo(DNS)
Hi! I have two Dcs, with Samba 4.7.7, i need tranfer(dont seize) fsmo between dcs, but dont work samba-tool fsmo transfer --role=domaindns -Uadmin Password for [XXXX\admin]: ERROR: Failed to delete role 'domaindns': LDAP error 16 LDAP_NO_SUCH_ATTRIBUTE -  <attribute 'fSMORoleOwner': no matching attribute value while deleting attribute on
2023 Jan 16
2
Transferring fsmo roles to new DC2
Hi Team I am transferring to a new AD DC So I started transferring the fsmo roles the first five transferred fine the domaindns and forestdns had the following error! root at DC2:/etc/sudoers.d# samba-tool fsmo transfer --role=forestdns -UAdministrator Password for [BALEWAN\Administrator]: ERROR: Failed to add role 'forestdns': LDAP error 16 LDAP_NO_SUCH_ATTRIBUTE -? <attribute
2019 Aug 04
2
Problems Transferring FSMO Roles
Hi >I take it that Administrator exists (hasn't been renamed or removed) and you are using the correct password, Administrator exists and marcio too. Passwords is correct: samba-tool fsmo transfer --role=domaindns -Uadministrator * The 'domaindns' role does not have an FSMO roleowner samba-tool fsmo transfer --role=domaindns -'U administrator' * The 'domaindns'
2016 Mar 31
3
DNS issues after FSMO seize
Aaaaaaand more problems... Welcome to the continuing saga of FILER. It appears that neither SOA or NS records were updated during the process of moving fsmo roles to CBADC01. SOA entries on all three active DCs point to FILER. There aren't any NS records for any of the new DCs, only FILER. In RSAT each DNS server's properties show filer.cb.cliffbells.com is the primary server. This
2014 Aug 14
1
Samba 4.1.6 vs Win2008R2 FSMO roles
Hi, we're using Zentyal 3.4/Samba 4.1.6 on two machine for our AD domain. We have to test the domain in "pure" microsoft environment, because a third party storage system. So I added DC and DNS role to one of our windows 2008R2, and joined it to our domain. Everything's fine at this point. Then I wanted transfer the 5 FSMO role to windows. Every role transferred successfully,
2015 May 28
2
Need another workaround for FSMO transfer problem
On 05/26/2015 07:34 AM, Rowland Penny wrote: > On 26/05/15 03:05, John Lewis wrote: >> https://wiki.samba.org/index.php/Flexible_Single-Master_Operations_%28FSMO%29_roles#Transfering_a_FSMO_role >> >> >> I ran into that while trying to rebuild my LXC's as Debian 8. The >> proposed work arrounds assume you have access to a Windows Domain >> controller in
2020 Oct 16
1
Problem transfering fsmo roles.
On Fri, 16 Oct 2020, Rowland penny via samba wrote: > On 16/10/2020 21:09, Tom Diehl via samba wrote: >> Hi, >> >> I have a Samba domain which currently has 4 DC's. I am in the process of >> trying to remove the old 4.8.12 self compiled DC's and ultimately replace >> them with (2) 4.12.8 DC's on Buster with samba from the VanBelle repo. >>
2023 Jan 16
1
Transferring fsmo roles to new DC2
16.01.2023 13:16, Callum G. MacEwan via samba wrote: > Hi Team > > I am transferring to a new AD DC > > So I started transferring the fsmo roles the first five transferred fine the domaindns and forestdns had the following error! > > root at DC2:/etc/sudoers.d#? samba-tool fsmo transfer --role=forestdns -UAdministrator > Password for [BALEWAN\Administrator]: > ERROR: