Check out my first novel, midnight's simulacra!

NetBIOS: Difference between revisions

From dankwiki
No edit summary
No edit summary
Line 1: Line 1:
NetBIOS is neither merely a protocol nor a topology; it is an API which makes assumptions about both. Communication endpoints are addressed by 16-byte strings ("NetBIOS Names"). A machine can support multiple names, though it typically '''registers''' a primary "Machine Name/Workstation Name" upon joining the network.
NetBIOS is neither merely a protocol nor a topology; it is an API which makes assumptions about both. Communication endpoints are addressed by 16-byte strings ("NetBIOS Names"). A machine can support multiple names, though it typically ''registers'' a primary "Machine Name/Workstation Name" upon joining the network. "Group names" may be shared by machines, implementing a multicast. There is no concept of routing (though a NetBIOS LAN may well be implemented over multiple routed networks).


==NetBIOS LAN Emulation==
==NetBIOS LAN Emulation==
Defined in RFC 1001 and RFC 1002, NBT/NetBT/TCPBEUI implements NetBIOS over [[TCP]]/UDP.
Defined in RFC 1001 and RFC 1002, NBT/NetBT/TCPBEUI implements NetBIOS over [[TCP]]/UDP.
===Mandatory Elements===
===Mandatory Elements===
* ''Name Service'': map NetBIOS names to network layer (IPv4/IPv6) addresses
* '''Name Service''': map NetBIOS names to network layer (IPv4/IPv6) addresses (UDP 137, TCP 137 specified but unused)
* ''Datagram Service'': delivery of NetBIOS datagrams over UDP
* '''Datagram Service''': delivery of NetBIOS datagrams over UDP (UDP 138)
* ''Session Service'': establishment and maintenance of circuits over [[TCP]]
* '''Session Service''': establishment and maintenance of circuits over [[TCP]] (TCP 139)


==See Also==
==See Also==

Revision as of 19:19, 7 December 2011

NetBIOS is neither merely a protocol nor a topology; it is an API which makes assumptions about both. Communication endpoints are addressed by 16-byte strings ("NetBIOS Names"). A machine can support multiple names, though it typically registers a primary "Machine Name/Workstation Name" upon joining the network. "Group names" may be shared by machines, implementing a multicast. There is no concept of routing (though a NetBIOS LAN may well be implemented over multiple routed networks).

NetBIOS LAN Emulation

Defined in RFC 1001 and RFC 1002, NBT/NetBT/TCPBEUI implements NetBIOS over TCP/UDP.

Mandatory Elements

  • Name Service: map NetBIOS names to network layer (IPv4/IPv6) addresses (UDP 137, TCP 137 specified but unused)
  • Datagram Service: delivery of NetBIOS datagrams over UDP (UDP 138)
  • Session Service: establishment and maintenance of circuits over TCP (TCP 139)

See Also