Lester said:
Wrong, people. It's not these KB updates. I have these and
all is well. XP home on box 2, and XP pro SP2 on box 1 (used
for main networking).
Check your defrag and disk tuneup reports for problems. If
the drive is more than 20% fragmented, you could have
application errors, causing "no network access" for
browsing. I've had that before.
Ah, the fragmentation myth is alive and well I see....
For this "people", I updated, installing the 6 latest fixes, re-boot,
then no network access.
It is fairly easy to mis-apply a network setting, or to configure the
TCP/IP settings wrong, and some programs can cause that... but
Microsoft's Update clearly was the source of the problem for me.
Now, that is not to say that previously some application "was not being
nice" and munged something, and XP just "let is slide" and now that I
"updated" XP decided to "be strict" and so therefore I now have no
Internet access. (Which is pretty far-fetched but certainly not out of
the realm of possibility.) But then, who really is at fault in my case?
I *had* access. I *updated*. Access *broke*. Pretty clear dontcha
think?
These were the updates (in no order):
KB899587
KB896727
KB896423
KB899588
KB899591
KB893756
Also, it is not like MS has a great record regarding updates. Updates
have boken Windows before.
P.S.
Which clusters a program resides in on a drive has nothing to do with
how that program interacts with the OS when that program runs.
Absolutely nothing.