BEFW11S4 v3 - Setting 128-bit WEP key

having problems doing this.
I get into the router ok, using no username and "admin" for password.
I set up the key, hit OK, then when I hit "apply" the prompt comes up for the username and password again. I skip the username, enter "admin" for password (just like I did getting into the setup earlier) except now it says it doesn't recognize, or it's invalid, etc.
Any help here would be appreciated very much.
Thank you.

Which browser are you using, if you are using Internet Explorer 6.0 and above then
go to tools menu -> click on internet options -> then click on delete cookies, delete files -> now go to Content tab -> click on AutoComplete -> and then click on clear forms and clear password.
Also if possible try to use different computer by connecting it directly to router.

Similar Messages

Aironet 350 in Mac OS9: 128-bit WEP possible?

Aftermarket-like, I have acquired a lovely Aironet PCM-352 card complete with the drivers on CD. I installed them with apparent success on my PowerBook G3 which runs OS 9 (OS X no-go due to FireWire issues), but it doesn't allow more than 16 hex digits for the WEP key (40bits). 128 bit is what I need. Cisco.com won't let me download new drivers, apparently since I don't have a TAC contract. Surely there are wiser places than here to post these questions, but:
- Is it possible, with newer drivers, to do 128-bit WEP keys with this model of Aironet card?
- Where to get those drivers, absent spending a grillion dollars for an otherwise useless tech support contract?

PCMCIA adapter firmware version is V4.25.30 which supports 128 bit encrytpion.

TKIP or TKIP w/ 128 bit WEP?

Can someone explain the difference between the cipher TKIP and the cipher TKIP w/ 128bit WEP? I thought you got a key when you selected TKIP...
Thanks in advance.
David Beaver

Thank you. So then it is better to use just TKIP as opposed to TKIP w/128bit WEP? I am assuming that by using TKIP w/ 128 bit WEP, that WEP has the added cipher to help protect it from attacks.
The reason I ask all of these questions is because I am in the beginning stages of a hospital wireless deployment and want to know the in's and out's of best practice security methods.
Is there a page on the Cisco website that details TKIP, and the details of how it works?
Thanks again for your input. I am so thrilled to have a resource like this to help me when I get in over my head.
David Beaver
Internetwork Engineering

128 bit WEP

Dear all, I have posted this in the Airport Extreme forum as well, but it sort of fits into both, so sorry for repetition!
I have an AE base station that is used to provide network access for a number of machines, most on AE cards, but one (G4 733mhz) has an original airport card. Until recently, I have had security set to 40 bit WEP, not wonderful I know, but I wasn't too concerned. However I recently allowed a PC to connect, and our local IT unit has suggested that, as PC's are more at risk, security should be at 128 bit. I set this up and I have had no end of problems with the G4. All of the other machines (with AE cards) have been fine. The G4 however either takes multiple trys to connect, or connects and then drops out. I first thought that the card might be failing, but having tried another one the same problems exist. I then thought curruption in keychain - but a untouched admin account seems to have the same issues. I have gone back to 40 bit and the problem appears to have gone. Has anyone seen these issues with original airport cards and 128 WEP?
thanks for your help
Andrew Platt

I have the same problem, I recently got an old G3 Blueberry iBook, and it works with no or 40 WEP, but i kick it up to 128, and it wont connect... I have seen Airport cards for sale that say "128" version.. I am wondering if the older cards can be up;graded through firmware of something, or maybe have to be using OS X (currently running OS 9)

How to set up wireless WEP keys in GPO? - possible?

Summary:
How to switch users from using Intel ProSet to manage their legacy SSID w/ WEP to using Windows Zero Config w/ both legacy & new SSID's automatically?
Detail:
Some of our sites are still using WEP for wireless encryption (believe it or not) over 802.11b AP's.
We're in process of upgrading encryption from WEP to WPA2 & from 802.11b to 802.11a/g AP's.
One immediate challenge we have is how to keep both networks in parallel and make this transparent to the end users.
We can't cut all floors over at once, but need to do one floor at a time because users move from floor to floor.
We were able to roll out the new network / SSID in Windows Zero Config through GPO, but learned that we can't do the same for the legacy SSID - setting WEP keys isn't an option in GPO, at least according to the server admins.
Does any of you know how we can do this in an automatic & transparent fashion?
So far we've been using sneaker net to switch users from Intel to Windows, & configure WEP keys in Windows, which is taking up way too much time.

If you use a GPO to manage the wireless it will disable the intel proset software. This can have a negative impact, as you may have user that like to use the Proset when not in the office.
If you are going to use GPOs then the transition should be pretty smooth, just setup the new secure SSID first and then roll out the GPO. There are several M$ patches that you should install as well. Do a search for Microsoft Wireless hotfix and rollup and you will find them.

How to connect Pocket PC to 128 bit WEP protected Airport network

Friends:
Can anyone lead me through the steps to connect my Hp iPaq 4155 Pocket PC to my 128 bit WEB protected Airport network?
Thanks for your help,
Migs

Accessing an Airport wireless network from a wifi enabled PocketPC 2003
http://tech.ifelix.net/2006.html

WEP # for 128 Bit; where do I find it?

I recently bought a Logitech internet radio (Squeeze Box). I have an Airport Extreme. In setting the radio up to recognize my wireless network, it's asking for a "WEP Key". Where do I find this? I have the Airport set up as 128 bit WEP, so I think the number should be 26 digits. Can anyone help??

When you setup the 802.11n AirPort Extreme Base Station (AEBSn) for WEP, you used the WEP Transitional Security Network which uses a 13-character password. For non-AirPort devices to connect, you just need to determine the Equivalent Network Password, and then use this password in the settings for the Squeeze Box.
(ref: AirPort Extreme: Getting an equivalent network password)

How to set a WEP key in hexadecimal (26 characters)

Hi everyone,
I am installing an airport extreme 802.11n base station in my office and I need to keep the same WEP key as my previous access point. The format of the key is 26 hexadecimal digits.
In the setup utility I tried to prefix the digits with a dollar sign but I doesn't seem to work with the new model (it keeps saying that I can only use 13 characters). I also tried to convert the key to ASCII but it is still rejected (probably because of the weird ASCII characters).
Any suggestions?
Cheers,
Thomas

One of the problems with WEP is that the actual standard relies on a 10 character HEX key for 40bit WEP and a 26 character HEX key for 128bit WEP.
In order to make things easier for people, vendors use certain algorithms to convert simple alphanumeric passwords (or passphrases) into HEX keys, thus enabling people to use simple memorable WEP password rather than lengthy HEX keys.
The problem is that different vendors use different algorithms to generate the HEX key and therefore a ASCII password on an AEBS will be hashed differently on a Netgear client and vice versa.
One thing is a 13 character 128 bit WEP password will be hashed by all vendors in the same way (if you use 40bit WEP then a 5 character password is required).
Though sometimes not even that works and the HEX key must be used regardless.
AirPort: Joining an encrypted wireless network
http://docs.info.apple.com/article.html?artnum=106424
Choosing a password for networks that use Wired Equivalent Privacy (WEP)
http://docs.info.apple.com/article.html?artnum=108058
WPA
"WPA Personal" on the Mac corresponds to plain WPA, with a pre-shared key (PSK) and TKIP encryption, on non-Apple wireless routers. The same alphanumeric password should work on both.

WVC54GCA setup won't take WEP key

Hi - I'm setting up this Linksys WVC54GCA Wireless-G Monitoring Camera and can't get it to take my WEP settings.The setup screen says, after you select 128 bit WEP, to leave the passphrase field empty and enter the WEP key on the next screen. When you hit enter you get an error saying that the WEP key should be 26 digits and and you cannot continue!
If I turn WEP off and do it without security it all works fine, so how am I supposed toenter the WEP key? Seem like a bug. Endless loop!
hanks
Mike

Hey just had the same problem as you and found the way around it. It looks like the Wizard has a bug in it that you have to use the Pass phrase not the pass key.
The way around it is to use the web interface, use the IP address that has been assigned to the camera as the web address in your browser, you can see this in the wizard or on your wireless router.
all the settings to manage the wifi can be found there, you need to use that area to manage everything else for the camera anyway.
You may need to reset the camera, there is a little button under the camera, use a pen and hold it in for a slow count of 10.

AP1200 dual SSID's with 128 bit encryption

I trying to setup a AP1200 radio with two different SSID's with encryption.
Each SSID must use a different 128 bit WEP encryption.
Both SSID's must have simultaneous access to the wireless radio.
I get the client & radio associated but can not pass
data. And the Clients Link Speed is listed at 1Mbps.
Any help on the would be greatly appreciated.

I too have tried this (multiple SSIDs with multiple wep keys). After re-reading the document pointed to in the previous reply I still do not know how to set multiple WEP keys and assign them to the SSIDs. The document doesn't mention WEP keys at all.
Anone have a sample config using more than 1 WEP key and multiple SSIDs?
michael

WEP key issues

I have been successfully using wireless over an unsecured network. Then I tried to connect to my home network with a WEP key, and, following this post I managed to get it to work with
sudo iwconfig wlan0 essid MYESSID key [1] XXXXXXXXXX
sudo dhclient wlan0
After rebooting and suspending successfully several times, I suspended again and got
Error for wireless request "Set Encode" (8B2A) :
SET failed on device wlan0 ; Invalid argument
whenever I tried the iwconfig command. (This was the error message I had been getting previously, before putting [1] in the iwconfig command.) Now, dhclient just hangs. I am really confused why this suddenly stopped working. I didn't do any updates between when it was working and when it wasn't. I don't know where to look for more specific error messages; dmesg and /var/log/syslog.log are unhelpful.
Using [2], [3], or [4] instead of [1] prevents the error message from being output, but dhclient also hangs. In either case, iwlist wlan0 key lists all four keys as "off", even though I tried setting iwconfig wlan0 key on. Is this supposed to happen?
My card is BCM4322 and I am using broadcom-wl from the AUR.
Any insight would be appreciated!

One of the problems with WEP is that the actual standard relies on a 10 character HEX key for 40bit WEP and a 26 character HEX key for 128bit WEP.
In order to make things easier for people, vendors use certain algorithms to convert simple alphanumeric passwords (or passphrases) into HEX keys, thus enabling people to use simple memorable WEP password rather than lengthy HEX keys.
The problem is that different vendors use different algorithms to generate the HEX key and therefore a ASCII password on an AEBS will be hashed differently on a Netgear client and vice versa.
One thing is a 13 character 128 bit WEP password will be hashed by all vendors in the same way (if you use 40bit WEP then a 5 character password is required).
Though sometimes not even that works and the HEX key must be used regardless.
Accessing a Airport Network with a Windows XP PC or laptop (with XP SP2)
http://www.ifelix.co.uk/tech/1011.html
Accessing a Airport Network with a Windows XP PC or laptop (with XP SP1)
http://www.ifelix.co.uk/tech/1010.html
iFelix

Graphite base station reverted to 40 bit WEP

My Graphite base station somehow reverted autonomously to 40 bit WEP. It had been set up for 128 bit WEP with a 13 ASCII character password that yielded a 26 character Hex Equivalent WEP key when queried. (And the 26 character key was necessary for PCs to join the network.) In the process of adding a wireless multifunction printer to the network, I opened Airport Admin Utility to double check the settings, and found that it was showing 40 bit WEP, and now indicated a 10 character Hex Equivalent WEP key, apparently derived from the same 13 character ASCII password, since my MacBook Pro had no problem joining the network. I then tried to reapply the original WEP settings, but found that 40 bit WEP and None are now the only available security choices. I am running Mac OS X 10.4.11, though the base station was originally set up under Mac OS 9.2 running on an iBook G3. On the MBP I had Airport Admin Utility 4.2.3, which I updated to Airport Admin Utility for Graphite and Snow v.4.2.5. However, there was no difference in the available security choices. Any suggestions on how to recover?

Yes, it's definitely a Graphite base station. I bought it not long after AirPort was introduced, initially using it at my primary home with dial up internet on a wireless/wired network. I replaced it with an AirPort Dual Ethernet when I upgraded to cable modem internet. Later I installed the Graphite in my vacation home with dial up internet, then upgraded to DSL, on a totally wireless network, where it is adequate, if antiquated. So I have set it up three times, though the last time was several years ago. Each time, there was a choice of two WEP levels, maybe 64 and 40 bits rather than 128 and 40, but each time I chose the higher level. That was borne out by interrogating the base station for its Hex Equivalent WEP Key in order to get a PC access to the network, since the response was a 26 character Hex Key. More than one PC used that 26 character key to join the network. Now that 40 bit WEP is the only choice available in AirPort Admin Utility, when queried, the base station returns a 10 character Hex Equivalent WEP Key, though the 13 ASCII character network password has not been changed, and I have done nothing to change its configuration.

WEP key index?

Hi, recently switched to a Macbook pro. The problem is that I can't connect with the wireless network in Mac OSX. When booted up in Windows XP on the same machine it works fine.
The problem seems to be the inability to select a WEP key index in Mac OSX? Am I the only one with this problem? Did i some how miss this setting? Please help!
Thanks in advance.
Macbook Pro Mac OS X (10.4.6)

If you can switch to WPA this will easily solve the issue and make your network secure.
One of the problems with WEP is that the actual standard relies on a 10 character HEX key for 40bit WEP and a 26 character HEX key for 128bit WEP.
In order to make things easier for people, vendors use certain algorithms to convert simple alphanumeric passwords (or passphrases) into HEX keys, thus enabling people to use simple memorable WEP password rather than lengthy HEX keys.
The problem is that different vendors use different algorithms to generate the HEX key and therefore a ASCII password on an AEBS will be hashed differently on a Netgear client and vice versa.
One thing is a 13 character 128 bit WEP password will be hashed by all vendors in the same way (if you use 40bit WEP then a 5 character password is required).
Though sometimes not even that works and the HEX key must be used regardless.
AirPort: Joining an encrypted wireless network
http://docs.info.apple.com/article.html?artnum=106424
Choosing a password for networks that use Wired Equivalent Privacy (WEP)
http://docs.info.apple.com/article.html?artnum=108058
iFelix

How to connect to wi-fi when WEP key is not compat...

i am using the nokia 93001 communicator and i have wi fi access point in my office but iam not able to connect to the access point because the phone supports 40 or 104 bit key lenth and my office router has 64 bit key so kindly suggest how to rectify this problem

Encrypted wireless networks use either 40-bit or 128-bit keys. The key is conveyed in either eight-bit (ASCII) or four-bit (hexadecimal) encoding.
When using hexadecimal, each character in the final encryption key is four bits long when converted to binary.
The 26 characters of a 128-bit key add up to 104 bits. This 104-bit password is combined with a 24-bit random number, called the initialization vector, to create the 128-bit encryption key. The initialization vector is supplied with each packet of information sent and is part of the Wired Equivalent Privacy (WEP) algorithm and 802.11b standard.
With 40-bit encryption, the 10 hexadecimal characters equal 40 bits, which are then combined with the initialization vector to create the 64-bit encryption key. In this case the 40-bit name is a misnomer; it is actually a 64-bit encryption key.
N95 v 21.0.016 14-02-08 RM-159 (03.01).
N93 v 20.0.058. 21-10-06 RM-55 D211 card-phone
-Android Hero :-)

40 bit WEP and Windows XP

I'm still using the original AirPort, purchased February 2000, every day. What a great innovation that was...! For the first time, I hooked up a Windows (XP) computer, my neighbor's new Dell notebook. I got it working pretty quickly, although there was a problem with the WEP encryption: my AirPort offers 40 bit WEP encryption, which was unavailable on Windows XP, where you can choose either 128 or 64 bit. A research on the Internet revealed that the 64 bit encryption is also called 40-bit, so we tried that (How comes 64 can also be called 40?? Why not call it 77-bit instead???). Then there was an issue with the password: In Windows XP, it stated that the password had to be 5 characters long, whereas, in the past, I always used a much longer password. But after changing the password, the Dell was hooked up and could access the Internet. Can somebody explain this password issue? If the max. length allowed is really 5 chars, why did my computer never complain? Does the password get truncated to 5 chars without notifying me?
Thanks for answers

Here's the link to the thread:
http://discussions.apple.com/thread.jspa?threadID=534141&tstart=30
and in case this link doesn't work, I copied the answer:
"One of the problems with WEP is that the actual standard relies on a 10 character HEX key for 40bit WEP and a 26 character HEX key for 128bit WEP.
In order to make things easier for people, vendors use certain algorithms to convert simple alphanumeric passwords (or passphrases) into HEX keys, thus enabling people to use simple memorable WEP password rather than lengthy HEX keys.
The problem is that different vendors use different algorithms to generate the HEX key and therefore a ASCII password on an AEBS will be hashed differently on a Netgear client and vice versa.
One thing is a 13 character 128 bit WEP password will be hashed by all vendors in the same way (if you use 40bit WEP then a 5 character password is required).
Though sometimes not even that works and the HEX key must be used regardless.
Accessing a Airport Network with a Windows XP PC or laptop (with XP SP2)
http://www.ifelix.co.uk/tech/1011.html
Accessing a Airport Network with a Windows XP PC or laptop (with XP SP1)
http://www.ifelix.co.uk/tech/1010.html
iFelix "
That did it for me, I hope your question's answered as well.
Kurt

BEFW11S4 v3 - Setting 128-bit WEP key

Similar Messages

Maybe you are looking for