<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Dear Jason and David,<div>I have the same problem, of course my JSS is a private network, but still the same issue.</div><div><br></div><div>My main problem is that I deployed this on all the laptops inhouse, and they use them all around the world and home for work.</div><div><br></div><div>I have think of 2 solutions</div><div><br></div><div>1- Reduce the amount of time JSS takes to contact the server. Do anybody knows how to do this?</div><div>2- Create an logout and login script hook to disable/enable network ports. Have you something like this?</div><div> I will try to focus on this before next week or ask the people from JSS at the WWDC</div><div><br></div><div>cheers and many thanks</div><div>carmelo</div><div><br><div><div>On Jun 3, 2009, at 9:34 PM, David Chitwood wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div> <font face="Verdana, Helvetica, Arial"><span style="font-size:10pt">Hi Jason,<br> <br> 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.<br> <br> You can quickly check to see if this is happening to your users by having them run a traceroute in Terminal (traceroute <i>yourJSSserver.mayo.edu</i>) 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.<br> <br> Good luck!<br> <br> David</span></font> <br> ______________________________________________________________________<br> <br> 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.<br> </div> _______________________________________________<br>Casper mailing list<br><a href="mailto:Casper@list.jamfsoftware.com">Casper@list.jamfsoftware.com</a><br>http://list.jamfsoftware.com/mailman/listinfo/casper<br></blockquote></div><br><div apple-content-edited="true"> <span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>Carmelo Lopez Portilla</div><div><br></div><div>ITS EMBL Heidelberg</div><div><span class="Apple-style-span" style="font-family: Arial; font-size: 13px; ">Tel. +49 (0) 6221 387 8444<br>Fax +49 (0) 6221 387 8517</span></div><div>email: <a href="mailto:lopez@embl.de">lopez@embl.de</a></div><div><br></div></div></span><br class="Apple-interchange-newline"> </div><br></div></body></html>