Normally dialing in and getting a connect is something I [now] take for
granted. But recently there have been problems with my ISP's primary
router, and it takes time to get a new unit in and get it ready to run
parallel for testing prior to bringing down the old one for repair and
who knows what all else [can you say "steel toed boots" ??]
Thus, I am sometimes having to abort current dial -- because when the
router isn't working it sends out a VERY loud tone that hurts my ears,
and I don't want to wait for Arachne to give up and recycle.
The "try again" page always comes up, as it should.
But if I allow Arachne to proceed on its own I can't initialize modem
because Arachne doesn't "hang up the phone"; even more aggravating, when
I give the ALT-H command Arachne *says* it is terminating dial-in
connection, but it doesn't. It most often requires 3 tries before I can
get phone line hung up, initialize modem, and try again. <sigh>
There is another problem I've been having with b2 & SR. It involves
SMTP & POP3. I'd say more than 1/3 of the attempts to download & send
mail result in an ABORT message from Arachne. At first it was just with
POP3, and I found that clicking on the "recycle" button would start the
download again ... and I thought the problem was with ISP the first
few occurences. Well after the last big problem I discovered that the
original problems I was having wasn't with ISP, it was with Arachne --
because when I'd go back to download the previously RETR messages had
been deleted, which means the POP3 server had received a QUIT. A couple
of days ago there *was* problems with ISP, and when I got back on the
POP3 retrieval started back at first message and downloaded from
scratch, which means no QUIT was received from Arachne. That was with
b1 & b2
Now there have been similar problems with SMTP, while using 60SR. I get
abort messages on uploads, prior to any files moving at all, hit the
"recycle arrows" and finally get a connect to SMTP and upload messages.
Third problem I've been having is in acquiring DNS. Sites I know exist,
or know *should* exist, can't be found after hunting numeric long enough
to cause Arachne to put the "I give up, it ain't there" message screen
from Arachne.
Is it strictly coincidence that I'm also finding Arachne "sleeping" on
me again? Or appearing to sleep on me?
Or can *everything* be blamed on the ISP? That's shouldn't be, should
it, since once I'm connected to the www and retrieving links, is ISP
hardware/software that involved??
I dunno ... anyone having *anything* similar that you've been marking
off to "weird" or "something wrong with ISP" or "dratted net messed up
again" ???
l.d.
-- Arachne V1.60, NON-COMMERCIAL copy, http://arachne.cz/
