Rex Dieter wrote:
Turns out the machines in question attempt to access the samba share
using their "machine" account in AD, and it appears samba has a problem
with this based on the plethora of these entries I'm seeing in samba's
logs:
[2005/10/09 15:30:24, 1] smbd/sesssetup.c:reply_spnego_kerberos(250)
Username DOMAIN\MACHINE-1$ is invalid on this system
Now to go off to look in smbd/sesssetup.c to see what criteria is used
to determine if a username is "invalid" or not.
I could have sworn I had tried this previously, but...
It turns out we're not (yet) using winbind for UIDs (only
authentication/passwords), so I needed
map to guest = Bad Uid
instead of
map to guest = Bad User
-- Rex
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
