From: rick.jones2@hp.com   
      
   Jorgen Grahn  wrote:   
   > On Wed, 2009-10-07, Pascal Hambourg wrote:   
   > > Hello,   
   > >   
   > > Jorgen Grahn a ?crit :   
   > >> On Mon, 2009-10-05, vikas wrote:   
   > >>>   
   > >>>    How to make Windows Netmeeing send Keepalives every minute.   
   > > [...]   
   > >> (BTW, "Keepalive" is an ambiguous term.  There's TCP keepalives and   
   > >> protocol-specific keepalives.)   
   > >   
   > > IIRC the recommended minimum period for TCP keepalive is 2 hours, so I   
   > > don't think this is what the OP is looking for.   
      
   > But "I want insane amounts of TCP keepalives!" is a common request,   
   > so I didn't want to rule out the possibility ...   
      
   ... and all but the most fanatically adhereing to RFC "SHOULD" stacks   
   allow tweaking the length of time before TCP keepalives start on an   
   idle connection.   
      
   Still, it is best to have applications send their own keepalives -   
   when "successful" they actually show the remote application is around   
   and kicking rather than just the remote TCP endpoint.   
      
   rick jones   
   --   
   I don't interest myself in "why." I think more often in terms of   
   "when," sometimes "where;" always "how much."  - Joubert   
   these opinions are mine, all mine; HP might not want them anyway... :)   
   feel free to post, OR email to rick.jones2 in hp.com but NOT BOTH...   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)