similar to: Classic Upgrade: Unable to enumerate group memberships

On 26/04/15 23:21, Sonic wrote: > 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

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

hello.these days ,I diceded to migrating a Samba NT4 domain to a Samba AD domain.I follow all the steps as this link " https://wiki.samba.org/index.php/Migrating_a_Samba_NT4_domain_to_a_Samba_AD_domain_(classic_upgrade) " but I have error when samba-tool domain classic upgrade using sernet-samba-4.4.logs like this: [root at pdc dbdir]# samba-tool domain classicupgrade

On 18/03/16 14:31, Sonic wrote: > On Mon, Mar 7, 2016 at 4:38 PM, Andrew Bartlett <abartlet at samba.org> wrote: >> Also just check you have the unix users and groups that you are trying >> to upgrade. > Do the mapped unix groups need to be added to the new host before > attempting the upgrade? There is nothing in the docs regarding that. No, I am sure you don't

On 07/03/16 19:04, Sonic wrote: > 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

On Fri, 2016-03-18 at 10:31 -0400, Sonic wrote: > On Mon, Mar 7, 2016 at 4:38 PM, Andrew Bartlett <abartlet at samba.org> > wrote: > > Also just check you have the unix users and groups that you are > > trying > > to upgrade. > > Do the mapped unix groups need to be added to the new host before > attempting the upgrade? There is nothing in the docs regarding

Am 2016-03-29 um 10:44 schrieb Rowland penny: > There are a few gotchas, such as you will need to change any normal user > & group SIDs that have RIDs less than 1000, note that I am not talking > about users like 'Administrator' or groups like 'Domain Users', just > normal users & groups. > > Try to use the latest supported version of Samba that you can.

On Thu, 2016-04-07 at 14:22 +0200, Stefan G. Weichinger wrote: > Am 2016-03-29 um 10:44 schrieb Rowland penny: > > > There are a few gotchas, such as you will need to change any normal > > user > > & group SIDs that have RIDs less than 1000, note that I am not > > talking > > about users like 'Administrator' or groups like 'Domain Users',

On Mon, Mar 7, 2016 at 4:38 PM, Andrew Bartlett <abartlet at samba.org> wrote: > Also just check you have the unix users and groups that you are trying > to upgrade. Do the mapped unix groups need to be added to the new host before attempting the upgrade? There is nothing in the docs regarding that. Am I mistaken in thinking that the AD does not rely on matching or mapped unix groups

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

Rowland Penny via samba wrote 2018-09-04 14:24: > On Tue, 04 Sep 2018 10:26:38 +0700 > Konstantin Boyandin via samba <samba at lists.samba.org> wrote: > >> Rowland Penny via samba wrote 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:

Hey All, I have a Samba 3 PDC (Debian, Samba version 3.5.6 with NIS groups and no winbind) with about 300 users, 200 client PC's, 15 member servers(mixed Windows Server 2003/2008 and Samba 3), and I'm attempting the classicupgrade to Samba AD. To test I've created a new Ubuntu 12.04 LTS and followed the HOWTO, successfully creating a blank Samba AD and testing adding users/PC's

Hello: First, sorry for my English. I'm testing samba4 rc5. I have compiled and installed samba4 and now I'm trying to simulate an upgrade from my samba3 site to my samba4 test installation. I have setup a isolated network and I have replicated server and clients, copied my samba3 ldap contents and tdb files. But, when I run samba-tool classicupgrade following to the docs,

Hi all, I have a Centos 6 box running samba-3.6.9 and I have a problem with files turning to 0 bytes after being edited and saved. One of the users reported that he changed the name of two files and both ended up sized 0 bytes and opening them revealed them to be empty. Has anyone had a similar problem? I've been looking for 3 days and there's obvious pattern to the events

i currently have a samba pdc, samba bdc and samba member server all running samba-3.0.23c-1.fc5. up until the 3.0.22 releases, i never had any problems with users authenticating to member servers. problem now is, a user from windows xp professional (which is part of the domain) can auth to the pdc and bdc, but not to the domain member server. the same thing happens from windows xp home (even

Hi, I'm trying to upgrade samba 3.6 with openldap backend to samba 4.4.5 through samba classicupgrade process. I'm getting plenty (but not in all entries) of these errors during samba classicupgrade process: "Ignoring group memberships of 'lmecardoso' S-1-5-21-2016195122-1048547273-1752533818-749512: Unable to enumerate group memberships, (-1073741596,This error indicates

I have a new server running CentOS 6.4 x64, which will serve as our new Samba4 server. It is set up in a test environment, and I've copied over the tdb files and the smb.conf file from our samba3 server (Same OS and version). I'm trying to do an in-place upgrade on the copied files, but keep hitting an assert / uncaught exception during the upgrade: # /usr/local/samba/bin/samba-tool

i have the error: couldn't find service ::{2227a280-3aea-1069-a2de-08002b30309d} in my samba.log. i've googled extensively and irc'd #samba and #samba-technical (no-response) and can't find the SOLUTION. thank you for your help. -anthony [global] workgroup = example.com netbios name = home server string = example Samba Domain Server hosts allow = 127.0.0.1 192.168.1.0/24

On Mon, 28 Nov 2016 09:49:31 +0100 "Stefan G. Weichinger via samba" <samba at lists.samba.org> wrote: > Am 2016-11-26 um 20:50 schrieb Stefan G. Weichinger via samba: > > > Thanks for the hints, I already read the wiki, yes. > > I will look at the users and groups next week then. > > attacked that now in a VM: > > cpied /var/lib/samba and /etc

Hi, I'm practising to do a classicupgrade of my samba3 domain. When I run the upgrade, I get this error : unpack_nt_owners: owner sid mapped to uid 0 idmapping sid_to_xid failed for id[0]=S-1-5-32-544: NT_STATUS_NONE_MAPPED unpack_nt_owners: unable to validate group sid. set_nt_acl_no_snum: fset_nt_acl returned NT_STATUS_INVALID_OWNER. ERROR(runtime): uncaught exception - (-1073741734,