similar to: domain group mapping in 3.0.23a issues

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

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 >

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

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

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

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

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

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

Hello all, I am having a some problems with groups. If I use this command "net rpc group list -Uroot%not24get" as the root users I get an error. "Could not connect to server 127.0.0.1 The username or password was not correct" If I try to add groups I also get the same error. and I don't know if this is relevent or not but when I try to join win groups and Unix groups

Hi I got a problem with groupmapping. It doesn't work correct: Wilma2:/home/root # net groupmap list | grep 512 Domain Admins (S-1-5-21-3371203057-3264423045-2392767973-512) -> domadm ldapsearch -x cn=domadm: # domadm, groups, wms-hn.de dn: cn=domadm,ou=groups,dc=my-domain objectClass: posixGroup objectClass: sambaGroupMapping cn: domadm gidNumber: 65669 memberUid: tilo sambaSID:

Hi, Before Samba 3.0.0 RC4 I was running Samba 3.0.0 beta3, and when I upgraded to RC4, I began having problems with group mappings. I didn't notice at first, because on my laptop I don't normally log on to the domain. I just noticed when I tried to use my desktop and log on to the domain... I don't have Domain Admin privileges. So, I look at 'net groupmap list' ... and it

I'm working with Samba 3 on my Gentoo box. So far setting up andconfiguring Samba w/ldap and krb5 support is pretty straight forwared. My Gentoo box is now a member server of the domain, shows up in Active Directory. I can get a kerbereos ticket from our W2K PDC and connect to windows shares with as little effort as: smbclient //server/share -k Now I'm ready to start moving into

I have a new Debian testing machine running the Debian Samba 3.0.5. Everything seems OK except that I cannot get users to have domain admin rights. I have Windows XP workstations. The workstations join and log onto the domain fine. A "net groupmap list" yields: server:/home/tnolen# net groupmap list System Operators (S-1-5-32-549) -> -1 Replicators (S-1-5-32-552) -> -1 Guests

Hello all, I am having a some problems with groups. If I use this command "net rpc group list -Uroot%not24get" as the root users I get an error. "Could not connect to server 127.0.0.1 The username or password was not correct" If I try to add groups I also get the same error. and I don't know if this is relevent or not but when I try to join win groups and Unix groups

Hello all, Let me say first I'm very new to Linux (only had it running 3 days), so bear with me if I'm a bit ignorant. I'm unsure if I should even post this here, or if this list is exclusively for hardware issues... I'm running into difficulties (on a win2k client) adding the Samba "Domain Admins" group to the Windows "Administrators" group. I am able to log

Is there more documentation for smbgroupedit than the manpage ? I'm trying to get the domain admins group to work. Steps i taken so far 1. create a unix group domadm 2. add my admin users to the domadm group 3. map the Domain Admins Group to the domadm group 4. make the domain admins group a domain group (smbgroupedit reported it as unknown) 5. remove all domain users and groups from the

Hello, Can anybody please help me with the following errors. Whenever a user from the group "accounting" logs in the the PDC, a login box pops up and the following message appears "Accessed Denied - Accou~!n.bat". The problems seems to ly with people who belong to the accounting group and are running Win98se on the desktop. Absolutely nothing has been changed on the system.

Hi!I have Samba 3.2.5 as PDC for 20 users with windws XP now I need that 5 users can write into C:\windows folder from each machine in my LAN. I have a Administrators group with RID 544 and i added these users to this group but it doesnt work, I did the same adding to Domain Admin and didnt . There is a something way to give to these users access to can write into this folder Thks.