On Mon, 2019-09-02 at 17:14 +0200, Dario Lesca wrote:
After few minutes almost everything work well, except for a thing ...
all windows PC cannot access to others windows PC.
Hey Dario.
Since in recent days I was testing and evaluating Samba as an AD domain
controller, but using another distro, I decided to configure a F30
server, and try to test what are you experiencing.
I can see a lot of the messages you reported:
Sep 03 01:14:09 adc1 krb5kdc[4059](info): TGS_REQ (5 etypes {aes256-
cts-hmac-sha1-96(18), aes128-cts-hmac-sha1-96(17), DEPRECATED:arcfour-
hmac(23), DEPRECATED:arcfour-hmac-exp(24), (-135)}) 10.97.69.24: ISSUE:
authtime 1567589350, etypes {rep=aes256-cts-hmac-sha1-96(18),
tkt=aes256-cts-hmac-sha1-96(18), ses=aes256-cts-hmac-sha1-96(18)},
WINUNO$(a)MY.LAN for krbtgt/MY.LAN(a)MY.LAN
But authentication and access to Windows machines (I'm using Windows
10) seems ok: I can join the domain and I can log in with the domain
administrator and with a user crated on the samba server.
Then, it is true that I can't browse the network from the windows PC,
but it could be a group policy or something else.
Accessing a folder shared by windows machine 1 from windows machine 2
doesn't work... if I use the computer name or the fqdn (name resolution
works using nslookup). But if I use the IP address I'm able to access
the shared folder.
Using another distro, I was able to access the shared folder using the
computer name as well.
What is the beavihour you are observing?
What I mean is: maybe the issue is something in some little
configuration and not a big incompatibility issue preventing you to use
Fedora as DC.
P.S. if this list is not the right place to discuss such topic, we can
go elsewhere.
Thanks,
A.