similar to: Checking data migration from samba3 to samba4

I used to upgrade samba3 to samba4 with almost successful with one problem, administrator can't access. As administrator, by default it is the only user account that is given full control over the system. My query is how to change the administrator password? we have one account which can join to the samba 4 AD based on the migrated data but the problem can't change the administrator or

Hi, I used to upgrade/migrated samba 3.3.10 to samba 3.4.17 with LDAP backend in place, while upgrading the CentOS from 5.5 to 5.9. In place to retain the trust relationship. The users can able to login without re-authentication from existing machines. Tested 3 XPs, and 3 Win7 but it takes 5-8 mins to login compared to 1 win7 that was re-connected (disconnected from domain, restart, then rejoin

Hi all, I have a problem during classic-upgrade : Importing groups Group already exists sid=S-1-5-21-4023731279-819928261-1073345436-512, groupname=Domain Admins existing_groupname=Domain Admins, Ignoring. Group already exists sid=S-1-5-21-4023731279-819928261-1073345436-514, groupname=Domain Guest existing_groupname=Domain Guests, Ignoring. Group already exists

Hi, I used to successfully migrated Samba3 to Samba4 but there are some problems which I can't proceed coz it needs to be re-authenticated the computers/machines previously connected in Samba3. As I observed, using the Windows Remote Administration Tools (Active Directory Users and Computers) under the Computers, the computer name properties in General tab some entries are blanks a) DNS name

Rowland penny wrote on 3/18/16 12:58 PM: > On 18/03/16 19:27, Robert Moulton wrote: >> Rowland penny wrote on 3/18/16 11:48 AM: >>> On 18/03/16 18:19, Robert Moulton wrote: >>>> Greetings - On our samba 4 (4.3.3) AD controller I just noticed >>>> something odd. When I run 'samba-tool fsmo show' I get an error: >>>> >>>> #

Rowland Penny via samba писал 2018-09-03 17:12: > On Mon, 03 Sep 2018 04:27:07 +0000 > "Konstantin Boyandin \(lists\) via samba" <samba at lists.samba.org> > wrote: > >> Hello, >> >> Going further with migrating NT4 domain (Samba 3) to Samba 4. Thanks >> for the previous suggestions. >> >> When doing >> >> #

When you try to upgrade on a test stand, an error occurs. I do not understand that you need to add ldap, or improve migration script? Before that I tried to version 4.1.7, but the error was the sam root at dc1:~/smb_old# samba --version Version 4.2.2-SerNet-Ubuntu-7.trusty I also modified the file --- ./upgrade.py 2014-10-01 00:00:00.000000000 +0600 +++

On Fri, Mar 18, 2016 at 4:04 PM, Andrew Bartlett <abartlet at samba.org> wrote: > The upgrade code assumes you run on the same host. I realise now that > folks doing an upgrade use that an an opportunity to upgrade hardware, > and keep old systems as fallbacks, so the assumptions cause trouble. > > Make the new host identical in terms of the data needed to upgrade >

On Fri, Mar 18, 2016 at 2:39 PM, Andrew Bartlett <abartlet at samba.org> wrote: > Exactly. Think about it a little - how can it determine the group > membership, if the users/groups do not exist locally on the host doing > the migration? To clarify then: Do I need both the users and groups on the new host as they are on the old host, or just the groups? Is there any constraint

Hi Marcin, There is no problem to make limitation on a linux bridge. The rule must be the same as for a router: there must be applied on eth0 and eth1. All my best, Liviu On Wed, 2005-04-13 at 10:48 +0200, lartc-request@mailman.ds9a.nl wrote: > Send LARTC mailing list submissions to > lartc@mailman.ds9a.nl > > To subscribe or unsubscribe via the World Wide Web, visit >

Testing this "classic upgrade" scenario on a test server and have some issues. I'm using the Sernet 4.2.1 packages on Debian Wheezy. I copied the required tdb files and the smb.conf to the new test server (named WHEEZY). Edited the smb.conf to reflect the new host/netbios name of WHEEZY (remember that I want to keep the old PDC in service afterword for file and print sharing duties

Rowland penny wrote on 3/18/16 11:48 AM: > On 18/03/16 18:19, Robert Moulton wrote: >> Greetings - On our samba 4 (4.3.3) AD controller I just noticed >> something odd. When I run 'samba-tool fsmo show' I get an error: >> >> # samba-tool fsmo show >> ERROR(ldb): uncaught exception - No such Base DN: >>

Sorry for the long post but attempted this several over the past year with no success but staying on an NT4 domain is no longer viable. Need to get this resolved so hopefully there will be a clue somewhere in this montage. The current PDC is samba-3.6.25 running on Gentoo using tdbsam backend. The new AD will be a Debian LXC container running on Debian Jessie using samba compiled from git

Good afternoon, it is possible make a two way trust relationship between samba 4.3 and active directory? best regards Germ?n Waisvol SR. Linux Unix System administrator

Hello Mates, I am facing a really weird issue with my mail server, somehow I cannot connect using port 993. It works with 143 but not 993 nor 995. Here is a little bit of more information: # telnet localhost 143 Trying ::1... telnet: connect to address ::1: Connection refused Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. * OK [CAPABILITY IMAP4rev1 LITERAL+

Hello Mates, I just reciently updated BIND on my CentOS 6.2 (don't remember which version) but now I am using version: BIND version 9.8.2 The packages I have: bind bind-libs bind-chroot bind-utils bind-devel First of all, doing "service named status" it throws me: WARNING: key file (/etc/rndc.key) exists, but using default configuration file (/etc/rndc.conf) rndc: connection to

Rowland Penny via samba <samba at lists.samba.org> writes: > On Thu, 22 Mar 2018 10:50:35 +0700 > Olivier via samba <samba at lists.samba.org> wrote: > >> Hi, >> >> I am progressing slowly with the migration from Samba3 to Samba4. >> >> I have escaped the bug 13060, now I get to: >> >> Adding groups >> Importing groups

Hi, I am progressing slowly with the migration from Samba3 to Samba4. I have escaped the bug 13060, now I get to: Adding groups Importing groups Group already exists sid=S-1-5-21-1360262076-8766554542-0991298654-513, groupname=Unix Group Users existing_groupname=Domain Users, Ignoring. Committing 'add groups' transaction to disk Adding users Importing users Committing 'add

Hello, I run Samba 3.6.3. on ubuntu server, whre the domain works fine. Hoever when I try to migrate to Samba 4.1 from sernet distribution, I finish with Classicupgrade on the below error. I know it hase to do with bad group mapping, but I am not able to find the mistake. Please help. root at server:/var/lib/samba# samba-tool domain classicupgrade --dbdir=/var/lib/samba.PDC/dbdir/

I am attempting to migrate a Slackware server with Samba 4.12.3 from an NT style domain to AD. I have done this about 7-8 times on other servers in the past following the instructions on Samba's wiki. This time however, the upgrade process is failing completely to import any users or groups from the NT domain. I have enclosed below the output of the classicupgrade command - I can't