Home All Groups Group Topic Archive Search About

Does XP SP3 break wireless?

Author
22 Jun 2009 2:15 PM
mark@no.spam
Hi,

I'm having a problem with both a Netgear WG311 V3 and a Linksys WMP54G v4.1
wireless cards on a XP Pro SP3 PC, where they can see, get a strong signal
from, and connect to the router with WPA2 PSK AES encryption, but fail to get
an IP address despite numerous repairs, IPCONFIG/RELEASE/RENEWS, etc.

The Netgear card is out of warranty, so I did not get far with Netgear tech
support.

Linksys engineering, however, said flat out that the problem is due to SP3,
and they do not have a fix for it as of yet.

When the Linksys wireless monitor cannot connect, it displays a specific
error message: "the internet cannot be found". When I google that as a
phrase, I'm finding many other complaints about this.

I'm surprised. Here we are over a year since SP3 was released, and there
still is no fix?

While I await further info from Linksys, is Microsoft aware of this, and do
they have any fixes or a way of troubleshooting this to determine what
exactly the problem is?

Thanks in advance.

Author
22 Jun 2009 6:29 PM
Anteaus
SP3 doesn't break wireless, in fact it adds some extra functionality.

I'd guess that what has happened here is that the Netgear management-app
replaces msgina.dll or suchlike, and the SP update puts the genuine one back.
After which the third-party app will no longer work. 

Have you tried disabling the Netgear app, and using the MS-supplied 
Wireless Zero Confguration applet?

http://www.ifelix.co.uk/tech/2007.html

Don't omit to stop the Netgear/Linksys app first, or the two will conflict.

Show quoteHide quote
"mark@no.spam" wrote:

> Hi,
>
> I'm having a problem with both a Netgear WG311 V3 and a Linksys WMP54G v4.1
> wireless cards on a XP Pro SP3 PC, where they can see, get a strong signal
> from, and connect to the router with WPA2 PSK AES encryption, but fail to get
> an IP address despite numerous repairs, IPCONFIG/RELEASE/RENEWS, etc.
>
> The Netgear card is out of warranty, so I did not get far with Netgear tech
> support.
>
> Linksys engineering, however, said flat out that the problem is due to SP3,
> and they do not have a fix for it as of yet.
>
> When the Linksys wireless monitor cannot connect, it displays a specific
> error message: "the internet cannot be found". When I google that as a
> phrase, I'm finding many other complaints about this.
>
> I'm surprised. Here we are over a year since SP3 was released, and there
> still is no fix?
>
> While I await further info from Linksys, is Microsoft aware of this, and do
> they have any fixes or a way of troubleshooting this to determine what
> exactly the problem is?
>
> Thanks in advance.
>
Are all your drivers up to date? click for free checkup

Author
23 Jun 2009 1:01 AM
Jack-MVP
Hi
Try it with WPA, these are rather old chipsets, it might be that the newest
rendition of WP2 (WPA+AES) does not work with them.
For normal private use WPA is adequate security.
Jack (MS, MVP-Networking)

Show quoteHide quote
"mark@no.spam" <mark@no.spam@discussions.microsoft.com> wrote in message
news:CDE40C44-12B7-4068-88EE-F9E4986053B1@microsoft.com...
> Hi,
>
> I'm having a problem with both a Netgear WG311 V3 and a Linksys WMP54G
> v4.1
> wireless cards on a XP Pro SP3 PC, where they can see, get a strong signal
> from, and connect to the router with WPA2 PSK AES encryption, but fail to
> get
> an IP address despite numerous repairs, IPCONFIG/RELEASE/RENEWS, etc.
>
> The Netgear card is out of warranty, so I did not get far with Netgear
> tech
> support.
>
> Linksys engineering, however, said flat out that the problem is due to
> SP3,
> and they do not have a fix for it as of yet.
>
> When the Linksys wireless monitor cannot connect, it displays a specific
> error message: "the internet cannot be found". When I google that as a
> phrase, I'm finding many other complaints about this.
>
> I'm surprised. Here we are over a year since SP3 was released, and there
> still is no fix?
>
> While I await further info from Linksys, is Microsoft aware of this, and
> do
> they have any fixes or a way of troubleshooting this to determine what
> exactly the problem is?
>
> Thanks in advance.
>

Bookmark and Share