Page 1 of 1

Unable to Join AD

Posted: Sun Jun 06, 2010 4:20 am
by Alexander25
Trying to join W2K3AD, pointed to DNS server, synced time with the local workstation using QNAP page and got following message:

Microsoft Networking configured failed. Cannot resolve domain, please check DNS server, AD Server Name and Domain.

======== DEBUG START =======
/usr/local/samba/bin/net time set -S Storage.domain name
Sync time with domain name fail, try to sync time with IP
/usr/local/samba/bin/net time set -S
[command] echo ******** | /usr/bin/kinit "adminuser name"
kinit(v5): Cannot resolve network address for KDC in realm domain name while getting initial credentials
[command] echo ******** | /usr/bin/kinit "
Microsoft Networking configured failed. Cannot resolve domain, please check DNS server, AD Server Name and Domain.

======== DEBUG START =======
/usr/local/samba/bin/net time set -S Storage.domain name
Sync time with domain name fail, try to sync time with IP
/usr/local/samba/bin/net time set -S
[command] echo ******** | /usr/bin/kinit "adminuser name"
kinit(v5): Cannot resolve network address for KDC in realm domain name while getting initial credentials
[command] echo ******** | /usr/bin/kinit "adminuser name"

Ok"

Ok

Any suggestions?

Re: Unable to Join AD

Posted: Mon Jun 07, 2010 2:19 pm
by QNAPJauss
Dear Alexander,

from your logs :
/usr/local/samba/bin/net time set -S Storage.domain name
I guess "Storage" is the name of your NAS.
When you fill up field "AD Server Name", it should be the hostname of your domain controller, not the NAS.
In the Application Notes "http://qnap.com/pro_application.asp?ap_id=153", you will find how to get the correct AD server name and the other information.


BR,
Jauss

Re: Unable to Join AD

Posted: Tue Oct 19, 2010 10:14 pm
by Kofl
Hi,

just for feedback:

I also missinterpreted "AD Server Name", it should - in my opinion - be called "AD domain controller".

Thanks for clearing that up,
Thomas

Re: Unable to Join AD

Posted: Wed Oct 27, 2010 8:40 pm
by schumaku
Dear Thomas,

There are no more Domain Controllers in ActiveDirectory. What is required under "AD Server Name" is indeed an ActiveDirectory server.

For the fun of it: In fact all what is technically required is correct DNS configuration of the NAS - and then it can resolve the (ActiveDirectory) Domain Name form DNS - and it will receive a list of IP addresses with all possible AD servers.

Never figured out, why SAMBA still follows a much to complex configuration process.

Enjoy,
-Kurt.