- Linksys wireless network SUCKS!
- Posted by mfell2112*NOSPAM*@yahoo.com on January 20th, 2004
From day one I could never access my downstairs machine. I just
spent two hours on the phone with Linksys tech support.The verdict?
They are emailing me new drivers for my 54g wireless network card. I
am surprised they did not tell me to reformat my hard drive. I am
haveing a hard time believeing new drivers are going to solve my
problem. I have too much time with this Linksys garbage. I should
have gone with the Microsoft wireless network. Considering I despise
MS that is really saying something. Sorry I just had to vent and
trash Linksys in the process.
Mike
- Posted by daytripper on January 20th, 2004
On Tue, 20 Jan 2004 03:56:43 GMT, mfell2112*NOSPAM*@yahoo.com wrote:
This sounds familiar. Two years ago this May I had intractable problems with a
new Linksys' wireless A wap and pccard on Win2K, was fortunate enough to
exchange them for Netgear, zero problems, works sweet, on 2K and XP Pro as
well.
It was clearly a driver problem with the nic. Maybe you'll get lucky...
/daytripper
- Posted by mfell2112*NOSPAM*@yahoo.com on January 20th, 2004
On Tue, 20 Jan 2004 04:10:32 GMT, daytripper
<day_trippr@REMOVEyahoo.com> wrote:
I hope so but, I have a feeling this is not going to work. Looking at
the instructions they made it look easy. I would love to get rid of
this although I have had it for a year or so. It never work right
from day one. Then when you call Linksys support it takes 40 mintues
to get a tech. All in all this has been a very bad expirence for me.
BTW, The router sucks as well.
Mike
- Posted by daytripper on January 21st, 2004
On Wed, 21 Jan 2004 17:04:45 GMT, rogblake10@iname10.com (Roger Blake) wrote:
Fat lot of good that'd do with a roaming notebook. You mean I can't read news
and surf out on my deck with a cold one any more?
A properly designed and implemented wireless segment works as these things
were originally intended to do - which is *not* to replace wired segments, but
to allow roaming clients.
No doubt 98% of wireless installation are negligently configured because 98%
of the users are clueless, refuse to rtfm, and already had security risks up
the keister with their *wired* segments so why should the wireless side be any
better.
Don't advertise a wap, use mac filtering to allow only known macs to get
through the wap, enable 128 or 156 bit WEP if capable to keep out the kiddie
riff-raff, use mac filtering at the routing appliance so only known macs get
to WAN, don't use Windows 95/98/ME which are outrageously insecure at their
best, make sure all systems require per-user authentication, turn off
unnecessary network services and protocols, and run software firewalls and
rogue application blockers on everything that has a pulse.
It isn't perfect, but it's pretty resilient. If someone does manage to get
through the intrinsic weak spot (the wap) they're not going to get very far...
/daytripper
