Unable to change tcpip settings after disaster recovery

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi,
I have been toying with disaster recovery to document full procedures for my clients. I have found that when doing a disaster recovery to new hardware the tcpip stack goes south. I can change the address details etc. but when I go back to look atthe settings it says it is all configured using dhcp. I have found this is not an issue (it is an issue but the server still functions normally) unless the server is multi-homed eg. SBS 2k server. On a multi-homed server, the only address details that are kept are the last ones entered. The other adaper(s) just have dhcp addresses. I can't remove tcpip because the servers are DC's. I have tried re-applying the service packs and cleaning out the registry hives from the info for the nic's from the previous hardware to no avail.

I'd be grateful for any assistance.

Derek
 
Actually what you are seeing is just a Network Shell Gui issue.

You can remove the TCPIP Stack on a DC, it's just a point in the butt. :(

299451 HOW TO: Remove and Reinstall TCP/IP on a Windows 2000 Domain
Controller
http://support.microsoft.com/?id=299451

This article works great, just make sure you don't skip a step.
--

Brian Oakes

This posting is provided "AS IS" with no warranties and confers no rights.
Please reply to the newsgroup so that others may benefit.
Derek said:
Hi,
I have been toying with disaster recovery to document full procedures for
Click to expand...
my clients. I have found that when doing a disaster recovery to new hardware
the tcpip stack goes south. I can change the address details etc. but when I
go back to look atthe settings it says it is all configured using dhcp. I
have found this is not an issue (it is an issue but the server still
functions normally) unless the server is multi-homed eg. SBS 2k server. On a
multi-homed server, the only address details that are kept are the last ones
entered. The other adaper(s) just have dhcp addresses. I can't remove tcpip
because the servers are DC's. I have tried re-applying the service packs and
cleaning out the registry hives from the info for the nic's from the
previous hardware to no avail.
 
If it is just the gui shell, then why am I unable to make/save changes to
the second card? I have set the addresses to both cards in the registry, but
always the first card configured reverts to dhcp even though dhcp was turned
off for the card. (TCPIP settings for the registry were copied from the
original server adjacent - by copied I mean manually enetered into the
relevant sections. Importing the settings with regedit just populates the
wrong hives because the nics are different).

I'm pretty sure that re-installing tcpip should fix the problem, I just find
it hard to understand that on 2 text-book disaster recovery scenarios I am
having the same problem. I followed the microsoft supplied guide for
disaster recovery to different hardware and everything was sweet except for
tcpip.
 
Back
Top