search for: in_group

...svolreset >> >> This solves the problem (at least in min). > > I believe the proper fix is to make sure all your DCs have the same > GID mappings. See: > > https://wiki.samba.org/index.php/Join_an_additional_Samba_DC_to_an_existing_Active_Directory#GID_mappings_of_built-in_groups > > > ...though this claims it should not be necessary after 4.2? Also note > that the rsync -XAa options are important when replicating sysvol: > > https://wiki.samba.org/index.php/Rsync_based_SysVol_replication_workaround >

...ibutes and seem to be given on a first come basis, only problem > is, the groups etc don't connect in the same order on every DC. Wasn't this supposed to be solved in 4.2? https://wiki.samba.org/index.php/Join_an_additional_Samba_DC_to_an_existing_Active_Directory#GID_mappings_of_built-in_groups The wiki seems to say that Builtin xID are now replicated but there is no clear upgrade path (if you've mixed 4.1 & 4.2 DC which mapping will be stored in 4.2 winbind? What happens when you upgrade the 4.1 to 4.2?) > > To get the same ID's on every DC, you will have to copy id...

Hi Louis, Marc, list, Quick update: On 7-10-2015 12:25, L.P.H. van Belle wrote: > Marc, > > Its for mourik important, because he wants to know why he has this error in his event logs. (i want to know also.) (learning mode) > > Mourik Jan, reboot the computer and login again, do you still see the error message, just to check if this wasnt an old message. > And/or, maybe this pc

Hello everyone! Whenever replicate the Sysvol need to run the DC command that received the data /opt/samba/bin/samba-tool ntacl sysvolreset This solves the problem (at least in min). Em 29-03-2016 08:28, mathias dufresne escreveu: > Check rights on sysvol (using samba-tool), check rsync process if several > DC. > > 2016-03-29 13:07 GMT+02:00 barış tombul <bbtombul at

On Thu, Apr 28, 2016 at 2:13 AM, Rowland penny <rpenny at samba.org> wrote: > On 28/04/16 07:31, Mueller wrote: >> >> This is a normal behaviour if you are using several dcs. Users und groups >> do have another gid/uid on each server >> until you fix it manually. This was a hard experiennce and work even fo >> rme which I suggest that this should be >>

...erstand what's wrong and how to fix >> it. > > > I believe this is the part you're looking for, which explains the problem > and gives the solution: > > https://wiki.samba.org/index.php/Join_an_additional_Samba_DC_to_an_existing_Active_Directory#GID_mappings_of_built-in_groups >

ok, I've investigated the problem more closely. First of all, I didn't mention that I have 2 domain controllers: dc(initial) and bdc (backup). Rsync command /usr/bin/rsync -XAavz --delete-after dc:/usr/local/samba/var/locks/sysvol/* /usr/local/samba/var/locks/sysvol/ fires every 5 minutes on bdc. However, if I try to gpupdate from bdc I get the above error. Gpupdating from dc works

...problem is, the >>> groups etc don't connect in the same order on every DC. >>> >> >> Wasn't this supposed to be solved in 4.2? >> >> https://wiki.samba.org/index.php/Join_an_additional_Samba_DC_to_an_existing_Active_Directory#GID_mappings_of_built-in_groups >> The wiki seems to say that Builtin xID are now replicated but there is no >> clear upgrade path (if you've mixed 4.1 & 4.2 DC which mapping will be >> stored in 4.2 winbind? What happens when you upgrade the 4.1 to 4.2?) >> > > Well, it is and it isn't,...

Problem is apparently with locking issues, disabled oplocks in the [general] section, and the problem actually got worse... Here's what happens: User-A part of group1, opens Excel file off of share, saves, exits... User-B (or even User-A for that matter) tries to re-open same file, get error stating it's locked and can only open for read-only access... Both users in the same group, and

...he problem (at least in min). >>> >> >> I believe the proper fix is to make sure all your DCs have the same GID >> mappings. See: >> >> >> https://wiki.samba.org/index.php/Join_an_additional_Samba_DC_to_an_existing_Active_Directory#GID_mappings_of_built-in_groups >> >> ...though this claims it should not be necessary after 4.2? Also note >> that the rsync -XAa options are important when replicating sysvol: >> >> https://wiki.samba.org/index.php/Rsync_based_SysVol_replication_workaround >> > >

...be given on a first come basis, only problem >> is, the groups etc don't connect in the same order on every DC. > > Wasn't this supposed to be solved in 4.2? > https://wiki.samba.org/index.php/Join_an_additional_Samba_DC_to_an_existing_Active_Directory#GID_mappings_of_built-in_groups > > The wiki seems to say that Builtin xID are now replicated but there is > no clear upgrade path (if you've mixed 4.1 & 4.2 DC which mapping will > be stored in 4.2 winbind? What happens when you upgrade the 4.1 to 4.2?) Well, it is and it isn't, yes winbindd will dis...

Le 10/06/2016 à 09:26, Rowland penny a écrit : > On 10/06/16 07:52, Sébastien Le Ray wrote: >> Hi >> >> Wasn't this supposed to be solved in 4.2? >> https://wiki.samba.org/index.php/Join_an_additional_Samba_DC_to_an_existing_Active_Directory#GID_mappings_of_built-in_groups >> >> The wiki seems to say that Builtin xID are now replicated but there >> is no clear upgrade path (if you've mixed 4.1 & 4.2 DC which mapping >> will be stored in 4.2 winbind? What happens when you upgrade the 4.1 >> to 4.2?) > > Well, it is and...

...apart from the FSMO roles. Next, the DCs are not equal if they are Samba Dcs :-) They should be, but they aren't because idmap.ldb is different on the two DCs. Have a look here: https://wiki.samba.org/index.php/Join_an_additional_Samba_DC_to_an_existing_Active_Directory#GID_mappings_of_built-in_groups Rowland

...so now I'm > guessing that idmap.ldb differs between dc2/4 and dc3. > Is there a way to check that? > > Is is safe to follow the instructions on the wiki page >> https://wiki.samba.org/index.php/Join_an_additional_Samba_DC_to_an_existing_Active_Directory#GID_mappings_of_built-in_groups >> > for an already working DC? > > (as the page is about joining a brandnew dc...) > >From personal experience yes. Create a backup however in case things go wrong. -- -James

Hi all, Here is our smb.conf: [global] workgroup = AD realm = AD.DOMAIN.TLD netbios name = DC200 server role = active directory domain controller server services = -dns idmap_ldb:use rfc2307 = yes #kccsrv:samba_kcc=true acl_xattr:ignore system acls = yes winbind nss info = rfc2307 [netlogon] path =

...;>> groups etc don't connect in the same order on every DC. >>>> >>> >>> Wasn't this supposed to be solved in 4.2? >>> >>> https://wiki.samba.org/index.php/Join_an_additional_Samba_DC_to_an_existing_Active_Directory#GID_mappings_of_built-in_groups >>> The wiki seems to say that Builtin xID are now replicated but there is >>> no clear upgrade path (if you've mixed 4.1 & 4.2 DC which mapping will be >>> stored in 4.2 winbind? What happens when you upgrade the 4.1 to 4.2?) >>> >> >> Well,...

I was running 1.9.18p10 on a test DEC Unix 4.0d box here and I decided to give 2.0beta3 a try. For some reason, I cannot connect to any of the server's shares or even get a list of it's services (via Start->Run->\\server) from Win95 clients. It asks for a password and no matter what I put in there I get "The password is not correct. Try again." I configured Beta3 a la:

Yup, compiled it myself and did not change the path. The query to the ldb returned the same thing on both DC1 and DC2. DNS and /etc/hosts are also fine, DC1 dns points to DC2 and DC2 to DC1. Everything seems to be completely fine... I was looking into this issue because I was doing the sysvol replication and noticed that the sysvol path had a '300000' as the group owner on DC2, where on