Re: [Samba] 4.2.14 (or newer) support "Windows for Workgroups 3.1a"?
- Date: Tue, 1 May 2018 10:31:57 +0200
- From: Andrea Baldoni via samba <samba@xxxxxxxxxxxxxxx>
- Subject: Re: [Samba] 4.2.14 (or newer) support "Windows for Workgroups 3.1a"?
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
> lanman auth = Yes
> client lanman auth = Yes
"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?
To unsubscribe from this list go to the following URL and read the