QTS 4.1 Domain Controller Documentation?

[Davide-NYC]

Pardon me if I'm missing something, but I cannot seem to find any documentation for the QTS 4.1 Domain Controller (SAMBA4) functionality.

I see that the Domain Controller feature is available in the QTS 4.1 demo, but there is nothing about it in the QTS 4.1 (SMB) manual.

Am I missing something?

[Q_Lover69]

Did you get any reply regarding your question?

[Davide-NYC]

No. I did not.

[Davide-NYC]

No. I did not.

[Joebar]

Hi,

I will also enable the Domain Controller on my TS-870 Ultra, but I get always the same error message.

--> [Domain Services] A domain xxx.local creating was failed

I have tested also on my second TS-669 Pro but there I have the same error, have someone a Idea why this failing ?

Kind Regards,
Joebar

[QNAPJason]

Hello,
We're sorry about the delay. The domain controller function has been added to QTS 4.1 user manual: Domain Controller

http://docs.qnap.com/nas/4.1/SMB/en/ind ... roller.htm

[Joebar]

Hi,

I will also enable the Domain Controller on my TS-870 Ultra, but I get always the same error message.

--> [Domain Services] A domain xxx.local creating was failed

I have tested also on my second TS-669 Pro but there I have the same error, have someone a Idea why this failing ?

Kind Regards,
Joebar

I have set this settings as written in the domain controller QTS 4.1 user manual.

To set the NAS as a domain controller, follow the steps below:
1. Go to "Control Panel" > "Privilege Settings" > "Domain Controller" > "Domain Controller" tab.
2. Select a domain controller mode from the drop down list.
3. Specify a domain (example: mydomain.mycompany.local.)
4. Fill out the administrator password and the same password again in the "Verify Password" field.
5. Click "Apply".

After a domain controller is not enabled ? --> [Domain Services] A domain xxx.local creating was failed

[doktornotor]

After a domain controller is not enabled ? --> [Domain Services] A domain xxx.local creating was failed

Yeah, creating "was failed"... So was QNAP's English.

Go to QNAP support http://helpdesk.qnap.com/index.php?/Tickets/Submit - the total lack of any useful information logged on errors makes debugging impossible.

[Eraser-EMC2-]

Are there other options which we have to set or unset like DNS-Server of the Router.
In the Log is only "[Domain Services] The Domain controller enable was failed", nothing more ....
I tried also different domain names with ".local" or my real ".de" domain, every time failed.

[doktornotor]

Well, not only that it fails, but... when I tried to enable the DC functionality and selected "Additional Domain Controller", it

- screwed permisssions competely
- created some junky duplicate AD users/group structure with the name QNAP on the NAS
- nuked the machine account in AD

Had to restore configuration backup, unjoin and rejoin the NAS to domain and redo all share permissions to get things back working.

Wondering how much testing went into this feature...

[geocast]

I had a similar problem.

First my nas was called "jupiter", so when I tried to set up the DC as jupiter.local it would fail. Changing it to saturn.local helped.

Also I had it in a different szenario. Naming the DC contoso.saturn.local helped in that case.

Besides that everything is working well since I mangaged to work out permission settings via ACL, these aren't set correctly by QNAP, but that also could be a setup problem.

Hope that helpes

[Eraser-EMC2-]

First my nas was called "jupiter", so when I tried to set up the DC as jupiter.local it would fail. Changing it to saturn.local helped.

That is a NetBIOS limitation and exists since Win NT 4.0.
It should be also impossible to create an user like the Domain name.

[agath]

Any luck??? I'm getting the same error when setting the my TS-253 Pro as a domain controller...

[agath]

I contacted QNAP supported and got the issue resolved. Looks like QNAP doesn't support long domain names (mine was about 17 chars). Once I provided a short name things started to work. QNAP is checking if this is a bug or a limitation.

[Davide-NYC]

Personally, I'm staying away from this until I see some better documentation and hear reports of ADDCs up an running smoothly.