{#} Replies are directed back to [EMAIL PROTECTED]
{#} To reply to the author, write to Alex Taylor <[EMAIL PROTECTED]>
Something else to add about Fire. Whether my connection is via cable
modem, or wireless network at the University (not behind a firewall) or
on a part of the wired University LAN that is not behind a firewall, it
acts the same. I haven't tried with dial up.
On Wednesday, January 16, 2002, at 07:45 AM, denni9800 wrote:
> {#} Replies are directed back to [EMAIL PROTECTED]
> {#} To reply to the author, write to "denni9800" <[EMAIL PROTECTED]>
>
> my friend is not behind a firewall. she's got a regular
> cable modem and cable service by the same cable company as i
> have mine thru. so our connections are the same.
>
>
> On Wed, 16 Jan 2002 07:44:14 -0800
> Gregory Lincoln <[EMAIL PROTECTED]> wrote:
>> {#} Replies are directed back to [EMAIL PROTECTED]
>> {#} To reply to the author, write to Gregory Lincoln
>> <[EMAIL PROTECTED]>
>>
>> I have a very similar problem with a friend of mine.
>> She's the only one I
>> have constant trouble with.
>>
>> It'll be fine, then it just fails and freezes. I sent a
>> sample to Eric a
>> month or so ago, and he said it looked like Fire was
>> awaiting a response
>> from MSN, and never gets it.
>>
>> If there is a variable I am aware of, that perhaps you
>> might check with your
>> friend, is if they are behind a proxy or firewall. I was
>> in my friends
>> office trying to figure out what she's got going there,
>> and found their
>> office connection is 100% routed through MS Proxy server.
>> I'm not terribly
>> familiar with it, but all traffic on every open port is
>> routed through that
>> POS. Needless to say, that's why she's now unable to run
>> Fire or even email
>> through her brand new shiny 14" iBook. Setting up SOCKS
>> routing doesn't seem
>> to work.
>>
>> Anyhow, that was the nature of my last message, on
>> whether anyone has gotten
>> fire working behind that hunk-of-junk.
>>
>> Maybe check with the buddy you have issues with and see
>> if they have such a
>> convoluted proxy/firewall setup. Could be inherent.
>>
>> I look forward to hearing more about this. I wouldn't
>> pull so much hair out
>> if I could fix this.
>>
>>> so this problem happens with one person. and it happens
>> on
>>> different occasions. it has happened with a first IM.
>> it's
>>> happened with a third one. it happens with the same
>> person.
>>> this person might have an old version of MSN i'm gunna
>> look
>>> into that.
>>
>>
>> {#} ----------------------------------------------------+[
>> fire ]+---
>>
>>
>
>
> {#} ----------------------------------------------------+[ fire ]+---
>
>
>
{#} ----------------------------------------------------+[ fire ]+---
