Page 1 of 1
Access Connections not seeing wireless?
Posted: Mon Dec 19, 2005 9:32 am
by sparta.rising
So I did a clean install of XP and used the IBM software installer to download all the programs. The Windows wireless is working, but the Access Connections wireless manager isn't picking up the wireless card. Any ideas? Its a T42 with the Intel Pro/Wireless 2200BG
Posted: Mon Dec 19, 2005 9:51 am
by jdhurst
A while back, order of install of NIC and Access Connections was important. Since you did a clean install, try this:
1. In the Properties of the Wireless NIC, make sure Windows is not trying to manage the connection.
2. Make sure your Access Connections settings match your access point (I have seen this failure more than once).
3. If the above fails, try uninstalling Access Connections including its profiles, restarting, and re-installing.
... JD Hurst
Posted: Mon Dec 19, 2005 10:05 am
by sparta.rising
I remember seeing this before, but I can't find it now. How do I change if windows manages the wireless?
Posted: Mon Dec 19, 2005 10:41 am
by jdhurst
Start -> Programs -> Accessories -> Communications -> Network Connections. Box opens. Right click on Wireless NIC and select Properties. Click on the Wireless Networks tab. .. JD Hurst
Posted: Mon Dec 19, 2005 12:06 pm
by sparta.rising
Ok I set it so Windows doesnt control the wireless. No luck.
I uninstalled Access Connections and the Wireless adapter, reinstalled both, set it so Windows doesnt control the wireless. No luck.
I uninstalled Acess connections and profiles, but not the Wireless adapter, reinstalled, still no luck.
Any suggestions? What do you mean by "Make sure your Access Connections settings match your access point". Its just not recognizing the adapter or something. Under Driver/Firmware it says N/A.
I have a working T43 where it does give the Driver/Firmware version.
Posted: Mon Dec 19, 2005 1:21 pm
by sparta.rising
Well I called IBM support, absoletly no help, I think the guy was a trainee because he put me on hold every other word, prolly to reference the manual or ask the guy the next cubicle over for help.
But I did find the problem, a little IBM set of incorrect drivers I had installed that I think was interfering with proper ones (which were also installed).