NetBIOS is a session-layer protocol and API. Of course, it is able to be 
routed (routable), just as RPC and NFS and TCP and UDP are also routable, 
as are HTTP, FTP, etc. In comparison, LLC, is a data-link-layer protocol. 
It is not routable without some major shenanigans. NetBEUI resides right on 
top of LLC and doesn't make any calls to a network layer. Also, NetBEUI 
does all its own reliability, etc. It doesn't rely on TCP, for example. 
NetBEUI handles all of the communication work relative to NetBIOS. This is 
different from the other implementations of NetBIOS.

NetBIOS refers to the programming interface in all implementations. In the 
NetBIOS/TCP environment, it also refers to the portion of the packet that 
carries NetBIOS commands, replies, and data. In the NetBIOS/NetBEUI 
environment, NetBIOS refers only to the API, and NetBEUI refers to the 
protocol. In the NetBIOS/IPX environment,  NetBIOS refers to both the API 
and to the protocol. To understand the details of terminology use, it's 
worthwhile to examine the three different frame structures for TCP, 
NetBEUI, and IPX.

Priscilla

At 03:54 AM 4/9/02, [EMAIL PROTECTED] (John Nemeth) wrote:
>On Aug 29,  7:34am, "Priscilla Oppenheimer" wrote:
>}
>} NetBEUI is non-routable. NetBIOS is routable. NetBIOS over TCP/IP should
>} supposedly work over the Internet. For example, can't you do file sharing
>} over the Internet? That uses NetBIOS and SMB of CIFS.
>
>      If you want to be pedantic (and, on this list we should be),
>discussing the routability of NetBIOS is non-sensical.  NetBIOS is a
>session layer protocol.  It would be like discussing the routability of
>TCP or UDP.  By themselves, these protocols only have port numbers,
>they don't have node addresses.  As someone else has mentioned, you
>really need to look at the underlying protocol.  NetBIOS over TCP/IP
>(aka NBT) is, of course, completely routable, since TCP/IP is a
>routable protocol.  NetBIOS over NetBEUI isn't routable as NetBEUI is a
>datalink layer protocol (i.e. it has hosts addresses and doesn't have
>any way of doing network addressing, so its addresses are for the local
>segment only, ala Ethernet MAC addresses) and must be bridged.
>
>}-- End of excerpt from "Priscilla Oppenheimer"
________________________

Priscilla Oppenheimer
http://www.priscilla.com




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=40942&t=40784
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

Reply via email to