TCP/IP, NETbeui, duplicate name detected

[wakubi]

Our network is NT4 SP6a. TCP/IP, WINS, NETbeui.

We experienced the following error in event viewer when we rebooted our PDC 10.0.0.1 and BDC 10.0.0.100 following the installation on SP6a.

Event ID 4320
Sourse NetBT
Type Error

Another machine has sent a name release message to this machine probably because a duplicate name has been detected on the TCP network. The IP address of the node that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state.

The conflict seems to be comming from services on the BDC. This is the relevant part of the nbtstat from the PDC:

DomainName <1C> Group Conflict
INet~Services <1C> Group Conflict

However there is no conflict from nbtstat on the BDC.

WINS tells me that both these names are on the BDC at the same address 10.0.0.100.

My understanding of netbeui over tcp/ip is that each service has a different service number, ie <1C> to identify that is it a different service under the same ip address, in this case 10.0.0.100.
The problem here it is there seems to be a conflict with DomainName <1C> and Inet~Services <1C> having the same service number and IP. I am unsure of the implications of this or how to correct it.

I would be grateful if anyone could help me to solve this problem.


Thanks in advance,

Julian K

 

[ifincham]

Hi,

Using nbtstat, the <1C> netbios suffix should indicate a domain controller in the context of domain and also the presence of IIS in the context of INet~Services. It would ordinarily look something like :

MYDOMAIN        <1C>     Group     registered
INet~Services    <1C>     Group     registered

Not sure whats wrong there but you could try 'nbtstat -RR' to release/refresh local netbiosnames with wins.

Regards

 

[wakubi]

Thanks for your help so far....

The event viewer error stated that &quot;The IP address of the node that sent the message is in the data.&quot; The MS says to convert the hexadecimal line 28, into binary to find the IP address of the conflicting PC. I have done this and it is our BDC, 10.0.0.100

this is nbtstat -n from the (PDC). (The BDC'c nbtstat contains no conflicts, ie Domainnamae<1C> Registered, INet~Services<1C> Registered)

nbtstat -n on PDC:

NetBIOS Local Name Table

name type status
PDCname <00> UNIQUE Registered
PDCname <20> UNIQUE Registered
DomainName <00> GROUP Registered
DomainName <1C> GROUP Conflict
DomainName <1B> UNIQUE Registered
DomainName <1E> GROUP Registered
PDCname <03> UNIQUE Registered
DomainName <1D> UNIQUE Registered
AdminAccount <03> UNIQUE Registered
..__MSBROWSE__. <01> GROUP Registered
PDCname <30> UNIQUE Registered
INet~Services <1C> GROUP Conflict
PDCname <06> UNIQUE Registered
IS~PDCname... <00> UNIQUE Registered
PDCname <BE> UNIQUE Registered
PDCname <6A> UNIQUE Registered
PDCname <87> UNIQUE Registered
PDCname <01> UNIQUE Registered

WINS database has these entrys:
(there are no static mapping in our wins database by the way)

10.0.0.100 INet~Services[1CH]
10.0.0.100 IMPFM[1CH]

I have looked in Help, which tells me that <1C> indicates a domain name.
DomainName is our domain name, INet~Services is not. INet~Services I think is something to do with IIS, which we used to run, but no longer have installed.
It looks to me like somewhere our system thinks INet~Services is a domain name. Maybe a program or service is trying to register the name, and we need to remove or configure something.

But what?
And where?

 

[Kjonnnn]

We had a simular problem and it revolved around WINS.. not sure how solved it. Make no one else is running WINS (We had a &quot;user&quot; secretly install Advance Service and with all the services runing.