Home › Forums › OS X Server and Client Discussion › Active Directory › Unable to log into AD account twice?
- This topic has 37 replies, 9 voices, and was last updated 16 years, 10 months ago by
lmadden.
-
AuthorPosts
-
June 3, 2008 at 9:55 am #372992
bentoms
ParticipantHi Lisa,
I know I am not getting the same parental issues as yourself but have came to the same conclusion about child domains.
We have some 30 odd domains under our root & these are located globally, I cannot bind to the ROOT domain but at least I know it may work.
Luckily we have no new Macs coming for a while for the next 3 months buit when we do we will have 30 clients to get working.
June 3, 2008 at 10:24 am #372993AgentOrange
ParticipantHi everyone.
I have finally given the Leopard A.D. plug-in the punt! This will sound like a sales pitch.
I have moved on to Centrify which provides me with a much cleaner interaction between A.D. and my OS X clients.
Authentication is FAST, GPO’s(really GPO’s) are read by my OS X clients, and there are command line utilities that work for troubleshooting.
I could not have asked for a better solution.
The cost is very managable at $60/client.
I am in my final stages of testing and will be going live in my local environment next week.
If you have not tried it, do so. http://www.centrify.com
June 3, 2008 at 11:49 am #372994lmadden
ParticipantHi,
Well, guess what? Apple has been able to duplicate my problem. We point the AD plug in to look in a specific field in AD for the UID, and the plug in works the first time, then on a restart it loses its brain and forgets about the UID. Can’t find one, so brings up the Parental Controls.
At least I know it is not something I was doing incorrectly.
We looked at Centrify, and I hear several folks going to WWDC will be talking to them next week. Also looked at Thursby’s AdmitMac. Would rather stick with Apple if possible since it is already in place.
You know the gov’t. We hate to spend money when we don’t have to 🙂
I’ll post once problem is resolved.
Lisa
June 10, 2008 at 6:38 pm #373055wfairchild
ParticipantJust a “me too” post. I have 8 new iMacs in a University lab. I’m trying to setup an image for them but can only login after binding to AD one time. If I unbind, then call the network admin to have the machine re-added, then rebind, I can log in one more time.
When I click through the selections under “Mac OS X” at the login screen the network one has a green light and says “network accounts available” but it continues to shake the login window at me as if to insinuate that my password is incorrect. Meanwhile, on 10.4.11, I’m still able to login to AD just fine.
Eagerly awaiting any news of progress and willing to try any suggestions.
June 10, 2008 at 6:51 pm #373056lmadden
ParticipantHi, the latest 10.5.3 has the same result of invoking parental controls, however, it does not give the error message splash screen. My guess is if you look at the account you can’t log in with in the Accounts pref pane, you will see the parental control checkbox has a check in it.
Apple has been able to reproduce this “bug” and is working on the issue. It only happens (as far as I know) if you bind to a child domain. If you bind to your forest root, it should be fine.
Do you have to bind to Active Directory? Can you get away with local login machines? We are currently reverting back to local login on the macs that are coming in Leopard only. Once this issue is resolved, we’ll then bind them to AD and life will be good.
Lisa
-
AuthorPosts
- You must be logged in to reply to this topic.
Comments are closed