hello, everyone. . . . .I did some searches on this in this forum, but didn't find anything that seemed to relate. if I've missed a resource here that would help me, i apologize in advance . . . . . .
Anyway, I'm working on binding some Mac's into an active directory domain running on windows 2k server.
Here's the story- when i first started trying to do this, I found that the windows servers did not have reverse DNS entries set up, so I was unable to bind. I had the active directory admin set up the reverse DNS, and I was able to bind 2 macs running 10.3.6. the next day, I tried to bind some more macs, and they would not bind- the Ad plug in in Directory Access gets up to step five, and then tells me i've supplied an incorrect username and password. Unfortunately, that's the correct username and password, and the same account info does successfully bind PC's to the same AD. I tried un-binding one of the Macs that I had already bound, changed it's name, and then tried to re-bind it, and got the same incorrect password error.
We are not using.local in the AD set up- it's a .com domain.
I know the macs are finding the domain controller and are able to read the AD, because if i try to bind one using the same name as the single mac that's still in there, it tells me that an account with that computer name already exists.
Also, the one mac that is still bound to the domain authenticates just fine and has no problems at all. argh.
i'm totally stumped. Why did it work for a couple of hours, and then NEVER work again?
Anyone have any ideas? i've spent over 6 hours on the phone with MS's corporate support over the last 2 days, and they just gave up and refunded my incident (!) . . . . .
thanks . . . .
elvisizer