I'm trying to connect a LaCie Ethernet Disk Raid (2TB) to a Windows Small Business Server 2008 domain. This is the error I'm getting in the final stage:
"The specified user name and password does no have sufficient privileges to join the domain where Active Directory server resides. Enter user name and password with sufficient privileges and try again."
Here is what I've done to troubleshoot:
1. Time is exactly the same between server and NAS.
2. NAS is on latest firmware.
3. Enabled and use the Administrator account. I has complete control of the domain and server.
4. Called LaCie and they don't know what is wrong.
5. Tried to use the second network port.
6. Tried specific IP address in a reserved range.
Any known issues between this disk and Windows Server 2008?
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
There isn't enough space to fit the domain\administrator text string in the user field. I tried that. Being SBS 08, it doesn't want to add a computer. It wants the device to run the setup utility and have it join.
I think the NAS has to run it's own conversion utilities b/c changes are required on the NAS. It must drive the connection.
It can only be done from the nas using the domain\username...
But maybe here's a workaround.
Don't you have an old pc which you can name exactly like the NAS and make it create a domain computer account with SBS.
Then remove this pc and connect your NAS. ( which now has a computer account in your SBS domain )
It turns out that SBS 08 wouldn't work. We set up a Server 03 R2 box and it worked.
BE WARNED!!!! The LaCie NAS reacts VIOLENTLY to a change in the domain. We rebuilt the domain, don't ask why, with the same name and the NAS refused to connect. The documented solution is to change authentication mode to local and then back to AD. Well, when you do that, it wipes the drive. Not a good solution.
We're going to call LaCie on Monday to find out WFT to do. My engineer has figured out how to hack it to get 1 file off at a time, but it's painful.
I had the same problem, connection with sbs2003 domain no problem, connection with sbs2008 not possible.
SBS 2008 is more secure with connections, because i dont wan't to mess with the local security policies (network security: Send NTLMv2 response only)
I made a cname dns record: laciedisk.domainname.local
created a local user on the laciedisk (admin) with password
changed the loginscript: net use o: \\laciedisk.domainname.loc
Now everthing is working fine.
Business Accounts
Answer for Membership
by: karstiemanPosted on 2009-05-15 at 12:23:35ID: 24398915
looks like networking is fine, but there's a permission problem.
Try to add the NAS to the domain using DOMAIN\USERACCOUNT and password. ( with domain\ in front )
if this not works, add the NAS to the computers OU in the active directory and try to add it to the domain again after this.