Unable to set node credentials...
apple Verified ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
I have setup the server as an OD master, and up until now it hasn't had problems binding, although I haven't been able to get any users to authenticate for any services, other than my local admin account.
I haven't made any changes, but now when opening ServerPrefs, I get the following error:
"Unable to set node credentials for /LDAPv3/127.0.0.1 with the record name server.
mydomain.com$ There may be a problem with the Open Directory service."
Any ideas where I went wrong?
15 replies
Sign in or join Beachball Help to reply.
- 0
lnail ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
For some reason, a restart fixed this.
- 0
sandinak ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
I am running 10.6.1 on a mac mini .. while trying to save/restore the ldap database .. I now get this error on Server Prefs no matter what I do. I have' tried several reboots.
- 0
Effect ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
I've been getting this same error as well. It won't even let me access the server preferences.
I'm thinking it might be what is causing our server to lock up. However here is the additional weird thing. When it locks up it causes all computes connected to the server via logins to lock up as well. Connection doesn't seemly drop but the client computers freeze up as well. Now no software is being run off the server but I can't for the life of me understand why it would even do that. Had no issues at all running 10.5 and thinking perhaps dropping back to that might be the best way to go.
- 0
AlanShutko ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
I am seeing the same problem on a brand new install of Snow Leopard server on a bare drive. I may try nuking it and reinstalling, updating to 10.6.1 before I configure any other services. Restarting doesn't cure the problem.
- 0
Nnooo ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
We had this problem when we migrated from Leopard Server to SL Server. The Leopard server had a different hostname (which we changed before migrating).
With a lot of help from Apple Support we tracked it down to a keychain item on the Servers System Keychain. There were two com.apple.opendirectory keychain items one for the new new hostname and one for the old. We deleted the old keychain item and this fixed the error without a reboot.
Warning delete stuff from the System keychain on your server at your own risk. We backed ours up first.
- 0
Roggie ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
I had the same prob with a new install of Snow Leopard. In my case the server had no ethernet, only wireless. The Server Prefs tool worked until I rebooted the server for the first time, then Serv Prefs wouldn't let me login - "unable to set node credentials"
Solution - Airport Wifi was turned on but not joined to a network. I joined my Wifi network and problem solved.
-Roger
http://www.thehypervisor.com - 0
cmon_stoke ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Thanks roggie it worked for me. Totally new to Mac OSX I have some *nix but it has been a while. and the last time I touched a mac was the late 90's.
I only had my mac mini server running for about 5 minutes it did an update rebooted and I couldn't do squat with the system. I thought great what I have done should have stuck to windows. But your message meant it took me just a few minutes. 😉
For any noobies like me, click on the wireless icon at the top of the screen. - 0
Badmin ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
I'm still stuck.
Last night in desperation I erased the server HD and re-installed everything. Same routine - everything OK until one of the software updates required a restart and now can't authenticate. Looks like Open Directory - don't have duplicate keychain items as the erase stopped this. Always have been able to see and connect to the WiFi.
Now it just taunts - every time we log in using laptops it goes through the routine of trying to (presumably) bind the local machine accounts to the central directory and can't of course as it won't authenticate.
Not sure what else to do other than have a long phone conversation when I can find time.
Could do without this.
- 0
reimer ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Thanks Roggie. That simple fix did the trick!
- 0
LanceD2009 ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Hi,
I'm having the same problem with our mac mini and have no cue have to solve this. Do Apple techs read these boards and offer help? Are there any patches for this problem?
Thanks
Lance - 0
q001 ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Same problem here too. Also did a complete reinstall of os x server on my new mac mini-server. But after downloading and installing the update this error message comes up and I can not access the server preferences anymore!
Unable to set node credentials for /LDAPv3/127.0.0.1 with the record name...
Anyone got this worked out yet? Airport is working but not solving this issue either!
Cheers Q!
- 0
Badmin ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
It isn't something that a patch is going to cure.
I believe it does have something to do with the network and probably therefore the ip address / naming as the authentication does seem to be tied to the network location.
I've managed to move things on a little in that I have bound user accounts on other machines such that when someone logs onto their laptop it will tell them they have an account on the server and provide a logon after which their account is bound and (I think) marked as 'managed' in their Preferences | Accounts. This provides additional sections in iCal and Address Book although these don't work. The only person who can log into the web stuff such as the wiki is the server admin and I still can't access the Server Preferences or authenticate the Server Admin so can't make much in the way of changes.
I've submitted my application to Apple for support using the card provided with the Mac Mini. This was last Thursday and I've not yet received confirmation that this is live. As soon as it is I'll be having a long conversation with Apple Support.
I sort of sympathise with Apple as the server is clearly at least an order of magnitude more complicated than the admin involved with just a desktop. Having said this, however, they do need to get this sort of thing sorted by making it slicker, providing more online support for these problems if they have any aspirations towards the smaller office or even home environment which don't have dedicated IT support staff.
- 0
Canadian Techie ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
I solved the issue by recreating the directory by changed the default address from Server17.local to server17.pretendco.com.
- 0
Jason Wood1 ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
I had the same problem - also a fresh install - and I also thought it was caused by software update, but it was fixed after finding a typo in the DNS zones setup.
- 0
MDF2 ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
I also have the same problem which seemed to occur after an update. Hopefully the next update will cure it!
I have checked the Open Directory settings and can find nothing that looks as if it could be altered to fix the problem. I have verified the Keychain settings. My ISP does not allow me to configure the router.Inerestingly, this bug does not affect Server Admin as opposed to Server Preferences. So it's only the unititated that are locked out.
I am at a total loss to know what to do.