Home Forums OS X Server and Client Discussion Open Directory "Record Type Not Mapped" when authenticating to LDAP Server

Viewing 9 posts - 1 through 9 (of 9 total)
  • Author
    Posts
  • #358577
    Anonymous
    Guest

    Hey all –
    I’m having some issues authenticating to the LDAP directory in my OS X 10.3.4 Server. I can login to the local directory just fine, but when I authenticate to the LDAP directory, it tells me "The record with the type "PresetUsers" is not mapped", followed by the same message for "PresetGroups". Workgroup Manager then kicks me back into the local directory. DNS is up and running on the server.

    Can anyone help me with this? It’s driving me crazy!

    Thanks,

    Mark D

    #358595
    Anonymous
    Guest

    Thanks for the response! I tried both settings (it was on Open Directory Server), and neither of them worked. Any other ideas?

    -> Mark D

    #358598
    Anonymous
    Guest

    Okay, so amazingly enough, quitting and restarting Workgroup Manager solves this issue. Go figure.

    #359639
    Anonymous
    Guest

    I am having this exact same error. Although quiting Workgroup Manager does not solve my issue. I have also tried going from “Open Directory Server” to “get from server” with no luck. I am completely lost on what to do from here. Please help.

    #359696
    td3005
    Participant

    if this issue is occuring after the initial set up or after changeing to an open directory master I would suspect and Issue with the ldp database. I would check the slap.conf log for more info about what happened when the server attempted to be promoted to ODM.

    #360807
    dtauvdiodr
    Participant

    I encountered this when trying to switch to a new IP/OD/LDAP configuration. I was able to clean out everything and start it right back up with slapd tools:

    slapconfig -destroyldapserver
    slapconfig -createldapmaster admin
    slapconfig -enableslapdlog

    Now you’ll have a brand spankin new LDAP server.

    #361258
    Anonymous
    Guest

    I had the same problem with a fresh OS X Server.
    Activing DNS Server (with out-of-the-box configuration) solved this. Big Grin

    #364117
    TBoxman
    Participant

    This has happened to my test server out of the blue. I have no idea what started it or how to fix it.

    Any clues?

    #364118
    TBoxman
    Participant

    Got it. Following the instructions to change Directory Access fixed the problem. I just didn’t follow along before responding.

    Thanks for the help and this great site.

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

Comments are closed