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



Hi Jamie, Hi Super

This looks like a lot of work for a problem that is bound to happen to
others, perhaps even me :-(.

What would happen if one installed a new nic, set up the nic and the router
as it was before the incident, and restored from backup?

Either immediately after the event or now.

Thanks for your input.
--
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: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.

I expect the first indicator of error would have been a long startup time
for the server. Seeing this I would have suspected networking from the
start
and having seen the state (thankfully, test system) of a server where
services had 'switched' interface, known I was in for a fun time.

I would not have 'accepted' the condition and attempted to get services up
on the existing NIC, I would have left it as 'external' and either
installed
a new NIC or the MS Loopback Adapter to operate as 'internal'. This would
have been performed in Directory Services Restore Mode and I may have
interrupted that first slow reboot to get here.

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: ConnectComputer Problem
    ... I'm a little confused by your network configuration. ... Switch2 --- SBS Server ... switch has internet access all the time, the second switch has the client ... NICs ...
    (microsoft.public.windows.server.sbs)
  • Re: Still cant connect to RWW or OWA remotely
    ... laptop plugged into port on DSL router. ... service, e-mail, and RWW is available to all users on the network. ... The server is a SBS2003 SP1 Standard box without ISA, ... of the two NICs by clicking the Advanced tabs, it won't open that box, ...
    (microsoft.public.windows.server.sbs)
  • Re: Cannot browse the network after migration
    ... the cause is the multiply NICs are all enable NetBT. ... >>> browse the network. ... >>> 189101 Understanding NetBIOS Resource Record Flags ... >>> NetBIOS setting from the DHCP server. ...
    (microsoft.public.windows.server.migration)
  • Re: Still cant connect to RWW or OWA remotely
    ... The server is a SBS2003 SP1 Standard box without ISA, ... the two NICs by clicking the Advanced tabs, it won't open that box, and ... program or service is running that might use the network address translation ... Is the Modem also your Router? ...
    (microsoft.public.windows.server.sbs)
  • Re: Missing domain controller in network neighborhood
    ... (2 NICs) ... network (My Network Places> Entire Network> Microsoft Windows ... Routing and Remote access is working well. ... It's a Windows Server 2003 Standard and as of today it is ...
    (microsoft.public.windows.server.dns)