[woody]

macshome, thanks for your reply.

We have tested different possible solutions now and there is none.

It seems to be a bug in MacOSX Server. They tested with an older version of 10.4 and did an upgrade to 10.4.6 step by step. The system worked until the update to 10.4.6. (7?).
It seems to be an issue with some special apps generating wrong permissions while saving. Because that should be a task of the OS, I guess it must be a bug in the Carbon-API in context with apps that create an new file and delete the old one, instead of overriding the existing files while saving,

The problem here was the Intel-MacPro that wouldn’t run on older Systems, so they now working with a PPC-Mac.

[woody]

There has changed a lot in the last year, especially with 10.3.5.

I figured out some steps, but at the end I run into an error that may depend on other reasons. Maybe others are interested and can check that too.
The first you need for an Trust (oneway – NT trusts MacOSX) is a machine account with a password for the trust and the interdomain-flag [I] on the MacOSX-Server.

In 10.3.5(!) there is a path to a new binary added to the smb.conf.

add machine script = /usr/bin/opendirectorypdbconfig -c create_computer_account -r %u -n “/LDAPv3/127.0.0.
1″

This programm has no manpage and is IMHO undocumented, but if you call it without any parms, it will give some help.
So I played a bit and added a machine account including a password with this tool. The option -p is not documented for machine accounts, but it works.

I used:
opendirectorypdbconfig -c create_computer_account -r TrustingDomainname$ -p password -n “/LDAPv3/127.0.0.
1″

(The TrustingDomainname must be written in capital letters and must be followed by a “$” for machine account)

Then you have to change the [W]-flag in the account to [I]. The easiest way to that may be the detailed view in the WGM.

After that you can open the User Manager for Domains and add the trust in the Policies Menu. Type in the name of the MacOSX
Domain and the password you provided.

After that you should get an “domain relationship successfully established” message.

In my case I got this message but it didn’t work after all. That may depend on that lack of an clean WINS-Server installation. Both Server must use the same WINS-Server, otherwise it will not work.
Happily the old NT-Server is aged, misconfigured and faulty. I can’t change the WINS-Server at time.

Maybe others have more luck with this.

[woody]

I think it’s easier to repair the repaired permissions:

# cd /usr/lib/sasl2/
# sudo chgrp 6 pwauxprop.*
# sudo chmod 705 pwauxprop.*

The process should work again after that.

[woody]

I think the frontpage would be a nice place.
The BBS is ok, for asking questions and getting hints. The frontpage could be a place for known issues and known solutions.

[woody]

I have done some more testing now. My first idea, that the reason was the 10.3.4 Comboupdate seems to be wrong.
I made an upgrade to 10.3.4 now in my testing environment and there are no problems in creating machine accounts for NT4 clients.
Maybe it¥s the security update, that¥s offered by apple after the upgrade.

[woody]

[quote=”Ao”] … Also, we have about 15 users who log into a Windows NT4 PDC computer, and I need to either migrate them, migrate their application settings, or start completely clean. ….[/quote]

I`m doing just a similar job here and we had trouble with the upgrade to 10.3.4.
I have had trouble to add the machine accounts for NT4 (Servicepack6a) Clients to the samba PDC (OD Master, Windows-Computerlists). XP-Clients worked without any problems.
I`ve made a clean install with 10.3.3 and now it works fine. Seems to be a problem with the last update. I contacted AppleSupport and they promised an answer until next week. So be careful with the update.

[woody]

Same problem here, but only when transferring files from client to server.
The other way, transferring files from server to client is working with normal speed.

[Author]

Posts