[Answer ID: 14208]
TeraStation Pro - Joining to Active Directory
- Run the active directory firmware update and reset the unit to default settings following the update.
- A computer account needs to be setup on the Domain with the name of the TeraStation Pro and set to pre-Win2000 machine. (note: on a 2003 Domain the TS needs to be set as a client machine and not a server)
- The Domain Controller needs to be supplying DNS for the network and needs to have Netbios over TCP/IP setup.
- In "IP Address Properties" under "Network", the DNS server address needs to be set to the Domain Controller's address.
- The clock on the TeraStation Pro LinkStation Pro needs to be set to the same timezone as the Domain Controller and the times need to be with in 5 minutes of each other.
The "Workgroup/Domain" page under "Network" needs to be set to the following settings - If ever a field is too short to enter the full information (particularly the Domain Name and the Domain Controller fields) they need to be filled in as much as possible:
- Network Type: "Domain"
- Workgroup Name: N/A (greyed out)
- Domain Name: Name of the user's Domain
- Domain Controller Name: Name of the server that controls the Domain
- WINS Server IP Address: The IP of what is running the WINS server
- Active Directory: "Domain"
- AD Full Domain: The full name of the Domain, typically "domainname.local"
- AD Full Domain Controller: The Domain Controller "dot" the full domain from the previous line so "domaincontroller.domainname.local"
- AD Administrator Name & AD Administrator Password:
The user name and password of an account with administration priveleges so the TeraStation Pro can properly be added to the network.
This information will not be stored. Also note, the TeraStation Pro is looking for JUST the username and password, not the full domain path.
NOTE: When the admin paswords have characters like *-^ it may not join, create another admin account with a simple password with just letters.
- All of the authentication settings will be greyed out and defaultly set to "Deligate to Windows Domain Controller"