[Casper] Slow to shutdown when not connect to internal network.

[David Chitwood]

Hi Jason,

I was plagued with the same issue and would hear about it from some of our
users sporadically.  I had the same log msgs you list.  After working with
JAMF support, we discovered that the issue was with my ISP.  In my case, the
problem was that my provider routes unresolvable domain requests to their
own custom search page.  When the JSS task would try to run at logout, it
would look for our internal server, my ISP would see it was unresolvable and
route it through a slew of hops and land on their domain server.  The JSS
task, not receiving instructions, would wait for roughly one minute before
finally giving up.  My ISP provides alternate ³opt-out² DNS servers, so I
popped those in my Network settings and voila! all good.

You can quickly check to see if this is happening to your users by having
them run a traceroute in Terminal (traceroute yourJSSserver.mayo.edu) or
Network Utility from their outside networks.  If it doesn¹t die immediately
and looks like it is trying to resolve it, then they may be having the same
issue.  If so, a quick workaround (while you search for a more permanent
fix) is to have them turn off their network connections before logging
out/shutting down.

Good luck!

David

______________________________________________________________________

This email (including any attachments) may contain confidential and/or privileged information. Any unauthorized distribution, copying or disclosure is prohibited. If you are not the intended recipient, please notify the sender immediately and permanently delete this email and any attachments. Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://list.jamfsoftware.com/pipermail/casper/attachments/20090603/7214999c/attachment.htm