On 11 Feb 2007 22:48:04 -0800, in alt.internet.wireless , "Alan"
<agarny@gmail.com> wrote:

>> >I have tried to use both Windows XPwirelesscontrol and Access
>> >Connections. In both cases, I got the same result: loss of connection.
>> Sorry, but I have no idea what "loss of connection" _exactly_ means.
>> Please stick to specific things, as Mark and I have suggested.
>
>Can't you accept that by 'loss of connection' I mean that the icon has
>a red cross, that I have more often than not 'limited connection',

The difficulty for John and I is that Windows uses this tiny
notification to mean a large number of very different things.
Apparently Microsoft thought it would confuse users to actually tell
them the precise problem. So the red X by itself doesn't really tell
you very much.

>that I cannot browse the internet, cannot receive/send emails, cannot
>ping anything, etc.? Do I have to spell it out every single time?

Each time, you are trying something new. Perhaps we fixed one problem
and so something has changed about precisely how you cannot connect.
Therefore its useful to be as descriptive as possible each time.

>> Both together add enough load of a given kind that the router falls over
>> and dies. I think your best bet is to try a different router.
>
>You are not answering my question.

The answer is that possibly your router cannot take the load of two
laptops. This probably means the router is defective, and you need to
try a different unit.

An example: A couple of years ago, I had a problem where my laptop
randomly lost wireless connectivity. I discovered that it happened
whenever anyone tried to use the printserver built into the router -
the router was rebooting occasionally. With a different router a few
years before that, it all worked fine except if I did a lot of
downloading. Then the router crashed.

>So, what kind of non-
>Internet related load could get my two ThinkPads to lose their
>connection?

The common factor is that both Thinkpads connect to the router and
negotiate access to the internet through it. So try a different
router....

--
Mark McIntyre