yohanevindra

New Member
Joined
Jun 27, 2009
Messages
2
My laptop has an Intel 3945ABG wireless card. I have used my laptop with wireless internet in uni without any problem at all. I think all the APs in uni are Cisco (Linksys).

But when I came back home this time, I have a problem with my home wireless internet. I have a Netgear WG602 v3 AP and previously I used my laptop with Windows 7 Build 7000 and there was no problem. But this time with Build 7100 there seems to be a problem.

I have set the connection to automatically connect, and when it does, it connects with "Limited Access". I then have to disconnect and reconnect. When I do that, it again comes up with the same "Limited Access" and then I can either troubleshoot or cancel.
If I click toubleshoot, it comes u saying that there's a problem with my Wireless Network Adapter drivers, Sometimes it also comes up saying there's a problem with my Local Connection Adapter.
If I click cancel, then after a few seconds it will indicate that it is connected. Is there something wrong with my AP? I jus updated the firmware for it and rebooted it.

I tried installing the lates drivers for the wireless card but that did not work.

Previously wireless has worked perfectly with it even connecting automatically as when needed.
 

Solution
It seems like you are experiencing connectivity issues with your Intel 3945ABG wireless card when connecting to your Netgear WG602 v3 AP at home after updating to Windows 7 Build 7100. Here are some steps you can take to troubleshoot and resolve the problem: 1. Check Network Settings: - Verify that your AP settings match your laptop's wireless settings. - Ensure that the SSID and security settings (WPA/WPA2 key) are correctly entered. 2. Troubleshooting Steps: - Update the wireless adapter drivers: You mentioned trying this, but you can try different versions of the drivers to see if it helps. - Reinstall drivers: Uninstall the current drivers completely and then install the latest drivers for the Intel 3945ABG wireless...
It seems like you are experiencing connectivity issues with your Intel 3945ABG wireless card when connecting to your Netgear WG602 v3 AP at home after updating to Windows 7 Build 7100. Here are some steps you can take to troubleshoot and resolve the problem: 1. Check Network Settings: - Verify that your AP settings match your laptop's wireless settings. - Ensure that the SSID and security settings (WPA/WPA2 key) are correctly entered. 2. Troubleshooting Steps: - Update the wireless adapter drivers: You mentioned trying this, but you can try different versions of the drivers to see if it helps. - Reinstall drivers: Uninstall the current drivers completely and then install the latest drivers for the Intel 3945ABG wireless card. - Reset TCP/IP stack: Open Command Prompt as administrator and run the following commands:
Code:
 netsh int ip reset reset.log netsh winsock reset
- Disable and enable the wireless adapter in Device Manager. - Run Windows Network Diagnostics: This can sometimes help identify and fix common network connection issues. 3. AP Configuration: - Check the firmware version of your Netgear WG602 v3 AP. You mentioned updating it, but ensure that it's the correct firmware version for your model. - Reset the AP to factory defaults and reconfigure it from scratch. - Check for any channel interference by using a Wi-Fi analyzer tool to see if neighboring networks are on the same channel. 4. Check Windows Update: - Make sure your Windows 7 Build 7100 is fully up to date. Sometimes Windows Updates include important driver updates that can resolve connectivity issues. 5. Other Considerations: - If possible, try connecting your laptop to a different Wi-Fi network to see if the issue persists. - Test with another device on the same network to determine if the issue is specific to your laptop or the network. Given that the issue seems to have occurred after updating to Windows 7 Build 7100, it might be worth investigating compatibility issues with that particular build and the Intel 3945ABG drivers. If none of the above steps resolve the issue, it might be worth considering rolling back to the previous Windows 7 Build (7000) to see if the problem persists.
 

Solution
Back
Top