Member Avatar for drblbaqker

I am replacing a Gigabyte mb with one by MSI. Seems like the last time I did this I had to boot in safe mode and edit the registry to remove some lines related to hardware drivers. Such a long time ago, I can't remember what I removed.

Seems like I should be able to do about the same thing in Device Manager. Both boards use the same chipset so there should not be too many conflicts.

Thanks in advance for any help.

B

  • 2 Contributors
  • 5 Replies
  • 211 Views
  • 1 Day Discussion Span
  • Latest Post Latest Post by Catweazle

Dani AI

Generated

Good work by for doing the safe‑mode driver cleanup that recommended — that usually prevents chipset/HAL conflicts after a motherboard swap. Because you can ping IP addresses (router and Internet) but not hostnames, this is almost certainly a name‑resolution (DNS) problem rather than a low‑level NIC or routing failure.

Quick, focused checks to run from a command prompt (Windows 2000):

ipconfig /flushdns
ipconfig /displaydns
ipconfig /registerdns
nslookup google.com    <-- shows which DNS server is being queried
nslookup google.com 8.8.8.8

If nslookup to a public DNS (for example 8.8.8.8) returns addresses but the plain nslookup google.com does not, the PC’s configured DNS server is wrong or the DNS Client cache/service is confused. Also try net stop dnscache and net start dnscache (administrator) to restart the DNS Client service, or restart the machine.

Checklist of practical steps that tend to fix this after a board swap:

  • Verify the adapter’s TCP/IP properties: confirm the DNS server entries (if static IP is used) or set them temporarily to 8.8.8.8/1.1.1.1 to test.
  • Inspect the hosts file (C:\WINNT\system32\drivers\etc\hosts) for bad entries.
  • Ensure the router’s DNS/forwarder settings are correct (the router can be the DNS forwarder for NAT setups).
  • In Device Manager use View → Show Hidden Devices and uninstall any ghost/old NIC entries, then reinstall/update the NIC driver.
  • Check for third‑party firewalls or LSPs that might intercept DNS and remove/reinstall them if present.

Typical root causes after a motherboard change are stale resolver cache, a mis‑applied static DNS entry, or a leftover network binding. The steps above resolve those in most cases.

Recommended Answers

All 5 Replies

Member Avatar for drblbaqker

Thanks for the feedback Cat. My system has W2k so I am not really concerned about authentication issues as with XP.

It just seems to me that there are some drivers specific to the olf MB that should be removed. Then the OS can just redetect the MB. I have the W2k install files in a directory on c:\.

Let me know if you have any other ideas.

Thanks,

B

Member Avatar for drblbaqker

Thanks again Cat. I had muddled through before I read your post. Basically, I went into safe mode and removed every hardware driver I could find.

Everything is working great except the LAN. For some weird reason I can ping the network, the router as well as IP addresses on the Internet. I cannot ping a domain name which tells me there is a DNS problem. (I will post this in the networking thread in case someone can give me some help.)

I have removed/reinstalled the Nic, updated the driver, tried multiple DNS settings (I use a static IP with a cable modem and NAT router). It is mind numbing. Tried both IE and Netscape.

Part of the price for cooking your own PC I guess.

Thanks again.

B

Member Avatar for Catweazle

Glad to hear you've got the motherboard changeover issue sorted out.

I'll mark this topic as solved. Good luck with the network issue.

Cheers.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.