Buffalo Forums

   

Hi:

I upgraded my LinkStation Pro Duo firmware to V3.08, and whenever I try to join it to my AD, I get

"Failed to join Active Directory Domain.
Please confirm the Active Directory Domain setting information, Administrator user name and password"

 

I reset the unit to factory defaults after upgrading the firmware, ensured that the time, date, and timezone match the AD server.  The AD admin user name and password I am using do not contain any special characters, only Caps, lowercase, and a number.  The AD only consists of one Domain Controller, and the LS and Domain Controller are on the same network.

 

Any other ideas?

 

Thanks,

 

Steve Schneebeli

   

Two things check and make sure the time on the unit is correct, AND the time zone (keep in mind GMT Eastern Time is -5, NOT +5.

 

Second thing you need an Admin user name and password with NO special characters. If you do have them then all you need to is change it or create a new until the LS joins AD, then change it back or delete it (if you need to).

   

I tried your suggestions, and the time was synced correctly, the timezone set correctly, and I created a test domain admin with a simple password of only lower case, and I still get the same error.

   

Do you have special characters in anything for any of the other fields?

Domain, DC name, ect. cannot have special character either. 

 

Have you added the TS to your AD client list as a Pre Windows 2k comp?

   I'm also having the same problem. I upgraded to Firmware 3.08, checked the time/timezone, used password with no special characters, added a pre Windows 2k account to the computer list in AD, and it's still not joining to my Win2008 AD domain. Has anybody had success with this?

   

Thanks for responding, I've been beating my head against the wall, and not looking forward to telling my boss that the new NAS boxes we have are not fully compatible with AD, even though the box says it is, and I used that as a selling point to purchase 2 of these.

 

Our domain controller name has two dashes.  This was not a problem when our domain was a  Win2K Active Directory.  The name of the LinkStation also has a dash in it.  Again, was not an issue on our old Domain.  I have no way of changing the DC name now.

 

I have also tried adding the TS to the AD computer list before attempting to join it, and I got the same results.

 

Do you have any idea as to why the LS is so picky now, when it joined our old W2K AD without a hitch?  Our old domain and DC were named the same as what our W2008 Domain is.

 

   

   

Miafya, Please let me know what you find out.  It is really frustrating!

 

Thanks!

 

Reset the device to defaults and try again.

   I've reset it to factory settings, and get the same result.

Schnabe, the LS isn't any picker than it was before, the issue is that Server 2k8 is MUCH picker :)

 

I'll see if I can get access to a Server 2k8 box to test this out.

   

Thanks for testing this for me!  If I would have thought of checking about compatibility before purchasing the new 2008 server, I'd probably would have gone with Win2003!  But, so far, this is the only issue I have had with our new 2008 server (knock on wood!)

You could try the Delegate Authority method:

 

http://forums.buffalotech.com/buffalo/board/message?board.id=0101&message.id=2043&query.id=44990#M2043

 

I'm not sure if it will work with server 2k8, but I don't see why not, since that method only uses the server for authentication verification.

   The Delegate Authority method does work, but my issue with that is users are then added to the LinkStation as Local Users, and I then need to maintain users and groups on the LinkStation.  So, if someone changes their password on our 2K8 AD, I would then have to manually update the LS.

Indeed. I was hoping you were using it for server-side backups :(

 

What did you put in the WINS server field on the Workgroup/Domain page when trying the AD integration? Is the domain controller's IP address set as the Primary DNS Server?

   I don't have a WINS server, so I left that blank.  The domain controller's IP address is set as the Primary DNS server as well.

Try putting the IP of the domain controller in the WINS server address field. If that doesn't work, PM me with contact info and I'll give you a call.

   

Hi:

 

That did not work.  I am out of the office for awhile.  I'll PM you when I get back.  At least users can access it now with Delagate Authority selected.  It's not something I want to keep this way, though.

 

Thanks again for the help.