This is a multi-part message in MIME format.
------=_NextPart_000_00C7_01C1452A.55DD6440
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Barry:
You are 100% correct. Do not use TCP/IP for your local network if you =
are going to use file and printer sharing. If you turn on file and =
printer sharing for TCP/IP, than the outside world will be able to =
access them. Make sure that if you do decide to use TCP/IP, because you =
do not want to share your files or printers, turn off file and print =
sharing.
73' Lloyd
----- Original Message -----=20
From: N3SL@aol.com=20
To: w2up@mindspring.com ; writelog@contesting.com=20
Sent: Monday, September 24, 2001 2:39 PM
Subject: Re: [WriteLog] Networking
In a message dated 09/24/2001 11:58:51 AM Central Daylight Time, =
w2up@mindspring.com writes:=20
I am far from a network guru, but from what I've read, NetBeui is=20
safer to use if the computer has an Internet connection. When=20
using TCP/IP, the outside world can see whatever is networked via=20
TCP/IP. This is not the case with NetBeui.=20
Barry W2UP=20
Not to belabor the point, but if a computer has an external =
connection, it's already using TCP/IP, so it's moot. As I said, NetBEUI =
is for peer-to-peer (in house, small group) networking. It won't =
connect to the outside world. I personally don't see the need to have =
NetBEUI on a PC as an extra protocol IF TCP/IP is there for some other =
reason - the KISS philosophy. NetBEUI will work just fine on 2 computers =
hooked together via a cross-over cable. But once the outside world is =
brought into the picture, TCP/IP is installed whether you like it or =
not. Besides, no one can "explore" your hard drive unless you're =
connected to an ISP or WAN or whatever. And if your home/ham computer =
contains stuff that sensitive, you need your own firewall program =
anyway.=20
73,=20
Steve=20
------=_NextPart_000_00C7_01C1452A.55DD6440
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2600.0" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial>Barry:</FONT></DIV>
<DIV><FONT face=3DArial></FONT> </DIV>
<DIV><FONT face=3DArial>You are 100% correct. Do not use TCP/IP for your =
local=20
network if you are going to use file and printer sharing. If you =
turn on=20
file and printer sharing for TCP/IP, than the outside world will be able =
to=20
access them. Make sure that if you do decide to use TCP/IP, =
because you do=20
not want to share your files or printers, turn off file and print=20
sharing.</FONT></DIV>
<DIV><FONT face=3DArial></FONT> </DIV>
<DIV><FONT face=3DArial>73' Lloyd</FONT></DIV>
<BLOCKQUOTE=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV=20
style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
<A title=3DN3SL@aol.com href=3D"mailto:N3SL@aol.com">N3SL@aol.com</A> =
</DIV>
<DIV style=3D"FONT: 10pt arial"><B>To:</B> <A =
title=3Dw2up@mindspring.com=20
href=3D"mailto:w2up@mindspring.com">w2up@mindspring.com</A> ; <A=20
title=3Dwritelog@contesting.com=20
href=3D"mailto:writelog@contesting.com">writelog@contesting.com</A> =
</DIV>
<DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Monday, September 24, =
2001 2:39=20
PM</DIV>
<DIV style=3D"FONT: 10pt arial"><B>Subject:</B> Re: [WriteLog] =
Networking</DIV>
<DIV><BR></DIV><FONT face=3Darial,helvetica><FONT size=3D2>In a =
message dated=20
09/24/2001 11:58:51 AM Central Daylight Time, <A=20
href=3D"mailto:w2up@mindspring.com">w2up@mindspring.com</A> writes: =
<BR><BR><BR>
<BLOCKQUOTE=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px"=20
TYPE=3D"CITE">I am far from a network guru, but from what I've read, =
NetBeui=20
is <BR>safer to use if the computer has an Internet connection. When =
<BR>using TCP/IP, the outside world can see whatever is networked =
via=20
<BR>TCP/IP. This is not the case with NetBeui. <BR>Barry W2UP=20
<BR></FONT><FONT lang=3D0 face=3DArial color=3D#000000 size=3D3=20
FAMILY=3D"SANSSERIF"></BLOCKQUOTE><BR></FONT><FONT lang=3D0 =
face=3DArial=20
color=3D#000000 size=3D2 FAMILY=3D"SANSSERIF">Not to belabor the =
point, but if a=20
computer has an external connection, it's already using TCP/IP, so =
it's moot.=20
As I said, NetBEUI is for peer-to-peer (in house, small group)=20
networking. It won't connect to the outside world. I =
personally=20
don't see the need to have NetBEUI on a PC as an extra protocol IF =
TCP/IP is=20
there for some other reason - the KISS philosophy. NetBEUI will work =
just fine=20
on 2 computers hooked together via a cross-over cable. But once =
the=20
outside world is brought into the picture, TCP/IP is installed whether =
you=20
like it or not. Besides, no one can "explore" your hard drive =
unless=20
you're connected to an ISP or WAN or whatever. And if your =
home/ham=20
computer contains stuff that sensitive, you need your own firewall =
program=20
anyway. <BR><BR>73, <BR>Steve</FONT> =
</FONT></BLOCKQUOTE></BODY></HTML>
------=_NextPart_000_00C7_01C1452A.55DD6440--
|