Configuring T42 for use with a Netgear wireless router

[breichjr]

Hello. I recently purchased a refurbished T42 (2373 CTO) from IBM and am trying to get it to work with a Netgear wireless router. It took awhile but I was able to figure out how to get the radio on on the T42 so now, at least, the laptop "sees" that the wireless router is there, but I still can't get it to connect to the internet. Both Netgear and IBM are playing the "call the other" game as neither feel it is their fault.

I'm no computer expert. What Netgear has told me is that I can't configure the WEP key and it's 64 bit encryption. They said they cannot figure out why we can't edit my profile to "enter a network key".

On the T42 page it says that the currently applied profile is "dlink" and when I click on the "Connect" tab it says "Unable to connect to the selected wireless network. You may need to configure your system to support the authentication method that is in use. Contact your network administrator."

I'll happily make a donation to the community if someone is able to assist.

Bob
Pittsburgh

GO PITT!!!!

[GomJabbar]

If you are using Access Connections, try creating a new profile. Depending upon how it is set up, you may need to be logged into Windows as Administrator.

If you still have trouble, try going to Start > Connect To > Show all connections > right-click on the wireless adapter and choose Properties. Highlight TCP/IP and choose Properties. If anything is set to manual, change it to automatic. Now try creating a profile in Access Connections again.

You can also try and repair the Winsock.
How to recover from Winsock2 Corruption

If all that fails, you may need to uninstall Access Connections and uninstall the wireless software (using Software Installer or Windows Add or Remove Programs). Reboot, then reinstall the wireless driver software and then Access Connections.

Here is where you can download all your drivers and software. Be sure to read and follow the installation instructions.
Software and Device Drivers - ThinkPad T42, T42p

Let us know if you are successful or not. If you still have trouble, tell us which wireless adapter you are using in your T42 (IBM used several).

[breichjr]

Not sure if I am using "Access Connections" or not. How can I tell?

I just got off the phone with Netgear (another hour in India) and it seems as though we are SO CLOSE but we still can't get it to work. He feels, though, that the problem is on his end and he says he will call me back within the hour. We'll see......

After your tip I went to the Wireless Connections tab and simply clicked on the box that said to allow windows to try and automatically configure every time (or something to that effect.) It looked as though that was going to do it but, alas, nothing ever gets fixed that easily.

Thanks, again.

BR

[breichjr]

Nevermind. I apologize. I went to the access IBM tool and created a new profile. Still no luck. I'll update after (and if) I hear back from Netgear again.

[GomJabbar]

If you are using Access Connections, you should know it. There will be a TV looking icon sitting on an inverted T - in the notification area on the lower right. You can launch the program from Start > All Programs > ThinkVantage > ThinkVantage Access Connections.OR Start > All Programs > Access IBM > Access Connections. You do not have to use Access Connections, but it is an option.

If you are using Windows to manage your connection, chedk that the Wireless Zero Configuration service is ON and set to Automatic start. Go to Start > Control Panel > Administrative Tools > Services, and scroll down to Wireless Zero Configuration to check the settings.

Try the Winsock Repair from the link posted above.

Here are a couple of other links that may help...

Troubleshoot TCP/IP Connectivity

Using the Network Diagnostics Tool

Corruption at the Jersey Shore

Minimizing 802.11 Interference Issues

[breichjr]

Thanks. I finally got through to someone at IBM tech support in Atlanta (Mario) who knew exactly what to do. First we disabled the Windows Zero function, then we had to (as you said) install four new drivers to get the thing humming. I can't believe it now actually works like a charm! Apparently this refurbished T42 was pretty out of date.