2nd NIC produces duplicate name on network

I applied the following patches to my windows 2000 server on 5/10
KB890830 and KB913580. after they were applied and system rebooted, my 2nd
NIC caused the system to think a duplicate system was on the network.

Any ideas as to why that may have happened?

Well the articles aren't that relevant to this. What we need to know is:
1. why 2 nics?
2. are they both the same subnet
3. how is the TCP/IP config done for both of them
4. binding order is important (NetPlaces Properties, Advanced, Advanced
Settings)
5. does the DNS and WINS services have old or rougue entries for this
machine
6. only one nic should register itself with DNS (bottom of the dialog box of
TCP/IP, Properties, DNS).
7. Only one nic should have WINS server IP#s entered into the TCP/IP config.
(same nic that does register with DNS).
8. There are probably more things, but this is all I can list without
knowing more.

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com


"BookerW" <(E-Mail Removed)> wrote in message
news:542450F9-8216-4709-80C1-(E-Mail Removed)...
> I applied the following patches to my windows 2000 server on 5/10
> KB890830 and KB913580. after they were applied and system rebooted, my
2nd
> NIC caused the system to think a duplicate system was on the network.
>
> Any ideas as to why that may have happened?