Buffalo Linkstation Joining domain.

[Stuart_C]

So I'm going with this here as I'm wondering if it's an issue with the server rahter than anything else.

I've just bought a Buffalo Linkstation Duo NAS. The firmware is up to date so in theory I should be able to join the AD domain... Well I can't.

 

It's on the network OK and I can access it normall. When I try and join it to the domain it tells me that it

"Failed to Join Active Directory Domain. Please check Active Directory Domain setting information, Administrator user name and password. Also, makes sure that you network settings are correct"

 

I've double checked everything, I can ping the domain, the servers are there, the time on the servers and device are the same yet still it won't connect. I've even tried creating the account first then "trusting for delagation" as per some trouble shooting I found. What it will do is create a computer account for itself in AD when it tries to join so it seems to be, at least in part, communicating with the domain. I can also "Join an NT domain" where it connects, picks up the groups then fails to let me connect to the shares.

 

So, anyone else got a Buffalo Link Station on their domain? How easy was it?

[leco]

I'd have to go look (not at school right now) as I can't remember if I actually got mine on the domain or not. I seem to recall that the addresses, that are required in the many boxes, were not what I expected them to be. I do remember that I couldn't get the username/passwords correct so some things hang as they have the "wrong" ones.

 

Having said that I'm still on a mixed W2003/W2008 (not R2) domain.

[leco]

Been to look - the Buffalo is still in a Workgroup, guess I couldn't figure out what I should be putting where in the path boxes. . Did try again just now but got the same message as you Sorry

[3s-gtech]

Right, I've just had to check this and it wasn't working on mine as I renamed my DC. The settings you need are:

 

NetBIOS domain name (so, what you'd have as your domain name shortened eg schoolname)

Domain name (eg schoolname.com)

Domain controller name (this MUST be a Server 2003 server - it will not connect to a 2008 R2 box)

Domain admin username

Password

WINS Server IP address (this can be server 2008 R2)

 

If you don't have a 2003 DC, you may need to make one just for this purpose, perhaps as a low spec VM. I have an old server which is a backup DC on 2003, this worked fine. Had to do exactly the same on my Terastation Pro. No more Buffalo units will be coming here, that's for sure. Hope this helps.

[leco]

Thanks, I'll try that on mine and see if it'll work.

[leco]

3s-gtech: Did I ever tell you that you were my favourite person? Having followed your list I now have a Buffalo that is a member of my domain and registered in Active Directory. Thanks you so much, just shows the power of shared knowledge:)

[Stuart_C]

Domain controller name (this MUST be a Server 2003 server - it will not connect to a 2008 R2 box)

.

Well that's a load of rubbish. I have been talking to their tech support (after me sending them a load of screen dumps) who suggested that the netbios version of the domian name is not what I think it is and they have suggested what I put in. Also that I make sure I use the "administrator" account without and special characters, well given I've got a complex secure password why would I make it less secure!!!

 

Do you have a reference to it not supporting 2k8 R2 server boxes or is it annecdotal based on what you've got to work? Just curious so when I e-mail buffalo and tell them off!

Actually I worked out how to get Acronis to write to it today and as I only need it for my servers to back up to disk I don't NEED it to connect to the domain but I thought it would be nice.

[leco]

Stuart_C: Sorry to hear of your woes, shows that differing situations have different solutions. I had been using the Buffalo successfully to back up from both my servers (2003 and 2008) so it was connecting OK. It just seemed like a good idea for it to be on the Domain, which it now is. As for names in boxes - maybe yours are more complex than mine, also my permissions on it are very restricted.

 

I'll see on Monday if it's all worked correctly.