I was reading the release notes for 3.0beta1, which says this:
1) When operating as a member of a Windows domain, Samba 2.2 would
map any users authenticated by the remote DC to the 'guest account'
if a uid could not be obtained via the getpwnam() call. Samba 3.0
rejects the con
Before I upgraded Samba, things worked :)
My samba box is a member of the domain, and my NT and Unix username are
the same, so it was allowing my samba session to modify my files as if I
were that Unix user.
Now, with the idmap stuff, my NT userid is mapped to uid 1, which is
not my unix UID,
On Wed, 11 Jun 2003, John H Terpstra wrote:
> Add:
> idmap uid = 1-15000
> idmap gid = 1-15000
> See if that helps.
Hey...look at that :) Thanks...that fixed it. I saw that in the smb log
and had assumed it had to do with winbind, though I guess things have
changed.
Thanks..
I have been using Samba for years and am at my wits end with this problem.
I have 3.0.0beta1-1 installed (actually, it's the latest Debian unstable
package). I just upgraded it - it was working fine yesterday.
I have rejoined my machine to the domain (did this by creating the account
using NT4'