golden wrote:
> Here's a weird one. My desktop computer is connected via
> ethernet to my mn-700. Everything was working fine until
> I installed XP SP2 (WindowsXP-KB835935-SP2-ENU.exe) on
> it. It worked fine until I reboot a few times under
> SP2. All of a sudden, my network connectivity completely
> ceased to exist. When I viewed my network connectivity
> properties, I was getting getting "sent" activity but 0
> for "receieved" activity. I changed absolutely no
> settings either hardware or software to cause that. I
> verified the Cat V cable was fine by connecting it to my
> laptop (XP SP1), and connectivity was fine. So, I
> installed a new NIC on my desktop computer and I was
> still unable to detect my mn-700...no connectivity. At
> this point, I uninstalled my two nic drivers through
> device manager and reboot. Upon bootup, I received a
> friendly message stating that I must reactivate my copy
> of XP since my hardware configuration had drastically
> changed...1 NIC added? At least I had 3 days to work on
> the network problem before activation was forced, so I
> uninstalled XP SP2, upon bootup it forced me to activate
> XP...from 3 days to activate to forced activation, hmm.
> So, I had to go through the phone activation, which was
> successful.
Don't know about the rest of the problem, but I do know
that for whatever reason, the nic cards on your system
carry the heaviest weight in the calculation of whether you
need to reactivate. Perhaps nics are regarded as the least
likely to fail or be changed.
Here is a site which will give you more info than you
want to know about how Windows determines if you need
to reactivate:
http://www.licenturion.com/xp/fully-licensed-wpa.txt
Here is Microsoft's site about product activation:
http://www.microsoft.com/piracy/activation_facts.mspx
Here is the info about the nic-under "How does product activation determine
tolerance":
http://www.licenturion.com/xp/fully-licensed-wpa.txt
Dick Kistler