samba - Aug 2019 - NT style domain users on Win10 cannot connect WIFI

hi guys,

I realize it's not necessarily Samba type of a question but since this
community here is vast with lots of win experience I thought I'd poke -
same one winstation(ver. 1903) and computer's domain users when logged
in can connect WIFI no problems, only Samba domain users cannot (to the
same WIFIs). Anybody?

many thanks, L.

On 15/08/2019 13:02, lejeczek via samba wrote:
> hi guys,
>
> I realize it's not necessarily Samba type of a question but since this
> community here is vast with lots of win experience I thought I'd poke -
> same one winstation(ver. 1903) and computer's domain users when logged
> in can connect WIFI no problems, only Samba domain users cannot (to the
> same WIFIs). Anybody?
>
> many thanks, L.
>
>
No, bit lost here, wifi normally has nothing to do with Samba except if 
you set 'interfaces' in smb.conf.

The wifi connection is normally started before Samba, so Samba uses it.

I think you need to give us more info, before we can say if this has 
anything to do with Samba.

Rowland

Well, this is really to little info to make any gues whats going on here.
So we need more info. 

What are you doing here and some info on OS samba version
What/how are you connecting to wifi. 


Greetz, 

Louis


> -----Oorspronkelijk bericht-----
> Van: samba [mailto:samba-bounces at lists.samba.org] Namens 
> lejeczek via samba
> Verzonden: donderdag 15 augustus 2019 14:03
> Aan: samba at lists.samba.org
> Onderwerp: [Samba] NT style domain users on Win10 cannot connect WIFI
> 
> hi guys,
> 
> I realize it's not necessarily Samba type of a question but since this
> community here is vast with lots of win experience I thought 
> I'd poke -
> same one winstation(ver. 1903) and computer's domain users when logged
> in can connect WIFI no problems, only Samba domain users 
> cannot (to the
> same WIFIs). Anybody?
> 
> many thanks, L.
> 
> 
> -- 
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/options/samba
> 
>

On 15/08/2019 13:02, lejeczek via samba wrote:
> hi guys,
>
> I realize it's not necessarily Samba type of a question but since this
> community here is vast with lots of win experience I thought I'd poke -
> same one winstation(ver. 1903) and computer's domain users when logged
> in can connect WIFI no problems, only Samba domain users cannot (to the
> same WIFIs). Anybody?
>
> many thanks, L.
>
>
I figure I might have not put it in the clearest possible way, so..

It probably has very little(likely nothing) to do with Samba, rather
purely Win10 and its this year's update - as this problem did not exist
prior to 1903, I'm quite sure.

So, you have a winstations which are clients/member of Samba domain, now...

When Samba domains user(s) is logged in then those users cannot connect
to a wifi.

When windows local domain user(s) is logged in then it works, wifi gets
connected.

(connect to wifi the standard way windows does, with GUI)

It's pretty certain that it has nothing to do with the hardware at
windows' end as it varies(number of different laptops).

I believe it should be easy to reproduce - Samba in NT style @ Centos
7.6, latest as of today version, make your win10 (=>1903) member of such
Samba's domain and they, being logged in on winstation as samba domain
user connect to a wifi.

many thanks, L.

On 15/08/2019 16:24, lejeczek via samba wrote:
> On 15/08/2019 13:02, lejeczek via samba wrote:
> I figure I might have not put it in the clearest possible way, so..
>
> It probably has very little(likely nothing) to do with Samba, rather
> purely Win10 and its this year's update - as this problem did not exist
> prior to 1903, I'm quite sure.
If nothing changed on the Unix side, but the Windows side was updated 
and the problem occurred, then it doesn't take a genius to work out 
where the problem lies ;-)

I have said this multiple times, if you are using a Samba NT4-style 
domain, then upgrade as soon as possible, it looks like Windows has 
broken them again, though it could be fall out from SMBv1 being turned off.

Rowland