Built-in Agere / XP Home won't connect to encrypted networks, only un-encrypted ones

[Curmudgeon]

The problem is straightforward. The built-in WiFi card in my Toshiba Satellite 501 laptop (a Toshiba card running Agere 7.82 drivers) will only connect to un-WEP'd unencrypted networks using XP Home.

I'm trying to connect to a Netgear FM114P 802.11b firewall router. There are two of these routers: One in my home office and an identical one in my partner's office. Both of these routers are running the latest BIOS and software, and are configured very simply. The Toshiba Wireless LAN Mini-PC card is model# PA3212U-1MPC.

When I purchased this laptop, I had to wait a few months before the built-in WiFi card arrived, so in the meantime, we (partner and I) ran out and picked up Linksys PC cards. Using the Linksys software ("Instant Wireless Configuratio Utility") we've had no problem connecting to our respective networks using 128bit WEP.

Now that my card has arrived, I can only connect to open networks (like the one at the coffee shop downstairs) with the built-in card. Connecting to encrypted networks requires that I use the Linksys.

here's what I've tried:
- completely uninstalling the Linksys software (no effect on the problem)
- XP Home is completely up to date with all patches.
- No mention of this problem exists on either the Microsoft or Toshiba websites
- insured that the phrase used to generate the 128bit key is of 13 characters (XP seems to require this - no effect on the problem)
- updated all drivers, BIOS's etc... (no effect)
- changed (and confirmed) the default key setting on the router and the laptop. (no effect)
- tried all combinations of shared and open keys (no effect)

Someone I spoke to at CompUSA (no horrible comments, please) said that the problem was familiar but rare, and was of no help (big suprise).

Is there a software utlity that will manage my built-in card better than XP? any ideas? fixes?

[x586]

When you try to connect to an encrypted network, does it connect and disconnect repeatedly ?
If it does then the problem may be that windows is setting the connection to 'open' instead of 'shared'.

Go in the properties for the nic and look at the wireless tab, I beleave the setting is there, or inside an advanced button on that tab.

You can also try unchecking the allows windows to control box if the 1st suggestion does not work. This should activate the manufacturer's driver utility to control the nic.
This is from memory so it may not be exact, but should give you a general idea.

x586

[Curmudgeon]

Nope.. it doesn't try to connect / reconnect repeatedly. it simply doesn't find or connect to the network.

If I uncheck the "Let Windows COntrol" button, then I have no way of searching or connecting to anything.

I was hoping that someone would point me to a utility that would control the card, rather than let windows drive it.

[x586]

With the linksys belkin and d-link cards I have used when you uncheck the 'let windows control' this allows the manf. utility to work, uncheck that and reboot see if the utility comes up, if nothing happens check the start menu and c:\program files for the wireless utility.

Also check the manufacturers website

[Curmudgeon]

Yeah yeah... But I'm trying to use the BUILT-IN card, replacing the linksys. the Linksys card isn't the problem. The Linksys operates perfectly.

I don't want to use the linksys card anymore. I want to use the built-in WiFi card that is now installed in my laptop. The built-in card won't connect to encrypted networks, only unencrypted ones.

my sense is that there is a Windows XP bug that's preventing the connection. I'm looking for a workaround or a utility that will manage the connection. The Linksys utility won't manage my built-in Toshiba Wireless Mini-PC card

[x586]

Yeah Yeah I understood exactly what you typed and you didn't understand what I typed. ( thats ok I type really bad)
Re-read my previous post and forget about your linksys card in fact you can even uninstall the linksys software.

[Curmudgeon]

Hasn't worked....

I re-read your post, and I'm assuming that you're referring to another piece aof software, the Agere driver or something else, that controls the card when you don't "let windows control the" wireless card. I haven't seen this software. and hare still ahving no luck

The network still connects, but is useless, because I can't unencrypt it.

[x586]

Yea : "another piece of software, the Agere driver" thats exactly what I was referring too. The driver should have some sort of utility for controlling it. Thats why I said check the start menu and program files. Also try reloading the driver with the 'allow windows to control' disabled.

Next would be to check the manufactures website for a driver/utility.

[Curmudgeon]

Still no luck.

The manufacturer (Agere) only has a driver, no utility.

I did, however, find a utility called WiNc from Cirond(http://www.cirond.com) that controls wireless cards (both built-n and PC cards).... This was exactly the kind of software I thought would work. It manages WiFi connection (replacing XP).

BUT IT STILL WON'T decrypt WEP networks. I connect, but can't get an IP address, or get online, or anything.

Is it concievable that the Agere card has a seperate chip for WEP and that this chip has gotten zapped? It doesn't seem like a software problem, but it doesn't seem like a hardware one either.

I'm stumped, and the idea of explaining all this to a tech at Toshiba seems like a losing battle.

[x586]

Is it possible that these AP's are using mac filters? From what you have described it sounds like that might be where your problem lies.
I'm not saying it is, just that the symptoms sound very simliar. If a client has the wep keys, sid, and channel set correctly, but the AP is set to block all connections except those with an approved mac address. Then it would have the same effect (problem) you are describing. And the only fix would be to add the client's mac address or disable mac filtering.

If thats not the case then it would seam you last resort at this time would be to contact the laptop manufacturer and see if they have a fix or are even aware of the problem.

[Curmudgeon]

nope... no MAC filtering. I get the same connection problem on other APs...

it's GOT to be the hardware, right??? I did, however hear something odd about different manufacterers computing the 128 key from a pasphrase differently, but that sounds silly.

[x586]

Didn't realise you were using a pass phraze.
Don't use a pass phase.
Use the actual hex key listed in the router and it is case sensitive.

So to recap:
You are using windows wireless zero to control the nic.
You will need to set it to shared or open depending on the setting in the router.
Set the sid and channel.
Use the actual hex key.
Make certain mac filters are disabled, or the nic mac address is added to the allow filter.

If after that it still fails and I'm not missing some info or having a memory laps then I'm out of idea's until something changes, or I can actually put my hands on the units.

[cruznnus]

Have u tried just for shits n' giggles goin back to 64bit encryption, just curious. and yeh thrown in your MAC address in the access list would be a good idea too.

[Curmudgeon]

Yup... I've done both these things. Still no luck.

The damn card simply refuses to decrypt anything.

[Curmudgeon]

Success!!!

It took two distinct things:

1- I picked up WiNc at Cirond (http://www.cirond.com) This little utility manages WiFi connections (replacing XP's control). It has a 30 day trial and then it's $20. WELL WORTH IT. It works with ALL built-in cards, and 95%of the PC cards. WiNc allowed me to use the hex code for WEP, and managed the process very well. This is a perfect utility. They'll make a fortune, $20 at a time until MS replicates the functionality.

2- no surprise anymore... I used the hex code rather than the passphrase. This was the trick.

May I vent?
WHY ON EARTH WOULD THE SAME PASSPHRASE BE CONVERTED TO HEX DIFFERENTLY ON SEPERATE SYSTEMS?? THIS IS INSANE!

Whew.

thanks for all your advice... x586 your advice kept me focused on working the problem. After I saw your comment about using hex, I realized that I hadn't tried it with WiNc (www.cirond.com).

I must say that Agere (http://www.agere.com) disapointed me. Agere makes OEM Mini-PC cards (among other things) for WiFi. There is no utility, only a driver.

thanks again

[x586]

Grats ;)

[HITMONEY]

Originally posted by Curmudgeon

May I vent?
WHY ON EARTH WOULD THE SAME PASSPHRASE BE CONVERTED TO HEX DIFFERENTLY ON SEPERATE SYSTEMS?? THIS IS INSANE!




In a nutshell ....40/64-bit WEP is part of the 802.11b Standard, while 104/128-bit WEP is proprietary. Apparently, some manufacturers use the same algorithm, as you will find that Brand A talks to Brand B, Brand C talks to Brand D, but the two groups will not talk to each other.

Add that to the fact that you have to get them all talking Hex in order to work, as the manufacturers' passphrase generators all seem to work differently, and you have a real mess.

[x586]

Just thought you might like to know, I had a client that purchased a new toshiba laptop with one of the Agere chipsets and it came with a utility. However I was unable connect to a d-link di-624 rev.C router with any type of encryption enabled 64/128 wep or wpa I spent 4 hours going through it even tried the winc utility and spoke to L3 toshiba support. They are aware of the problems with encryption, but currently there are no fixes.

It works fine without encryption, I put a d-link card in and setup wpa as an open network is not exceptable in this case.

[Curmudgeon]

You went through all the stuff that I did?? Tried Hex? Got WinC? everything and it still didn't work?

You know, other companies make MiniPC cards... I was considering getting one while I was going through all my problems.

m