-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Domain Controller seems not work in Internal Server #97
Comments
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? |
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. |
After successful setup, all clients login with a domain account ( socbed/provisioning/ansible/roles/configure_win10_client/files/win10_assets/init_tbf_client.py Line 144 in 2b55da6
A shared directory is created on the internalserver but currently not used AFAIK:
Hope that helps! 😃 |
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 usewhoami /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:

The text was updated successfully, but these errors were encountered: