3 ms·
your Windows clients are probably using NTLM (or NTLMv2), Microsoft's old, terrible auth protocol that the Windows team eventually abandoned for Kerberos. ther
by vogonj 15y ago
your Windows clients are probably using NTLM (or NTLMv2), Microsoft's old, terrible auth protocol that the Windows team eventually abandoned for Kerberos. there are policy settings you can change to force Kerberos; I'd suggest Googling to see if you can find them, and see if it breaks your Windows clients as bad as your OS X clients seem to be.
- X-Istence 15y agoI had not thought about that, would OS X fall back to using that in case Kerberos doesn't function? Thanks for the suggestion!
- vogonj 15y agoquite possibly. I'm not terribly familiar with Kerberos as a protocol, but I know I've definitely seen Kerberos login misbehave in a way that caused it to take multiple minutes and then time out. anyway, hope you figure out the problem. :)
- w1nk 15y agoYou should also check the clocks on all the machines involved. Kerberos is quite finicky when the time between machines starts drifting.