Give more details, and fix up some stuff.
add reference to WINS Replication -- firstname.lastname@example.org
|Deletions are marked like this.||Additions are marked like this.|
|Line 11:||Line 11:|
'''WINS''' (Windows Internet Name Service) uses the same protocol, but unicast messages to a WINS-Server,
multiple WINS servers can replicate the content with the ["WINS-Replication"] protocol.
NetBIOS Name Service (NBNS)
This service is often called WINS on Windows systems.
The NetBIOS Name Service is part of the NetBIOS-over-TCP protocol suite, see the ["NetBIOS"] page for further information.
NBNS serves much the same purpose as ["DNS"] does: translate human-readable names to IP addresses (e.g. www.ethereal.com to 220.127.116.11). (As NetBIOS can run on top of several different network protocols (e.g. ["IP"], ["IPX"], ...), other implementations of the NetBIOS services have their own mechanisms for translating NetBIOS names to addresses.) NBNS's services are more limited, in that NetBIOS names exist in a flat name space, rather than DNS's hierarchical one (multiple flat name spaces can exist, by using NetBIOS scopes, but those are rarely used), and NBNS can only supply IPv4 addresses; NBNS doesn't support IPv6.
With the advent of SMB-over-TCP, it is no longer necessary to have a machine's NetBIOS name in order for that machine to make connections to SMB servers or in order for SMB connections to be made to that machine, and with the advent of "dynamic DNS", a host can register its name and its IP address or addresses with a ["DNS"] server when it boots (note that its IP address might not be static - it might be granted by a ["DHCP"] server - so you can't necessarily statically register a machine's host name and IP address with a ["DNS"] server). Therefore, newer Windows systems, starting with Windows 2000, can use ["DNS"] for all the purposes for which NBNS was used. NBNS is still widely used especially on Windows networks, as there might still be older versions of Windows on those networks, or it might not yet have been converted to use only ["DNS"].
WINS (Windows Internet Name Service) uses the same protocol, but unicast messages to a WINS-Server, multiple WINS servers can replicate the content with the ["WINS-Replication"] protocol.
See the ["NetBIOS"] page for the history of NetBIOS.
- ["UDP"]: Typically, NBNS uses ["UDP"] as its transport protocol. The well known UDP port for NBNS traffic is 137.
- ["TCP"]: NBNS can also use ["TCP"] as its transport protocol for some operations, although this might never be done in practice. The well known TCP port for NBNS traffic is 137.
XXX - Add example traffic here (as plain text or Ethereal screenshot).
The NBNS dissector is partially functional; it dissects NBNS-over-UDP, but not NBNS-over-TCP (I'm not sure we've ever seen any NBNS-over-TCP traffic).
(XXX add links to preference settings affecting how NBNS is dissected).
Example capture file
XXX - Add a simple example capture file to the SampleCaptures page and link from here. Keep it short, it's also a good idea to gzip it to make it even smaller, as Ethereal can open gzipped files automatically.
A complete list of NBNS display filter fields can be found in the [http://www.ethereal.com/docs/dfref/n/nbns.html display filter reference]
Show only the NBNS based traffic:
You cannot directly filter NBNS while capturing. However, as it runs atop ["UDP"] or ["TCP"] port 137, you can filter on those ports.
Capture NBNS traffic:
[http://www.ietf.org/rfc/rfc1001.txt RFC1001] Protocol Standard For a NetBIOS Service on a TCP/UDP Transport: Concepts and Methods
[http://www.ietf.org/rfc/rfc1002.txt RFC1002] Protocol Standard For a NetBIOS Service on a TCP/UDP Transport: Detailed Specifications