Can't connect wirelessly (Limited or no connectivity)

Message

Vasant56 · #1 Post by **Vasant56** » Sun Jul 24, 2005 3:50 pm

Hi,
I've been trying to connect to several wireless networks, and every time I connect, I have trouble aquiring the network address (and thus get limited or no connectivity), I haven't had problems connecting to these networks before, and other computers are working okay. I have tried updating my drivers, however, the problem still persists.. This initally happened yesterday, and I've tried all the standard practices to fix my connection (rebooting, repairing, re-enabling/disabling).

I have a T42 /w1.7ghz Dothan, 512mb of Ram and an 2200 b/g card.

Does anyone know a remedy to this problem?

Thanks you

Ground Loop · #2 Post by **Ground Loop** » Sun Jul 24, 2005 4:20 pm

Make sure you have only one wireless manager running -- either the Windows (Zero Config?) service, OR the IBM Connection Manager.

If you run both, they will fight.

Even with just the IBM service running, I sometimes see a stray taskbar icon that is stuck in "Aquiring address" even though the network is working just fine.

Overall, I'm surprised to find that I like the IBM Connection tool much better than the XP default wifi manager.

Vasant56 · #3 Post by **Vasant56** » Sun Jul 24, 2005 7:04 pm

Hi,

As I generally don't use access connections I uninstalled it, but I still seem to be getting limited or no connectivity in my wireless connection.. Is there anything else I can try?

wwarlock · #4 Post by **wwarlock** » Sun Jul 24, 2005 9:06 pm

Ya there are a few things you can try I dont know what configuration you have so I am going to go over a few.

1 you may have a bug or a spyware program running so get rid of those buy using norton or what ever virus tools you have. next use ad-aware you can get it free off the net. I also like using Hijack this but be carfull when using this you can really mess things up.

2 you may just have a stuck wifi the best explination I can give you. it is when your wifi thinks it is working and thinks it is connected but is not. like 2 things trying to use the same port. try to shut down restart then remove your wifi router from the list then try to find it again.

3 winsock error. you will have to do a serch for "fix winsock" and run that program to fix your windsock.

4 you will need to do a full network reconstruction. you will need to go into your wirless conection remove everything in there. then go into your control panels go to network and remove just your internet protocalls. shut down then hope xp will redetect everything if not you will have to manually put it all back.

Hope this helps.

If someone knows another way please let us know.

William

Rod1105 · #5 Post by **Rod1105** » Sun Jul 24, 2005 9:11 pm

I had a similar problem and ended up going through the network wizard to recreate the connection. That seemed to fix the problem but a number of things can cause this to happen. Try that. I would also be careful about updating the latest drivers for the Intel adapter (2200 I believe) - I had problems with the latest ones and rolled back to the 8.x series to clear it up.

#6 Post by **carbon_unit** » Sun Jul 24, 2005 9:20 pm

Are you running any kind of firewall? Norton Internet security or McAfee firewall?
If so try temporarily disabling it and see if you can connect.

lanbaba · #7 Post by **lanbaba** » Tue Jul 26, 2005 2:11 am

Agree with Rod1105, try rolling back the wireless driver.

#8 Post by **GomJabbar** » Tue Jul 26, 2005 6:02 am

Just some thoughts.

(1) Remove power from the router to let it power off, then plug the power back in. Reboot your laptop, and see if it will connect.

(2) Turn off or disconnect all other computers on the network. Reboot your laptop, and see if it will connect.

(3) Go to the following driver matrix page and download the readme text files for your wireless driver. Even though you aren't currently using Access Connections, you might want to download that text file too. There are things you can check that are listed in the above files if you read them carefully.

(4) wwarlock has some good ideas. You could have a corrupted winsock.

(5) I have a T42 with the 2200BG adapter. I use the latest ver. 9.0.1.21 driver from IBM/Lenovo's website, along with IBM Access Connections ver. 3.71. Contrary to some others here, this has been the best driver/software setup for me. Access Connections has a choice to set the power level of the adapter card, when you set up a profile. If you are in an area where you need a stronger signal, you can chose a different power level. While my setup worked pretty good as first set up, I found that I have the most reliable connections with my home router by using manual TCP/IP settings (IP address, etc.).

Go to the driver matrix page by starting here:

http://www-3.ibm.com/pc/support/site.ws ... date=false

Vasant56 · #9 Post by **Vasant56** » Wed Jul 27, 2005 5:13 pm

Hi,

I removed the wireless adapter from my network connections, and rebooted. It detected, and reinstalled the device (although as Wireless Connection 2). Everything is working fine now, though.

Thanks for the help.

Can't connect wirelessly (Limited or no connectivity)

Can't connect wirelessly (Limited or no connectivity)

Who is online