NetBIOS - revision history

Dank: /* NetBIOS LAN Emulation */

2011-12-09T16:39:35Z

NetBIOS LAN Emulation

← Older revision		Revision as of 16:39, 9 December 2011
Line 5:		Line 5:
	===Mandatory Elements===		===Mandatory Elements===
	* '''Name Service''': map NetBIOS names to network layer (IPv4/IPv6) addresses (UDP 137, TCP 137 specified but unused)		* '''Name Service''': map NetBIOS names to network layer (IPv4/IPv6) addresses (UDP 137, TCP 137 specified but unused)
			** 16-bit Transaction ID
			** 16 bits of flags
			** 16 bits each of Question Count, Answer Count, Additional Count, and Authority Count (just like [[DNS]])
			** Resource records, using NetBIOS encodings and NB (0x0020) resource types
	* '''Datagram Service''': delivery of NetBIOS datagrams over UDP (UDP 138)		* '''Datagram Service''': delivery of NetBIOS datagrams over UDP (UDP 138)
	* '''Session Service''': establishment and maintenance of circuits over [[TCP]] (TCP 139)		* '''Session Service''': establishment and maintenance of circuits over [[TCP]] (TCP 139)

Dank at 19:19, 7 December 2011

2011-12-07T19:19:09Z

← Older revision		Revision as of 19:19, 7 December 2011
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==

Dank at 11:05, 7 December 2011

2011-12-07T11:05:05Z

← Older revision		Revision as of 11:05, 7 December 2011
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==

Dank: 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..."

2011-12-07T11:03:21Z

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..."

New page

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/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==
* "[http://ubiqx.org/cifs/NetBIOS.html Implementing CIFS]" from the Samba team

[[CATEGORY: Networking]]