i am not sure what happens to it at install - i had a similar problem but I
had moved the original samba tree to another location so of course ended up
with an empty winbind database. this file is the one which keeps all the
mappings between NT users/groups and Samba's user/groups. If you lose it
then you might have similar problems to those you describe - ie samba
behaves as if it has no ideas who these windows users are. if you can
actually see the files in these share then perhaps this is a red herring.
-----Original Message-----
From: Kevin [mailto:kevin@mpcf.com]
Sent: 19 December 2001 15:54
To: Noel Kelly
Cc: samba@lists.samba.org
Subject: Re: latest samba_2_2 problem
I didn't do anything to that file so unless it was written over by the new
installation, it was unchanged.
Should i have removed it?
Thanks,
VeKTeReX
On Wed, 19 Dec 2001 09:08:00 -0000
Noel Kelly <nkelly@tarsus.co.uk> wrote:
> did you keep the original winbindd_idmap.tdb etc in samba/var/locks ?
>
> -----Original Message-----
> From: Kevin [mailto:kevin@mpcf.com]
> Sent: 18 December 2001 18:09
> To: samba@lists.samba.org
> Subject: latest samba_2_2 problem
>
>
> Just tried the latest cvs samba_2_2 (trying to avoid the winbind memory
leak> thing).
>
> It configured, compiled and installed fine, but when it came up there was
an> issue. When my Windows users (Win98 ad Win2K) went into explorer, they
> could see no names on the folders in samba shares, just blank folders.
>
> I quickly put it back to the older 2.2.2 configuration and everyone is
back> to normal. Was this something i missed or did wrong, or is it an issue
with> the latest samba?
>
> Thanks,
> VeKTeReX
>
> --
> To unsubscribe from this list go to the following URL and read the
> instructions: http://lists.samba.org/mailman/listinfo/samba