Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the '10.5: A possible fix for Active Directory integration issues' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
10.5: A possible fix for Active Directory integration issues
Authored by: redclawx on Aug 14, '08 01:26:45PM

I have been having the same problem with computers becoming unresponsive when the authentication dialog came up. The computers are bound to AD. The odd part was, this only occurred when the computer was attempting to authenticate across any other network than the one that could communicate with the Active Directory Controller. For instance, the problem would arise when the computer would be connected to a wireless network and not a wired network. The screen saver would be password protected, so coming out would invoke the authentication window. When the user attempted to authenticate the computer would often times delay so long that authentication never occurred and the system went back to the screen saver.
According to Apple this is a known issue. The Apple Engineers are working on a fix for it. I do not know the time line for this fix. Of course, we didn't know about this being a known issue until after we had paid Apple for the extra support. We had to pay Apple because because according to them this problem was not covered under the standard AppleCare 3-year protection plan. Fortunately we were able to get a refund once we found out that this was a known issue.



[ Reply to This | # ]
10.5: A possible fix for Active Directory integration issues
Authored by: Jaharmi on Jan 30, '09 07:44:18AM

Since you didn't specify, are these problems with Mac OS X 10.4 or 10.5 or both?

Under certain circumstances, Mac OS X 10.4 can become unresponsive and not fail over to a locally-cached Active Directory mobile account when the Active Directory domain controllers are "reachable" (i.e. their names can be resolved by DNS through your current network connection) but traffic to them is blocked (perhaps by a border firewall between your current network connection and your organization's).



[ Reply to This | # ]