This is a discussion group - attached files are a no-no.
In any case, there are a great many free programs that do this without
having to take the performance hit of having a DOS window devoted to
the task. A more useful solution is to use a time client that resets
your system clock to correct time from a primary or secondary time
standard site every few minutes. Not only does that keep your
connection open, but it keeps your system clock running more
accurately.
T.E.D. (tda...@gearbox.maem.umr.edu - e-mail must contain "batch" in the subject or my .sig in the body)
Ted Davis wrote:
> On Sun, 6 Feb 2000 07:17:23 -0600, "Matthew Brewer"
> ?mjbr...@warpnet.net? wrote:
>
> ?This batch file pings yahoo.com every ten minutes to keep your internet
> ?connection alive.
> ?
> ?
>
> This is a discussion group - attached files are a no-no.
>
> In any case, there are a great many free programs that do this without
> having to take the performance hit of having a DOS window devoted to
> the task. A more useful solution is to use a time client that resets
> your system clock to correct time from a primary or secondary time
> standard site every few minutes. Not only does that keep your
> connection open, but it keeps your system clock running more
> accurately.
>
> T.E.D. (tda...@gearbox.maem.umr.edu - e-mail must contain "batch" in the subject or my .sig in the body)
Besides the issue of what happens if a million people start using a ping
utility as a keep alive, all at the same time, all pointed toward the same
happless site. Could have the same effect as a denial of service attack,
and would be frowned upon. A better alternative ping target, that is if
you want to use such a thing, would be to do an IPCONFIG to obtain
the address of the remote gateway, i.e., if you are on a line with dynamic
addressing as most are. You then ping that in a timing loop, that way
you only generate traffic between your machine and you ISP, rather than
adding to the gridlock on the information highway. Now the challenge
then is to create a batch file that does something like:
IPCONFIG > CONNECT.BAT
REM OBTAIN REMOTE IP
. . . blah . . . blah . . .
:WAIT
SLEEP 300
PING %IP%
GOTO WAIT
Last time I checked, ICQ generates enough background fluff to keep
a connection alive . . .
Other thoughts: my suggestion to use a time client is subject to the
same denial of service problem as pinging a single server. In my case
it's not an issue because the firewall stops time requests to outside
servers - only the secondary erver provided by my ISP is accessible.
Ping or time clients should be directed to the most local suitable
system.