Home Forums OS X Server and Client Discussion Open Directory Mobile account authentication goofiness

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #362568
    eableson
    Participant

    I have an odd one here. A powerbook that’s joined to an Active Directory domain at the office, but also has an Open Directory instance at the house for personal accounts. The bizarre issue is that I keep running into instances where (with FUS activated or not) that I can’t authenticate against one or the other environments. Sometimes killing the network permits the logins so it’s looking in the cache, but this isn’t foolproof.

    Currently, I’m at the office, have a session open on the personal mobile account in the background and am logged into an AD authenticated mobile account. When I try to switch to the home account, it won’t accept the password. Now my server is accessible from the internet and I can connect via LDAP with various utilities, and I can browse the OD environment via dscl so there’s no connectivity issues.

    I’m at a loss to why this would be the case. Can anyone point me to some documentation that shows the sequence of events and checks that are performed when doing opening a session? And perhaps a means of simulating the sequence so that I can observe where it’s dying?

    #362595
    andyinindy
    Participant

    I can also attest to some oddness, although it’s probably my fault. Recently I have been unable to login to machines (iBooks) that are bound to active directory if the “create mobile account at login” checkbox is ticked. Deselecting this option allows logins to continue. The logs show an inability to mount the user’s share (UNC path) at /private/Network/Servers/servername/username/ with permissions errors. These errors continue indefinitely. The result is that the login panel hangs with a spinning pinwheel of doom.

    I later discovered that there was an issue with the image that I was using on the machines displaying this odd behavior. I had made the mistake of creating my image from a machine that was already bound to active directory. I am not sure whether this is the cause of this login oddness or not (manually removing the machine record from AD didn’t seem to change matters). I’m currently rebuilding my image from scratch, and I’ll report results.

    Sigh…

Viewing 2 posts - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.

Comments are closed