search for: grepit

I did some experimenting on my raspberry pi with samba-4.4.2 as AD server (fresh install, no upgrade), and adding a new user: samba-tool user add grepit --gid-number=513 --login-shell=/bin/bash and then checking it: root at pi6lan:/etc# wbinfo -i grepit ROEST\grepit:*:3000017:100::/home/grepit:/bin/bash root at pi6lan:/etc# id grepit uid=3000017(ROEST\grepit) gid=100(users) groups=100(users),3000017(ROEST\grepit),3000009(BUILTIN\users) my new u...

On 29-04-16 08:45, Rowland penny wrote: > On 28/04/16 23:12, Gerben Roest wrote: >> I did some experimenting on my raspberry pi with samba-4.4.2 as AD >> server (fresh install, no upgrade), and adding a new user: >> >> samba-tool user add grepit --gid-number=513 --login-shell=/bin/bash >> >> and then checking it: >> >> root at pi6lan:/etc# wbinfo -i grepit >> ROEST\grepit:*:3000017:100::/home/grepit:/bin/bash >> >> root at pi6lan:/etc# id grepit >> uid=3000017(ROEST\grepit) gid=100(users) &gt...

...u using winbindd and rfc2307 UIDs/GIDs? I had to implement both of the above on my DC to resolve this. (Neither of which I /wanted/ to do.. but since switching over and running 'net cache flush' etc., the problem hasn't reoccurred) On 26 April 2016 at 09:14, Gerben Roest <g.roest at grepit.nl> wrote: > Hi, > > using Samba 4.4.2, on the Samba AD server the users have their primary > group at 513 (domain users) but after a non-fixed time they get set to > 100, like: > > > [root at sambaserver:~]# id john > uid=6032(DOMAIN\john) gid=513(DOMAIN\domain users...

On 28/04/16 23:12, Gerben Roest wrote: > I did some experimenting on my raspberry pi with samba-4.4.2 as AD > server (fresh install, no upgrade), and adding a new user: > > samba-tool user add grepit --gid-number=513 --login-shell=/bin/bash > > and then checking it: > > root at pi6lan:/etc# wbinfo -i grepit > ROEST\grepit:*:3000017:100::/home/grepit:/bin/bash > > root at pi6lan:/etc# id grepit > uid=3000017(ROEST\grepit) gid=100(users) > groups=100(users),3000017(ROES...

...quot;gidNumber" setting. I suspect this setting to somehow cause samba to think that "Domain Users" is 100. I have removed via RSAT the settings of gidNumber for all active users, and I hope that will fix it. Gerben > > On 26 April 2016 at 09:14, Gerben Roest <g.roest at grepit.nl> wrote: > >> Hi, >> >> using Samba 4.4.2, on the Samba AD server the users have their primary >> group at 513 (domain users) but after a non-fixed time they get set to >> 100, like: >> >> >> [root at sambaserver:~]# id john >> uid=6032...

Hi, With Samba 3 and Windows XP, it used to be possible to install he printer drivers on the Samba server, so when an XP workstation joined the domain, it would find the printer drivers automatically. Does such a functionality exists with Windows 7? 64 bits? 32 bits? Thanks in advance, Olivier --

Hi, my dovecot installation dovecot-2.0.9-19.el6_7.2.x86_64 can't authenticate using winbind from 4.4.3, but it can with winbind from 4.4.2. 4.4.3: May 5 22:11:07 sambaserver auth: pam_winbind(dovecot:auth): getting password (0x00000010) May 5 22:11:07 sambaserver auth: pam_winbind(dovecot:auth): pam_get_item returned a password May 5 22:11:07 sambaserver auth: pam_winbind(dovecot:auth):

I have set up a samba 4.4.2 AD server, and it works fine for its Windows and Linux clients. Only the server itself behaves peculiar: Linux accounts show up as DOMAIN\username (in prompt and with whoami), on all Linux clients the user accounts are normal (just their username), and only on the server "wbinfo -K username" fails. On the clients it works. The server complains about that: