"DJA" <(E-Mail Removed)> wrote in message
news:bjkh55$k2um3$(E-Mail Removed)...
> I have tried several brands of WiFi router (b) and with each brand I
> experience regular wireless connection drops. Some brands (D-Link) just
> hiccup and keep going, while others (Netgear, Linksys) freeze and need to
be
> reset.
>
> After reading user reviews from several sites, I see that ALL brands seem
to
> suffer from this to some degree. However, many users report no problems at
> all. I don't think interference is my cause since I don't use any other
> 2.4ghz devices and my closest neighbors have either 900mhz or old 46-49mhz
> cordless phones.
>
> An earlier post mentioned a "Use IEEE 802.1x authentication" network
setting
> that has to be disabled or you'll see brief drops on an intermittent
> basis....which is exactly what I'm seeing! However, in Win2k this is not
an
> option. MS says "You cannot enable 802.1x authentication on computers
> running Windows 2000 because support for 802.1x is not provided by default
> in Windows 2000. Therefore, the associated user interface (the
> Authentication tab) does not appear in the Network Connection Properties
> dialog box."
>
> There is a patch from MS (Q313664) that will update Win2k to allow that
same
> IEEE 802.1x options as their other OS's. (This patch requires SP3) I'm
> debating whether or not this could be a possible solution.
>
> Has anyone else using Win2k seen drops that cannot be explained or
> eliminated? Or, has anyone using Win2k had stable wireless connections? In
> either case, which service pack is installed? I'm using SP2 on my desktop
> and wireless laptop.
>
> Could Win2k(SP2) be susceptible to this problem because of this IEEE
802.1x
> authentication issue?
>
> TIA,
> Dave
>
I use Win2000 and had this effect with the default settings in a D-Link card
but not a Buffalo card. I found that the answer was in my own card settings.
I cannot remember exactly what they are called, but there are a couple of
options to play with. If I describe them, then you might recognise
something:
By default, the D-Link card was set up to connect to "any" available
wireless network that it found. This meant that every so often the card
would drop the current connection and go off scanning its spectrum looking
for available networks. Sometimes it came back, sometimes not.
You need to directly specify the ESSID of the network you wish the card to
lock on to and the frequency band [in my case, #8 out of numbers 1 to 11].
If you specify these directly in your card management software then the card
will not have a reason to "look elsewhere" for a better connection.
Does this make sense? hope so.
L
|