To All XP SP2 Upgraders:
I don't know if it has been reported before or not, but after installing
a clean Windows XP SP1 OS, I immediately ran the SP2 updater on it.
After the update I noticed the PC became VERY SLUGGISH especially with
the usage of IE.
It was acting as if the DNS couldn't resolve the IPs of the web
addresses. The downloads, once established were fine however. The issue
was to get them started!!! I would hit the same address and 8 out of 10
times it wouldn't catch on...
Anyways, after much browsing, reading people's recent issues with XP
SP2, I saw someone mentioning an article for IPSec properties. That gave
me a little bit hope and following from that I located my problem: KB#
811259: Winsock2 Corruption
I found out that systems with 2 or more network connections, when
upgraded to XP SP2 could get their Winsock and Winsock2 protocols
corrupted. Best way to determine whether or not the system has been
corrupted: msinfo32
In there if you expand Components, expand Network, and then click
Protocol, you will have ten sections under Protocol.
* If you have a third-party add-on installed, the name of the
add-on will replace the letters "MSAFD" in the list.
* If there are more than ten sections in the list, you have
third-party additions installed.
* If there are fewer than ten sections, there is information
missing. *THIS WAS MY ISSUE*
It also in the article tells you how to fix it!
Please enjoy this finding and fix for it that I compiled and I sincerely
hope that you don't encounter this. It was one annoying issue.
Aras "Russ" Memisyazici
knightmare@mse.vt.edu
Systems Administrator @ Virginia Tech
-----
NTBugtraq Editor's Note:
Want to reply to the person who sent this message? This list is configured such
that just hitting reply is going to result in the message coming to the list,
not to the individual who sent the message. This was done to help reduce the
number of Out of Office messages posters received. So if you want to send a
reply just to the poster, you'll have to copy their email address out of the
message and place it in your TO: field.
-----
