[inkswamp]

The one thing that jumps out at me that might be worth further investigation is this line:

“[email protected]@my.domain.com:389”

Should it be idenfying this user as user@domain@domain? Interestingly, this occurs right before the lines that appear to be a series of failures in the log. Is the “[email protected]” the network admin account you’re using to bind the machine? Any idea why it’s showing up with two domains like that?

[inkswamp]

> Wow, thanks for your replies. I didn’t know that a local user would conflict with a network
> user (I thought it will be an automatic transition somehow).

I wish it was automatic. It would have saved me a lot of time and trouble last year, but unfortunately, it doesn’t work that way.

> I just want to clarify one thing though. I am not using Open Directory at all and I am trying to
> set up a direct connection between AD plugin on Mac and AD on Widows 2003 server.
> Please stop me this is something the AD plugin is not meant for…

The AD plugin will work just fine binding the machine to AD on a Windows 2003 Server. I’m doing it myself and it works great.

[inkswamp]

The exact same thing is happening to me. The Leopard Macs aren’t showing the password expiration notice. The Tiger machines are showing them. I just filed my own bug report for this. It’s 100% consistent. Leopard shows nothing. Tiger does. These are Macs set up identically in every other respect and connected to the same network. Definitely some kind of bug going on there.

[inkswamp]

It sounds like you’re not understanding the difference between local accounts and network accounts. A local account doesn’t automatically become a network account just because the machine is bound to AD and the local account shares the same name as a network account.

I went through the process of converting two dozen Macs from using local accounts to network accounts last year. The users were all keeping their local user accounts in synch with the network accounts so I went through the process of converting the local user accounts over to the network accounts so I know what you’re trying to do.

You can move all the files in the local account to temporary, safe location, delete the local user account in the Accounts control panel, and then log in using your network credentials. That will create a user account with the same login name, but it will be a network account instead of local. Then you move all those files back over to the home folder, chown them to the network account and carry on like normal.

[Author]

Posts