WriteLog
[Top] [All Lists]

[WriteLog] RE: NetBEUI?

To: <writelog@contesting.com>
Subject: [WriteLog] RE: NetBEUI?
From: aaron.hsu@unistudios.com (Hsu, Aaron)
Date: Fri, 20 Oct 2000 10:23:50 -0700
I think you might be confusing NetBEUI with NetBIOS.  NetBEUI is an actual 
transport protocol that runs seperate of TCP/IP.  NetBIOS can "ride" on top of 
NetBEUI, or TCP/IP (and, with a little help, IPX/SPX).

The main advantage with NetBEUI is that it's fast and simple, great for small 
networks.  The main disadvantage is that it's a broadcast based protocol.  A 
toss-up is that it's non-routeable...good if you don't need to access more than 
one logical network segment, bad if you do.  If you don't need I-net access, 
NetBEUI is great for small networks, plus it's native to Windows.

I've heard of a firewall package that uses TCP/IP on the Internet side of the 
firewall and NetBEUI on the "local" LAN side.  To me, this sounds perfect 
since, theoretically, data from PC's on the LAN side can never "leak" out to 
the Internet and hackers should never see anything past the firewall even if 
they do break-in.  I could be wrong in my accessment though...real hackers are 
typically a very intelligent breed...  =)

Anyways, I digress.  73!

  - Aaron Hsu, KD6DAE
    [athsu]@unistudios.com
    [kd6dae]@arrl.net
    No-QRO Int'l #1,000,006
     . -..- - .-. .-   " .... . .- ...- -.-- "


p.s.  I generally prefer IPX/SPX...

> ----------
> From:         Gerry Hull[SMTP:windev@inetmarket.com]
> Sent:         Friday, October 20, 2000 9:42 AM
> To:   writelog@contesting.com
> Subject:      Re: [WriteLog] NetBEUI?
> 
> 
> FWIW,
> 
> Actually, WriteLog uses NetDDE, which is layered on NetBEUI.  On Windows
> 95B and all other versions, NetBUEI is transported via TCP/IP, so there is
> no need to support NetBUEI as a seperate protocol; in fact, you'll see in
> your Network dialog box that you cannot enable "NetBEUI over TCP/IP", it's
> already enabled and greyed out.  In other words, NetBUEI is transported on
> top of TCP/IP.  Exposing the NetBUEI ports to the internet is a bad thing.
> 
> 73,
> 
> -Gerry, W1VE
> 
> 
> > 
> > Thanks to all for the info.  I really don't want NetBEUI on my network.  If
> > WriteLog networking works properly with just TCP/IP, then that's all I'll
> > have enabled.  Internet is firewalled with a NAT/DSL router so I don't
> > really worry about someone getting at my shares.
> > 
> > 73 de Mike, W1NR
> > 
> > -----Original Message-----
> > From: Barry Kutner [mailto:w2up@mindspring.com]
> > Sent: Friday, October 20, 2000 7:41 AM
> > To: Michael A. McCarthy; writelog@contesting.com
> > Subject: Re: [WriteLog] NetBEUI?
> > 
> > 
> > No, but if you have an internet connection it's risky. When sharing
> > is enabled in TCP/IP, you are opening your hard drive to the
> > outside world. For more info go to www.grc.com.
> > 73 Barry
> > 
> > On 20 Oct 00, Michael A. McCarthy wrote:
> > 
> > >
> > > In the manual under Network Operations, there is a line that states "Be
> > sure
> > > that NetBEUI is installed."  Is that REALLY an absolute requirement?
> > Isn't
> > > TCP/IP sufficient?
> > >
> > > Thanks,
> > > Mike, W1NR
> > >
> > >
> > > --
> > > WWW:                      http://www.writelog.com/
> > > Submissions:              writelog@contesting.com
> > > Administrative requests:  writelog-REQUEST@contesting.com
> > > Problems:                 owner-writelog@contesting.com
> > >
> > 
> > 
> > --
> > Barry Kutner, W2UP              Internet: w2up@mindspring.com
> > Newtown, PA         FRC         alternate: barry@w2up.wells.com
> > 
> 
> 
> --
> WWW:                      http://www.writelog.com/
> Submissions:              writelog@contesting.com
> Administrative requests:  writelog-REQUEST@contesting.com
> Problems:                 owner-writelog@contesting.com
> 

--
WWW:                      http://www.writelog.com/
Submissions:              writelog@contesting.com
Administrative requests:  writelog-REQUEST@contesting.com
Problems:                 owner-writelog@contesting.com


<Prev in Thread] Current Thread [Next in Thread>