Post by pjp
I have 13 pc's networked in house. All use regular TCP-IP with no
homegoup allowed :) All but one of them is running Win7 in some flavour,
e.g. 32 or 64 bit. They all behave fine and network more or less works
as expected :)
A week or so ago, as I've often had occassion to do, I redid someone's
pc. In this case I did a reinstall of Win7 Pro on a fairly fancy pc, an
Athlon 6 core "something" running in the 3.5Gz range with 16 Gb memory
and in total 5 hard disks in unit. I did take out the PCI-IDE card which
dropped the hd number down to 4, all SATA.
After install which went very smoothly given Windows knew about every
piece of hardware (clean device manager, a surprise), I connected
network cable and started updating it, e.g. Windows Update. I gave the
pc the name AMD-SEPCORE as it showed 6 cpu's in device manager.
Problem is now when viewing Workgroup pc's an AMD-SEPCORE pc shows up
under a second "Computer" listing. You can do nothing basiclly with the
Now I did nothing more with that pc than I have with literally a hundred
others over the years. None of the others have persisted in this way.
Anyone with any insight and specifically how can I get rid of this
The network browser protocol "remembers" machines that
have just shutdown and powered off. It may take some
period of time, or followup event, to clear it.
For example, if another computer acquires that IP
address from DHCP on your LAN, then the name will
undoubtedly be lost.
On a proper domain, a server keeps track of stuff
and is a "boss".
Whereas on a home LAN, the NetBIOS Browser election
process, nominates a standin for a domain controller,
and that machine then provides a list of machines
in the neighborhood. That's sort of the basic idea.
Elements of that protocol, have a ten or fifteen minute
time constant (the events are given a different color
in Wireshark, making it easier to see them). Browser
elections don't occur in a microsecond, or get updated
once a second. This is part of the reason that network
state information seems to change so slowly.
You should take a screenshot of what you're seeing,
and share it with us. If you're seeing a separate
entry that is graphically separated from where those
are normally displayed. Perhaps the location of
the orphan will jog someones memory on the topic.
As an alternative, have a look at the pictures here,
and see if yours is similar.
One of the protocols on Windows 7, exists mainly
to draw the ball and stick picture of
Network Map. That blog entry doesn't include a picture
of that ball and stick model, to demonstrate.
You can see a Network Map example here. At one time,
you had to install SSDP as a separate step to enable
stuff like this.