wireless problem..

[Dutch]

I know the XP wireless problem has been covered before, but I'm in the midst of trying to solve mine.

Just received my new R51 yesterday. Everything is fine except the wireless connection to my linksys wlan. I also own a T41 whose internal card never did work right with my wlan, but which runs fine through a Belkin PC card. But I'm determined to make the R51 internal card work.

It's the same problem as many have reported---trouble holding a connection, trouble using the internet once I actually DO have a connection, etc.

Spent three hours with IBM tech support yesterday. Eventually got a connection that appeared stable, but two hours later, all was for naught--back to the same problems. (An aside here: Wow, the IBM tech support was less than impressive.)

My first question is this: If I'm using two laptops on one wireless access point, should I be using two different WEP keys? My router generates multiple WEP keys, but I've only ever used the first one on the list. Is it possible that my T41 is interfering with the operation of my R51?

Thanks!
-Dutch

[jdhurst]

You only need one WEP key. And having multiple computers with the same WEP key on one Access Point is fine as well.

Next - what wireless network card does your T41 and R51 have. A number of T41's came with the Intel 2100 card which had connection problems as you describe. Any Intel card needs to have the very newest drivers to have a hope of a solid connection. I junked my Intel card, got an IBM 11 a/b/g (Atheros) card and never looked back.
... JD Hurst

[Dutch]

Hi JD. Thanks for the info.

My T41's internal card is an Intel Pro/1000 MT. That machine is owned by my employer, and at the time I got it, I worked with our IT dept to try to overcome the problems (I work in my home). They were less helpful than the IBM support and I eventually figured out by experimentation that by turning off Microsoft's network connections control software and just using the Belkin card and the Belkin software, I could get a stable connection.

The R51's internal card is an Intel PRO/Wireless 2200BG. I just got the system yesterday, so all was brand-spanking new. IBM support was sort of flailing around and had me downloading different drivers, etc. We uninstalled and updated IBM's ACCESS CONNECTIONS software (and driver) a couple of times.

I feel as though the problem MIGHT be with security settings or something similar, but the fact that it all works SOMETIMES (as oppposed to NEVER) just has me scratching my head.

Part of the issue might be that there could be more than one system trying to control the connection (XP and ACCESS CONNECTIONS), though I THINK I've got the XP stuff turned off (including WZC). It's hard to tell, actually. I'm not a wizard with this stuff.

I've embarked on a little self-education--I just returned from the bookstore where I bought a decent-looking book on wireless networking. In the past, though my T41 has been runnning fine, my understanding of wireless networking, security, DHCP, DNS, etc., has been pretty sketchy. It's time for me to learn at least how things are supposed to work, so maybe I can diagnose this problem. I plan to work through the book tonight and tomorrow.

Thanks for any thoughts.

Dutch

[jdhurst]

The Intel Pro/1000MT is the Wired Network card (NIC). If the T41 ever did wireless, it will likely be the Intel 2100. You need to check the device manager. Right click on My Computer, select Manage and look for Device Manager. It may be, that if you never got it to work except for the Belkin PCMCIA card that it was wireless enabled without the card. Surely your IT guys would have seen that.

Now to the R51. The Intel 2200 is known to work. Get the latest drivers for it. Also get Access Connections V3.7. Explode these drivers and look carefully where they go in C:\Drivers. I put my explodes in C:\Drivers\WinXPP\ACCONWIN or WLLANATH or such like. You get the picture and just know where they are.

Uninstall Access Connections completely (profiles and all). Go to Device Manager and uninstall the wireless NIC. When it restarts, if it is looking for a driver, point it to C:\Drivers\... where you exploded the wireless driver download. If it doesn't ask, go to that Drivers location and run the setup program (usually setup.exe). If it restarts, let it. Then install Access Connections. Go to the Drivers folder and run the appropriate setup program.

At this point Access Connections should have disabled Windows Management (it always does for me) but it won't and should not disable Wireless Zero Config. Set up a Wireless Profile with the correct WEP key, and you should get a connection.

If you have no other modern software firewall, make sure the Windows Firewall is not getting in the way. Disable it to test, and then configure it for safety when working.

Learn to run a Command prompt (Start->Run->CMD) and use the ipconfig command to determine what IP you are getting. That kind of info is helpful here.
... JD Hurst

[Dutch]

oop, you're right--I gave you the wired card. The T41's wireless is Intel Pro/Wireless LAN 2100 3B Mini PCI adapter.

I will follow your instrux, JD (tonight/tomorrow), and report back. Two questions:

1) given the installing and unstalling that went on yesterday (lots of files), and the fact that I've not really loaded up any of my software on this machine yet, do you think it would be a good or a bad idea to run IBM Rescue and Recovery to return the machine to its original state before I run the operations you suggest? Or is that process deadly and ill-advised?

2) just so I'm clear, what should the WZC settings be (after I do all the updating we're talking about)?

THANKS again, JD.

Dutch

[jdhurst]

On the T41, I never had any luck with the Intel 2100 and junked it.

On Wireless Zero Config. It is an automatic service. It is running on my T41 (Atheros NIC) and running on my IBM Desktop (no wireless at all). I would not try to configure it.

On rebuilding. If you have just started, it may be a good idea to try again by starting again. Then if wireless doesn't work, try IBM again.

... JD Hurst

[Dutch]

Well, I did the restore and updated to Access Connections 3.7. I didn't update the driver because the one I have is the latest. At first, I wasn't getting a connection at all. Finally, tonight, I thought of changing the WEP key (i.e., set up a new one). I did that, and I released and renewed the DHCP while I was in the router. Then I restarted computer, got a connection easily, and was able to pull up the web for about 2 minutes. Then I lost the web, but the connection/association were still strong as you like. I haven't been able to get the web back. So, now it's "connected" and "associated," but I have no internet connection.

[Dutch]

newsflash:
I updated the firmware for my router, rebooted all, and I've been enjoying a stable internet connection now for half an hour or so. Maybe that was the final piece... fingers crossed and knocking on wood in Cinci.

thx,
Dutch