Wireless Failure after Service Pack 3

After configuring a new installation of XP at Service pack 2 Compact wireless
usb adapter (model wusb54gc) I connected to the update site to download the
patches and went ahead with sp3. Since instaling sp3, if I use the XP
configuration utility I cannot get any connection and if I use the Linksys
tool, I get a very low speed.

The only way I got this to work was deleting and reinstalling the device
driver. Needless to say I have stopped all upgrading until we can figure out
why wireless is being disrupted. Is it USB related or is it wireless?
Any suggestions would be appreciated.

Free unlimited installation and compatibility support is available for
Windows XP, but only for Service Pack 3 (SP3), until 14 Apr-09. Chat and
e-mail support is available only in the United States and Canada.

• US:
http://support.microsoft.com/oas/def...3&gprid=522131

• CA:
http://support.microsoft.com/oas/def...3&gprid=522131

• UK:
http://support.microsoft.com/oas/def...3&gprid=522131

• AU:
http://support.microsoft.com/oas/def...3&gprid=522131

• Other: http://support.microsoft.com/oas/def...spx?gprid=1173 | select
Windows XP | select Windows XP Service Pack 3

same with me. After installing SP3 (why I continue to torture myself I'll
never know) my wireless connection keeps dropping and I have to continually
"repair" the connection to get to the Internet. I've downloaded the latest
drivers fron Linksys and uninstalled and reinstalled the drivers for it 3
ways to sunday, each time resulting in lost connections. Equipment is
Linksys Wireless G, (WMP54G).

I had a similar event back about December, but after I installed the newer
driver, everything worked fine... until SP3. Anyone have any advice, besides
system restore? System restore doesn't address the issue at hand, it is a
band-aid for those who aren't willing to find a fix.

Same problem here! I downloaded service pack 3 from windows update, and after
it was installed my wireless stoped working.

Did someone managed to solve this problem?

I have a sitecom wireless network usb adapter.

thanks in advance...

I THOUGHT my problem had been solved after chatting with a Microsoft tech a
few days ago, but when I rebooted my modem and router last night, I once
again lost connectivity.

It's not happening with all wireless connections, though: The old Netgear
802.11b that I use on my spare PC has had no problems at all with SP3.

The funny thing is that my wireless device connects to my wireless router.
But when i try to acess the internet it doesnt work. Can this be a internal
security block from service pack 3 preventing the wireless connection to
access the internet?

I've searched the net with my other computer ( the one with no sp3) and it
seems a lot of people are having wireless problems after the sp3 instalation.

Free unlimited installation and compatibility support is available for
Windows XP, but only for Service Pack 3 (SP3), until 14 Apr-09. Chat and
e-mail support is available only in the United States and Canada.

• US:
http://support.microsoft.com/oas/def...3&gprid=522131

• CA:
http://support.microsoft.com/oas/def...3&gprid=522131

• UK:
http://support.microsoft.com/oas/def...3&gprid=522131

• AU:
http://support.microsoft.com/oas/def...3&gprid=522131

• Other: http://support.microsoft.com/oas/def...spx?gprid=1173 | select
Windows XP | select Windows XP Service Pack 3

I have the exact same situation, Daniel.

I see the internal SSID, and it shows up in the Wireless Zero properties.

But I can't get on to the 'Net.

I know that SP3 has "new and enhanced functionality" that does something
about "Black Hole" Router Detection and Network Access Protection (NAP).
(I know....that's so descriptive. LOL)

But I have no idea if that could be what's causing problems.

I too tried Wireless Zero, and a few other things. I also read the vague
descriptions for what changed in SP3 and wondered if the NAP is the root of
the evil, but can't seem to find what it is exactly it encompasses. Also, my
HP 1300 series All in One still prints but can't figure out why it won't scan
anymore, even after reloading the program. I haven't had this much fun sice
shoving bamboo under my finger nails and lighting it on fire. I can find no
resolution for either problem anywhere on the web.

I worked software in VA a few years back and used to cringe when our
programmers gave that same vague statement of "new and enhanced
functionality" as a description of what they changed. The "between the
lines" meant we, supporting the program, were left holding the bag explaining
to the customer all the work arounds and taking lots of aspirin. Despite my
first posting I think I'll wimp out and uninstall SP3 until MS gets their
crap in one sock. And if not, maybe buy that Apple I've been eyeing, can't be
any worse than MS. Could it?

Good Luck on the quest.

Have you seen the white paper?

<http://www.microsoft.com/downloads/details.aspx?FamilyID=68c48dad-bc34-40be-8d85-6bb4f56f5110&DisplayLang=en>

It's fairly specific about what has been added.

It's not so much what the White Paper says. Rather, this discussion is more
along the lines of what it MEANS.

There are also some other publications or KB articles from Microsoft, which
state that SP3 will "change the functionality" of some third party apps.

That's true.

But it offers no details other than to blandly say (or at least imply) that
some things that used to work just fine now won't.

I don't think there's much more Microsoft can say about third party software.
It's up to the vendors in question to advise customers of what functionality has
been lost, and to correct it - that is, assuming the problem is a bug or
incompatibility in their software.

I am on a wireless connection too with Sp3 installed.

Working fine.

This worked for me...

1. Rebuild the Winsock LSP chain. To do this, follow these steps: a. Log on
to the Microsoft Windows XP workstation as an administrator.
b. Click Start, click Run, type cmd, and then click OK.
c. At the command prompt, type the following, and then press ENTER:
netsh Winsock reset
When the program is finished, you will receive the following message:
Successfully reset the Winsock Catalog. You must restart the machine in
order to complete the reset.
If you receive this message, go to step 1d.

If you are not logged in as an administrator, you will receive the following
error message:

Unable to reset the Winsock Catalog. Access is denied.
If you receive this message, log off the computer, and then log back on by
using an account with Administrator access. Typically, the first user account
that was created has Administrator access. Then, repeat steps 1b and 1c.
d. Restart your computer.

2. Test each of your third-party programs that are known to use LSPs.
3.

Reinstall any malfunctioning third-party programs that are known to use LSPs


Lastly, I do not even know if it is relevant but, in an attempt to help the
process along, can I throw in a wild card that might, or might not, provide
some "out of the box" food-for-thought on getting this problem closer to a
resolution:

http://support.microsoft.com/kb/811259/en-us

"How to determine and to recover from Winsock2 corruption in Windows Server
2003, in Windows XP, and in Windows Vista"

If this is a waste of time, sorry, but I thought that I would give the
suggestion a go.

A couple of days after installing Service Pack 3, my wireless connection suddenly dropped out. On checking available wireless networks, my network was available but clicking connect just left the connection in a permanent loop waiting for "acquiring network address". I am using a Linksys Wireless G ADSL Gateway and a LevelOne WNC-0301 11g Wireless PCI Card. Since my other computer that did not have SP3 was still connecting to the network without problems, I think the problem may be that my LevelOne driver provided by Ralink Technology Inc - version 2.02.06.0000 (dated 2004) is not digitally signed.

I could have persevered trying to solve this problem but I took the easy option and uninstalled SP3. My computer now connects to my network again.