On Tue, 21 Feb 2017 11:14:19 +0100 Alain-Pierre Perrin via samba <samba at lists.samba.org> wrote:> > This behavior could be triggered by a "map untrusted to domain = yes" > into your smb.conf. The "map untrusted to domain" directive serves > precisely this purpose. >Except the OP was logging into a windows computer and the Samba DC has 'map untrusted to domain' set to 'No' by default. I think it is a windows thing, though I couldn't see anything in the event logs when I tried logging in with a mixed-up DOMAIN name. Rowland
On Tue, Feb 21, 2017 at 6:22 AM, Rowland Penny via samba <samba at lists.samba.org> wrote:> Except the OP was logging into a windows computer and the Samba DC has > 'map untrusted to domain' set to 'No' by default.Correct. And I am not overriding the default. Testparm displays "map untrusted to domain = No".> I think it is a windows thing, though I couldn't see anything in the > event logs when I tried logging in with a mixed-up DOMAIN name.Were able to recreate this? The client system was a 'fresh' (new, out the box), Windows 7, that was then fully patched, then joined to the domain just previous to my fat fingered logon attempt (that was surprisingly successful). Chris
On Tue, 21 Feb 2017 07:26:47 -0500 Sonic <sonicsmith at gmail.com> wrote:> Were able to recreate this?Yes.> The client system was a 'fresh' (new, out the box), Windows 7, that > was then fully patched, then joined to the domain just previous to my > fat fingered logon attempt (that was surprisingly successful).Windows 7 enterprise laptop, fully updated and joined to domain Never thought to try it (well, you wouldn't, would you), but if you swap around the letters in the DOMAIN name, you can still log in ;-) Rowland