{#} Replies are directed back to [EMAIL PROTECTED]
{#} To reply to the author, write to Andrew Chisholm <[EMAIL PROTECTED]>
>> Could that be part of the problem? Just asking.
>
> Well, yes and no. Yes, in that it's a different server than what AOL's
> client uses. No, in that the problem lies solely with the server we're
> trying to talk to; that it's not the same server AOL uses is coincidental,
> unless they don't take as good care of the lowly public server. *sniff*
>
>> As I say, the problem I've experienced (with AIM) is rare. Maybe it happens
>> once every two months or so. but when it does happen gees it's annoying.
>
> Has it happened recently? I recently checked a change in which has Fire
> wait for a few seconds before reconnecting. I was hoping that would
> alleviate the situation you're describing.
I experienced the same problem on two different days at home, using v0.29b.
It happened about two weeks ago. Thinking from outside the box, thought it
was due to using a cable modem with 1 IP address and having DHCP router
connected to it to server a few other computers. Had two computers connected
to AIM, and when adding the third (with Fire) the denied message kept
appearing. I also changed settings to not connect automatically. Seemed like
it was trying to connect too soon when waking up from sleep, almost as if
the rest of the network services were not available yet. Again, I think
completely outside the box, so most of this might not make any sense.
Andrew
{#} ----------------------------------------------------+[ fire ]+---
