Originally Posted by
SeijiSensei
In mixed networks where DNS is provided by a Windows Active Directory server netbios names and DNS hostnames are usually identical.
Only in the sense that they are the same characters (up to the first 15) and can be perceived as the the same by humans. Thats as far as it goes.
Windows Active Directory manages DNS in the same way as BIND. All windows machines broadcast their COMPUTER NAME as a NetBIOS name. NetBIOS has nothing to do with AD. Perhaps you are confusing NetBIOS over TCP (NBT) with the SMB protocol.
Hostnames are defined in *nix based systems in /etc/hostname. The /etc/hosts file maps this hostname to a network interface of the host. DNS consolidates these names in a centralized data base.
NetBIOS names are not defined in /etc/hosts at all. The mapping can be handled in numerous ways. But in the end it has more to do with identifying the hosts capabilities. A windows share (SMB resource) is only one of those. See here for a list of identifiers.
In the end, just because things look the same or appear to have the same purpose doesn't make them the same.
I couldn't tell if he was working on a Windows network, in which case advertising via nmbd will help.
Not with mapping hostnames to IP addresses. From the nmbd man pages:
Code:
nmbd is a server that understands and can reply to netbios name service requests, like those produced by LanManager.
He didn't give us any information on how DNS is structured in the network he is using.
The Op was explicitly asking about broadcasts of hostnames. There is no 1 to 1 relationship between hostnames/DNS and NetBIOS names.
If it's just his Ubuntu box, a Mac, and a router, then I agree, this technique won't help.
Right, but we have needlessly wandered down the NetBIOS road.
Bookmarks