Don't know anything about trillian, except that it's an IM program, and
from the web site says it let's one download all sorts of news, etc..
One possible cause of the symptoms you're seeing could be especially
heavy data traffic.
Is trillian downloading or uploading a bunch of data?
Is someone hacking computers that register with trillian? (I've seen
lots of extra traffic to my computer when I use AOL IM, so I don't use
AOL IM anymore, perhaps there's something similar going on with
trillian? Just speculation.)
To eliminate this as a possibility, try taking a look at the amount of
data being transferred with and without trillian running.
I hope this helps!
Greg
On Tue, 2003-03-18 at 07:24, Jon from Nova Wireless wrote:
> I couldn't possibly be the only one...
> is anyone else having all sorts of trouble with user having trillian
> running?
> I am experiencing extremely unstable links when users connect to trillian
> services.
> Perfect links (no packets lost for 24 hours) are suffering disassociation
> and packet loss as soon as users connect to trillian.
> other trillian users are unable to maintain a constant connection. the
> problem goes away as soon as trillian is closed. no trouble when the users
> use AOL IM client.
> really frustrating...
>
> here is a ping test while running trillian:
>
> Reply from 192.168.1.223: bytes=32 time=2ms TTL=64
> Reply from 192.168.1.223: bytes=32 time=4ms TTL=64
> Request timed out.
> Request timed out.
> Request timed out.
> Request timed out.
> Request timed out.
> Reply from 192.168.1.223: bytes=32 time=6ms TTL=64
> Reply from 192.168.1.223: bytes=32 time=2ms TTL=64
> Reply from 192.168.1.223: bytes=32 time=2ms TTL=64
> Reply from 192.168.1.223: bytes=32 time=2ms TTL=64
> Request timed out.
> Request timed out.
> Request timed out.
> Request timed out.
> Request timed out.
> Reply from 192.168.1.223: bytes=32 time=6ms TTL=64
> Reply from 192.168.1.223: bytes=32 time=2ms TTL=64
> Reply from 192.168.1.223: bytes=32 time=3ms TTL=64
> Reply from 192.168.1.223: bytes=32 time=2ms TTL=64
> Request timed out.
> Request timed out.
> Request timed out.
> Request timed out.
> Request timed out.
> Reply from 192.168.1.223: bytes=32 time=9ms TTL=64
> Reply from 192.168.1.223: bytes=32 time=3ms TTL=64
> Reply from 192.168.1.223: bytes=32 time=2ms TTL=64
> Reply from 192.168.1.223: bytes=32 time=2ms TTL=64
> Reply from 192.168.1.223: bytes=32 time=2ms TTL=64
> Request timed out.
> Request timed out.
> Request timed out.
> Request timed out.
> Request timed out.
> Reply from 192.168.1.223: bytes=32 time=5ms TTL=64
> Reply from 192.168.1.223: bytes=32 time=4ms TTL=64
> Reply from 192.168.1.223: bytes=32 time=5ms TTL=64
> Request timed out.
> Request timed out.
> Request timed out.
> Request timed out.
> Request timed out.
> Reply from 192.168.1.223: bytes=32 time=5ms TTL=64
> Request timed out.
> Request timed out.
> Request timed out.
> Request timed out.
> Request timed out.
> Reply from 192.168.1.223: bytes=32 time=7ms TTL=64
> Reply from 192.168.1.223: bytes=32 time=2ms TTL=64
> Reply from 192.168.1.223: bytes=32 time=2ms TTL=64
> Reply from 192.168.1.223: bytes=32 time=2ms TTL=64
> Reply from 192.168.1.223: bytes=32 time=2ms TTL=64
>
>
> and here is results when it is closed:
>
> Reply from 192.168.1.223: bytes=32 time=2ms TTL=64
> Reply from 192.168.1.223: bytes=32 time=4ms TTL=64
> Reply from 192.168.1.223: bytes=32 time=2ms TTL=64
> Reply from 192.168.1.223: bytes=32 time=3ms TTL=64
> Reply from 192.168.1.223: bytes=32 time=2ms TTL=64
> Reply from 192.168.1.223: bytes=32 time=3ms TTL=64
> Reply from 192.168.1.223: bytes=32 time=2ms TTL=64
> Reply from 192.168.1.223: bytes=32 time=3ms TTL=64
> Reply from 192.168.1.223: bytes=32 time=2ms TTL=64
> Reply from 192.168.1.223: bytes=32 time=2ms TTL=64
> Reply from 192.168.1.223: bytes=32 time=2ms TTL=64
> Reply from 192.168.1.223: bytes=32 time=4ms TTL=64
> Reply from 192.168.1.223: bytes=32 time=2ms TTL=64
> Reply from 192.168.1.223: bytes=32 time=2ms TTL=64
> Reply from 192.168.1.223: bytes=32 time=2ms TTL=64
> Reply from 192.168.1.223: bytes=32 time=36ms TTL=64
> Reply from 192.168.1.223: bytes=32 time=2ms TTL=64
> Reply from 192.168.1.223: bytes=32 time=2ms TTL=64
> Reply from 192.168.1.223: bytes=32 time=2ms TTL=64
> Reply from 192.168.1.223: bytes=32 time=2ms TTL=64
> Reply from 192.168.1.223: bytes=32 time=2ms TTL=64
> Reply from 192.168.1.223: bytes=32 time=2ms TTL=64
> Reply from 192.168.1.223: bytes=32 time=2ms TTL=64
> Reply from 192.168.1.223: bytes=32 time=3ms TTL=64
> Reply from 192.168.1.223: bytes=32 time=3ms TTL=64
> Reply from 192.168.1.223: bytes=32 time=4ms TTL=64
> Reply from 192.168.1.223: bytes=32 time=4ms TTL=64
> Reply from 192.168.1.223: bytes=32 time=2ms TTL=64
> Reply from 192.168.1.223: bytes=32 time=2ms TTL=64
> Reply from 192.168.1.223: bytes=32 time=3ms TTL=64
> Reply from 192.168.1.223: bytes=32 time=4ms TTL=64
> Reply from 192.168.1.223: bytes=32 time=3ms TTL=64
> Reply from 192.168.1.223: bytes=32 time=2ms TTL=64
> Reply from 192.168.1.223: bytes=32 time=3ms TTL=64
>
>
> perfect link, yes?
>
> what is going on here?
> any ideas?
>
>
> sorry about all the text...
>
> --
> general wireless list, a bawug thing <http://www.bawug.org/>
> [un]subscribe: http://lists.bawug.org/mailman/listinfo/wireless
--
general wireless list, a bawug thing <http://www.bawug.org/>
[un]subscribe: http://lists.bawug.org/mailman/listinfo/wireless
