Re: WEP key wrong and static IP address setting

In article <1178718054.227865.248450@xxxxxxxxxxxxxxxxxxxxxxxxxxx>, barry@xxxxxxxxxxxxxx wrote:
On May 9, 1:52 am, Bin Chen <binary.c...@xxxxxxxxx> wrote:
Hi,

In Windows, if AP A's WEB key is 1111111111, but I input the WEP key
to 2222222222 and set the IP address to static , say 192.168.1.3. The
windows will connect to AP A, and it reports connect successfully. But
obviously, the data can't transfers.

This makes software designers very hard to junior users who don't know
why 'connected' but can't transfer data. Is there way to optimize
this?

Thanks.
Bin

Don't get hung up on "connected". What matters is that your client
associates with AP, has full, workable IP config, and has its packets
routed properly.

In manually setting IP, you're ignoring all the other stuff the DHCP
server on the AP would be providing: netmask, gateway, dns servers,
mostlikely domain-name.

You can check the full IP config., etc. in Windows (which version/SP,
please?) with winipcfg (GUI) or at shell "ipconfig /all". If that
passes
muster, then "tracert www.google.com" or some other hostname
would tell you much about how it's talking with the world. They are
easily researched, and left as an exercise.

Meanwhile ... why not just enter the same key? And make it a
_good_ one: long, melange of do-do with WPA. Few or no words
found in dictionary is a starter. Don't waste your time with WPA,
most especially if you're in an area of any population density.

HTH,
J

I think what he is trying to say is that if the WEP key is mis-typed,
but they use static IP's, there is no real connectivity ( packets don't
flow) but the PC believes the AP is connected. As a matter of course,
I always re-type the WEP keys just to make sure I have typed them
in correctly, but I also always use DHCP. Is there any reason not to
use DHCP? Most AP's have simple DHCP servers built into them.

Gordon


Gordon Montgomery
Living Scriptures, Inc
gordon@xxxxxxx (anti spam - replace lsi with livingscriptures)
(801) 627-2000
.

Relevant Pages

  • Wireless Networking Issue
    ... and it has an Intel 2200BG wireless card built in. ... it said connected with Limited or No Connectivity. ... I guessed at this point that the WEP key was causing havoc, ... landlord disabled the WEP key, and I tried to connect to the Unsecured ...
    (alt.internet.wireless)
  • Re: Wireless Networking Issue
    ... and it has an Intel 2200BG wireless card built in. ... it said connected with Limited or No Connectivity. ... I guessed at this point that the WEP key was causing havoc, ... landlord disabled the WEP key, and I tried to connect to the Unsecured ...
    (alt.internet.wireless)
  • Re: Wireless Networking Issue
    ... and it has an Intel 2200BG wireless card built in. ... landlord, via his wireless router. ... Connectivity. ... I guessed at this point that the WEP key was causing havoc, ...
    (alt.internet.wireless)
  • Re: ESET NOD32 or ESET Smart Security?
    ... Even amateurs can break a WEP key in a matter of minutes with software downloaded from the Internet, and thereby make you the neighbourhood free bandwidth supplier. ... an updated driver for my wireless card; ... driver updates are better downloaded form the manufacturer's support site than from Windows Update. ...
    (microsoft.public.windows.vista.general)
  • Re: 128bit WEP keys and ifconfig
    ... >> my WEP key to ifconfig, ... It works correctly under Windows XP when I swap the HD with the ...
    (freebsd-current)