Have a cronjob go off Sunday morning at 3:00 that pings
every machine on the hub in sequence? Or have each machine
ping a couple of others at about the time... a bit of traffic
all of a sudden, but no problem. You might even want to have
some "liveness" test done nightly, and have it email you
(or beep, or whatever) if a machine is unexpectedly down.
That would best be coordinated by a particular machine.
Of course, if all it takes is ANY traffic, you could also
set up xntp... have one machine act as a time server, the others
would sync to it, always a nice thing and the benefit is that
it would keep your ports alive and active :)
Just a thought....
Bill Ward
-----Original Message-----
From: linda hanigan [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, February 22, 2000 12:44 AM
To: [EMAIL PROTECTED]
Cc: recipient.list.not.shown; @nswcphdn.navy.mil
Subject: hub connection dies over weekend
Hi,
I am having a small problem with my network. Almost
every Monday morning they call to tell me they can not
connect to some machine on the network. I think the
hub is shutting down the port after a long period of
inactivity. I can plug it in to an empty port and it
works
but to get the original port to work I have to unplug
the
hub and plug it back in. If I have to work over the
weekend
so I log on and telnet between machines it is still
working on monday. Any ideas on how to solve this
minor annoyance besides working every weekend?
Linda
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.