Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 794
  • Last Modified:

duplicate IP reported on AD Controller - offset 028?

This error is bugging me.  Mostly because it does not register offset 028 in the event log as the MS KB states.  I wonder if I need to take the 169.x.x.x IP's on the NICs and set to a bogus, static IP in a subnet that we do not use.  The Teamed Adapter is set for static, the individual adapters are set for DHCP.  Here is the error, please see the output from nbtstat -n below and help me...  I think there is something in the results below that you may see that I am not seeing...  

--------------------
Event ID 4319
Source:  NetBT
A duplicate name has been detected on the TCP network.  The IP address of the machine that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state.
--------------------

Output from nbtstat -n.......
   
Team:
Node IpAddress: [172.16.16.132] Scope Id: []

                NetBIOS Local Name Table

       Name               Type         Status
    ---------------------------------------------
    PADS0101       <00>  UNIQUE      Registered
    MYDOMAIN         <00>  GROUP       Registered
    MYDOMAIN         <1C>  GROUP       Registered
    PADS0101       <20>  UNIQUE      Registered
    MYDOMAIN         <1B>  UNIQUE      Registered
    MYDOMAIN         <1E>  GROUP       Registered
    MYDOMAIN         <1D>  UNIQUE      Registered
    ..__MSBROWSE__.<01>  GROUP       Registered

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

                NetBIOS Local Name Table

       Name               Type         Status
    ---------------------------------------------
    PADS0101       <00>  UNIQUE      Registered
    MYDOMAIN         <00>  GROUP       Registered
    MYDOMAIN         <1C>  GROUP       Registered
    PADS0101       <20>  UNIQUE      Registered
    MYDOMAIN         <1B>  UNIQUE      Registered
    MYDOMAIN         <1E>  GROUP       Registered
   
Local Area Connection:
Node IpAddress: [169.254.198.58] Scope Id: []

                NetBIOS Local Name Table

       Name               Type         Status
    ---------------------------------------------
    PADS0101       <00>  UNIQUE      Registered
    MYDOMAIN         <00>  GROUP       Registered
    MYDOMAIN         <1C>  GROUP       Registered
    PADS0101       <20>  UNIQUE      Registered
    MYDOMAIN         <1B>  UNIQUE      Registered
    MYDOMAIN         <1E>  GROUP       Registered
    MYDOMAIN         <1D>  UNIQUE      Registered
    ..__MSBROWSE__.<01>  GROUP       Registered
0
stowyo
Asked:
stowyo
  • 3
  • 2
1 Solution
 
rparsons1000Commented:
It looks like you have only 2 NIC's and they are teamed? Is 169.254.x.x part of your network somehow? It looks like the default addresses Windows goves if no DHCP is available and you're not static.

If 169.254 is not on your network, then that should not be where the duplicate name comes from as you can't hear anything coming from those addresses by anything. Maybe there really is a duplicate name?

0
 
stowyoAmericas Regional IT ManagerAuthor Commented:
If there really is a duplicate, it will pop what is called offset 028 in the event log's details screen.  Since this is not there it makes me think that there is not a duplicate and the error is coming from the 169.x.x.x addresses.  169.x.x.x is what you get when DHCP will not give an an address.  When I look in WINS, I do see some duplicates there.
0
 
rparsons1000Commented:
I've never teamed NIC's so am just working off of theory here and hope it helps in some way. I have a lot of systems using IScsi so in essence have multiple IP's for the system. For the IScsi NIC's I disable bindings but I doubt you can do that with teamed NIC's. Another thing is disabling Netbios over TCP and not register in DNS.

My thought is disable Netbios over TCP, delete the bad WINS addresses and see if that fixes it.

Sorry I can't be 100% sure on this but that's what I'd try.
0
 
stowyoAmericas Regional IT ManagerAuthor Commented:
I am going to try to disable NetBIOS over TCP off of the adapters before the team and let you know how it goes.  Good idea.
0
 
stowyoAmericas Regional IT ManagerAuthor Commented:
It was indeed Wins.  Thank you rparsons1000
0

Featured Post

Upgrade your Question Security!

Your question, your audience. Choose who sees your identity—and your question—with question security.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now