16:21 - Wednesday, 23 April 2014

Adding Lion Client To Win2008 Active Directory “Unable To Add Server. Node Name Wasn’t Found. (2000)”

#Topics: node name wasnt found 2000,unable to bind mac to active directory os x 10 7 5,Node name wasnt found,Unable to add server Node name wasn\t found (2000),unable to add server node name wasnt found

I try and bind a Mac running 10.7.3 to a Windows 2008 active directory using System Preferences and Directory Utility. It comes back saying “Unable to add server. Node name wasn’t found. (2000)”. What does this mean? Can anyone help?

Thanks

I managed to fix it. Here’s how:

  • set the client’s time to the network time from the windows server
  • deleted the computer account off from the Active Directory
  • restarted the Mac client!
  • tried again…works fine

Not really sure what was causing the problem, but it’s now working. Thanks for the input!

I had similar issues and resolved it by doing the following:
- ensured the mac’s time was the same as my domain controllers (i have NTP servers so i used that). kerberos will not tolerate anything greater than 5 minutes skew in time!
- updated to the latest apple OSX updates. I was on 10.7.3 and 10.7.5 had significant Active Directory bug fixes.

that’s it, worked first time after that. i’d like to point out that i did not create the computer object first, it was created upon joining the domain. Also i just typed in my adminisrative username not domainusername.

Hope this helps someone else.

I’ve seen this in Snow Leopard when the OS X client has a strange name. Do you have anything other than letters, numbers, and underscores/dashes in the OS X machine’s name? If so, you’ll have to remove them before binding to AD. Also, you should make sure that the name is 16 characters or less, though this seems to be less of an issue nowadays than it used to be.

I think the time issue is key, I came across that one before and forgot the solution until I found this post (whilst trying to get another MacBook on the domain). If the time is too far out (in our case it was 20 minutes out) the domain controller will have none of it.

Share

Advertisement

Comment