Duplicate Networked Devices/PCS displayed - Resolution?

Hello,

We run Server 2008 R2 here at work utilizing ADUC, DHCP Server, DNS Server, File Server, etc.  We have approximately 14 Kiosk-Pc's on the fabrication floor and here lies the issue.

In Windows Explorer, under the network icon on the left lower-side, virtually every networked PC shows a duplicate, with the exception of 2-3 machines.  This isn't really causing us a problem, it's really more of an annoyance to see duplicate network names on all of our kiosks.  We utilize network shares so it's not a critical item to fix.

What I have checked:

1) DNS issues
2) Duplicate names assigned to each kiosk (Duplicity dose not exist)
3) WINS is not in use, only DNS
4) nbtstat -a shows:

Total of 4 system names under 'NAME,' two of which are duplicated, so only two names are actually present.

ITSYS <00> Unique Registered
VNT   <00> Group Registered
ITSYS <20> Unique Registered
VEI     <1E> Group Registered

Local area connection 2:
Node IPAddress: [0.0.0.0] Scope Id: []

This is what I have checked thus far, I'm sure there's much that I am missing.  Your help in quick resolution to this issue would be much appreciated!

-T
LVL 1
TasticVNTAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

ChiefITCommented:
Here's your answer:

Both the Server and workstation service are active on this computer:

ITSYS
<computername>[00h]      Workstation Service
<computername>[20h]      Server Service

ITSYS <00> Unique Registered<<Workstation Service is sending out a netbios broadcast on:
VNT   <00> Group Registered<<This group name or domain name

ITSYS <20> Unique Registered<<The Server Service is sending out broadcasts on:
VEI     <1E> Group Registered<<This groupname or domain name

They are both on the same broadcast domain:

The duplicate name means the computers are seeing duplicate NetBIOS broadcasts on the broadcasts domain that are the same as another computer on the Broadcast domain. This may come from a multihomed machine (meaning multiple nics that you don't need). It could also mean the computer is advertising itself as a server and a workstation (A SERVER SHOULD DO THIS).

Your best bet is to go to the command prompt of problem children and type: Net Config Redir   ,,, and  Net config server ,,, and   Net config workstation     to compare what's going on with the broadcasts on that computer. Compare the workstation and server services with the redirector service to ensure they are using the right adapter.  If not make only one network adapter on line and then clear your netbios cache entries by going to the command prompt and typing: NBTSTAT -rr and NBTSTAT -RR
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
TasticVNTAuthor Commented:
You are too correct sir.

Literally 5 minutes after I asked this question I checked out our ADUC tree and found that 90% of the workstations were moved from the 'Computer Organizational Unit' to a separate folder under a subfolder (subfolder of user-ou) labeled 'Workstation.'  

I noticed that the systems in the original 'Computer' organizational unit was not broadcasting twice, thus no duplicity.  I moved all the networked devices from the Workstation OU back to the original 'Computer' OU and voila.

Here's what I don't understand:  

Why would the server continue to duplicate netbios broadcasts if the systems were moved to a separate OU labeled 'Workstations?'

I accept your answer but this brings up another point of confusion for me, thanks.

-T
0
TasticVNTAuthor Commented:
Thank you Mr. ChiefIT, but please respond to my comment if you find the time.

-T
0
ON-DEMAND: 10 Easy Ways to Lose a Password

Learn about the methods that hackers use to lift real, working credentials from even the most security-savvy employees in this on-demand webinar. We cover the importance of multi-factor authentication and how these solutions can better protect your business!

ChiefITCommented:
--Active Directory is integrated within DNS. NetBIOS has nothing to do with registering in a certain OU..

However, Group Policies are broadcast out using Netbios. Computer policies are not broadcast out to CN folder called USERS> in an OU called workstations. So, your computers were not getting group policy to the workstations. All workstations and Users were within the Users' CN.. HMMM, never seen that before.

In your shoes, I would check ALL active directory computers EVENT LOGS for replication errors in Active directory and FRS.. I believe you will find some problems there. Clear the logs and see if the 1030 and 1058 events for group policies were resolved and the 13000's events in the FRS logs. Monitor the FRS event logs and System Event logs for any future errors. Also, go to the AD servers and type DCDiag /v to look for additional errors.
0
ChiefITCommented:
By the way, there is nothing wrong with creating an OU called workstations and putting your computers in that... Just don't make the workstations OU a subfolder of the USERS CN folder.
0
TasticVNTAuthor Commented:
Thank you for your thorough explanation!

I'm new to the field of IT so this was very helpful.

-T
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Consulting

From novice to tech pro — start learning today.