Skip to main content
NetApp Knowledgebase

"nbt.NetBIOSName.nameConflictIF" message shows up after node reboot or cifs restart

Views:
166
Visibility:
Public
Votes:
0
Category:
data-ontap-8
Specialty:
cifs
Last Updated:

Applies to

Data ONTAP 8 7-mode

Issue

  • After node reboot or cifs restart, EMS reports "nbt.NetBIOSName.nameConflictIF".

Example:
[node-name:nbt.NetBIOSName.nameConflictIF:error]: NBT: NetBIOS conflict on name TEST           0 with xxx.xxx.xxx.xxx. Unable to register this name.  
[node-name:nbt.NetBIOSName.nameConflictIF:error]: NBT: NetBIOS conflict on name TEST           3 with xxx.xxx.xxx.xxx. Unable to register this name.  
[node-name:nbt.NetBIOSName.nameConflictIF:error]: NBT: NetBIOS conflict on name TEST           20 with xxx.xxx.xxx.xxx. Unable to register this name.

  • "nbtstat" command shows one node has "In Conflict!".

Example:
Node-A*> nbtstat
interfaces:
  xxx.xxx.xxx.xxx
  xxx.xxx.xxx.xxx
  xxx.xxx.xxx.xxx

broadcast interfaces:
  xxx.xxx.xxx.xxx
  xxx.xxx.xxx.xxx
  xxx.xxx.xxx.xxx

servers:
NBT scope []; NBT mode [B]; NBT names:
  TEST           <00> ( Broadcast ) ( )
  TEST           <03> ( Broadcast ) ( )
  TEST           <20> ( Broadcast ) ( )
  WORKGROUP       <00> ( Broadcast ) ( group )


Node-B*> nbtstat
interfaces:
  xxx.xxx.xxx.xxx
  xxx.xxx.xxx.xxx
  xxx.xxx.xxx.xxx

broadcast interfaces:
  xxx.xxx.xxx.xxx
  xxx.xxx.xxx.xxx
  xxx.xxx.xxx.xxx

servers:
NBT scope []; NBT mode [B]; NBT names:
  TEST           <00> ( "In Conflict!" ) ( )
  TEST           <03> ( "In Conflict!" ) ( )
  TEST           <20> ( "In Conflict!" ) ( )
  WORKGROUP       <00> ( Broadcast ) ( group )

 

CUSTOMER EXCLUSIVE CONTENT

Registered NetApp customers get unlimited access to our dynamic Knowledge Base.

New authoritative content is published and updated each day by our team of experts.

Current Customer or Partner?

Sign In for unlimited access

New to NetApp?

Learn more about our award-winning Support