windows-afsd-nat-handling-20070310

windows-afsd-nat-handling-20070310

Improve cache manager performance behind NATs:

 * drop cm_daemonCheckUpInterval from 10 minutes to 4 minutes to bring
   it under the minimum recommended default port mapping idle timeout
   value for NATs

 * when a timeout on an rx connection occurs, retry the request once
   after forcing a new rx connection.  If there was a NAT and the port
   mapping changed, the server would respond to the original addr:port
   associated with the rx connection.  Forcing a new connection will
   allow the request to be responded to if the server is accessible.

   This should eliminate the UP-DOWN-UP-DOWN bouncing that user's have
   seen when working from behind a NAT.