NT Domain

[gdemery]

   

I've done everything possible to try to join my Windows 2003 domain but can't seem to get the Terastation Pro to complete the handshake.  I'm putting in the right information to join the domain.  Is there something that has to be done on the domain side to get the terastation to join the domain.   I've given the AD admins the name of the terastation and they have added it just like any other computer. 

Thanks

[gdemery]

   

All I get is Failed to join NT domain...reconfirm nt domain and nt comtroller name...reconfirm computer account

[gdemery]

   

The BT says the admin administrator's password can't have any special characters other than hypen or underscore.  I change the password to meet this requirement but still can't join domain.  Anybody got any ideas?

[JoshC]

Whats your GMT set to?  What time zone are you in.  If the time isnt set to within 5 min. of the domain controller it wont sync with it or pull any of the users and groups.

 

Go here to check your GMT.

 

 

 

 

Here is something else you can check out also.

 

 

<!--       @page { margin: 0.79in }       TD P { margin-bottom: 0in }       P { margin-bottom: 0.08in }    -->

Does your domain controller require Digitally Signed SMB Packets? On Windows 2003 Server these policies are enabled by default.  They need to be set to 'Disable', not 'Enable', or 'Not Defined'.  If not I would initialize the unit and set it back up.  Make sure the settings are correct:

 

 

Configuring the Buffalo Nas for Active Directory:

• A computer account with the name    of the Buffalo NAS needs to be created on the domain. It needs to be    configured so that a pre-2000 machine can use this account.

• In "IP Address Properties"    under "Network", the DNS server address needs to be set to    the Domain Controller's address.

• The clock on the Buffalo 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:

Workgroup and Domain Properties:

• Network Type: "Active Directory"

• Active Directory Domain Name (NetBIOS Name): NETBIOS Legacy    Domain name, ex. "DOMAIN"

• Active Directory Domain Name (DNS/Realm Name): Full Domain    name, ex. "domain.com"

• Active Directory Domain controller Name: Domain Controller    name, ex. "server"

• AD Administrator Name & AD Administrator Password: The    user name and password of an account with administration privileges    so the Buffalo can properly be added to the network. This    information will not be stored.

• WINS Server IP Address: IP    address of the WINS server (if not using WINS, enter domain    controller's IP address)

 

 

 

 

 

[gdemery]

   

Josh,

I will go back tot he Buffalo and verify all my settings and discuss the domain settings with the AD folks.  I appreciate your feedback so much.

 

G

[elanf]

   

I have encountered the same problem. I have a TeraStation Duo 2.0.

 

I followed all the above instructions except the security policy changes on Windows 2003 server. I want to clarify the correct settings.

 

I have:

 

- Microsoft network server: digitally sign acommunications (always) as Disabled

- Domain member: ditigally encrypt or sign secure channel data (always) as Enabled

- Microsoft network server: digital sign communications (if client agrees) as Enabled

 

and

 

- Domain member: digitally encrypt secure channel data (when possible) Not Defined

- Domain member: digitally sign secure channel data (when possible) Not Defined

 

Is that correct, or not?

 

- Elan

[gdemery]

   

Still working this issue. I have one of our AD guys helping me.

 

Thanks

[Memoryman]

   

gdemery - you state you have a Terastation Pro - do you have firmware 1.01 or above on it? AD support was fixed in 1.01

[elanf]

   

Apparently, I tried two more things, the latter of which I think was the issue.

 

1) I set the NTP server to be my Domain Controller (time was already set to within 3 seconds with the correct GMT)

2) Disabled port trunking

 

I attempted to join the domain after disabling port trunking and it joined no problem.

 

- Elan