From: "John Beamish" 

If it's a batch file put this as the first line:

prompt $p $t $g

The prompt will become the path ($p) the time ($t) and a greater than
symbol ($g) that the command line prompt was displayed.

"Ellen K."  wrote in message
news:870lb05fp95guomiq8h4t222cnoq3o7jf9{at}4ax.com...
> That is a very good idea, I can make a one-line batch file and set it to
> start at 6:00 a.m. Tuesday because based on experience so far if a
> problem is gonna happen it will happen between 6:00 and 8:30.
>
> What would be even better would be to also record the time after each
> set of 4 pings, that way we could see what time it happens... because it
> seems to recover spontaneously.   Well, my shell scripting book is at
> the office, I can always try that for Wednesday if necessary.
>
> On Sun, 30 May 2004 18:09:45 -0400, "Geo."
 wrote in
> message :
>
> >"Ellen K."  wrote in message
> >news:ee2kb0p2tq0ba8oft24tajm0fmrssljdp7{at}4ax.com...
> >
> >> However, I don't think the 6509 is constantly rebooting because that
> >> would affect ALL the servers, and I've only had problems with one.
> >
> >Easy enough to tell, next time you start having connections dropped do
this
> >from the command line
> >
> >ping ipaddress_of_server -t > c:\temp.txt
> >
> >let that run while you are doing whatever you do and if the connection
drops
> >then terminate that window and go look at temp.txt to see if there were
> >timeouts. If you see timeouts it's a network issue of some sort and show
the
> >file to your network guy, if you don't see timeouts during the period the
> >connection drops then the network is probably fine and you can look
elsewhere.
> >
> >Geo.
> >
>

--- BBBS/NT v4.01 Flag-5