opendirectorysam.so error

[Spectrum]

I’m trying to create a two way domain trust between an XServe (domain “mac”) and a Windows NT4 style domain (domain “lab”).

I created a machine account lab$ in WGM as articles suggest.

[code:1:199ca668a0]net rpc trustdom establish lab [/code:1:199ca668a0]

worked fine though the trust itself doesn’t work.

[code:1:199ca668a0]smbpasswd +a +i lab[/code:1:199ca668a0]

yields:

[code:1:199ca668a0]/etc/pdb/opendirectorysam.so undefined reference to _get_opendirectory_authenticator expected to be defined in the executeable. Trace/BPT trap[/code:1:199ca668a0]

Anyone know of a fix for this issue?

[Spectrum]

Yes, I ultimately came to that conclusion after a 6 week run-around with Apple. So much for that 80k that Apple was going to get from us.

I’m just a little bit more than annoyed that Apple strung me out that long apparently hoping that I wasn’t going to try a proof of concept lab test.

As to why they decided to break basic functionality of Samba for their custom build, only they know. Hard to fathom that they tout the ability to seamlessly integrate with NT style domains when they simply can’t (or, probably, more aptly, chose not to do so).

IMO, until they come clean and either:

a.) Create a “Unified Messaging” solution on the OSXS platform and change the current line of thought on seamless migration (which they broke most of in their Samba build as well)

or

b.) allow domain trusts to occur to allow existing NT domains the ability to import existing userbase info for authentication to utilize Microsoft (or others) Unified Messaging solutions

they will not be accepted widely in the mainstream corporate sector.

Quite honestly, I don’t think that my organization does anything extreme in the arena of technology. Too bad that Apple can’t support it.

My thoughts on Apple after about 3.5 months:

1. Great hardware, maybe the best there is.

2. Server platform fine for homogenous clients. Mediocre at best for heterogenous clients.

3. Community: Snobbish and aloof – generally unwilling to take a few minutes to help. (Sorry, but that’s how it has played out in my scenario)

Too bad, because I really wanted to make this work, but, alas, it never will until Apple changes their tune.

[Spectrum]

Thanks for the reply Joel.

I guess I’m just venting some frustration over about 350 hours of lab work at about 60-70 hours a week.

My problem stems from the fact that I need to maintain Exchange 5.5 for a legacy voice mail product. (since it has no upgrade path and there’s nothing out there for the OSX platform)

Without either a method to export the existing users + their NT SIDS (required to access exchange mailboxes) or another solution that is OSXS native, I’m basically hosed.

I looked at both Firstclass and at Kerio. Neither can do what I need and there are some other wierdo things about them as well.

Firstclass license fees make M$ look inexpensive. $80k for 100 users. The interface looks like it was written for DOS 3.1, no vmail support and no support for Blackberry.

Weirdest thing: all email (both inbound and outgoing) threaded in a single mailbox. Makes it quite interesting to sort through your mailbox looking for a message.

Kerio is much more attractive from a price standpoint, but, no vmail support, no public folders and no Blackberry support.

Weirdest thing: Issuing a beta with no dev contact, no feedback from beta users, no beta forums and no support at all (even to install) for the beta.

[Author]

Posts