samba - Jul 2015 - Next Problem: windows 10 as samba domain member

Good Morning Marc,

Marc Muehlfeld <mmuehlfeld at samba.org> wrote on 09.07.2015 17:49:36:
 > Am 09.07.2015 um 14:35 schrieb Roland Schwingel:
 > > I got windows 10 pro build 10159 running in a vm. I added the 2 well
 > > known registry changes I always add to windows 7 also to windows 10.
So
 > > far so good. I joined the machine to my samba 4.2.2 PDC. Heureka! It
 > > worked smoothly. Now I try to logon with a domain user. On the login
 > > screen I see the error message:
 > >
 > > There are currently no logon servers available to service the logon 
request
 >
 > I've renamed the old "Registry changes for NT4-style
domains" page in
 > the wiki, because Win10 in an Samba NT4 domain requires also an smb.conf
 > setting. Otherwise you will stop at the "No logon servers
available"
 > problem. To cover everything on one page, a page rename was required.
 >
 > https://wiki.samba.org/index.php/Required_settings_for_NT4-style_domains

This is great news. I can confirm that this is working here for me too.
After changing to max protocol NT1 I restarted samba on my PDC. But 
immediately afterwards a domain logon from win10 was not possible. I 
tried it twice (still the old error message) but than was interrupted by 
a phone call. After the phone call (~2min) it worked without changing 
anything.

Regarding the switch to NT1. This does not make me really happy. I tried 
domain logons with win7 and 8.1 using a user with a profile containing 
lots of small files. It takes longer on win7/8.1 to login/logout now. 
Its about 1.5 times slower in my case. (My PDC
is also hosting the windows profiles.)

Is this going to be the permanent solution? Or is this just 
intermediate? Has MS changed/extended something in smb2/3 that samba is 
yet not aware of or is it maybe "just" a bug in sambas implementation?

Anyhow: I am glad that samba works now with windows 10. THANK YOU!

Roland

Hello Rowland,

Am 10.07.2015 um 09:36 schrieb Roland Schwingel:
> Regarding the switch to NT1. This does not make me really happy. I tried
> domain logons with win7 and 8.1 using a user with a profile containing
> lots of small files. It takes longer on win7/8.1 to login/logout now.
> Its about 1.5 times slower in my case. (My PDC
> is also hosting the windows profiles.)
The newer SMB protocol versions have some speed improvements compared
with the old SMB1, so this is possible. :-)

However, you can put all the data on a member server with SMB2/3 and
only run the pure PDC with SMB1.


> Is this going to be the permanent solution? Or is this just
> intermediate? Has MS changed/extended something in smb2/3 that samba is
> yet not aware of or is it maybe "just" a bug in sambas
implementation?
The problem is, that NT4 support ended a long time ago. Andrew asked MS
a while ago about Win10 and NT4 support:
https://lists.samba.org/archive/samba-technical/2015-June/107624.html

If there are things to fix on the server side, to make everything work
smooth, just file a bug, but if something has been removed on the client
side, then it's time to think about moving to AD or stay at maximum
Win8(.1), which is supported by MS until Jan 2023.



Even if it looks like everything is working now with Win10, I'm curious,
if maybe a future Win update breaks this. MS said, that they want to
continually work and develop Win10. So hopefully Win10 users in an NT4
domain don't have a problem some day after installing a major Windows
update and rebooting... :-/


Regards,
Marc