.... If someone is already utilising the NetBIOS name plus type, it is the responsibility of the Name service, running on the host that owns the name, to send a "Node Conflict" message out to absolutely everyone it can possibly find, including on all other transports. Joy. It may amuse people to know that there is a long-standing bug in Microsoft's NetBIOS stack implementation in Windows NT...
Well I /am/ an expert and all I can do is curse Microsoft.
nmbd is part of the Samba distribution: it's the Unix implementation of Microsoft's NETBIOS protocol handler. It doesn't do file sharing, it does the Microsoft equivalent of something like DNS or Rendezvous. It can be needed if you're doing anything in a Windows-like manner, for instance talking to printers which only speak Windows, but if you're just doing Unix or Mac you don't need it at all.
So do you have any Windows functions enabled ? Are you printing to Windows computers or enabling file-sharing with Windows computers ? If not, go to the Sharing System Preferences panel and turn everything you're not using off. Then reboot. Then see if the problem continues to happen.
Simon.
That, and don't bother looking at the packets. A waste of time.
You don't even need that. 'tcpdump' will do it. It's complicated to use but can do everything, including monitoring only packets from/to specific ports. Use 'man tcpdump' for more info.
Simon.
Cabling-Design.com Forums website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.