[Samba] 4.2.14 (or newer) support "Windows for Workgroups 3.1a"?

Andrea Baldoni aba004a31 at ermione.com
Tue May 1 08:31:57 UTC 2018

On Mon, Apr 30, 2018 at 05:48:29PM +0000, Chris Weiss via samba wrote:

> I have a couple win9x and DOS machine controllers in a similar situation.
> I decided that having these on the domain was less important than running a
> little bit tighter security for the rest of my LAN, so I have this work
> around and it seems to be working well enough:
> - I have a virtual machine running samba 4.x standalone with these global
> options:
>    lanman auth = Yes
>    client lanman auth = Yes

Hello Chris.
"client lanman auth = yes" is ineffective unless you also set
"client NTLMv2 auth = no". However if I understood correctly, this is used
by smbclient and both you and me don't need it.

You solved my problem anyway, the culprit was exactly

"server signing = disabled"

Now I can pass to diagnose stability problems.

> - the VM has only the required local users and groups created to match the
> UIDs of the domain.

I think I will prepare a similar configuration.

> the drawback of this is the user management is outside the domain, but here
> these are station specific shared accounts on auto-login anyway, so not
> being on the domain is actually a bit beneficial.

The samba inside the VM couldn't be a domain member?


More information about the samba mailing list