Thank You for the response.
The which you have referred that shows how to add the computer to windows active directory.
I am adding my computer TO UCS Domain. while adding the computer i am getting above error message.
Well, for the client there is not really a difference if he joing MS-AD or UCS-AD which is the purpose of UCS!). The error message mentioned surely points to a misconfigured DNS.
And what about my second question: die you try to join as a member server or as a DC-controller?
If asked for output, please post the output here so we can verify- it is not helpful to tell us everything is fine. The error message points to an DNS error, so we would like to verify.
So, what is the output of the ipconfig /all on Windows? What is the output of ip a on UCS DC?
What is the output of nslookup _ldap._tcp.pdc._msdcs.your.domain on Win?
I am just wondering what domain name do you enter when trying to join? And, again, you join the Win machine as a member server, correct? Or are you trying to join as a backup or slave?
root@ucs-7370:/etc/init.d# /etc/init.d/bind9 status
● bind9.service - LSB: bind9 Domain Name Server (DNS)
Loaded: loaded (/etc/init.d/bind9)
Drop-In: /run/systemd/generator/bind9.service.d
└─50-insserv.conf-$named.conf
Active: active (exited) since Mon 2018-02-26 07:45:28 EST; 1 day 22h ago
Process: 1190 ExecStart=/etc/init.d/bind9 start (code=exited, status=0/SUCCESS)
Feb 26 07:45:28 ucs-7370 systemd[1]: Started LSB: bind9 Domain Name Server (DNS).
Feb 26 07:45:28 ucs-7370 bind9[1190]: Starting bind9 Domain Name Server (DNS): samba4.
but samba-ad-dc is not providing any status.
root@ucs-7370:/etc/init.d# /etc/init.d/samba-ad-dc status
root@ucs-7370:/etc/init.d#
root@ucs-7370:/usr/share/univention-samba4/scripts# ./check_essential_samba4_dns_records.sh
gc._msdcs.mytech.intranet has address 172.16.17.163
_gc._tcp.mytech.intranet has SRV record 0 100 3268 ucs-7370.mytech.intranet.
_ldap._tcp.gc._msdcs.mytech.intranet has SRV record 0 100 3268 ucs-7370.mytech.intranet.
_ldap._tcp.mytech.intranet has SRV record 0 100 389 ucs-7370.mytech.intranet.
_ldap._tcp.dc._msdcs.mytech.intranet has SRV record 0 100 389 ucs-7370.mytech.intranet.
_ldap._tcp.pdc._msdcs.mytech.intranet has SRV record 0 100 389 ucs-7370.mytech.intranet.
_ldap._tcp.0a9c5f6e-6bfe-4301-a05b-4ccf587f55a2.domains._msdcs.mytech.intranet has SRV record 0 100 389 ucs-7370.mytech.intranet.
_kerberos._tcp.dc._msdcs.mytech.intranet has SRV record 0 100 88 ucs-7370.mytech.intranet.
_kerberos._tcp.mytech.intranet has SRV record 0 100 88 ucs-7370.mytech.intranet.
_kerberos._udp.mytech.intranet has SRV record 0 100 88 ucs-7370.mytech.intranet.
_kpasswd._tcp.mytech.intranet has SRV record 0 100 464 ucs-7370.mytech.intranet.
_kpasswd._udp.mytech.intranet has SRV record 0 100 464 ucs-7370.mytech.intranet.
Located DC ‘ucs-7370’ in site ‘Default-First-Site-Name’
5728fcd5-8fe0-496f-a11d-09b2e88e5ca7._msdcs.mytech.intranet is an alias for ucs-7370.mytech.intranet.
Records for site Default-First-Site-Name:
_ldap._tcp.Default-First-Site-Name._sites.mytech.intranet has SRV record 0 100 389 ucs-7370.mytech.intranet.
_ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.mytech.intranet has SRV record 0 100 389 ucs-7370.mytech.intranet.
_kerberos._tcp.Default-First-Site-Name._sites.mytech.intranet has SRV record 0 100 88 ucs-7370.mytech.intranet.
_kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.mytech.intranet has SRV record 0 100 88 ucs-7370.mytech.intranet.
Optional GC Records for site Default-First-Site-Name:
_gc._tcp.Default-First-Site-Name._sites.mytech.intranet has SRV record 0 100 3268 ucs-7370.mytech.intranet.
_ldap._tcp.Default-First-Site-Name._sites.gc._msdcs.mytech.intranet has SRV record 0 100 3268 ucs-7370.mytech.intranet.
_kerberos.mytech.intranet descriptive text “MYTECH.INTRANET”
Well, it points to exact the same reason we were pointing to all the time - DNS. We just have not found the root cause yet.
So please re-check your network settings again. Check if you have external nameservers configured and in your network settings your DC master ist set as DNS-Server, too.
root@ucs-7370:/etc/init.d# ./samba-ad-dc status
● samba-ad-dc.service - LSB: start Samba daemons for the AD DC
Loaded: loaded (/etc/init.d/samba-ad-dc)
Active: active (exited) since Wed 2018-02-28 10:54:12 EST; 23min ago
Process: 26670 ExecStop=/etc/init.d/samba-ad-dc stop (code=exited, status=0/SUCCESS)
Process: 27299 ExecStart=/etc/init.d/samba-ad-dc start (code=exited, status=0/SUCCESS)
Feb 28 10:54:12 ucs-7370 systemd[1]: Starting LSB: start Samba daemons for the AD DC…
Feb 28 10:54:12 ucs-7370 samba-ad-dc[27299]: samba-ad-dc disabled by ucr var samba4/autostart=false
Feb 28 10:54:12 ucs-7370 systemd[1]: Started LSB: start Samba daemons for the AD DC.
It looks like samba4 did not get installed in the UCS system…
root@ucs-7370:/etc/init.d# systemctl status samba4.service
● samba4.service
Loaded: not-found (Reason: No such file or directory)
Active: inactive (dead)
Same result i am getting when i am trying to start from GUI.
I had install it but it was not coming up automatically.
even though samba4 seems to be not required running in back end the service is required that is samba-ad-dc.
I checked samba-ad-dc was not coming up automatically because it was masked by other services.
root@ucs-7370:/var/log/samba# systemctl start samba4.service
samba-ad-dc Failed to start samba-ad-dc.service: Unit samba-ad-dc.service is masked.
I have unmasked this service and start it. Still it did not work.
so i installed UCS server again and now i am able to add my windows client in domain and able to login with Domain user.
Still we did not have root cause, why this issue comes but i had learnt many things regarding UCS server and clients.
Thank You for all the UCS help users that supported and answered my Queries.