Replacing Network card on primary DC / DNS server

I am running Windows 2003 Advanced Server. It is the PDC and also acts as the
DNS server. I wish to upgrade its existing NIC to a new GB NIC but keep all
the TCP/IP info the same. The old NIC is embedded into the motherboard. I
tried to install the new one and disable the old one, got an error that there
was an IP address conflict and the new NIC didn't work.

How do I do this? Thanks in advance.

"imobius" <(E-Mail Removed)> wrote in message
news:A6062B35-2267-4316-A212-(E-Mail Removed)...
> I am running Windows 2003 Advanced Server. It is the PDC and also acts as
the
> DNS server. I wish to upgrade its existing NIC to a new GB NIC but keep
all
> the TCP/IP info the same. The old NIC is embedded into the motherboard. I
> tried to install the new one and disable the old one, got an error that
there
> was an IP address conflict and the new NIC didn't work.
>
> How do I do this? Thanks in advance.

A few preliminary ideas -- if you Disable or Uninstall
the old NIC you will be able to avoid it -- and anytime
it tries to re-install just decline.

You can always go in a strip out the IP info for that
NIC -- easiest would be to just making it Automatic
and that (initially) erases pretty much everything.

BUT, most such hardware has a BIOS setting that
will disable onboard devices like such NICs.

Finally, I believe that error message on configuring
the IP can be bypassed if you JUST INSIST but you
have to read that Message Box carrifully since it
says something almost the opposite of what it seems
to say on Ok or Cancel.

Still you should remove the other IP settings, and even
the NIC if possible.

--
Herb Martin

"Herb Martin"
> "imobius"
> > I am running Windows 2003 Advanced Server. It is the PDC and also acts
as
> the
> > DNS server. I wish to upgrade its existing NIC to a new GB NIC but keep
> all
> > the TCP/IP info the same. The old NIC is embedded into the motherboard.
I
> > tried to install the new one and disable the old one, got an error that
> there
> > was an IP address conflict and the new NIC didn't work.
> >
> > How do I do this? Thanks in advance.
>
> A few preliminary ideas -- if you Disable or Uninstall
> the old NIC you will be able to avoid it -- and anytime
> it tries to re-install just decline.
>
> You can always go in a strip out the IP info for that
> NIC -- easiest would be to just making it Automatic
> and that (initially) erases pretty much everything.
>
> BUT, most such hardware has a BIOS setting that
> will disable onboard devices like such NICs.

Yes, but still the setting are in the registry. And this is what Windows is
really complaining about. (Even if the NIC is no more physically present.)

> Finally, I believe that error message on configuring
> the IP can be bypassed if you JUST INSIST but you
> have to read that Message Box carrifully since it
> says something almost the opposite of what it seems
> to say on Ok or Cancel.

Actually I ran onto such a situation. One of our DC plainly failed
(motherboard) and we had to swap the disks with the disks for another
(spare) server.
The trouble was that we were not able to define the proper IP address. And
there was no way to get around that error message.

The solution ought to be to remove the device from the device manager, but
since it was not the same hardware, it was not shown.
And since the motherboard was dead, we couldn't plug back the disks on the
former computer.
:-)

The solution I designed was to use the following trick
(http://www.microsoft.com/resources/d...ll/reskit/en-u
s/Default.asp?url=/resources/documentation/Windows/XP/all/reskit/en-us/prdh_
dmt_lhfg.asp) to display the hidden devices in device manager and to remove
the former NIC from the Windows's "memories".

> Still you should remove the other IP settings, and even
> the NIC if possible.
That is :
- disable in the bios,
- and then, remove from the device manager.

--Richard.

A Repair Install will usually fix such problems.


--
Herb Martin