AFP548 Changing the world one server at a time.

Probably more of an LDAP question …

Home › Forums › OS X Server and Client Discussion › Active Directory › Probably more of an LDAP question …

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #357335
    agc
    Participant

    The “LDAP browser (2.8.2)” that is recomended in a number of posts on this site fails to connect to the AD LDAP server. I went back to my Win2k box and used _exactly_ the same information and it I was browsing the LDAP diectory in seconds …. I have scoured the forums for other instances of this problem and found that most people just browse the LDAP server and move on to the next problem …. getting OSX to authenticate to the AD Server.

    A little background:
    client: OS 10.3.2 Server (clean install with all the latest patches)
    AD LDAP Server:Win2k Server
    PC client that works happily: Win2k (workstation)
    All boxes get an ip from DHCP and there is a DNS server (used by the whole University). All machines are in the same subnet (/24)

    Aim of the exercise:
    eventually to authenticate to AD and serve home directories from OS X server

    I’m quite sure that there is something quite simple that I am missing…. Any help would be greatly appreciated.

    Alistair

    #357350
    agc
    Participant

    I have tried both ways, with both PC and Mac and the PC can get in (both ways) the Mac does not. It seems as if the Mac can’t even see the LDAP server, as the error it returns is something along the lines of “failed to conect to server x.y.z……” so it isn’t even getting as far as authenticating.
    mmmmmm……

    (when the PC binds without username/pass I can only see the top level of the directory… which is normal)

    Alistair

    #357937
    agc
    Participant

    it ended up being a DNS problem…. the enterpirse DNS (on a unix box) did not have a record for the AD domain and so it couldn’t resolve any domain controllers to bind to

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