On Mon, Sep 2, 2019 at 1:56 PM Alessio <alciregi(a)gmail.com> wrote:
On Mon, Sep 2, 2019, 5:16 PM Dario Lesca <d.lesca(a)solinos.it> wrote:
>
>
> After few minutes almost everything work well, except for a thing ...
> all windows PC cannot access to others windows PC.
Wait. I'm not an expert. Said that, are we sure that the cause is krb MIT? Also on
the samba ml it seems a supposition.
Windows PCs are all running windows7?
The same happens with windows 10?
And all these deprecated entries?
krb5kdc[6764](info): AS_REQ (6 etypes {aes256-cts-hmac-sha1-96(18),
aes128-cts-hmac-sha1-96(17), DEPRECATED:arcfour-hmac(23), DEPRECATED:arcfour-hmac-exp(24),
(-135), DEPRECATED:des-cbc-md5(3)})
As one of the people who backport current releases Samba to RHEL 7,
with the domain controller enabled, I can vouch that "yes, it's the
Kerberos". My work is over at
https://github.com/nkadel/samba4repo,
and it seems to work fairly well with Fedora 30, though I've not
tested it as thoroughly. I have some test rigs in place for samba
4.11rc2 there.
The samba default values are all, by default, set as simply and
generally as possible. Activation of a real domain requires a good
deal of control and authority over local DNS, and the minimal setup
works really well for testers who don't need to start with all that
power and strenuous requirements.
II'd urge you to hop over to the samba-devel or samba mailing lists,
post your smb.conf and version of Samba, and look for debugging help
there.