You replace an integrated 10-Mb Ethernet adapter with a new 100-Mb PCI adapter on Windows 2000 Server. After reboot, System log errors say the new adapter is missing or not working. What should you do to resolve hardware conflict and ensure the new adapter initializes?

Introduction / Context:
When adding a new PCI network adapter to replace an onboard NIC, Windows may still enumerate and load the original adapter. This can cause resource conflicts, binding confusion, or drivers competing for the same role, resulting in “missing/not working” errors for the new device. The safest fix is to disable the onboard adapter cleanly.

Given Data / Assumptions:

• Integrated (onboard) 10-Mb NIC remains present.
• New 100-Mb PCI NIC is installed.
• System reports the new adapter is missing/not working.
• Goal: initialize the new NIC, avoid conflicts.

Concept / Approach:
Disabling the onboard adapter in Device Manager prevents Windows from loading its driver and competing for resources. Removal attempts can be reversed by PnP on the next boot; outright file deletion from driver cache is risky and unnecessary. A new hardware profile won’t resolve a persistent resource/binding conflict. The clean, supported approach is to disable the device (or turn it off in BIOS), then verify the new adapter's driver and bindings (TCP/IP, client for Microsoft Networks, file and printer sharing).

Step-by-Step Solution:
1) Open Device Manager and expand Network adapters.2) Right-click the onboard NIC → Disable.3) Confirm the PCI NIC shows as working; install/verify correct driver.4) Rebind protocols/services to the new NIC; verify link, IP configuration, and connectivity.

Verification / Alternative check:
Check Event Viewer for cleared errors; confirm “Media State: connected,” valid IP, and successful ping/SMB access. Optionally disable in BIOS for permanent deactivation.

Why Other Options Are Wrong:

• Create a new hardware profile: Does not remove the conflict.
• Remove device: Windows may re-detect and reinstall the onboard NIC on reboot.
• Delete driver files: Unsupported and risky; may break future reinstall or rollback.

Common Pitfalls:
Leaving both adapters enabled without clear binding order; deleting system driver caches causing repair installs.

Final Answer:
Use Device Manager to disable the integrated 10-Mb Ethernet adapter