Attn: Quaoar

[RFL]

Your recommendation didn't work...please see below. Can
you suggest anything else?

Also, I have another issue where I can't roll-back the
system restore to a date prior to loading SP2, nor can I
do an uninstall as SP2 does not appear in the Add/Remove
area.SBC is my DSL provider. There is an inherant problem

connecting wirelessly to the 2Wire modem once SP2 is
installed. SBC/Yahoo has no solutions. They have no
suggestions other than contacting the PCI card
manufacturer (NetGear) to see if they have a propritary
Client Mangaer utility to bypass the MS Client Manager.
Does MS have a patch for this problem which is resident
with the SP2 patch?

I've run ipconfig /all and get a "media is not
connected".I've installed the newest driver version for
the Netgear PCI firware which did not fix the problem.
I've diabled the WEP encryption and this as well, did not
fix the connection problem.

Perhaps this is MS's solution to eliminate any unwanted
hacker intrusion...I guess if i can't connect to the web
then I'm not at risk of getting a virus or worm. Good Job
MS, System Secured!

Open TCP/IP properties for the wireless, on the General
tab, select
Advanced, Options tab, TCP/IP filtering properties, check
that Permit
All is checked. Otherwise, you will not connect to
squat. You do have
a firewall operating?

Q"



"

 

[Quaoar]

Your recommendation didn't work...please see below. Can
you suggest anything else?

Also, I have another issue where I can't roll-back the
system restore to a date prior to loading SP2, nor can I
do an uninstall as SP2 does not appear in the Add/Remove
area.SBC is my DSL provider. There is an inherant problem

Take a look at KB884020. SP2 has for whatever reason, limited
connecting to any loopback address to *only* 127.0.0.1, and any
communication service, device, etc., that formerly used any other
127.0.0.X address is now broken. This includes Citrix Metaframe clients
(for anyone trying to figure out why their Metaframe is broken).

Ask your DSL ISP if they use any loopback addresses in the 127.0.0.X
range other than 127.0.0.1. KB884020 will fix this but requires a call
to MS support who will supply a patch to SP2 if you can justify the
patch.

http://support.microsoft.com/default.aspx?scid=kb;en-us;884020&Product=winxp

Q