ThinkVantage Access Connection Problem

[greghead]

tokjdm did you try this link?

...I have uploaded their VBS script and the instructions (DOC) they send me into a ZIP file here http://rapidshare.de/files/11778007/Wireless.zip.html

I was only able to get it there, not on the first link that was posted in this forum.

The ZIP contains a DOC with instructions and the script, IntelWLANCleanup.VBS. You can right click the VBS file and choose Edit to examine how it works.

[greghead]

I have tried all those without any success . Could you please tell detail the order in which it was done. The documentation speaks nothing of AC. Does AC have to be installed all along? If so, what version did you have? What is the version of the wireless driver you installed? Please Please specify in more detail.

* I had Access Connections completely uninstalled.

* I have 2915ABG.

* I used the latest Intel PRO/Wireless driver, version 9.0.2.31, same as helloguys specified:
ftp://ftp.software.ibm.com/pc/pccbbs/mo ... wc38ww.exe

For me I suspect the two key points were:
(a) I had turds leftover from a faulty uninstall. The VBS helped remove those.
(b) I realized I had to run the SETUP.EXE manually (doh). Doing so installed the PRO/Wireless application, not just the raw drivers. Installing the app must install some DLL or API that allows Fn+F5 or AC to control the radio.

I hope this helps, good luck!

[helloguys]

If you uninstall all wireless/profile management utility cleanly, and you run the driver setup manually (not by Software Installer), you should have a chance to get it work.

I recommend 'Your Uninstaller! 2006'. It does a very good job on cleaning up leftovers. Run the VBScript to double check. Don't be lazy, reboot as Windows prompts you to do so (or after each uninstall/install). Remeber to click 'Cancel' when Windows prompts you to install new found hardware (the wireless card).

[tokjdm]

No success for me either. I was well aware of the necessity of installing the Intel/Pro software and not only the drivers and I have always installed them both, in the proper order and while rebooting before after uninstalling and after installing. The VB script did not find any files to delete in my case. Access Connections work for my wired connections but ignores my wireless card (2915). The wireless status screen (ACWLicon.exe) shows a wrong MAC address but the correct name of the wireless adapter.

I tried before to uninstall/reinstall the hot key drivers but the problem was not solved either.

[GomJabbar]

You might try ininstalling the Winsock and reinstalling it (after you have uninstalled the wireless driver and Access Connections). Then after reinstalling the Winsock, install your wireless driver, then Access Connections.

How to recover from Winsock2 Corruption

Troubleshoot TCP/IP Connectivity

[hoya]

that worked for me.

1) uninstalled AC 4.01

2) uninstalled Intel ProSet Wireless Software

3) reinstalled Intel ProSet version 31 using the setup.exe program, checking both boxes after choosing custom install

4) re-booted and now I see the proper screen when I hit Fn + F5

I don't plan to install AC again because this new version seems too buggy.

[tokjdm]

Gomjabbar, thank you very much for your suggestion. I can use the wireless device with windows or with the intel software but i cannot use it with AC. Do you think that in this case a winsock corruption would be possible ?

[tokjdm]

I repaired winsock as suggested by GomJabbar but it did not solve the problem.
However I got an interesting finding from netdiag /test:winsock /v.
It found 17 protocols which is more than the 10 described in the Microsoft Support paper (I don't know if this is good or bad) but with regard to the 2915 card, it says that the card may not be working (although Windows Device Manager reports it to be working fine and I can use the card with Windows). It also says:

- Media State: Disconnected
- Device State: Connected

No packets were sent or received. Does anyone know how to interpret these results ?

[DDGuy]

Glad to report that thanks to various hints offered in this thread I could get this problem solved in my T43 (with Intel 2200BG) this forum sure rocks ...

My problem was same as reported by many..I had AC3.81 and it FN+F5 didn't used to show Wireless radio (only BT radio was there), I installed AC4.11a and the latest power management driver (via Software installer) and I started getting Wireless Radio in Fn+F5 but couldn't on/off it from there at all.

Now I did this-
1) Remove wireless adapter from Odyssey and Disabled it.
2) Remove AC4.11 a (keeping the profile) from Software installer
3) reboot
4) remove Wireless LAN adapter s/w for 2200BG using Your uninstaller ! 2006 (it did clean 7 registery keys left over by uninstall program)
5) remove Intel Proset s/w using Your Uninstaller! 2006 (it did clean 7 registery keys left over by uninstall program)
6) Ran Intel's cleanup script, it also found 4 files to delete
7) Reboot and cancel the hardware installation wizard.
Check FN+F5, it was showing only BT radio and was working fine for it.
9) Manually install Wireless driver from C:\ Drivers\1YWC38WW
10) Reboot
11) Check FN+F5, it was now showing Wireless as well as BT radio and was working fine for both.
12) Add wireless adapter from Odyssey and Enabled it and check if able to connect to office wireless LAN -was fine
13) Uncheck "let windows manage wireless option" and see if the Wireless Icon in tray turns green - was fine
14) Manually install AC4.11a from C:\ Drivers\79CN18WW
15) Final Reboot

If you use Odyssey, chances are that like myself you can't use AC to connect to Wireless. In that case remember to uncheck automatic radio control in AC's global settings, else it will keep turning the wireless radio off due to some stupid reason.

thanks to all who helped.

[gleesonb]

I'm in the same boat as tokjdm (T43 1871-F1G, Intel 2915ABG) - AC is picking up a spoofed MAC address from somewhere, but the Proset software is finding the real one. Trying everything in this thread hasn't helped, so I've emailed a forlorn support request. Thanks for your suggestions so far.

[cerebral_mamba]

SOLUTION AT LAST


I tried everything mentioned in this forum and it did not work for me..and as you may see i am the one who started this thread. After exhausting all options I decided to give "Your Uninstaller! 2006" a try

1. Yes, "Your Uninstaller! 2006" scanned my registry after Intel Uninstaller unistalled the wireless drivers and it detected 14 entries in my registry, which it removed.

2. After that I installed the IBM recomended wireless drivers, REBOOTED and now its working .. It will not ask you to REBOOT after wireless driver installation, but it is a MUST. Without rebooting, it was showing the same wrong MAC address, and after rebooting everything is great.

All throughout the above steps, I had AC 4.11a installed. After reboot, AC will show the correct MAC address for the wireless NIC

Do let us know what worked for you. This thread now contains 3 basic steps.

1. First using the VB Script method.

2. Second using the HotKey Installation method

3. Lastly, using "Your Uninstaller! 2006".

I would suggest using "Your Uninstaller! 2006" the first time itself and you should have it up an running.

ALL THE BEST!!

[greghead]

SOLUTION AT LAST

I tried everything mentioned in this forum and it did not work for me..and as you may see i am the one who started this thread. After exhausting all options I decided to give "Your Uninstaller! 2006" a try

It did seem unfair that you started this thread, which eventually helped so many others -- but not you. Glad you got it working!

[davedave]

My 3.81 never worked, nor did my F5 key nor did my standby key. When I try to install 4.11A it just gets hung up. I tried to unistall 3.81 and Your Uninstaller cant even find it. And IBM updater wont unistall it because of some error. WHat can I do?

[cerebral_mamba]

My 3.81 never worked, nor did my F5 key nor did my standby key. When I try to install 4.11A it just gets hung up. I tried to unistall 3.81 and Your Uninstaller cant even find it. And IBM updater wont unistall it because of some error. WHat can I do?

Did you try if AC 3.81 installs again? Once you get it to install properly, you will be able to uninstall it.

If nothing works, and after talking to IBM for any solutions, the last thing I would do is go to the registry and delete and reference to AC. I had a massive CAD software with faulty installation that won't uninstall nor install again... so this is what I did..

But it does seam strange that AC is not installing at all.. Best of luck.

[finalpatch]

without success.

[cerebral_mamba]

Oops.. I just realized that I have been using wireless driver 9.0.1.21. Any later driver and I can't enable wireless radio with AC.

This version of drivers are rare to find and another kind user send it to me since he has the same problem I have and works only with v9.0.1.21.

Let me know if anyone needs it and can't find it online.. I will upload it somewhere and send the link.

[finalpatch]

for those cannot get FnF5 working:

the new drivers install the DLLs to "C:\Program Files\Intel\Wireless\Bin" instead of "system32" that's why the Fn-F5 software cannot locate them. Just add "C:\Program Files\Intel\Wireless\Bin" to the PATH environment variable and reboot, everything will be fine.

[smithchen]

Finalpatch, Thanks you very much.

I try every solution in this subject, and fn+f5 never work.
But your is the most simple one, and it really works.
My computer is T43 upgraded from T42 harddisk image.
And the wireless card is Intel 2915 ABG!!
I try to find out every registry related to wireless card driver.
And also Your Uninstaller 2006!
I never think about that resolution is so easy.
Anyway, Thanks again!!
I have still one problem with my new T43, it could not power off or shutdown properly.

[GomJabbar]

I have still one problem with my new T43, it could not power off or shutdown properly.

Try: Microsofts UPHClean service.

[paulnatale]

I've been following this thread trying to fix the same issue on my T43. I currently have the 9.0.4.8 drivers, but it looks like no one can get them to work with AC. Can someone help me find the 9.0.1.21 drivers?

[bill bolton]

I currently have the 9.0.4.8 drivers, but it looks like no one can get them to work with AC.

They are working fine for me, on a T43 with AC 4.11a!

Cheers,

Bill

[paulnatale]

Well, I've been through every solution in this thread several times trying to get the 9.0.4.8 drivers to work, and have had no luck. AC still shows the wrong MAC address for the wireless card, and thinks the card is off when it is actually on.

[paulnatale]

Huge thanks to Cerebral_Mamba for all the time, work, and help on this issue. I got the 9.0.1.21 drivers and they work perfectly with Access Connections.

[cerebral_mamba]

Glad you got it to work 'paulnatale'... getting AC to work is really worth the effort.

I have uploaded the old drivers to

http://rapidshare.de/files/11552508/WLANCX2A.zip.html

for anyone that may again need it.

[francisy3k]

what is Uninstaller 2006!??????

[byron]

i fought with this problem on and off for about a year and opened like 4-5 trouble tickets with IBM (none of which were ever resolved by them).... finalliy i got sick of it and called tech support and referenced each of my previous cases and asked that they replace my wireless card (i had a 2200BG MiniPCI) with the IBM dual band ABG card, he was hesitant but somehow found that a part number that was a replacement for another part number was considered a replacement for the 2200BG card. So he sent me the ABG card and said not to worry about returning my 2200BG card. I've been extremely happy since then. No problems whatsoever.


<knocks on wood>

[Riddil]

Holy smokes. You guys have had a lot of problems with this.

The sad part is that Access Connections really has very little to do with the problem. It's the Intel driver / upgrade process. There are three components which contribute to the "Fn-F5" working correclty, and there's only two that can potentially have a problem.

The three components:
- wireless supplicant (The AEGIS protocol)
- wireless driver
- PM driver / on-screen display util

So! The parts that you don't have to worry about are Access connections, the PM driver, and the on-screen display util. Just make sure they're at the latest level, and then you can completely forget about them. The next thing you need to do is focus on the driver, and the supplicant.

The supplicant is basically the middle man that sits between the hardware and the OS. There are a two ways you can have problems here:
1) The driver is installed with the wrong supplicant
2) The driver can't communicate with the supplicant

So! You need to make certain that you've got all the right pieces in play. First, check your network device properties. You should have one entry in there for "AEGIS" something or other alongside your TCP/IP and other components. Make certain that it's present. If it's not, then you have a problem. One way you can get into this state is if your system has done a PnP install of the driver with the INF file. If you install by this method you'll get the driver alone, and not the supplicant. You must run a setup install to get the supplicant.

One way to check if the supplicant is correctly installed is to launch Access Connections, and try to create a new wireless profile. When you get to the part to select your method of "Authentication", check for what options it gives you. If you only see three options: "None, WEP, Windows Managed", then you do not have a problem with Access Connections.... you DO have a problem with your supplicant.

Okie dokie, so, check to make sure that the AEGIS is properly installed in the stack. If it *is*, then the next thing you should check is for other wireless utils you've installed. Unfortunately most providers all use the AEGIS protocol. Unfortunately they all use different versions of the protocol! If you've installed Cisco, or anyone else's util, odds are you've got dueling supplicants. Someone won't work. Uninstall the guy you don't want to use any more.

The next part.... if your supplicant is installed OK, it's still possible that it's not communicating with the driver. And it's for this reason that the cleanup VBS script exists. The problem is that Intel has gone through three different variations for where the supplicant is stored, and what it's called. In 8.x it was in Windows\System32, and had one name. In early 9.x versions it was in the same place, but had a different name. In later versions of the 9.x it kept the new name, but it was moved out to the Program_Files directory. The problem is that the Intel driver will check for ALL those locations / names. If it finds any, then it will use the earliest varition as the highest priority. So, latest driver, older supplicant. It doesn't work too well.

So the VBS script just runs through the system location and removes those old tid-bits. You could honestly use the SETUP.EXE "remove" option and clean out a lot of those same chunks. The intent is the same with the VBS and and the "remove" option in the installer.

Anyhow, after you've cleaned all those bits out, the next step is to run the SETUP.EXE to make certain that the driver is installed correctly. Get it set up, reboot, and then launch a CMD window. Type "PATH", and glance through there to make absolutely certain that you see an entry in there that looks something like, "C:\Program Files\Intel\Wireless\Bin". If you DON'T see that entry, then you have a problem. Make sure that it exists physically, and if you want you can go add that entry manually so that it will exists in the system path. (The latest 9.0.4.8 driver on the web shouldn't have a problem updating the path. Keep in mind, there's a NEW 9.0.4.8 driver on the web to specifically fix the PATH problem. If you got the OLDER 9.0.4.8, then it still has this issue)

So anyhow. There's basically three things to check:

1) No old remnants of the Intel driver (supplicant) are hanging around
2) The supplicant is installed correctly, and in the correct location
3) The system knows how to find the supplicant

You get those things working, and your Fn-F5, and your ability to select all of the authentication methods should be fixed.

It sure would be nice if Intel would admit this stuff is a problem, and actually fix it in the installer. It would make it so much easier.

[aardwolf]

I have also given up the AC until somewhere in the forum says it can be safely used.

Uninstalled AC, installed the Intel PROSet/Wireless Software 10.1.0.6 and it worked flawlessly. Use the 9.0.3.6 driver that comes with it, manual installation or otherwise.

I can live without the Fn-F5 until then.

[Paul Unger]

Is there any real surprise that some of us are having problems with this when we're dealing with 'supplicants', 'VBS scripts', and 'stacks', Riddil?! That's all WAY beyond me But thanks for taking the time to troubleshoot that for us! And here I thought a 'supplicant' was someone who asked his *god* for something--which is about where trying to get AC to work had left me

[abvc]

had same problem.
i installed back the 3.81 ac and 9.0.3 something wirelss driver.

what i noticed from the new intel driver is it includes profile selection like in ac, but did not notice performance increase. plus it can't detect 'hidden' network SID.

Therefore i prefer the old driver + working ac.