Hello,

I've noticed that when a client either jumps off the network or has a
firewall installed that blocked server scheduled sessions, a message is
logged every 4 minutes during the schedule window stating it could not
connect to the client:

Mon Nov  6 06:01:11 2006 ANR8210E Unable to establish TCP/IP session with <IP 
address> - connection request timed out.
Mon Nov  6 06:04:50 2006 ANR8210E Unable to establish TCP/IP session with <IP 
address> - connection request timed out.
Mon Nov  6 06:08:29 2006 ANR8210E Unable to establish TCP/IP session with <IP 
address> - connection request timed out.
Mon Nov  6 06:12:08 2006 ANR8210E Unable to establish TCP/IP session with <IP 
address> - connection request timed out.
Mon Nov  6 06:15:47 2006 ANR8210E Unable to establish TCP/IP session with <IP 
address> - connection request timed out.
Mon Nov  6 06:19:26 2006 ANR8210E Unable to establish TCP/IP session with <IP 
address> - connection request timed out.
Mon Nov  6 06:23:05 2006 ANR8210E Unable to establish TCP/IP session with <IP 
address> - connection request timed out.

I anticipate this could happen quite a bit for a number of clients (where
I want them in a schedule in case they happen to be available, but if they
aren't I'm not going to worry too much.)  Is there a way to adjust this
level of logging?  Say, 10 clients during a 12 hour schedule window
spitting out log messages every 3-4 minutes is a lot of static in the logs
and reports.  Ideas?

Dave