Re: How do you recover an SBS2003 server with a failed internal NIC

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

A Month? Really? Good thing this was a test. It would be a long time to
keep a production server off line.

(somewhat kidding, I know Jamie had other things to do in the meantime, and
I am glad he posted the solution)

Still interested in why one could not/should not recreate the proper
assortment of nics and restore.

Or are we saying that once booted, expand the device list for hidden
devices, remove the failed nic and replace with identical settings, run the
CECIW and all will be well?

Although nic failure is rare, it is not unheard of, and with lightning,
other electrical problems and device lifetime bell curves, it would seem to
be a potential problem in need of a ready solution. Add that one cannot
really tell that the nic(s) have failed until the OS has started?

--
Regards:

Anna Clark
-----
Please do post the conclusion or solution
to your issue so that others may benefit.


"SuperGumby [SBS MVP]" <not@xxxxxxxxxxx> wrote in message
news:eacc4irPHHA.448@xxxxxxxxxxxxxxxxxxxxxxx
glad to be of service and glad it's sorted.

also good to hear the feedback, tks. Note to other readers: it's good to
hear feedback both when it works and when it doesn't.

"Fisheye" <support@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:e6w8k5oPHHA.3544@xxxxxxxxxxxxxxxxxxxxxxx
Great. We got is sorted. Basically exactly what you are saying about the
uninstallation of hidden devices and loopback device. Allowed us to
remove
the faulty card, and add the new one in.

Thanks for the backup on this!
Jamie

"SuperGumby [SBS MVP]" <not@xxxxxxxxxxx> wrote in message
news:ulbVUW7IHHA.448@xxxxxxxxxxxxxxxxxxxxxxx
I'm not sure of recovery in your situation, I expect it possible but
you
have further complicated your situation by the steps you have taken.


but where can you go?
1st, I think your remediation steps mean you should continue with the
single NIC for now, throwing another NIC at it now may just confuse
things further.
IS ISA involved? If so, remove it. ISA is gonna be confused, installed
in
firewall mode but now having only a single NIC.
Check the binding of services. Are DHCP and DNS bound to the NIC?
(setting such services to 'all interfaces' may help)
DNS forward and reverse lookup zones. Explore the whole tree, are all
references to the existing IP framework?
You know the various IP ranges of the NICs during change, search the
registry for references to them. CAREFUL about what you change.

Device manager, are all references to the previous NIC gone?
set devmgr_show_nonpresent_devices=1
start devmgmt.msc

then 'show hidden devices' in the console

Tidy it up as much as possible then again run 'change server IP' and
CEICW.

Time to clear and SAVE the logs, restart.

I then go into 'holistic' mode with the event logs and eventid.net.
Look
at the logs and start looking up articles. You're not looking to
resolve
each error individually, you want to read up on the cause(s) of as many
errors as you are comfortable tracking, looking for similarities,
patterns, across the errors.



"Fisheye" <support@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:%23Eu98A7IHHA.1280@xxxxxxxxxxxxxxxxxxxxxxx
Hi all,

We have just had an experience on our test network (2 NIC's, SBS2003
SP1
Prem) where the internal network card was removed the the server was
booted back up.

What happened was when the server booted, it let the external network
card assume the role of the internal card.
However, the external card has a static IP address, and this messed up
all of the routing.

CIECW was run, along with the Change server IP wizard, which did get
the
server in to a semi working state.

However, AD and group policy can not be accessed any more.

Some documentation for disaster recover of this type was found
relating
to Server 2003 with ISA, but not SBS2003.

We are not in a critical state, as we have backups and this is a test
network.
But we have no solid recovery solution for this situation in SBS.

Has anyone worked on this issue before? Any references or guides which
may help you could suggest?
Tips of what to look for?

Thanks in advance!
-Jamie









.

Relevant Pages

  • Re: How do you recover an SBS2003 server with a failed internal NIC
    ... start and having seen the state of a server ... You know the various IP ranges of the NICs during change, ... Prem) where the internal network card was removed the the server was ... CIECW was run, along with the Change server IP wizard, which did get the ...
    (microsoft.public.windows.server.sbs)
  • Re: How do you recover an SBS2003 server with a failed internal NIC
    ... for the server. ... You know the various IP ranges of the NICs during change, ... We have just had an experience on our test network (2 NIC's, ... CIECW was run, along with the Change server IP wizard, which did get the ...
    (microsoft.public.windows.server.sbs)
  • Re: How do you recover an SBS2003 server with a failed internal NIC
    ... Yes, once booted, expand hidden devices, uninstall missing/dead/offline ... NICs, Shutdown and fit new NICs, Give the new NIC's the IDENTICAL ... This situation happened in the first place, because we had a test server ... CIECW was run, along with the Change server IP wizard, which did ...
    (microsoft.public.windows.server.sbs)
  • Re:(offtopic) How do you recover an SBS2003 server with a failed internal NIC
    ... Yes, once booted, expand hidden devices, uninstall missing/dead/offline ... NICs, Shutdown and fit new NICs, Give the new NIC's the IDENTICAL ... This situation happened in the first place, because we had a test server ... Tidy it up as much as possible then again run 'change server IP' ...
    (microsoft.public.windows.server.sbs)
  • Re: How do you recover an SBS2003 server with a failed internal NIC
    ... Yes, once booted, expand hidden devices, uninstall missing/dead/offline ... NICs, Shutdown and fit new NICs, Give the new NIC's the IDENTICAL settings, ... change server IP and rerun CIECW. ... references to the existing IP framework? ...
    (microsoft.public.windows.server.sbs)