similar to: Samba DC sync issues - help

Hai Nico,   Ok great, its fixed, and yes, i do think that the reboot fixed it, dont ask my why, i dont know.. i only know the fix ;-) Seen this few times before..   About the script, did you run it without the password in the script or with the password in the script? So i can check whats wrong there.   Your running samba 4.1.17 ? on which os?   Greetz,   Louis       Van:

Hi, I am running a Windows Domain based on 2 Samba AD servers. The setup is running mostly fine but I have the impression that the 2 DC's are not syncing their information. For instance: - I added a Windows pc to the domain last week, when I started 'Active directory users and computers' today on a windows pc I could not see that pc, after rebooting one of the DC's the pc

Hai, Reboot both servers first, DC1 and wait until its fully up, then reboot DC2, and run the replicate again but now like this : samba-tool drs replicate dc_WITH_FSMO_ROLES dc_TO_SYNC_TO DC=win,DC=office report if this worked. And check with this one, you can run it on any samba DC. https://secure.bazuin.nl/scripts/samba-check-db-repl.sh configure it, and run it, and report back. For the

Thanks! That's exactly what I was looking for. Nico On Mon, Dec 7, 2015 at 11:57 AM, L.P.H. van Belle <belle at bazuin.nl> wrote: > Hai Nico, > > Yes, you can do the same for linux laptops. > Read : https://wiki.samba.org/index.php/PAM_Offline_Authentication > > And here is an example. > >

Hi Louis, I tried restarting samba on the server already. I also tried rebooting the client pc a number of times. The folders are mounted via GPO's. I assume rebooting the pc should have the same effect as remounting the shares? I also had a look at the permissions from Windows. When I look at the permissions of the new folder I managed to create I see there is a strange user with only

I tried using sssd but I couldn't get it working based on the info on https://wiki.samba.org/index.php/Sssd I may give it another go anyway. Nico On Mon, Dec 7, 2015 at 1:24 PM, mathias dufresne <infractory at gmail.com> wrote: > In case of... SSSD comes also with a caching method. Using SSSD rather than > Winbind could help in certain cases... > > 2015-12-07 13:00

I have a storage server running samba 3.6.6 on Debian. Unfortunately I cannot easily upgrade samba as this is a production server. The server is a member of a Samba-based domain, unix users are still handled by NIS. When I logon to a Windows 7 pc (also part of the domain) with my own user my homedirectory is automatically available as H:\. I can see the content of the directory but when I try to

I'm setting up a new Samba-based AD domain. The domain will be used to authenticate access to both Windows and Linux desktops and portables. When a Windows portable is not able to access the AD servers (e.g. you are using a portable outside of the office) you can still happily logon using cached credentials (as long as the user logged on the pc at least once before). Is there a way to get

I'm coming from a Debian system so my system accounts are below 1000, regular accounts start at 1000. For some historical reason somebody gave our main group id 500 so therefor I want my usable range to start at 500. Do I need both idmap config *:range and idmap config SAMDOM:range? I also tried with only 'idmap config *:range' but that didn't seem to help. I'll try again

Hello again, I'm getting close to a working setup but still run into glitches here and there. I have 2 Ubuntu servers working as AD server, one Ubuntu desktop with winbind configured. I've setup a number of accounts with Unix properties. I've been primarily testing with my own account which works just fine. I've now assigned Unix properties to another account. When I run

Samba version: 4.1.17 I want to use a Samba AD controller to manage access to both my Windows and Linux boxes. I managed to import my old Samba users using pdbedit however as I want to use the new Samba AD controller to manage access to the Linux workstations too I want to configure Unix properties on all my accounts. Unfortunately I cannot find any command-line tool on Linux that will allow me

Am 07.12.2015 um 20:18 schrieb Rowland penny: > On 07/12/15 18:55, Ole Traupe wrote: >> I always wondered why to reserve 8000 IDs for built-in accounts. I >> see ~40 built-in groups in ADUC and 2 such users (Administrator and >> Guest)... >> >> Ole >> >> > > There are more potential users and groups than that, but you are > correct, you do

In case of... SSSD comes also with a caching method. Using SSSD rather than Winbind could help in certain cases... 2015-12-07 13:00 GMT+01:00 Nico De Ranter <nico.deranter at esaturnus.com>: > Thanks! That's exactly what I was looking for. > > Nico > > > > On Mon, Dec 7, 2015 at 11:57 AM, L.P.H. van Belle <belle at bazuin.nl> wrote: > > > Hai Nico,

I tried the following: * rebooted both Samba DC's -- no change * restarted samba on storage server -- no change * remove client pc from domain, tried accessing the folder from non-domain pc -- no change * created a temporary server (running samba 4.x) to serve the same homedirectores -- no problem at all So that narrows the problem down to something on the storage server. I'll try

Hai Nico, Did your stop samba and start samba already. I have on one old server, also debian wheezy samba 3.6.6 about the same problem, stopping samba and starting solves it. !! restarting samba not !! Give it a try. If that does not work, try the following. Disconnect all you netwerk shares on the computer and reconnect them. I have 1 pc here (win7 64bit) which is getting a

Hi, On 8 December 2015 at 08:53, Nico De Ranter <nico.deranter at esaturnus.com> wrote: > On Mon, Dec 7, 2015 at 8:39 PM, Ole Traupe <ole.traupe at tu-berlin.de> > wrote: > > Can I ask something related? Once I had used '23456' as uid for some test > > account, ADUC always wants to go that high, although I have plenty of > space > > below that. Is

I was wondering if anyone has come across an error in their winbindd log: could not lookup membership for group rid S-1-5-21-3506869558-4124343851-970148941-2025 in domain BOGUS (error: NT_STATUS_NO_SUCH_GROUP) I have all the mappings done correctly: domainadmin (S-1-5-21-3506869558-4124343851-970148941-512) -> domainadmin domainusers (S-1-5-21-3506869558-4124343851-970148941-513) ->

On Fri, Dec 4, 2015 at 1:48 PM, Rowland penny <rpenny at samba.org> wrote: > On 04/12/15 11:52, Nico De Ranter wrote: > >> Samba version: 4.1.17 >> >> I want to use a Samba AD controller to manage access to both my Windows >> and >> Linux boxes. I managed to import my old Samba users using pdbedit however >> as I want to use the new Samba AD

dn: cn=Domain Admins,ou=groups,dc=mydomain objectClass: top objectClass: posixGroup objectClass: sambaGroupMapping gidNumber: 512 cn: Domain Admins description: Netbios Domain Administrators sambaSID: S-1-5-21-3936576374-1604348213-1812465911-512 sambaGroupType: 2 displayName: Domain Admins memberUid: root memberUid: sadmin dn: cn=Domain Users,ou=groups,dc=mydomain objectClass: top objectClass:

Hello again, I'm trying to move all my users from an old Samba server to a new Samba AD server. When I try to do a 'classicupgrade' the process crashes after a while without giving me a clear indication of what is going wrong. When I try to export the users using pdbedit -e smbpasswd , some of the accounts simply fail. If I look at the output I see something like: Processing