Hi all
I have been trying to figure this out but have decided to give in and
ask the list.
I am setting up a samba share that is writeable by numerous users. This
is no problem - put them in the necessary group and chmod g+w that
directory. The problem is that only the user who owns the parent
simo wrote:
On Tue, 2006-10-31 at 15:52 +1300, Richard Greaney wrote:
Hi all
I have a peculiar problem that has been ongoing over the last few years.
I have a mail server which is running winbind and giving distributed
authentication from a Windows server. Winbind UID mapping
simo wrote:
On Wed, 2006-11-01 at 08:52 +1300, Richard Greaney wrote:
Hi Simo
Thanks for your reply. I might have made things a little hazy in my
initial post. The 40-odd servers I mentioned are all on remote client
sites and each has it's own corresponding Windows server. Effectively, I
Hi all
I have a peculiar problem that has been ongoing over the last few years.
I have a mail server which is running winbind and giving distributed
authentication from a Windows server. Winbind UID mapping is in the
typical 1-2 range. Everything works fine... for the first little
Hi all
This one has me baffled - leading me to beleive it could be a bug
similar to https://bugzilla.samba.org/show_bug.cgi?id=2695
I am running samba 3.0.20b on debian unstable and am having problems
with some users not resolving properly using winbind.
wbinfo -u shows all users on the
Hi all
I have set my Samba server up to join an AD realm. Winbind is working
fine and I am able to use it for authentication as needed. When I try to
connect to one of my shares via a Windows client, I get the following error:
[2004/11/04 11:57:54, 0] auth/pampass.c:smb_pam_account(573)
(Written as standalone message and not reply this time!!)
Hi all
This one has been puzzling me for quite a while now. I have been able to
set up Samba 3 as an NT4 DC replacement, using the passdb backend. For
other applications, I have run Samba and Winbind alongside a Windows
Server 2003
This one has been puzzling me for quite a while now. I have been able to
set up Samba 3 as an NT4 DC replacement, using the passdb backend. For
other applications, I have run Samba and Winbind alongside a Windows
Server 2003 Domain Controller and used distributed authentication across
the two