I should also mention that we had recently changed out the boot device to a
larger RAID volume, and right after CHKDSK finished Windows Activation
immediately started complaining. That's the point at which networking
appears to have broken.
Should a Windows Reactivate dialog cause networking to break until
reactivation is finished? It hasn't on other machines.
--
Will
"Will" <westes-(E-Mail Removed)> wrote in message
news:(E-Mail Removed) ...
>I have a Windows 2003 Web Edition Server on which Windows networking has
>become badly damaged. The computer refuses to ping or connect to any
>computer. ARP -A is always empty. Strangely, a sniffer run on the
>affected workstation shows no traffic. A sniffer run on the router that
>is the next hop for the computer shows it doing simple background traffic
>to the domain controller, so there is some activity there.
>
> This happened after a CHKDSK that did show some file structures
> compromised, so perhaps we have hosed some critical drivers or OS files.
> What is the best sequence for attempted recovery of damaged files?
>
> I can attempt a recovery console with a slipstreamed SP1 boot CD, but this
> would overwrite a lot of service pack files. Would it be better to
> attempt a stand alone SP2 install first? Any other ideas?
>
> --
> Will
>
|
Similar Threads
Linear Mode
