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
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
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thank you Mr. ChiefIT, but please respond to my comment if you find the time.
-T
-T
--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.
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.
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.
ASKER
Thank you for your thorough explanation!
I'm new to the field of IT so this was very helpful.
-T
I'm new to the field of IT so this was very helpful.
-T
ASKER
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