Ghost network card

  • Thread starter Thread starter Scott
  • Start date Start date
S

Scott

I have a 2000 server that thinks it has a network card
configured that is not physicaly in the machine. What can
I do to get rid of the record of the card. The card
(realtek 8029) is no longer around to reinstall and then
deinstall.

TIA

Scott
 
You have inserted, re-inserted, moved, removed, or swapped your NIC card
across various PCI slots without first removing it from the Device Manager.
That's a no-no. It results in a phantom NIC card evidenced when another NIC
is installed and is reported as Adapter #2.

The "Set DEVMGR..." along with "View Hidden Devices" trick may not work for
you. It didn't for me. The 'phantom' NIC card wasn't really hidden. 'Non-
present' may indicate 'yanked', maybe not.

You've got half of your networking subsystem wanting to access a now
phantom card and the other half accessing the current card in the current
PCI slot.

It's going to be messy getting the extra Local Area Connections and/or the
extra Adapters cleaned out of your registry.

I have an article that might point you in the right direction.

http://www.sacpcug.org/archives/0303/tech0303.pdf

I don't know if any of the various registry cleaners will find and clean
references to improperly removed hardware.

Brian Smither
 
-----Original Message-----
You have inserted, re-inserted, moved, removed, or
swapped your NIC card across various PCI slots without
first removing it from the Device Manager. That's a no-
no. It results in a phantom NIC card evidenced when
another NIC is installed and is reported as Adapter #2.

The "Set DEVMGR..." along with "View Hidden Devices"
trick may not work for you. It didn't for me.
The 'phantom' NIC card wasn't really hidden. 'Non-
present' may indicate 'yanked', maybe not.

You've got half of your networking subsystem wanting to
access a now phantom card and the other half accessing
the current card in the current PCI slot.

It's going to be messy getting the extra Local Area
Connections and/or the extra Adapters cleaned out of your
registry.

I have an article that might point you in the right
direction.

http://www.sacpcug.org/archives/0303/tech0303.pdf

I don't know if any of the various registry cleaners will
find and clean references to improperly removed hardware.

Brian Smither
Click to expand...

Oh! Thank you thank you thank you Mr. Smither! On page
12 or so of this newsgroup, I describe this very same
problem. I've checked this nightly, and the "networking"
newsgroup, hoping for some ideas for almost a week. No
responses in this newsgroup, but the link to the tech
article explains the problem on my husbands PC exactly.
Now I know what he did... Another person responded in
the "networking" newsgroup, but this person has the same
problem and is going to try his OEM drivers for the
device. No solution posted / anything I could use /
haven't yet tried. This article, however, hits it right
on the head!

I'm going to refer that other person in the "networking"
MS newsgroup to your post. If you don't mind, I'd like to
post your link to the article in the "networking"
newsgroup for that other person as well. Let me know if
that would be okay and if so I'll do that.

Yeah, it's gonna be messy, but it looked like a registry
thing. Thanks again!
 
Back
Top