CAJensen

I've tried this script as well as setting the mDNS interval to 10s as per apple's article, neither worked. Still get users who start up and have the 'domain not responding' show up. Although I didn't read too deeply, and as we have local accounts under the 'administrator' name, that could be the culprit. I'll give it another whirl looking up a different AD account, and report back. I was also interested in the logging. I have the script setup with the proper permissions to run at startup, and I don't see any notifications in the console that it is having any issues running, but a log file is not being produced. Is there a permissions change that needs to be applied in order for this to work, or perhaps I just did something incorrectly? Thanks

I'm taking it back. Had the issue occur this morning with a user. No indications of why, as usual. Just unbound and rebound to the domain.

As a follow-up, I haven't seen the issue plague any of our machines since implementing this script. Obviously not sure whether no users have lost their connection with the domain, or whether the script is doing it's job. But given the duration since implementation, it's quite possible that it's resolving the problem. Thanks again.

Thanks, Eph. We experience a similar issue, but have an actual domain. Logging in generally works fine for most of our users, but maybe twice a week I get a user who cannot login. Upon logging in under a locadmin account, the domain status reports as 'not responding'. I then have to simply rebind. Would pointing your script at our domain and setting it to run at login likely resolve this issue? If I don't see a response, I'll certainly be testing it. Thanks again for the work.

That's kind of disappointing you rolled back. I was hoping for a solution. Been having the same issues, although not as often with my 10.6.x (now 4) clients. They remain bound for X amount of days, but at random (usually 2 machines a week or so) will just report that the AD domain is no longer responding.