Displaying 3 results from an estimated 3 matches for "date0".
Did you mean:
date
2018 Mar 27
5
ODP: Re: freeradius + NTLM + samba AD 4.5.x
...9;s unnecessary, it doesn't break
anything, and unfortunately I was unable to test if it works (I doubt
it) without this option while denying ntlmv1 overall on ad dc.
If everything works as intented, in the AD DC audit log You will see
something like this:
{"timestamp": "some-date0", "type": "Authentication", "Authentication":
{"version": {"major": 1, "minor": 0}, "status": "NT_STATUS_OK",
"localAddress": "ipv4:xxx.xxx.xxx.xxx", "remoteAddress":
"ipv4:xxx...
2018 Mar 28
0
ODP: Re: freeradius + NTLM + samba AD 4.5.x
...;t break
> anything, and unfortunately I was unable to test if it works (I doubt
> it) without this option while denying ntlmv1 overall on ad dc.
>
> If everything works as intented, in the AD DC audit log You will see
> something like this:
> {"timestamp": "some-date0", "type": "Authentication",
> "Authentication": {"version": {"major": 1, "minor": 0}, "status":
> "NT_STATUS_OK", "localAddress": "ipv4:xxx.xxx.xxx.xxx",
> "remoteAddress":...
2018 Mar 27
2
ODP: Re: freeradius + NTLM + samba AD 4.5.x
ok, tested it, and it works.
so to summarize:
on samba ad 4.7.x in smb.conf "ntlm auth" is set to "mschapv2-and-ntlmv2-only"
fr + samba domain member (4.6 and 4.7) in mods-available/mschap you have to add to ntlm_auth --allow-mschapv2 to the whole string OR just use winbind method, which sets correct flag without explicitly adding it.
with those settings ntlmv1 is blocked