Wireless on WinXP Pro honked up by SP2

JoeM · 03-23-2005

My wireless network connection was working fine until I installed SP2 for WinXP Pro. Since then it has been flakey even though it shows maximum signal strength. When I boot up or restart the computer it connects fine. If I disable and enable the wireless connection it fails when trying to obtain an IP address. It also fails the same way if I try a repair. If I restart the computer, it connects successfully. If I hibernate the computer it reconnects successfully if it was connected before the hibernation, but it fails if it had a problem before the hibernation. I also have increased problems connecting to other access points.

Any ideas on what's happening and how I might go about fixing it?

Is this the right place to ask this question?

My laptop is a Dell Latitude C610 with a Dell True Mobile 1150 mini PCI card (802.11B -- I believe that this is an Orinoco Gold). The BIOS is A16 (latest at Dell). The WinXP Pro has SP2 and all updates pushed by Windows Update. The 1150 driver is the latest on the Dell site (I was one rev behind when I applied SP2 and started getting the symptoms). I have the SSH Sentinel 1.4 VPN client installed (to get IPSec without L2TP). I find no relevant entries in the event logs. My access point is a LinkSys WAP11 (original model) with latest firmware.

Dell tech support has not provided any ideas. I have never had a problem with a connection via my onboard wired NIC.

I have tried disabling the Windows Firewall with no change in behavior. My access point is on channel 8 without any encryption. It has a MAC access list which I have turned off with no change in behavior.

I have tried re-installing the 1150 drivers. I have "uninstalled" the 1150 and let Windows find it and reinstall it. When I updated the driver after first getting the problem with SP2, the name changed from "Wireless Network Connection" to "Wireless Network Connection 2". I still had the problem. I changed the name back to "Wireless Network Connection". I looked in the registry and found multiple entries suggesting that Windows was not removing old definitions for the wireless connection. This last time I did multiple uninstall/installs to get to "Wireless Network Connection 3" to hopefully avoid any name duplication (although I hope it just uses the GUIDs).

After a "repair" has left me a NIC with "Limited or no connectivity" I can force a connection by unbinding TCP/IP from the NIC and then rebinding it. I then get a useful connection. After I do this Windows will not let me disable the NIC. All is reset on the next reboot.

Thanks,

Joe M

wrzwaldo · 03-23-2005

WWW.MICROSOFT.COM

Dutch · 03-23-2005

Quote:

Originally Posted by JoeM

Is this the right place to ask this question?

No.

Contrary to popular belief, this isn't a general hardware/software support site.

Your problem has no relevance to the usage of Netstumbler/Ministumbler, or other similar network auditing tools.
Contact your cardmanufacturers support, and/or your operating system suppliers support.

Dutch

JoeM · 03-23-2005

Quote:

Originally Posted by wrzwaldo

WWW.MICROSOFT.COM

Would you please be a little more specific?

I have searched Microsoft (including support...) and news groups without finding a solution. I have applied KB884020 and reset winsock to no avail. I have followed MS documents on troubleshooting wireless and TCP/IP with not success. If you know of something else I would appreciate learning about it.

wrzwaldo · 03-23-2005

Quote:

Originally Posted by JoeM

Would you please be a little more specific?

I have searched Microsoft (including support...) and news groups without finding a solution. I have applied KB884020 and reset winsock to no avail. I have followed MS documents on troubleshooting wireless and TCP/IP with not success. If you know of something else I would appreciate learning about it.

Sorry, no.

JoeM · 03-23-2005

Quote:

Originally Posted by Dutch

No.

Contrary to popular belief, this isn't a general hardware/software support site.

Your problem has no relevance to the usage of Netstumbler/Ministumbler, or other similar network auditing tools.
Contact your cardmanufacturers support, and/or your operating system suppliers support.

Dutch

Sorry, I misunderstood the description "Discussion forum for non-Netstumbler wireless auditing or wireless related software".

wrzwaldo · 03-23-2005

@JoeM

The more I think about it here is what I would do.

Backup all data you want saved, format and re-install windows.

Dutch · 03-23-2005

Quote:

Originally Posted by JoeM

Sorry, I misunderstood the description "Discussion forum for non-Netstumbler wireless auditing or wireless related software".

Appearently... Discussing Wireless auditing or wireless related software depends on having a functioning setup in the first place.
Try a general hardware support site, the support options from the manufacturers of your equipment, and not to forget the trusty RTFM, in order to get a functioning setup.

Dutch

streaker69 · 03-23-2005

Your IP stack is hosed, probably due to malware.

Download HijackThis, run it and it will show you if there is something extra in your IP stack.

G8tK33per · 03-23-2005

Has this entire month been blessed with full moons? Fucking Christ! Ides of March my ass....Ides of Morons is more like it.

03-23-2005	#1 (permalink)
JoeM Registered Member Join Date: Mar 2005 Posts: 8	Wireless on WinXP Pro honked up by SP2 My wireless network connection was working fine until I installed SP2 for WinXP Pro. Since then it has been flakey even though it shows maximum signal strength. When I boot up or restart the computer it connects fine. If I disable and enable the wireless connection it fails when trying to obtain an IP address. It also fails the same way if I try a repair. If I restart the computer, it connects successfully. If I hibernate the computer it reconnects successfully if it was connected before the hibernation, but it fails if it had a problem before the hibernation. I also have increased problems connecting to other access points. Any ideas on what's happening and how I might go about fixing it? Is this the right place to ask this question? My laptop is a Dell Latitude C610 with a Dell True Mobile 1150 mini PCI card (802.11B -- I believe that this is an Orinoco Gold). The BIOS is A16 (latest at Dell). The WinXP Pro has SP2 and all updates pushed by Windows Update. The 1150 driver is the latest on the Dell site (I was one rev behind when I applied SP2 and started getting the symptoms). I have the SSH Sentinel 1.4 VPN client installed (to get IPSec without L2TP). I find no relevant entries in the event logs. My access point is a LinkSys WAP11 (original model) with latest firmware. Dell tech support has not provided any ideas. I have never had a problem with a connection via my onboard wired NIC. I have tried disabling the Windows Firewall with no change in behavior. My access point is on channel 8 without any encryption. It has a MAC access list which I have turned off with no change in behavior. I have tried re-installing the 1150 drivers. I have "uninstalled" the 1150 and let Windows find it and reinstall it. When I updated the driver after first getting the problem with SP2, the name changed from "Wireless Network Connection" to "Wireless Network Connection 2". I still had the problem. I changed the name back to "Wireless Network Connection". I looked in the registry and found multiple entries suggesting that Windows was not removing old definitions for the wireless connection. This last time I did multiple uninstall/installs to get to "Wireless Network Connection 3" to hopefully avoid any name duplication (although I hope it just uses the GUIDs). After a "repair" has left me a NIC with "Limited or no connectivity" I can force a connection by unbinding TCP/IP from the NIC and then rebinding it. I then get a useful connection. After I do this Windows will not let me disable the NIC. All is reset on the next reboot. Thanks, Joe M Last edited by JoeM : 03-23-2005 at 03:46 PM.

03-23-2005	#9 (permalink)
streaker69 Psychic Amish Stumbler Join Date: Jul 2004 Location: Virginville, BlueBall, Bird In Hand, Intercourse, Paradise, PA Posts: 12,240	Your IP stack is hosed, probably due to malware. Download HijackThis, run it and it will show you if there is something extra in your IP stack. __________________ Treat your gun like your genitals, only whip it out when it's absolutely necessary.

03-23-2005	#10 (permalink)
G8tK33per Asshole Emeritus Join Date: May 2003 Location: Goomba's Booty Boardwalk Posts: 6,128	Has this entire month been blessed with full moons? Fucking Christ! Ides of March my ass....Ides of Morons is more like it. __________________ "My mind is aglow with whirling, transient nodes of thought careening through a cosmic vapor of invention." Sons of Confederate Veterans

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

03-23-2005	#2 (permalink)
wrzwaldo I amuse you? Join Date: Dec 2003 Posts: 9,147	WWW.MICROSOFT.COM

03-23-2005	#7 (permalink)
wrzwaldo I amuse you? Join Date: Dec 2003 Posts: 9,147	@JoeM The more I think about it here is what I would do. Backup all data you want saved, format and re-install windows.