Re: [Samba] Incompatibility Windows 7
- Date: Fri, 21 Jul 2017 09:15:38 -0400
- From: Gaiseric Vandal via samba <samba@xxxxxxxxxxxxxxx>
- Subject: Re: [Samba] Incompatibility Windows 7
In October, when samba was patched for "badlock" I had to set the following
client signing = auto
client ipc signing = auto
server signing = auto
otherwise some of the signing behavior was defaulting on on. You may
want to try turning some of the signing options to auto or off.
I am also using NT1 as the min and max server and client protocol. SMB
2.x causes problems.
I am running Samba 4.4.14 on my domain controllers and key file
servers. I think Samba 4.2.x is end-of-life so at some point there will
be some windows update that will break compatibility. I had Samba
3.6.x running last year and I couldn't keep it working anymore.
On 07/21/17 08:32, Manon JEANJEAN via samba wrote:
False Server max protocol = NT1 doesn't work because all my server fell there are 20 minutes.
So it's necessary to find a new idea.
De : Manon JEANJEAN via samba [mailto:samba@xxxxxxxxxxxxxxx]
Envoyé : vendredi 21 juillet 2017 11:47
À : samba@xxxxxxxxxxxxxxx
Objet : Re: [Samba] Incompatibility Windows 7
Ok Marco, I'm reassured to look you have the same problem.
My friend speak of NTML for my problem, it can help me?
What is NTML?
De : Marco Gaiarin via samba [mailto:samba@xxxxxxxxxxxxxxx] Envoyé :
vendredi 21 juillet 2017 11:27 À : samba@xxxxxxxxxxxxxxx Objet : Re:
[Samba] Incompatibility Windows 7
Mandi! Manon JEANJEAN via samba
> In chel di` si favelave...
I'm still in these situation, a samba4 NT-like domains with windows 7 pro clients.
The error reads : There are currently no log on servers available to
service the log on request
I'm hitting this also i, recurring but ''random''; apart effectively troubled box (eg, a box that boot bad, do an automatic rollback from a restore point and so lost the machine account) i hit errors like these, normally in twin with user password change troubles.
Tipically it sufficies to look at windows updates, most of the time the box have some update stuck or half-installed, and so a windows update runnign and a reboot fix the trouble.
All these sort of troubles start last autumn by the infamous KB3167679 update, that broke for a month or so NT domains.
Rowland, i've not set:
Server max protocol = NT1
>but, as stated, these trouble are spot and random...
To unsubscribe from this list go to the following URL and read the