Domain Controller seems not work in Internal Server

[1ncludeSteven]

Dear author:

I know that samba had been installed in internal server successfully, and we use socbed/provisioning/ansible/roles/configure_win10_client/files/win10_assets/init_tbf_client.py in windows client to add current client to this domain controller. Howerver, configuration in internal server may not be effective so that we use whoami /upn in ClientClone1 doesn't running successfully as below:

I have checked that ClientClone1 have been added to domain controller successfully as below:

By the way, kerberos in internal server also runs failure:

[ru37z]

Thank you for reporting this issue! We have experimented quite some time with the Samba server in the past but never really managed to make it fully behave like a real Windows domain controller. We add clients to the domain mainly for two reasons: (1) Being able to login with domain credentials and (2) being able to use a shared directory on the internal server. Both features work, while certain other domain functionality might not. Currently, we do not see any concrete reasons to improve this situation from a functional perspective - do you?

[1ncludeSteven]

Thank you for your reply. Regarding your comment about being able to log in with domain credentials, I would like to ask how you tested it. Regarding the shared directory, how did you test it? I did not find the test code in the systest directory.