<div dir="ltr"><div><div><div><div><div>Okay got it working.<br><br></div>Had to edit the smb.conf file not the smb4.comf file in "/usr/local/etc/smb.conf"<br><br></div>I have added some extra commenting to the line to explain the fix then I commented out the line and it still works!<br><br></div>I also added a section in SOE page on the wiki detailing the fix for windows 10.<br><br></div>Thanks for your help!.<br><br></div>- JVB<br><br><div class="gmail_quote"><div dir="ltr">---------- Forwarded message ---------<br>From: <<a href="mailto:zanchey@ucc.asn.au">zanchey@ucc.asn.au</a>><br>Date: Tue, 24 Nov 2015 at 18:41<br>Subject: Re: UCC Windows 10 Machine<br>To: Jonathan Van buren <<a href="mailto:vanbujm@gmail.com">vanbujm@gmail.com</a>><br></div><br><br>On Tue, 24 Nov 2015, Jonathan Van buren wrote:<br>
> I have been attempting to get the clubroom windows 10 machine to login to<br>
> accounts on the UCCDOMAIN, however I am getting the "There are currently no<br>
> logon servers available to service the logon request" error. Now the fix<br>
> seems to be to add the line "max protocol = NT1" to the smb.conf. But to my<br>
> knowledge we are running samba4 with active directory not NT correct?<br>
><br>
> So my question is; is it safe to try this config change or is there a<br>
> better solution?<br>
<br>
Hi J<br>
<br>
We're running Samba 4, but still in NT Domain mode. I'm sort of amazed<br>
that it still works; I would have thought they would have given 15+ year<br>
old tech the boot by now.<br>
<br>
I take it you're looking at<br>
<a href="https://wiki.samba.org/index.php/Required_settings_for_NT4-style_domains#Windows_10:_.E2.80.9ENo_logon_servers_available.E2.80.9C" rel="noreferrer" target="_blank">https://wiki.samba.org/index.php/Required_settings_for_NT4-style_domains#Windows_10:_.E2.80.9ENo_logon_servers_available.E2.80.9C</a><br>
<br>
I think it should be safe to try this config change. You probably need to<br>
make it on the PDC, which is molmol, in /usr/local/etc/smb4.conf . Restart<br>
the service with `service samba_server restart` and then probably reboot<br>
the Windows 10 machine as well.<br>
<br>
Unfortunately this will probably make the performance of file transfers<br>
even worse. However, this thread:<br>
<a href="https://lists.samba.org/archive/samba-technical/2015-June/107642.html" rel="noreferrer" target="_blank">https://lists.samba.org/archive/samba-technical/2015-June/107642.html</a><br>
suggests that once the Windows 10 machine has logged on to the domain<br>
once, you can remove the `max_protocol` line and it should keep working!<br>
If that's the case, we can probably have the best of both worlds.<br>
<br>
Good luck, I'd be keen to hear how you get on.<br>
<br>
One of these days we should move to full Active Directory with Samba - but<br>
it will require rewriting quite a lot of scripts so perhaps February is<br>
the time.<br>
<br>
Cheers<br>
<br>
[DAA]<br>
</div></div>