Text 5006, 148 rader
Skriven 2005-03-16 14:49:00 av CHARLES ANGELICH (1:123/140)
     Kommentar till en text av ALAN ZISMAN
Ärende: Re: lan
===============

123c53f8a436
win95



Hello Alan - 

--8<--cut 

CA>> That's another thing that confuses me. At one time there
CA>> were 'token ring' networks, LANs (Novell or Lantastic),
CA>> and then direct connections via null cable. Now there is
CA>> P2P which seems to me to be a _renamed_ LAN? My
CA>> understanding is probably warped but 'token ring' networks
CA>> had a server connected to by 'clients', LANs did not have
CA>> a central sever with all machines sharing resources.
CA>> Resources being primarily printers, and drives ( I don't
CA>> recall them sharing modems - maybe they did?). 

CA>> If there is no server involved I don't think 'network' is
CA>> an entirely accurate designation for P2P. Seems there was
CA>> a time when a distinction was made in this case. 

CA>> Other software that _emulates_ networking via null cables
CA>> will not allow the use of the machine designated as the
CA>> 'server'. Only the 'client' machine can execute other
CA>> software during the connection to the machine that is
CA>> designated as the server. 

AZ>> Although the Win98 server showed up in the My Network
AZ>> Places list, it gave an error message saying I was not
AZ>> permitted to connect. I installed NetBEUI from the XP CD,
AZ>> and it now connects without problem. 

What "server" are you referring to? From what you have
described there are no "servers" it's a LAN with shared
resources - no server. An unused client does not constitute a
'server'. 

CA>> I remembered that you had mentioned NetBEUI as a solution
CA>> to printer sharing and I did try adding NetBEUI several
CA>> times. 

CA>> Theoretically there is no logical reason why NetBEUI
CA>> should be required. Linux and the entire internet function
CA>> (network) using TCP/IP and no NetBEUI? 

AZ> 1) I don't have any direct experience using Token Ring... 

--8<--cut 

AZ> and finally to Ethernet using twisted pair cabling-- but
AZ> all running the same Lantastic software. 

AZ> 2) Local Area Networks can be designed to work around a
AZ> dedicated server-- Novell Netware, or one of a variety of
AZ> Windows server versions are examples. Peer-to-peer networks
AZ> use software in which any of the systems can be sharing
AZ> resources (typically files or printers) with the others.
AZ> WFWG, Win9x, WinNT Pro, Win 2000 Pro, or Win XP (Home or
AZ> Pro) can all be set up for peer-to-peer networks (as could
AZ> the old Lantastic). 

When there is a machine designated as a 'server' that machine
is executing 'server software' and the workstations access that
machine using software described as a 'client'. With P2P there
are no servers/clients. All machines are executing the same
software. Or am I wrong about this fact? 

AZ> In my school, I use Win9x peer-to-peer networking, but
AZ> designate a couple of systems as what I refer to as
AZ> quasi-servers; they're acting as servers because no one
AZ> sits down at them and uses them as workstations. I do that
AZ> for a couple of reasons. One is security; I wouldn't want a
AZ> kid to be working at the system that stores everyone else's
AZ> files, records for keyboarding and ESL software, etc. The
AZ> other is performance... I found that having someone using
AZ> possibly CPU or Disk-intensive programs while others were
AZ> accessing files or printing via that system made for a
AZ> poorly-performing workstation and a poorly-performing
AZ> server. 

This arrangement works for you, obviously, but the designation
of 'server' and 'client' seems to be clouding what is actually
there. This is one of many reasons why discussions of
networking become confusing (to me). The terminology is applied
to anything and everything and it becomes a mishmash of random
information with no way to find the proper path. 

AZ> But it's a 'quasi-server' because it's running Win9x rather
AZ> than a 'real' network operating system. In some cases, the
AZ> distinction can be nominal-- there are reportedly only a
AZ> few Registry settings different between NT 4 Server and
AZ> Workstation or Win 2000 Server and Professional-- and a
AZ> hack floats around the Net to instantly switch between one
AZ> and the other. 

I've not tried to write any Windows telecom software or
networking software but I have written telecom for several
machines over the years (not just Intel) and not long ago wrote
a telnet terminal app for testing zmodem downloads while
connected using TCP/IP. From a programming standpoint (my
opinion) if the OS can manage TCP/IP or any other network
'protocol' it is _real_networking_software_. I have a link at
my website to use an 80xx machine running MSDOS as a server
connected to the internet and the authors do have an XT machine
online that you can view for yourself. :-) 

AZ> (One of the differences is that NT4 Workstation and Win2000
AZ> Pro are limited to 10 connections at a time). 

I've already hacked that registry entry to 40 if I remember
correctly - it's been some years ago now. 

AZ> A Linux installation can be used either as a workstation or
AZ> a server; the difference is what optional programs are
AZ> installed (Apache for web serving, for instance). 

This would also be true for Windows. I don't see a difference
here? 

AZ> 3) I agree-- I don't know of any 'theoretical' reason why
AZ> NetBEUI should be needed on a properly set up TCP/IP
AZ> network... but it seems to make a big difference in real
AZ> life. 

I have zero doubts that what you are telling me (and others) is
true, that NetBEUI makes it all 'come together' and work. I
just don't like shooting blind not knowing what I am adding to
my OS or why I am adding it. Somewhere down the road when
trouble starts I have no place to start because I never knew
why it worked in the first place. 

I know, I'm being a pest about this but if no one here on FIDO
knows then I will ask elsewhere and continue my search until it
ends or I do whichever comes first. :-) 

>
>        ,                          ,
>      o/      Charles.Angelich      \o       ,
>     <|                              |>  __o/
>     / >          USA, MI           < \   __\__
 

--- * ATP/16bit 2.31 * 
... DOS the Ghost in the Machine! http://www.devedia.com/dosghost/
 * Origin: Try Our Web Based QWK: DOCSPLACE.ORG (1:123/140)