Hi Timur,
Just a wild guess - could it be the result of moving lockdir in
Samba3.5 port from /var/db/samba34 back to /var/db/samba ? Can you
check, that, by renaming appropriate directory?
I have installed Samba 3.4.9, and it started working immediately. So it
seems that nss_winbind FreeBSD
Hi,
idmapping does not work perfectly for me. idmap_ad backend means it
should use active directory info to determine the unix uid and gid. It
may
bypass the issues with local tdb files.
In my case Samba is able to allocate UID and GID itself.
However, it seems not to be able to
Hi, Peter!
Just a wild guess - could it be the result of moving lockdir in
Samba3.5 port from /var/db/samba34 back to /var/db/samba ? Can you
check, that, by renaming appropriate directory?
Regards,
Timur.
On Tue, Nov 30, 2010 at 12:54 PM, Peter Trifonov
pet...@dcn.ftk.spbstu.ru wrote:
Hi,
Hi Timur,
Just a wild guess - could it be the result of moving lockdir in
Samba3.5 port from /var/db/samba34 back to /var/db/samba ? Can you
check, that, by renaming appropriate directory?
I have created a symlink /var/db/samba34 pointing to /var/db/samba, but it
still does not work.
With
My configuration has Samba domain controllers, not Windows domain
controllers, so my setup may not be applicable to you.
However, in order for unix to use windows groups I believe it needs to
use getent group to pull the information from winbind. First of all,
you need to make sure that
Hi,
getent group to pull the information from winbind. First of all, you
need
to make sure that winbind itself is showing users and/or groups from the
Windows server
wbinfo -u
wbinfo -g
wbinfo does provide the correct information.
Then you need to make sure that
The problem seems to be with idmapping.In you smb.conf file do you
have a section for idmap- this tells samba which unix user id and
group id ranges can be used to correspond to windows users and id's.
the docs on samba.org may be a little out of date so you should also
check the man
Hi,
The problem seems to be with idmapping.In you smb.conf file do you
have a section for idmap- this tells samba which unix user id and group
id
ranges can be used to correspond to windows users and id's.
the docs on samba.org may be a little out of date so you should also check
the
idmapping does not work perfectly for me. idmap_ad backend means it
should use active directory info to determine the unix uid and gid. It
may bypass the issues with local tdb files.
If you read the man page on wbinfo, you can manually allocate uid's and
gid's
[--set-uid-mapping
Does getent group show the Windows groups?
-Original Message-
From: samba-boun...@lists.samba.org [mailto:samba-boun...@lists.samba.org]
On Behalf Of Peter Trifonov
Sent: Saturday, November 27, 2010 11:58 AM
To: samba@lists.samba.org
Subject: [Samba] Missing secondary groups
Hello all,
Hi,
Does getent group show the Windows groups?
No, it does not.
However, the id command displays only the primary group for domain
users.
Furthermore, domain users are not able to access any files owned by
their
non-primary domain groups.
For example, running
$ id petert
11 matches
Mail list logo
