Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #366530
    BobC
    Participant

    Hi folks,
    I have a 10.4.7 server as an OD Master connected to AD for auth of users. I made a new computer list, where I added just one test computer, which I bound to LDAP before. For this computer I set preference to use the xserver for software update.
    After restart of client I found this in log:
    [code]
    Jun 29 15:27:20 117-farm-g5 configd[35]: setting hostname to “117-farm-g5.local”
    Jun 29 15:27:20 117-farm-g5 /System/Library/CoreServices/mcxd.app/Contents/MacOS/mcxd: DSGetLocallyHostedNodeNames(): dsFindDirNode() == -14008
    Jun 29 15:27:20 117-farm-g5 /System/Library/CoreServices/mcxd.app/Contents/MacOS/mcxd: DSGetSearchPath(): DSGetLocallyHostedNodeNames() == -14956
    Jun 29 15:27:20 117-farm-g5 /System/Library/CoreServices/mcxd.app/Contents/MacOS/mcxd: DSGetCurrentConfigInfo(): DSGetSearchPath() == -14956
    Jun 29 15:27:20 117-farm-g5 /System/Library/CoreServices/mcxd.app/Contents/MacOS/mcxd: DSGetCacheInfo(): DSGetCurrentConfigInfo() == -14956
    Jun 29 15:27:20 117-farm-g5 /System/Library/CoreServices/mcxd.app/Contents/MacOS/mcxd: *** MCXD.getComputerInfo: Couldn’t get cache info -14956
    [/code]

    Any idea?

    #366760
    Flash
    Participant

    Yes, I am having the same problem. None of the prefs I’ve set for machine lists are being applied to the clients. I am seeing the exact same errors in the client logs. Prefs assigned by user or group work fine, but no prefs assigned by machine list are working. Machine list prefs worked fine earlier this summer. The only thing I’ve done to my server since then was the 10.4.7 update.

    Aug 5 14:20:03 US-Science-1 /System/Library/CoreServices/mcxd.app/Contents/MacOS/mcxd: DSGetLocallyHostedNodeNames(): dsFindDirNode() == -14008
    Aug 5 14:20:03 US-Science-1 /System/Library/CoreServices/mcxd.app/Contents/MacOS/mcxd: DSGetSearchPath(): DSGetLocallyHostedNodeNames() == -14956
    Aug 5 14:20:03 US-Science-1 /System/Library/CoreServices/mcxd.app/Contents/MacOS/mcxd: DSGetCurrentConfigInfo(): DSGetSearchPath() == -14956
    Aug 5 14:20:03 US-Science-1 /System/Library/CoreServices/mcxd.app/Contents/MacOS/mcxd: DSGetCacheInfo(): DSGetCurrentConfigInfo() == -14956
    Aug 5 14:20:03 US-Science-1 /System/Library/CoreServices/mcxd.app/Contents/MacOS/mcxd: *** MCXD.getComputerInfo: Couldn’t get cache info -14956

    #366761
    Flash
    Participant

    I found a workaround, at least in my case. I can only guess as to why this fixed my problem, but it did. When you configure the LDAP plugin in Directory Access, don’t “bind” the client. Merely create a new node, type in your server address, then hit Continue without providing diradmin credentials. Now, no more of the above startup errors and machine list prefs are working perfectly. This may be somewhat less secure. Note, computer records won’t automatically appear in WGM, but you can easily browse to them so they can be added to machine lists. Further, this method does not create a machine record in the server’s kadmin.local database (kerberos Db). I would assume that Kerberos authentication would not work because of this.

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

Comments are closed