More Microsoft Bashing!
This is turning into the official Microsoft Week
of Hate, but so it goes..
A friend
called me up last evening with a problem he had with his Windows 2000 machine.
He used the Microsoft PPTP (VPN) client to connect to a Windows 2003 Server at
his office. Now, he had been doing this for a while with his XP box with no
problems. He got the client to connect, everything was groovy - until he
disconnected.
At that point, his
networking ceased to function. Just flat didn't work. Suspecting a static route
(for the VPN) was left active, he rebooted. Still nothing. Completely removing
the TCP/IP configuration, rebooting, and re-adding it didn't work either. Even
the VPN client itself didn't work any longer. We went through a bunch of things
and nothing worked.
Funny thing was a
mutual friend had the exact same problem a few days earlier. Now I use this
configuration fairly often with no troubles - but something weird was going on.
The mutual friend had to reinstall.
So
- out came the Win 2K disks. Attempting to update the system (in the hopes that
the errant files/settings would get overwritten and, hence, working again)
resulted in the wonderful situation where Windows wouldn't reinstall because the
install disk had service pack 3 on it, and his system had been updated to 4.
What a junker. So, since he had to reinstall anyway, out came an upgrade copy of
Windows XP. In went the disk, up came the error message that notified him that
this copy of Windows 2000 (a fully licensed, non-pirated version, mind you) was
not eligible for upgrading to XP.
So
now he's stuck reinstalling an old OS (Windows 2000) from scratch and all his
software. All because he mistakenly used a piece of Microsoft software. Thanks,
Bill.
Posted: Fri - January 21, 2005 at 04:51 PM