I have a 2326-D8U T60p with the Intel 3945ABG wireless LAN card, Bluetooth, and the Sierra Wireless WAN card inside running a very up-to-date XP SP2. After receiving the laptop back from EasyServ for an LCD fix, the Access Connections manager refused to show the 3945ABG LAN connection.

At that time, I was at home and it would still connect as normal to my home network (802.11 B with WEP 128-bit encryption). I "made the mistake" of trying to connect elsewhere and lost the ability to connect to my home network. I mean, I can see it in the Windows "View Wireless Connections" tool, but I can't connect to it unless I turn off the encryption.

I've been on the phone with IBM Support for about 2 hours today installing the Power Manager, Hotkey, and Wireless driver (10.1.0.13) [and 10.1.13, though that was after the calls in a desparate attempt to fix this]. And Access Connections 4.12. Nothing helps.

The curious thing is that the Tech's records show that EasyServ updated my BIOS to 1.04 but it is quite clear that it was returned to me at 1.02. More joy was found reverting to 1.01a and now 1.04, (reinstalling and rebooting all along the way) but without any help to my problem. Makes me think EasyServ might have done other things they didn't document.

As it stands now, I can connect to unsecured networks and function fine, can see the 3945ABG card in the Device Manager but not in Access Connections.

Anyone have a clue about what is going on here?

--or-- should I just send this $3k lemon back?

(Oh, and sometimes around the logging-in time the Trackpoint stops working, as does some of the keyboard--Ctrl+Alt+Del doesn't do anything but Alt+F4 puts it right to sleep...sometimes even clearing up the Trackpoint problem!)

-----------------------
ThinkPad 760XL -> ThinkPad 600 -> ThinkPad T60p

Uninstall Access Connections and uninstall your wireless driver using Windows Add or Remove Programs, or ThinkVantage Software Installer. Note that if you see Intel(R) PROSet/Wireless Software in Add or Remove Programs, uninstall that also. You can leave Intel(R) PROSet for Wired Connections. Reboot, and if you see the Found Hardware Wizard, choose cancel.

Using your wired ethernet connection, or a dial-up connection, run Software Installer and install the Wireless Driver only. Reboot. Now run Software Installer again and install Access Connections. Reboot again. Hopefully, now everything will work correctly.

I tried your suggestion, GomJabbar, just now--had to update the Software Installer first, then it made me download the Scroll Lock Utility and the Verizon Wireless WAN Modem Driver. I unchecked all but the Wireless Driver (10.1.0.13) and the ThinkVantage Access Connections 4.12 and installed them. Rebooted.

Access Connections still doesn't show the Wireless LAN (still just BT and WAN) when you press Fn+F5. The funny thing is that when creating a new AC profile, the 3945ABG Adapter is shown as "Enabled, 100Mbps" but you get no response from the "Authentication Properties..." button. The "Find Network" button on the next page finds no networks, even if I turn off WEP Encryption on the router...

On the wireless driver download page I see the following:

Intel PRO 3945bg and 3945abg Mini PCI adapter wireless software for Windows 2000, XP - ThinkPad T60/p, X60/s



Verify that you have no red X's or yellow exclaimation marks in Device Manager.

I believe you should see the following in Add or Remove Programs (Windows Control Panel): Intel(R) PROSet/Wireless Software.

I believe the following path should be in your environment variables. C:\Program Files\Intel\Wireless\Bin . Type "path" without quotes and hit the ENTER key at a command prompt to verify.

Try running setup.exe from the following directory: C:\DRIVERS\WIN\WLANINT\ . Tell the software to Repair when the menu pops up.

I am basing the above information from what I have on my T42 using the Intel 2200BG wireless adapter. You may see things slightly different, but I think much will be the same. Note that you will have to reboot for changes to take place.

GomJabbar: Good calls, but no headway. The Adapter wasn't/isn't a bridge. No red X's in the Device Manager. That path is in the path. "Repairing" it from the setup.exe file with rebooting before and after also didn't help. Bummmmmmer.

Have you tried to use the latest drivers from intel instead of those delived by software installer.

Take a look in Start > Control Panel > Administrative Tools > Event Viewer for clues. Look for error messages that occur at the time you are trying to connect.

Other Ideas:

You have a service that should be running but isn't. Look in Start > Control Panel > Administrative Tools > Services. See if the IPSEC service is started. Look for any services that are set to Automatic but are not started. Look for disabled services and try to determine if this could be the cause your problem.

Here is a site that can provide additional information on services:
http://web.archive.org/web/200410190835 ... icecfg.htm]

Look in Device Manager, and under the menu at the top, choose View > Show hidden devices. Do any trees expand, indicating one of the devices has a problem?

Make sure you don't have any Viruses Spyware or Trojans running on your system.

Go to Start > Run > type sfc /scannow in the box and hit the ENTER key. This is System File Checker that checks your operating system files.

You could have a hardware problem with your 3945ABG Wireless adapter.

Open Device Manager, and from the menu bar choose the option for "View" -> "Show Hidden devices". Expand the section for "Non-plug-and-play drivers". Near the top of the list you should seen an entry for an AEGIS device. If you DO see it, then you're OK. If it's not there, or has a yellow bang, then you have a driver install problem. Try using the driver's SETUP.EXE to "remove" the current install driver, reboot, and run the setup from the latest driver on the web.

Next, assuming that you DID see AEGIS correctly installed on the system, the next thing to do is launch a CMD window and type "path", to display your system path. Take a glance through the folder names and ensure that you see the entry for, "C:\Program Files\Intel\Wireless\Bin".... if it's not there, add it.

If you DO already have the path set correctly the last thing to do is open up your My Computer, and head out to C:\Windows\System32. Look for the file LIBEAY32.DLL. If you see it, rename it to LIBEAY32.DLL.BAK.

Reboot. Give it another shot.

kimx: Yes, I tried the ones from the Intel Site 10.1.1.3 (thanks AuroraGuy for the link:
http://downloadfinder.intel.com/scripts ... uctID=2259 )
There was no change with or without this driver and I've reverted to the "blessed" version from lenovo.

IPSEC service is Started and starts Automatically.
How about these that are Manual starts: "IBM PSA Access Driver Control" "Net Logon" "Network DDE" "Network DDE DSDM"?

Device Manager when "Show hidden devices" is checked, nothing expands and even when expanding and looking manually at everything, no problems. Anywhere! (good, right? ;)

Ran a freshly updated definitions Symantec Antivirus Scan and a Spybot S&D, with 0 viruses and 1 errant cookie (I must have turned that off for a little while sometime...)

I see under the Non-Plug and Play "AEGIS Protocol (IEEE 802.1x) v3.4.9.0".

My path comes out with it twice:.
PATH=C:\Program Files\ThinkPad\Utilities;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\IBM ThinkVantage\Client Security Solution;C:\Program Files\Diskeeper Corporation\Diskeeper\;C:\Program Files\ATI Technologies\ATI.ACE\;C:\Program Files\QuickTime\QTSystem\;C:\Program Files\Common Files\Adobe\AGL;C:\PROGRA~1\SecureFX;;C:\Program Files\Intel\Wireless\Bin\;C:\Program Files\ThinkPad\ConnectUtilities;C:\Program Files\Intel\Wireless\Bin\

Run... "sfc \scannow"--it just exited, I guess. I came back after 15 minutes and it had finished without message

The only thing I've found so far that mentions anything is in the Access Connections Log, which lists: this kind of message sometime shortly after booting:
Ok AcSvc( SYSTEM(Prvlg).2404.3148) 14:30:52:859 CAcIPMgr:ACIPMgriUpdateState: No state change detected for the adapter Intel(R) PRO/Wireless 3945ABG Network Connection - Packet Scheduler Miniport (Current state = AC_IP_ADDR_ZERO)
and
Ok AcSvc( SYSTEM(Prvlg).2404.3148) 23:14:55:718 CAcIPMgr:ACIPMgriNotifyAllCallbacks: Notifying IP notification event AC_IP_ADDR_ZERO for Intel(R) PRO/Wireless 3945ABG Network Connection - Packet Scheduler Miniport to callback#0
The rest of the stuff there is goobledegook. Obviously written by obfuscators.

I don't see "LIBEAY32.DLL" in ...System32, though I do see it in C:\WINDOWS\, C:\Program Files\Adobe\Adobe Bridge, C:\Program Files\Adobe\Adobe GoLive CS2, C:\Program Files\WebRoot\Spy Sweeper, and C:\Program Files\IntelWireless\Bin

Oh, YES! So, renaming the instance in C:\WINDOWS and rebooting makes the ol' 802.11 Wireless Radio show up in Access Connections and eventually connect!
And WE'RE ON!

Does it make a difference that the Wireless WAN (The Sierra Wireless Ev-DO) doesn't show up now in AC?

(And I mentioned this before, but possibly unrelated: I basically have to make the T60p sleep TWICE after a reboot to get the Trackpoint to respond, sometimes the keyboard as well (except Fn keys... It is fine before logging into XP but almost immediately afterwards it doesn't respond. Another Thread, maybe?)

Spoke a couple of reboots too soon...

So the Wireless WAN shows up now as well and I just updated the drivers for the trackpoint and it _seems_ to have stopped all that reboot-login-sleep-wakeup-login-sleep-wakeup-login-use trackpoint nonsense.

Looks like we're rockin' out! Thank you all for the excellent advice!!!

Now how can I turn everything off from ever updating again?

So Riddil's tip of renaming LIBEAY32.DLL to LIBEAY32.DLL.BAK did the trick? Great!

I have to admit that I have not seen this tip before. I searched this forum for LIBEAY32.DLL, and only found it mentioned in one other thread, and that was by Riddil. No mention was made in that thread of the success of changing the name of that file.

If you don't mind, could you check in each of the directories you mentioned that that file was located in [ C:\WINDOWS\, C:\Program Files\Adobe\Adobe Bridge, C:\Program Files\Adobe\Adobe GoLive CS2, C:\Program Files\WebRoot\Spy Sweeper, and C:\Program Files\IntelWireless\Bin ], and see if they are the same size, same version, etc.? I think I know the answer, but I would just like to verify.

If you don't want to update the IBM software anymore, just don't run Software Installer or IBM Update Connector (if it's still in use). Actually with Software Installer, you can run it and it will tell you the updates available - you choose which, if any, you wish to install.

C:\WINDOWS\libeay32.dll -- 684,032 bytes
C:\Program Files\Adobe\Adobe Bridge\libeay32.dll -- 843,776 bytes
C:\Program Files\Adobe\Adobe GoLive CS2, libeay32.dll -- 880,128 bytes
C:\Program Files\WebRoot\Spy Sweeper\libeay32.dll -- 684,032 bytes
C:\Program Files\IntelWireless\Bin\Libeay32.dll -- 876,544 bytes

Doing a diff between the WINDOWS and Spy Sweeper versions shows no difference in their contents. The others are all different sizes.

I came upon that other bit of Riddil's after the fact. If Intel is listening: "Stop doing stupid things like relying on a path search order you can't control."

Someday I'll probably have to answer the question: Why doesn't program X work? Oh, because it needs the version it put in C:\WINDOWS... That'll be bad.

Yeah, you would think that a big company like Intel, would make sure they have control of the files used by their programs and drivers. It makes one wonder, how many other times peoples problems are caused by exactly this same sort of thing.

I'm the coolest kid on the block.

Actually, I can't claim omniscience. I ended up finding that fix by complete accident. Noticed on a laptop image that everything was working fine all the way until you install Crystal Reports v10. As soon as that goes in, the Intel driver explodes. (Has the same failure you mentioned). After spending a day pulling out hair trying to figure what was causing something in CRYSTAL REPORTS to cause the intel WIRELESS driver to break, I finally found that they had ONE file in common....

LIBEAY32.DLL.

Whodathunkit.

Apparently someone is paying attention to this problem...

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

Who'da thunk it

Should I be really happy that they posted that on the Internet, or miffed because the tech I talked to (Melvin lastnamewithheld) is way overdue his promise of calling me back on May 17th?

Cool. Riddil's cool.

I had a similar problem with my T60 and the Intel Pro 3945 ABG internal wireless card. It either would not connect to my router or disconnect after 30 seconds. With the help of Linksys the problem was resolved. I disabled (unchecked) the WLAN Transport Protocol in the properties box for the Intel card. I think this disables the ThinkVantage Connection software that come with the computer. I then configured the wireless services with Wireless Zero Configuration (WZC) which can be accessed by Run Services.msc . After that the card worked without problems.

LV1

This is fantastic, and I am VERY grateful. I have been struggling with this exact problem for months. I finally had to restore and resolved it, but yesterday I installed the same app that seemed to cause the problem last time -- none other than Spy Sweeper -- and lo and behold today i see this -- and Spy Sweeper is in fact one of the culprits...(though Webroot has never acknowledged the problem)

Now off I go to rename files

Glory be, it worked. Found three instances of the file, used the one in intel folder to overwrite them -- and bingo, Access Connections works like a charm, not even requiring a reboot.

Thanks Riddil and all others -- a year of grief is over.

Mmmmm, *chuckle*

Wiii, fun with Libeay32.dll; wait until you hit Ssleay.dll, its friend.

They are used for various secure and crypto protocols, beginning with SSL; the thing is that there are various implementations of SSL a la OpenSSL. Hence, there are teeny variations in the libeay32.dll when it is compiled for various platforms. Install OpenSSL and you might mess things up. Not everything that installs seems to have a problem, though. Intel's version probably differs in a tiny way from the libeay32.dll in the windows directory. *Anything* that messes with dll in the Windows directory can cause this problem if it differs alot from the Wireless card's driver's implementation of libeay32 and windows.

This also popped up on certain T4X Thinkpads and was noted awhile back.