duplicate name has been detected on the TCP network - event id 4319

supportodq
supportodq used Ask the Experts™
on
Hi,
i started seeing this error in event viewer 4319 for a few weeks on my server.
And it may or may not be the cause of some computers disconnecting from athe network and not finding shared drives (a reboot on those machines fixes the problem).
It's a Windows Server 2008 R2 (Service Pack1), its a secondary DC on our network.
it has 4 Network cards, and is a host to 3 virtual machines (Hyper-V).

Event Viewer

Log Name:      System
Source:        NetBT
Date:          8/7/2012 8:44:08 AM
Event ID:      4319
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      ODQFARP.ODQ.interne
Description:
A duplicate name has been detected on the TCP network.  The IP address of the computer that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state.

nbtstat -n Result


C:\Users\vdavidescu>nbtstat -n

Local Area Connection 2:
Node IpAddress: [169.254.96.143] Scope Id: []

                NetBIOS Local Name Table

       Name               Type         Status
    ---------------------------------------------
    ODQFARP        <00>  UNIQUE      Registered
    ODQINTERNE     <00>  GROUP       Registered
    ODQINTERNE     <1C>  GROUP       Registered
    ODQFARP        <20>  UNIQUE      Registered
    ODQINTERNE     <1B>  UNIQUE      Registered

Local Area Connection 6:
Node IpAddress: [192.168.62.102] Scope Id: []

                NetBIOS Local Name Table

       Name               Type         Status
    ---------------------------------------------
    ODQFARP        <00>  UNIQUE      Registered
    ODQINTERNE     <00>  GROUP       Registered
    ODQINTERNE     <1C>  GROUP       Registered
    ODQFARP        <20>  UNIQUE      Registered
    ODQINTERNE     <1B>  UNIQUE      Registered

Local Area Connection 7:
Node IpAddress: [192.168.62.166] Scope Id: []

                NetBIOS Local Name Table

       Name               Type         Status
    ---------------------------------------------
    ODQFARP        <00>  UNIQUE      Registered
    ODQINTERNE     <00>  GROUP       Registered
    ODQINTERNE     <1C>  GROUP       Registered
    ODQFARP        <20>  UNIQUE      Registered
    ODQINTERNE     <1B>  UNIQUE      Registered

Local Area Connection 8:
Node IpAddress: [192.168.62.205] Scope Id: []

                NetBIOS Local Name Table

       Name               Type         Status
    ---------------------------------------------
    ODQFARP        <00>  UNIQUE      Registered
    ODQINTERNE     <00>  GROUP       Registered
    ODQINTERNE     <1C>  GROUP       Registered
    ODQFARP        <20>  UNIQUE      Registered
    ODQINTERNE     <1B>  UNIQUE      Registered
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
delete machine from AD and re-add.

Author

Commented:
Hi
thanks for that but I do not have the WINS Server installed. Either as a "server role" (On our main DC Windows server 2003 R2) or as a "server feature" (On our secondary DC Windows server 2008 R2) installed.

in the KB article you linked it says:
1. Delete the static mappings
2. Clean the WINS database
3. Disable the WINS client

This alarms me a bit, mainly because I don't know what this dose, will this screw up my network mappings/rights at all and is it good to do this outside of production hours?

thanks
Ensure you’re charging the right price for your IT

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!

Svet PaperovIT Manager

Commented:
Make sure that you can communicate to the host by one NIC only. The other 3 physical NICs, if they are connected to the same network segment, should be configured for virtual machines only by disabling “Allow management operating system to share this adapter” in the Virtual Network Manager.

Author

Commented:
Virtual Network Managerspaperov:
Here is a printscreen of whats going on in Virtual Network Manager on my server. If I disable this checkbox will it change anything on the virtual machines or on the host? do I have to reboot either? any downtime?

chubby_informer:
delete machine from AD and re-add.
Actually if it is a duplicate machine on the network with the same name, i'm trying to find out which machine it is (either name or ip would help). any ideas how?
Svet PaperovIT Manager

Commented:
No, disabling this checkbox won’t change anything for the virtual machines and you don’t need to restart. It will only prevent the host from using this network connection.

In my opinion you don’t have a duplicated machine name; the warning is generated by having a multi-hosted server in the same domain. By disabling the sharing of the additional adapters you should fix the problem.

You need to have only one active connection to the host.

Author

Commented:
spaperov
i disabled #1 (in image above) it was ok.
then i disabled #2 and i lost remote network connection with the host
so freaked out, i went physically to the server and re-enabled it.
there might be a shared network card between 2 virtuals or even with the host?!
IT Manager
Commented:
Yes, you can have one adapter shared between the host and multiple virtual machines.

There are advantages of sharing a single adapter between multiple virtual servers, as a 10Gbps speed for example, but there is almost no advantage of sharing it with the host, unless in test environment.

I suggest keeping one adapter for the host use only and all other adapters for the virtual servers. What you could do is:
  1. Go to the physical host and disable the sharing on all of the 3 virtual adapters. The Connectivity and Network Category fields of Local Area Connections 6, 7 and 8 will become blank)
  2. Configure the unused adapter (Local Area Connection 1 or 4 – I cannot guess which one from the screen shot) with the IP address of the Host server. The adapter must be physically connected to the network  
  3. RDP to the host to check the connectivity.
  4. Configure a static A record in the DNS for the host, if is not done yet.
If the host is the only DC in the network, the clients and servers could lose connectivity during the reconfiguration, so I suggest doing all of that in a downtime.

Search the Internet a little bit about networking with Hyper-V R2 to understand how it works.

Author

Commented:
Although i didn't solve my problem, I still see the error in event viewer NetBT (4319), spaperov's suggestion is good. Since my collegue confirmed to me that there are 4 physical network cards in the server, only 2 are connected (problems with the initial configuration). Aand each NIC is shared : #1)  the Host and a virtual machine and #2) between 2 virtual machines.
The ideal thing is to re-connect the other 2 network cards, dedicate one to the host, and each of the 3 others to a virtual server.
And configure a static record in the DNS for the host...

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial