Discussion Locked

Removing/changing a NIC

0 helpful
12 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have changed/replaced different types of cards (video, sound, capture) without loosing or reinstalling Win OS. But for NIC, a had to reinstall Windows each and every time. There is no other possibility?
The network config is simple: MS client andTCP/IP, static address. To change the NIC, I would delete the protocol, the client and the NIC. Shut down the system. Replace the NIC, installing the new drivers (Win prompts for the new hardware). When configuring the client and the protocol, thereare the following:
- in the protocol section, at the IP Address there is nothing (as it should be). But, at the DNS there are the old settings;
- in the client identification, the old values, again.
Now, not that the above values would not be usefull but, should those fields not be empty (there is a new driver).
Still, the computer does not connect to the network, even the NIC and the switch communicate.
Thank you for any help.

12 replies

by stillatit

You should NOT have to reinstall the OS, but you will need the CD (or files) to reinstall drivers.

The old settings stick around because they are stored in registry entries, which do not get deleted when you delete the protocol.

By the way, itis NOT necessary to do it the hard way. You can change the card first, add the drivers for the new card, then delete the drivers for the old card. This avoids having the tcp/ip and MS client going away and having to be reinstalled.

When you startputting in the new settings, in the tcp/ip properties sections, check for a pull-down box marked "Adaptor" (in NT). Make sure your new card is selected before you start putting in numbers. In Windows 9x, you will see entries for protocol -> adaptorpairs -- select properties for the correct set.

When you click OK, you should be asked for the CD and the driver database should be updated.

After you reboot, check the device manager to see the status of the network card. Select its properties to check drivers, etc.

Tests for tcp/ip:
a) Ping 127.0.0.1 -- tests protocol stack
b) Ping your station by IP
c) Ping the default gateway

Note -- if your machine is really attached to a switch rather than a hub, you may have to do some magic to the switch so that it realizes that the MAC address for your station changed. (Depends on switch.)

Good luck.

by angsax

Have you tried doing all you've tried and then fully rebooted the PC (to completely remove drivers/registry entries.

Stillatit is correct I think. We have had some NIC cards that have stuff hanging around after removal. Also, if you're using NDS for connectionto Novell servers, you need to be careful when removing that protocol and should do so first.

by michael.spellman

If you remove the stack and all the other associated drivers you are left with nothing ...or so you thought ...I have had this before and very frustrating it is ...try running a utility called regclean after removing these settings from windows Makethe regclean disk bootable and run this before booting into windows

by wgonzlez

Some NICs need some software installed before hardware installation be performed. Did your NIC bring a CD and documentation?

by skutts

If you are connected to a switch, rather than a hub, you may need to set the card to use full duplex mode (advanced properties of the card). Also check the media type while you are there (I always hard code the speed to either 100BaseT or 10BaseT dpeneding on the hub/switch. I have had all sorts of problems with the auto-select option)

Hope this helps

Skutts

by vfrunza

The problem was solved as follow:
- for Win 98 it was almost simple, removing the protocol, client and old NIC's drivers. After restarting twice the system, I was able to install and work with the new NIC;
- for Win 95, it was as I said: I had to reinstall from scratch the OS. I think, on the other hand, that removing all the cards (less the video) will allow one to use the new NIC.

This discussion is closed to new replies.