Receiving NetBT vent error 4319 on Hyper-V server using 2 ports on a quad-port NIC

Receiving the following error in event viewer. This is on a server 2012 Hyper-V server using 2 ports on a quad-port NIC:

Log Name:      System
Source:        NetBT
Date:          4/21/2015 11:02:10 AM
Event ID:      4319
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      HCSO-HyperV
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.

I get the following when I run "nbtstat -n"

C:\Users\Administrator>nbtstat -n

Ethernet:
Node IpAddress: [10.0.1.205] Scope Id: []

                NetBIOS Local Name Table

       Name               Type         Status
    ---------------------------------------------
    HCSO-HYPERV    <00>  UNIQUE      Registered
    WORKGROUP      <00>  GROUP       Registered
    HCSO-HYPERV    <20>  UNIQUE      Registered

vEthernet (TEAM-V):
Node IpAddress: [10.0.1.207] Scope Id: []

                NetBIOS Local Name Table

       Name               Type         Status
    ---------------------------------------------
    HCSO-HYPERV    <00>  UNIQUE      Registered
    WORKGROUP      <00>  GROUP       Registered
    HCSO-HYPERV    <20>  UNIQUE      Registered

It appears that something is messed up with the mapping or such like that is assiggning 2 IP addys to the same computer (HCSO-HYPERV)?  

Thank you for your help!
ImImInAsked:
Who is Participating?
 
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
What we would do in your situation:
 + Team 0: 2 Ports - Management OS Access and IP 10.0.1.205
 + Team 1: 2 Ports - vSwitch (Dedicated not shared with host OS)

I'm not sure what is trying to be accomplished here?

The VMs will be able to communicate with the host if they are on the same subnet with no VLAN/Routing enabled anywhere.

There is no reason that I can think of to have an IP address assigned to a vSwitch team?

EDIT: I have an EE Article here: Some Hyper-V Hardware and Software Best Practices.
0
 
Zephyr ICTCloud ArchitectCommented:
Did you add both the IP-addresses into your DNS server? One A-record for each IP-address might solve the issue.
0
 
ImImInAuthor Commented:
The 10.0.1.205 is the Hyper-V host address.
The 10.0.1.207 is shared for the virtual LAN access by 3 different VM's on the host.

How would I set the a-records for such a scenario? (the Hyper-v is obvious, I'm of course referring to the VM's).

Thanks again!
0
Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

 
Zephyr ICTCloud ArchitectCommented:
OK, maybe I'm missing, something, it was a long day :)

The Hyper-V host is reachable by those two IP-addresses no? If is the case this can cause strange things on the network because it would mean that the server is thought to have two IP-addresses.

I'd just try to add 2 A-records for this server with the name HCSO-HYPERV and these two IP-addresses...

Or, is it so that these 3 VM's all use this 10.0.1.207 IP-address?
0
 
ImImInAuthor Commented:
The Hyper-V is only reachable by 10.0.1.205
The VMs use port 2 on the quad-port NIC to virtulize their NIC connection from within the VM (each machine of course uses a different IP from within the VM but all come out through port 2 of the quad-port NIC).
0
 
ImImInAuthor Commented:
As mentioned above, the VMs use port 2 on the quad-port NIC which is set to 10.0.1.207
0
 
Zephyr ICTCloud ArchitectCommented:
Well, I'm still pretty sure the error is caused by the two ip-addresses on the system, which could either be solved by start using VLANs or try creating an extra A-record, but besides that, there's things to check, like:

- There maybe is a computer on the network with the same name.
- Identical user name(s) logged on to multiple computers.
- Inactive or duplicate names in the WINS database. (doubt you still use WINS)
- Conflicting network adapters in a multi-homed computer. (this again :-) )
-  “ipconfig/all” returns incorrect host name.
- Try disabling NetBIOS over TCP/IP on the NIC.
0
 
ImImInAuthor Commented:
Thanks guys!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.