Hello All,
I think that the line between NetBIOS and NetBEUI was blurred a little here.
NetBEUI is a Data Link protocol (as in IEEE 802.2 stuff), Logical Link
Control - Type 2 (connection oriented) which was written to transport
NetBIOS. Like all LLC protocols, it is unroutable. So everyone started
bridging it. Within a campus (LAN bridges) it was acceptable and usually
neither the NetBEUI nor NetBIOS timers expired from end to end. Then people
tried transporting it across the wide area. All sorts of timers expired.
(Naturally, the routers were suspected ;^)
Since everyone loves NetBIOS (well... at least the people who had invested
great amounts of resources in getting their Net OS's to work over it) wanted
to add the capability of routing to NetBIOS, they came up with RFC-1001 and
RFC-1002 which specifies how to implement NetBIOS over TCP/IP (replaces
NetBEUI as the transport). If you're going to run NetBIOS across a LAN, or
even a few LANs which are locally connected, then NetBEUI is generally
accepted to be the fastest. However, if you're going to scale it up to a
wide area or across a large campus, then you'll want to use a routable
transport. (I seem to recall NetBIOS over XNS was an option from someone at
one time.)
TCP/IP was created before the ISO model, so everyone just commonly agreed
upon how an IP frame was to be laid down on a media. (Someone once told me
that Vint said, "We'll just use the Ethernet frame on Ethernet media, of
course," and Bob agreed. :-). RFC-894 cemented this and when the more ISO
modeled networks were architected (e.g. token ring), which specified an
802.2 layer, RFC-1042 was written. This RFC specifies that (when you really
can't use Ethernet frames) you must use LLC Type 1 (connectionless) to
transport IP.
So, if you've got an IP-firewall, then you cannot transport NetBIOS/NetBEUI
accross it. If you want to transport NetBIOS (NT Server stuff) across your
IP-firewall, then you've got to make sure that both the client and the
server are using NetBIOS/TCP/IP and that you open the appropriate holes in
your firewall. I don't know the specifics of the Firewall-1 to know if it
can do that or if it has some mechanism to allow the passage of
NetBIOS/NetBEUI. Any Firewall-1 NT experts out there?
Hope this helps,
Chris Lonvick
Cisco Systems
Consulting Engineering
Houston, Texas, USA
+1-713-778-5663
At 11:29 PM 9/27/96 -0100, Frank J.J. De Hert wrote:
>>Yep... that is what it is for..... For many reasons you might
>>not want to run netbuei without TCP/IP....
>>
>
>Could you elaborate on that? Somehow I was convinced that NetBEUI and TCP/IP
>were two separate stacks/protocols that don't need each other to run.
>
>>--------------------------------------------------
>>Anthony Thomas, Network Engineer, TASC Inc
>>E-mail: adthomas @
tasc .
com
>>http://www.tasc.com
>>Phone : 617 - 942 - 2000
>>Fax : 617 - 942 - 7100
>>--------------------------------------------------
>>
>>----------
>>From: Andy Watts[SMTP:andywatt @
loxinfo .
co .
th]
>>Sent: Tuesday, September 24, 1996 6:58 AM
>>To: firewalls @
greatcircle .
com
>>Subject: netbeui & tcp
>>
>>Hi,
>>
>>While playing with FW-1 on NT I saw that it can allow the service NetBEUI.
>>
>>
>>What is this for?
>>
>>Does this allow people to connect and become part of a microsoft network
>>across TCP/IP?
>>
>>Is there anyway users can become share MS network files & directories
>>accross TCP/IP
>>
>>Thanks
>>
>>Andy
>>
>>
>>
>>
>>
>--
> While re-installing the newest version of The Operating System for the
>umpteenth time, it struck me that I would spend the better part of my active
>life sitting around, staring at a computer screen, waiting for The System to
>show some sign of life...
> \\ //
> O O
> |
> O Aaaaahhhhhh
>
>
>
|
|
