Currently Being ModeratedFeb 18, 2011 8:53 AM (in response to Marc Monaro)COME ON! You've got to be kidding me?
NO ONE HAS EVER EXPERIENCED THIS ERROR?!?
Here, I'll rephrase it...
How do you fix the dreaded, 'INVALID USERNAME AND PASSWORD COMBINATION' when trying to bind a 10.6.6 Mac to Active Directory when you know the username and password are correct?
Thanks!Mac Pro, Mac OS X (10.6.6), Active Directory on the Mac *****!!! It always has...
Currently Being ModeratedFeb 18, 2011 11:36 AM (in response to Marc Monaro)See Special Report- Active Directory Issues with Mac OS X Leopard. Also do a Google search where I found quite a number of links to discussions some of which offered possible solutions.Mac Pro 2.66 Ghz; MBP Unibody; MBP C2D 2.33 Ghz; 11" MBA, Mac OS X (10.6.5), iMac C2D 17"; MB 2.0 Ghz; iPad 32G; 80GB iPod Video; iPod Touch; iPod Nano 2GB
Currently Being ModeratedFeb 18, 2011 2:48 PM (in response to Marc Monaro)Ultimately, sounds like something for MS to resolve.27" iMac i7 12 GB RAM, Mac OS X (10.6.6), G4 450 MP GB 1.5 GB RAM w/(10.5.8/10.4.11/9.2.2)
Currently Being ModeratedApr 1, 2011 10:28 AM (in response to baltwo)Why is that always any Apple support person or Mac users answer? It's a Microsoft problem. How can it be, I have 20 macs connected to the same network. The mac having the problem has been successfully working for 3 months. It started shaking when the user came in and in the troubleshooting process we removed it and are trying to rejoin it backl on to a domain it has been working on for months and 19 other machines are still working on. How is this a microsoft problem? Please enlightne me? If it sounds like I am frustrated, I apologize, but I AM!Mac OS X (10.6.7)
Currently Being ModeratedApr 1, 2011 10:55 AM (in response to NoMacs)By the way, if you come across this problem, run the following commands at a console prompt (terminal).
sudo rm -rdfv /Library/Preferences/DirectoryService
sudo rm -rdfv /var/db/dslocal/nodes/Default/config
sudo killall DirectoryService
Then try to Rebind client.
This fixed it for me and I didn't have to do anything to my AD Microsoft server.Mac OS X (10.6.7)
Currently Being ModeratedApr 13, 2011 7:17 AM (in response to NoMacs)NoMacs, I didn't get a chance to try this.
In the end, I had to reinstall the system from disc.
From 10.6.6 back down to 10.6.4. Once I did that, i was able to bind.
Upgraded back to 10.6.6 and now 10.6.7, and so far so good.
If and when this happens again, I'll definitely try your little fix.
Thanks a bunch!Mac Pro, Mac OS X (10.6.7)
Currently Being ModeratedApr 13, 2011 2:50 PM (in response to NoMacs)Thanks NoMacs, resolved my issue.MacPro, Mac OS X (10.6.7)
Currently Being ModeratedMay 25, 2011 3:12 AM (in response to NoMacs)
This worked for me many thanks for the tip... I look after 400 + students and staff this has just started happening on some of our 10.6.7 clients.
Univeirsity of Gloucestershire
Currently Being ModeratedJun 16, 2011 6:47 AM (in response to Marc Monaro)
Just as an aside, if this crops up again, boot into Single User Mode and type in the date command to make sure the date and time are within five minutes of server time. If the time drift is outside five minutes, active directory won't authenticate. You can enter date hhmm in 24 hour format (3:14 pm would be 1514) to reset it.
Currently Being ModeratedSep 27, 2011 11:19 AM (in response to Marc Monaro)
The problem has been solved by running the commands on a 10.6.7 client.
Currently Being ModeratedFeb 1, 2012 9:03 AM (in response to Marc Monaro)
NoMacs, thank you so much, this worked perfect. We are a school and have over 600 client machines about 50 of them Macs. We use a Windows 2008 Active Directory environment. Never had this problem before until today. A teacher brought me a macbook that would not login. All that I read online was that it was a MS issue, I knew that it had to be the machine because everything else including the other mac machines where fine.
Thank you for clearing this up.
Currently Being ModeratedMar 5, 2012 8:14 PM (in response to NoMacs)
NoMacs, this worked like a charm. Sat for several hours pulling my hair out trying to fix this and your terminal commands did the job. Thanks so much!