X40 wifi woes...

[Nitehawk]

I have an X40, and I am having problems with the intel wireless card.

It wont connect to certain networks! I just get the message "Connection Failed" after it tries to connect. The problem can be temporarily solved if I uninstall then reinstall the intel software. BUT THEN IT COMES BACK. this is particularily annoying because it does this with my schools wireless network. and I bought the X40 specifically for school!

Anyway. I thought I would try to solve this problem by using windows to configure the wireless network. But I can only succesfully do this without Access Connections installed. Now I haven't actually tried it with this solution on the culprit networks, because without access connections installed the Function F5 Utility doesnt work, so I can't turn the wireless off!

But if i try to just use the intel drivers, and Access connections installed. when I use the Function F5 utility it wont actually turn the wireless on, and I have no wifi at all. it just remains off regardless of how many times i click power on.

So do any of you have advice other then switching to the Atheros card? I have the Atheros card in my T42, and it works fine on every network. the function F5 utitility works without access connections installed. it's great.

I have a friend that also bought the x40, and he's had similar problems with his wifi not connecting to certain networks, but the problem is solved when he reinstalls the intel drivers/software.

[x40guy]

I have an IBM X40 myself and have had the same problem occasionally. My internal wifi setup is type "B". For the most part, i just use a PCMIA card to connect and that works nearly all the time. Since I don't have anyother PCMIA cards for other duties, this works fine with me. However, with only one PCMIA slot, this could be a minor pain if you need the slot for another card.

[nampord]

Hi

I had a similar problem and found a fix on the Lenovo support site:

http://www-307.ibm.com/pc/support/site. ... MIGR-64439

apparently there is an interference with the libeay32.dll in the windows/system32 path

renaming this file to libeay32.dll.bak fixed all probelms with Fn + F5 and Access Connections