Kevin Oberman wrote:
> The problem is that the Airport died. Looks like a power supply issue
> or a bad cap as it fails whenever it's moving lots of data and then
> recovers after several quite seconds. My wife's laptop link dies at
> the same time, so that's why I bought the Linksys. (Sorry for saying
> D-Link. I get them confused too often.)
> No. I am monitoring signal strength and it is excellent. I use a
> static address and gateway and they're fine, too. Both 'arp -a' and
> 'netstat -rnf inet' show what I would expect including the proper MAC
> address for the firewall and the hub.
> I've been using this card for about a year and a half and this problem
> has just shown up in the past few weeks.

Sorry to hear of the death of your Airport, since it seems to
have worked up to now; it might not be the Airport, and it may
be something else.

There's a lot of possible causes; one is if you live in an
apartment, and someone recently bought a wireless video setup, a
camera with a set top box, a spread-spectrum cordless phone, or
installed their own Airport/DLink/Linksys/whatever.

If it's the same type of equipment, it's likely to have the
same numbers assigned, which would mean a lot of confusion for
your hardware.

Someone nearby might be leeching a connection off you.

Another possibility is location of the Linksys box; some spots
are just a bad location for an access point, and relocating it
might make it "just work".

The best thing to try would be to boot up Windows and use the
Windows tools to try to find out if there's anything out there
in your same band.  You may also want to make sure that you
have enabled what little encryption these things normally have,
to do what you can to avoid a leech.

Other than that, it may be time to get someone with the right
equipment to come over and see if they can find any RF issues.

Good luck...

-- Terry
[EMAIL PROTECTED] mailing list
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Reply via email to