Chapter 5: LAN Software

Architectures
LAN Software Architecture
In this lesson, we will examine the various
software technologies that operate at Layer 3 and
above. We will introduce the key elements and
protocols of most important network operating
system (NOSs), and compare the layered
protocols of each NOS to the OSI model.

Keypoint: Most LAN architectures conform largely

to the OSI reference model. All major LAN
architectures support TCP/IP.
NOSs and LAN Architectures
NOS manages the interface between a network’s
underlying transport capabilities and the applications
resident on a server. On the PC LANs and OSI Model
Diagram, the NOS itself operates at a high level in the OSI
model.

However, each major NOS also includes protocols that

operate between the Session Layer and Data Link Layer.
We call this combined suite of NOS and underlying
protocols a “LAN architecture”.
PC LANs and OSI Model
These suites of software are sometimes referred to as “internet-working
protocols,” because the upper layers of the OSI model provide communication
between separate LANs. For example, Layer 3 protocols are responsible for
routing data from one network to another. Communication between different
LAN architectures is provided by higher layers. One of the most common
examples of this practice is the use of the worldwide internet as a common
ground to link separate LANs.
NetBIOS and NetBEUI
On the PC LANs and the OSI Model Diagram, the Session
Layer is represented by a protocol we have not discussed
yet. NetBIOS was originally developed by Sytek and IBM to
allow a NOS to communicate with computer hardware.

Thus, just as a desktop operating system (OS) calls its

local computer’s Basic Input/Output System (BIOS) for
services such as reading a file, a NOS can call NetBIOS for
network services such as transmitting a file to a remote
node.
An application makes its request for a network services in
the form of a Network Control Block (NCB). Each NCB
includes information such as the destination node.
Although NetBIOS is often shown as operating as the
Session Layer, it also provides some Transport Layer
services.

Thus, it can control continuous sessions between two

computers, as well as provide connectionless packet
transmission. However, it does not support routing of data
to destination in another network, and must use the
services of TCP to do that job. NetBIOS also does not
specify its own standard format for the data it transmits.
IBM later developed NetBEUI, which functions at
the OSI Network and Transport Layers. NetBEUI
defines a standard format for data frames to be
passed down to the Data Link Layer. It also does
not route messages to other networks.

However, for data transmitted within the same

network, NetBEUI can increase network
efficiency. Because it does the job of both the
Transport and Network Layers, it reduces the
amount of network overhead.
NetWare
Novell, incorporated in 1983, has experienced
phenomenal success. Originally developed as a file
server OS, NetWare has gone through several
revisions, each one strengthening and broadening the
product.

The current version, NetWare 6, has become a top

choice for Internet-enabled business. Today, NetWare
provides a full suite of networking functions and
services, including directory, communications,
Internet and e-business solutions, and messaging
services.
With NetWare, customers can start small and
build to massive networks, based on their
networking requirements. Novell’s distributed,
multitasking NOS is designed to provide and
coordinate all network services, including file
directory services, print services, software
protection services, network security, and
messaging.
NetWare Protocol Layers
NetWare’s legacy architecture readily maps to the OSI model, as shown on
the OSI Model and NetWare Diagram. NetWare 5 and newer commonly use
TCP/IP as the native protocol suite, but continue to support IPX/SPX for
backward compatibility. At the Physical and Data Link Layers, NetWare
supports the 802.2 Logical Link Layer, Ethernet, and Token Ring, as well as a
number of other network architectures.
The Network and Transport Layer functions are handled
by Novell’s Network and Transport Layer protocols,
Internetwork Packet Exchange (IPX) and Sequenced
Packet Exchange (SPX), respectively.

At the Session Layer, NetWare supports the NetBIOS

interface. The Presentation and Application Layers
provide NetWare value-added services, various user
applications, and NetWare Core Protocol (NCP) services.
PCs and workstations use NCP to communicate with the
OS to obtain network services for their local applications.
AppleTalk
AppleTalk is Apple Computer’s proprietary LAN software
for Macintosh computers. Consistent with the simple
Macintosh interface, an AppleTalk network was designed
to be very easy to set up. Originally, an AppleTalk
network used a proprietary Physical Layer technology
called “LocalTalk”.

Users plugged a low-price LocalTalk connection box into

the Macintosh printer port, then attached a 2m cable to
the connection box on the next Macintosh or peripheral
device in the network. Each Macintosh was shipped with
hardware and software required to participate in the
network.
Shift to Open Standards
However easy an AppleTalk network was to build, users
argued that it had major flaws. Its data transfer rate was
only 230.4-kilo-bits per second (Kbps), and the network
could only support 32 Macintoshes. Customers were also
required to use shielded twisted pair (STP) wiring in a
daisy-chain topology.

In June 1989, Apple’s determination to be taken seriously

resulted in AppleTalk Phase II. AppleTalk Phase II
represented a complete turnaround from Apple’s usual
proprietary stance.
The LocalTalk Physical Layer offered alternatives, such as
the PhoneNET system, which used unused telephone wires
as cabling. Fiber optic connections were also developed,
and wiring concentrators for both types of cable made
star topologies possible.

In addition to the improved LocalTalk, AppleTalk Phase II

also operated over Ethernet and Token Ring networks (by
means of EtherTalk and TokenTalk software,
respectively), supported coaxial cable as well as STP, and
supported products that facilitate the integration of
Macintoshes into digital, IBM, TCP/IP, UNIX, and OSI
environments. The OSI model and AppleTalk Phase II
Diagram illustrates how this software maps to the
reference model.
OSI Model and AppleTalk Phase II
Microsoft Windows NT
Microsoft’s Windows NT is a 32-bit OS that was designed
to support client applications easily and transparently in a
distributed network environment. Networking is built into
Windows NT, including both client and server capabilities.
This allow any Windows NT computer to participate in a
network in either capacity.

Windows NT supports a variety of network protocols,

including TCP/IP, NetBIOS/NetBEUI, NWLink (for IPX/SPX
compatibility), AppleTalk, Point-to-Point Tunneling
Protocol (PPTP), and Data Link Control (DLC) (for
mainframe connectivity).
Windows NT can interoperate with the following
networks:
● Microsoft networks
● Novell NetWare
● TCP/IP, including UNIX hosts
● AppleTalk (Windows NT Server only)
● Remote access clients
At press time, Microsoft has built on Windows NT 4.0 to
develop Windows 2000 Professional and Server, Windows
XP Home and Pro, and its latest products, the Windows
Server 2013. Hence, the basic Windows NT features and
functions discussed here also apply to newer Windows
operating systems.

The OSI Model and Windows NT Diagram shows how

Windows NT relates to the OSI reference model. At the
Physical and Data Link levels, Windows NT supports
various NICs and protocols, such as Ethernet and Token
Ring. The low-level device drivers that run on the NICs
interface with the Network Layer protocols through the
Network Driver Interface Specification (NDIS).
NDIS provides linkage between the Physical
Layer protocols and several Network Layer
protocols including:
●NetBEUI Format (NBF)
●DLC
●IPX
●IP
At the Transport Layer, Windows NT supports
TCP and SPX. The Transport Device Interfaces
(TDI) layer provides an interface between
multiple transport protocols, such as TCP, and
multiple networking environments.
At the Session Layer, client redirectors for
Windows NT and NetWare can be loaded on
the same workstation. The client/server
provider, at the Presentation Layer, allows
multiple applications to access the underlying
protocol stack.
Windows NT provides support for both
client/server applications and peer-to-peer
processing through preemptive mutlitasking,
and shared and protected memory support.
This allows Windows NT to be used in small
business that do not require large LAN service.
UNIX and TCP/IP
Networking in UNIX is
accomplished using
interprocess
communication (IPC)
between applications and
the networking protocol
stacks.

The UNIX Networking

Diagram shows a typical
UNIX protocol stack.
As we can see on the diagram, the UNIX
protocol stack essentially compress the OSI
model. UNIX uses one process to perform some
tasks that the OSI model splits into two layers.
The reason for this is simple: UNIX was
developed before the OSI model.Most UNIX
systems provide multiple protocol suites,
including TCP/IP, SNA, Xerox Network System
(XNS), and NetBIOS.
Common Ground: TCP/IP
The acronym TCP/IP represents the common working combination of the
Transmission Control Protocol and Internet Protocol. However, the term is
often used to denote much more than just the protocols themselves. The
TCP/IP “world” can be considered to include other components, such as the
entire suite of protocols, software, and applications that are standard parts
of most UNIX-based and PC-based OSs.

TCP/IP is normally used as the protocol stack in UNIX networking

implementations. As we have just seen however, those protocols are also
supported by all major NOSs. Now that the Internet has become an essential
business tool, many corporate networks find it convenient to use TCP/IP as
their Transport and Network Layer protocols. Thus, while various networks
may use NetWare, Windows NT, or AppleTalk, it is likely each of those OSs is
also configured to use TCP and IP.