Check out my first novel, midnight's simulacra!
NetBIOS: Difference between revisions
From dankwiki
(Created page with "NetBIOS is neither merely a protocol nor a topology; it is an API which makes assumptions about both. ==NetBIOS LAN Emulation== Defined in RFC 1001 and RFC 1002, NBT/NetBT/TC...") |
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. | 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 LAN Emulation== | ==NetBIOS LAN Emulation== | ||
Revision as of 11:05, 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.
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
- Datagram Service: delivery of NetBIOS datagrams over UDP
- Session Service: establishment and maintenance of circuits over TCP
See Also
- "Implementing CIFS" from the Samba team
