So I'm not sure if this is the best place on the Internet to be posing this question, and I tried to use MS TechNet, but the UI was a disaster and I figured I'd try the easy route before the hard one.
The long and short of is is that a computer lab of 25 Macs recently upgraded to Mavericks take a few minutes to reconnect to our AD server to allow authentication to users. A Mac will wake, immediately display the "Network account unavailable" error, and won't allow logins for at least 2 minutes. This is problematic because I work at a school where no one is patient enough to wait that long (not that they should have to!), and I keep getting tickets about it. Its rather annoying to say the least, for everyone involved.
Does anyone here have any idea what could be going on? We don't use .local addresses for our AD servers. On older version of OS X this behavior also occurred but the delay was nowhere near as long, only a few seconds or so.
If anyone could reccommend a better place to ask this question, that would also be very helpful and appreciated. Thanks!
The long and short of is is that a computer lab of 25 Macs recently upgraded to Mavericks take a few minutes to reconnect to our AD server to allow authentication to users. A Mac will wake, immediately display the "Network account unavailable" error, and won't allow logins for at least 2 minutes. This is problematic because I work at a school where no one is patient enough to wait that long (not that they should have to!), and I keep getting tickets about it. Its rather annoying to say the least, for everyone involved.
Does anyone here have any idea what could be going on? We don't use .local addresses for our AD servers. On older version of OS X this behavior also occurred but the delay was nowhere near as long, only a few seconds or so.
If anyone could reccommend a better place to ask this question, that would also be very helpful and appreciated. Thanks!