Sign in with
Sign up | Sign in
Your question

The network password needs to be 40bits or 104bits

Last response: in Wireless Networking
Share
June 29, 2012 12:39:02 AM

No matter how many times I enter the correct key, it gives me the same message. I am the one who set this network up initially, and the passkey has not been changed. It is a 4g network with a router, and I desperately need this computer to be wireless.
June 29, 2012 3:30:07 PM

Sounds like you're probably using WEP security, which was broken (hacked) years ago. So it’s probably not a good idea to continue using it. But if you insist…

It might be that you're entering a passphrase rather than the actually hexadecimal value. WEP devices/routers sometimes allow you to enter a passphrase. But that passphrase is not the actually key. The passphrase is only used to GENERATE the key. And that key comes in two options; 40 and 104 bits (obviously the latter is slightly more secure). Unfortunately, you usually need to provide the generated key rather than the passphrase once you need to use it. And that’s why ppl get confused. They keep supplying the passphrase, while the system thinks you’re trying to pass the generated key (in hexadecimal) and so it chokes.

So whenever you setup a WEP-based router, it’s important to record the generated hexadecimal key, not just provide a passphrase and ignore the results. Or else (if supported) just provide the hexadecimal key directly. And record it! Or you'll end up in this conundrum.

If you don’t remember the key, then you might be forced to reset the router and start over.

m
0
l
October 11, 2012 4:19:01 AM

Lilith_Holmes said:
No matter how many times I enter the correct key, it gives me the same message. I am the one who set this network up initially, and the passkey has not been changed. It is a 4g network with a router, and I desperately need this computer to be wireless.




WHich operating system are you running and what service pack, install the latest service pack the problem should be solved, i encountered the same issue with windows XP SP1, but when i upgraded the SP to SP 3 the problem disapeared and i have successfully tetsed it so would recommend you try the same.
m
0
l
Related resources
!