Transcript COS338_Day1and2 - Tony Gauvin`s Web Site

COS 338
Day 1 Introduction
Agenda

Roll Call

Introduction to Course

WebCT Overview

Syllabus Review

Introduction to Networking
2
INSTRUCTOR

Tony Gauvin, Assistant Professor of ECommerce

Contact info

216 Nadeau

[email protected]

(207) 834-7519 or ext 7519

WebCT (Tony Gauvin COS 125)
3
Instructional Philosophy

Out-Come based education

Would rather discuss than lecture


Hate grading assignments


Requires student preparation
Especially LATE assignments
Use class interaction, assignments, quizzes,
labs and projects to determine if outcomes are
met.
4
COS 338 Survival Primer

Read Material BEFORE the class discussion

Check WebCT Often

Use the additional resources identified in syllabus

ASK questions about what you didn’t understand in readings

DON’T do assignments and projects at last minute.

REVEIW lectures and notes

Seek HELP if you are having difficulties

OFFER feedback and suggestions to the instructor in a
constructive manner
5
Computer Accounts



Computer login

Sys admin
 Pete Cyr (x7547) or Art Drolet (x7809)

Applications
MSDN Academic Alliance

Free Stuff

See Dr. Ray Albert
Access Cards

$10 deposit

See Lisa Fournier
6
WebCT

http://webct.umfk.maine.edu

Login

First name. Last Name

John Doe  John.Doe

Initial password is webct

Help with WebCT available from Blake Library staff

All quizzes and assignments will be administered from
WebCT
7
COS 338 Specifics

Fully WebCT enabled


Market Driven Content


All Quizzes, assignments, projects
Wireless, Ethernet, QOS, Security, Frame Relay, TCP/IP, Windows XP
Cohesion Case

First Bank of Paradise

Managerial Perspectives instead of technical

Lab Components


Hands-on using OMS CIAG Lab
 Students will build a SOHO LAN with working apllications

Simulations using Opnet IT Guru and ACE
Follow-up Course Cos 420 Internet and Intranet Architecture will be
much more technical and will be based on TCP/IP
8
Syllabus review

Requirements

Grading

Course outline

Special Notes

Subject to change
9
Introduction
Chapter 1
Panko’s
Business Data Networks and Telecommunications, 5th edition
Copyright 2005 Prentice-Hall
The Chapter

This chapter is a survey of
the key concepts we will
see in this course

The rest of the book
essentially fleshes out out
the concepts we will see
in this chapter
11
The Chapter

Networking is a Head
Game

There is a lot of
information to master

There are many TLAs
(three-letter
acronyms)

For design and
troubleshooting, you
must know everything
to do anything.
12
Learning Objectives

By the end of this chapter, you should be able
to

Discuss the First Bank of Paradise (FBP), our
running case study for this book.

Discuss the major types of networked applications.

List the eight elements of networks.

Explain the major types of networks in businesses:
LANs, WANs, internets, intranets, and extranets.
13
Learning Objectives

By the end of this chapter, you should be able
to

Discuss major concerns for network
managers: staffing, network architecture,
standards, security, wireless networking,
efficiency, and quality of service (QoS).

Explain the elements and operation of a
small home PC network using a LAN.
14
Learning Objectives

By the end of this chapter, you should be able
to

Use some key hands-on network
management tools, including bandwidth
measurement services, ping, ping 127.0.0.1,
tracert, ipconfig, winipconfig, nslookup, and
the use of Windows Calculator to compute
dotted decimal notation IP addresses.
15
First Bank of Paradise (FBP)

The book’s cohesion case study

Composite mid-size bank in Hawaii

Banks are fairly “typical” firms, although they
have stronger need for security

Warren Chun is the chief information officer
(CIO)

Yvonne Champion is the network manager
16
First Bank of Paradise (FBP), Continued

Annual Revenues: $4 Billion

Operations


50 Branches

350 ATMs (Automated Teller Machines)
Network

500 Ethernet switches

400 Routers
17
First Bank of Paradise (FBP), Continued


Computers

2,000 desktop and notebook user PCs

200 Windows servers

30 Unix servers

10 Novell NetWare file servers
Information Systems Staff

150 people
18
Figure 1-1: Networked Applications at the First
Bank of Paradise

Networked Applications are
Applications Made Possible by
Networking


E-mail, etc.
Users Only Care About
Applications

The rest is just details to them
19
Figure 1-1: Networked Applications at the
First Bank of Paradise, Continued

E-Commerce

Buying and selling on the
Internet

Users typically interact with
databases

Customers will soon be
able to talk to customer
representatives while online
20
Figure 1-1: Networked Applications at the
First Bank of Paradise, Continued

Transaction
Processing

Simple, highlystructured, and highvolume interactions,
such as check
processing

Built around
databases

External settlement
networks
21
Figure 1-1: Networked Applications at the
First Bank of Paradise, Continued

Transaction Processing

Back-office transaction
processing applications
 Accounting, payroll,
purchasing, human
resources, etc.

Functional databases in
individual departments
22
Figure 1-1: Networked Applications at the
First Bank of Paradise, Continued

Office Applications

Word processing,
spreadsheeting, etc.

E-mail, instant messaging
(IM), and Web access
23
Figure 1-2: Elements of a Network
Message (Frame)
Application
Application
Client
Station
Switch
Server
Station
Networks connect
Switch
applications Trunk
on different stations.
AccessApplications
Switch are all users care about
Line
Trunk
Line
Line
Mobile Client
Station
Switch
Outside
World
Router
Mobile Client
Station
24
Figure 1-2: Elements of a Network, Continued
Message (Frame)
Application
Application
Client
Station
Switch
Server
Station
Networks connect stations:
Switch
clients (fixed and
mobile) and servers
Trunk
Access Switch
Line
Trunk
Line
Line
Mobile Client
Station
Switch
Outside
World
Router
Mobile Client
Station
25
Figure 1-2: Elements of a Network, Continued
Message (Frame)
Application
Application
Client
Station
Switch
Stations (and routers)
usually communicate
Access Switch
by sendingLine
messages
called frames
Mobile Client
Station
Trunk
Line
Switch
Server
The path Station
a frame takes
Switch
is called its data link
Trunk
Line
Outside
World
Router
Mobile Client
Station
26
Figure 1-2: Elements of a Network, Continued
Message (Frame)
Application
Application
Client
Station
Switch
Server
Station
Switch
Access
Line
Mobile Client
Station
Trunk
Switch
Switches
Linemove frames
Trunk
to or closer to the destinationLine
station
Outside
World
Switches handle a packet sequentially
Switch
Router
Mobile Client
Station
27
Figures 1-6 and 1-7: Workgroup and Core
Switches
19 inches (48 cm) wide
19 inches (48 cm) wide
Small Switches
(Stacked):
Workgroup Switches
To Link Stations
To Network
Central Core Switch
28
Figure 1-2: Elements of a Network, Continued
Message (Frame)
Application
Application
Client
Station
Switch
Access
Line
Server
Station
Routers connect networks Switch
to the outside world;
Trunk
Switch Treated just like stations
Line
Trunk
Line
Mobile Client
Station
Outside
World
Switch
Mobile Client
Station
Router
29
Figure 1-2: Elements of a Network, Continued
Message (Frame)
Application
Application
Access lines
Client
connect stations
Station
to switches
Trunk lines
Switch
connect switches
to switches (and routers)
Server
Station
Switch
Access
Line
Switch
Mobile Client
Station
Trunk
Line
Switch
Trunk
Line
Trunk
Line
Outside
World
Router
Mobile Client
Station
30
Figure 1-2: Elements of a Network (Recap)

Applications (the only element that users care about)

Stations


Clients
Servers

Switches

Routers

Transmission Lines



Trunk lines
Access Lines
Messages (Frames)
Never talk about an
Innovation “reducing cost,”
“increasing speed,” etc.
without specifying
which element is
cheaper or faster.
For example, multiplexing
only reduces the cost of
trunk lines; other
costs are not decreased
31
Figure 1-3: Multiplexing in a Packet-Switched
Network
Trunk line
multiplexes the
messages of
different
conversations
AC
Client
Station A
AC
AC BD
BD
Mobile Client
Station B
AC
AC
Trunk Line
Access
Line
AC
This reduces
trunk line
costs through
cost sharing
by users
Server
Station C
BD
BD
Router D
32
LANs and WANs

LANs transmit data
within corporate sites

WANs transmit data
between corporate sites

Each LAN or WAN is a
single network
WAN
33
DAY 2 Agenda

Questions?

8 elements of a network?

Differences between LAN and WAN

Assignment 1 due next class

Opnet Lab 1 next class


Read Home PC Network Lab Manual.pdf loaded in WebCT
Today

Finish Introduction

Some Hands on Computer stuff
34
Figure 1-4: The First Bank of Paradise’s
Wide Area Networks (WANs)
North Shore
Operations
OC3 Private Line
T3
T3
Headquarters
Bank has multiple
facilities connected
by multiple WANs
35
Figure 1-5: Local Area Network (LAN) in a
Large Building
Multi-floor
Office Building
The bank has multiple
LANs—one at each site
36
Figure 1-5: Local Area Network (LAN) in a Large
Building, Continued
Wall Jack
Workgroup Switch
Workgroup Switch
To
WAN
Router
Core Switch
37
Internets

Most firms have multiple LANs and WANs.

They must create internets

An internet is a collection of networks connected by
routers so that any application on any host on any
single network can communicate with any
application on any other host on any other network
in the internet.
Application
Application
LAN
WAN
Router
LAN
Router
38
Figure 1-8: Internet with Three Networks
Host A
R1
Packet
Network X
Network Z
A packet goes all the
way across the internet;
It’s path is its route
Network Y
Route A-B
R2
Host B
39
Figure 1-8: Internet with Three Networks,
Continued

Messages in single networks (LANs or WANs) are
called frames

Message in internets are called packets


Travel from the source host to the destination host
across the entire internet
Within a single network, the packet is encapsulated in
(carried in) the network’s frame
Packet
Package
(Packet)
Truck
(frame)
Frame
40
Figure 1-8: Internet with Three Networks,
Continued
Frame X
Details in
Network X
Packet
Data Link
A-R1
Switch
Host A
Switch
Server
Host
Switch
X1
Mobile Client
Host
Switch
X2
Route
A-B
Router R1
Network X
41
Figure 1-8: Internet with Three Networks,
Continued
Details in
Network Y
To
Network X
Route
A-B
Router R1
Data Link
R1-R2
To
Network Z
Router R2
Frame Y
Packet
Network Y
42
Figure 1-8: Internet with Three Networks,
Continued
Data Link
R2-B
Details in
Network Z
Packet
Frame Z
Switch
Z1
Host B
Switch
Router R2
Switch
Z2
Mobile Client
Hosts
Switch
Router
Network Z
43
Figure 1-8: Internet with Three Networks,
Continued

In this internet with three networks, in a
transmission,



There is one packet
There are three frames (one in each network)
If a packet in an internet must pass through N
networks,


How many packets will be sent?
How many frames must carry the packet?
44
Figure 1-8: Internet with Three Networks,
Continued

Lower-case internet is any internet

Upper-case Internet is the global Internet
45
Figure 1-11: The Internet
Webserver
User PC
Access
Line
The Internet Backbone
(Multiple Carriers)
Access
Line
Router
NAP
ISP 2 NAP
NAP
ISP 1
ISP 4
ISP 3
Internet
Service
Provider
For User PC
NAP = Network Access Point
Internet Service
Provider
For Webserver
46
Figures 1-9 and 1-10: Routers
19 inches (48 cm) wide
19 inches (48 cm) wide
Small Routers
Stacked
For Branch Offices
Large Routers
for Large Sites and ISPs
47
Figure 1-12: The Internet, internets,
Intranets, and Extranets

internets versus the Internet

Intranets


Internal internet for use within an organization

Based on the TCP/IP standards created for the
Internet
Extranets

Connect multiple firms
 Only some computers from each firm are on the
extranet

Use TCP/IP standards
48
Recap


Switches versus Routers

Switches move frames through single networks
(LANs or WANs)

Routers move packets through internets
Messages

Messages in single networks are called frames

Messages in internets are called packets

Packets are encapsulated within frames
49
Figure 1-13: Major Network Technical
Concerns

Network Architecture

A broad plan for how the firm will
connect all of its computers
within buildings (local area
networks), between sites (wide
area networks), and to the
Internet

New systems must fit the rules
of the architecture

Undisciplined growth in the past
 No overall plan
50
Figure 1-13: Major Network Technical
Concerns, Continued

Network Architecture

Legacy networks

Use obsolete technologies that
do not fit the long-term
architecture

Many exist in the bank

Too expensive to replace
quickly; must live with many for
awhile
51
Figure 1-13: Major Network Technical
Concerns, Continued

Network Architecture

Scalability
 The ability of selected technologies to be able to
handle growth efficiently
Cost
Per
Bit
Poor
Scalability
Good
Scalability
Demand
52
Figure 1-13: Major Network Technical
Concerns, Continued

Standards

Standards govern message interactions between
pairs of entities (Figure 1-14)

For example, HTTP request and response messages for
WWW access
Webserver
HTTP Request Message
Client PC
Browser
Client
Program
HTTP Response Message
Webserver
Application
Server
Program
53
Figure 1-13: Major Network Technical
Concerns, Continued

Standards

Standards create competition

This reduces costs

It also stimulates the development of new
features

Protects the business if the main vendors go
out of business
54
Figure 1-13: Major Network Technical
Concerns, Continued

Standards

Competing standards organizations create
incompatible standards

FBP will standardize to save money

LANs: FBP will standardize on Ethernet (some
legacy LAN technologies are still in use)

WAN standards: will have fewer but still two to four

Internetworking: will standardize on TCP/IP
55
Figure 1-13: Major Network Technical
Concerns, Continued

Security

A Major Problem

Many attacks

Growing trend toward
criminal attackers
56
Figure 1-15: Firewalls
Allowed Legitimate Border
Packet
Firewall
Attacker
Hardened
Server
Hardened
Client PC
Border firewall
should pass
legitimate packets
Log File
Legitimate
Packet
Legitimate
Host
Internal
Corporate
Network
57
Figure 1-15: Firewalls, Continued
Border firewall
should deny (drop)
Hardened and log
Server attack packets
Hardened
Client PC
Border
Firewall
Attack Packet
Denied
Attack
Packet
Log File
Network Management
Console
Attacker
Legitimate
Host
Internal
Corporate
Network
58
Figure 1-13: Major Network Technical
Concerns, Continued

Security

Virtual Private Networks (VPNs) (Figure 1-16)

Provide communication over the Internet with
added security

Cryptographic protection for confidentiality
(eavesdroppers cannot read)

Cryptographic authentication (confirms sender’s
identity)
59
Figure 1-16: Virtual Private Networks
(VPNs)
Site-to-Site VPN
Using Gateway
Client
VPN
Remote Access
Gateway PC 1
VPN Using
Corporate
Gateway
Site B
VPN
Gateway
Internal
Server
Corporate
Site A
Internet
Host-to-Host
VPN
Remote
Client PC 2
Remote Client PC 3
60
Figure 1-13: Major Network Management
Concerns, Continued

Wireless
Communication

To improve mobility

Drive-by hackers can
eavesdrop on internal
communication

Drive-by hackers can
break into the network
bypassing firewalls
Drive-By Hacker
61
Figure 1-13: Major Network Technical
Concerns, Continued

Need for Efficiency
 User demand is growing rapidly
 Budgets are growing slowly if at all
 For projects, need burning justification
 Still add new services by squeezing maximum
payback from each dollar
Money/
Demand
User Demand
Budget
Time
62
Figure 1-13: Major Network Technical
Concerns, Continued

Quality of Service (QoS)
QoS

Numerical objectives for performance

Transmission speed in bits per second (bps)



A bit is a single one or zero
NOT bytes per second
Increase by factors of 1000, not 1024
 kilobits per second (kbps)—lower-case k
 Megabits per second (Mbps)
 Gigabits per second (Gbps)
 Terabits per second (Tbps)
63
Figure 1-13: Major Network Technical
Concerns, Continued

Quality of Service




For Transmission Speed, have 1 to 3 places
BEFORE the decimal point.
Example
 .5 Mbps is wrong
New
 500 kbps is correct
Not in the Book
Example
 2,300 Mbps is wrong
 2.3 Gbps is correct
Example
 473.2 Mbps is correct
64
Figure 1-13: Major Network Technical
Concerns, Continued

Quality of Service

Typical transmission speeds in
most firms:

LANs: 100 Mbps to each
desktop

WANs: most site-to-site links
only are 56 kbps to a few
megabits per second because
long-distance transmission is
very expensive and so must
be used more sparingly
LANs:
100 Mbps
WANs:
56 kbps
to a few
Mbps
65
Figure 1-13: Major Network Technical
Concerns, Continued

Quality of Service

Congestion, Throughput, Latency, and
Response Time

Congestion: when there is too much traffic for
the network’s capacity

Throughput: The speed users actually see
(often much less than rated speed)

Individual throughput is less than total
throughput on shared-speed links
66
Figure 1-13: Major Network Technical
Concerns, Continued

Quality of Service

Congestion, Throughput,
Latency, and Response Time
 Latency: delay (usually
measured in milliseconds or
ms)

Within corporations, latency is
typically under 60 ms 90% of
the time

On the Internet, typically 30
ms to 150 ms
67
Checking latency

Use Ping

Start -> Run-> cmd

Try ping 127.0.0.1
68
Checking throughput

Use an available bandwidth tester on the
Internet

http://reviewszdnet.com.com/Bandwidth_meter/7004-7254_160.html?tag=is

http://www.dslreports.com

http://www.bandwidthplace.com/speedtest/
69
Other XP Command line networking tools

Start -> run -> cmd

ipconfig /all /release /renew
 Show tcp/ip settings

Tracert
 Shows path of packet through Internet

nslookup
 Does DNS testing
70
Figure 1-13: Major Network Technical
Concerns, Continued

Quality of Service

Congestion, Throughput, Latency, and Response
Time
 Response Time

The time to get a response after a user
issues a command

A quarter second
or less is good
71
Figure 1-13: Major Network Technical
Concerns, Continued

Availability

Availability is the percentage of
time a network can be used

Downtime: when the user cannot use the network

Want 24x7 availability

Telephone network gives 99.999% availability

Typical networks reach 98% today
72
Figure 1-13: Major Network Technical
Concerns, Continued

Error Rate

Measured as the percentage of messages
damaged or lost

Substantial error rates can disrupt applications

Substantial error rates generate more network
traffic because of retransmissions
73
Pat Lee’s Home Network

Pat Lee is a vice president at FBP

Wants a network in her home


Family’s main computer is the downstairs PC

Daughter Emily has a PC in her room

Wants to connect both to the Internet through a
broadband (high-speed) cable modem service
Perspective

A small LAN but has all the key network elements
74
Figure 1-18: Pat Lee’s Home Network
1.
Coaxial Cable
to ISP
2.
Cable
Modem
3. UTP Cord
4.
Access
Router
75
Figure 1-22: Home Network Access Router
About 4 inches (10 cm) Wide
Power
Jack for
External
Power
Switch Ports
UTP Cords
Run to Stations
WAN Port
UTP Cord
Runs to
Cable Modem
76
Figure 1-18: Pat Lee’s Home Network, Continued
6.
A1-BD-33-6E-C7-BB
PC in Emily’s Room
5. UTP
Cord
5. UTP
Cord
6.
B2-CD-13-5B-E4-65
PC in Study
77
Figure 1-18: Pat Lee’s Home Network, Continued
6.
A1-BD-33-6E-C7-BB
PC in Emily’s Room
7. File
Sharing
6.
B2-CD-13-5B-E4-65
PC in Study
78
Figure 1-18: Pat Lee’s Home Network, Continued
6.
A1-BD-33-6E-C7-BB
PC in Emily’s Room
8. Printer
Sharing
6.
B2-CD-13-5B-E4-65
PC in Study
79
Figure 1-19: Network Interface Cards
(NICs) (Photo)
Internal NIC. Installed inside
systems unit. Plugged into
expansion slot on the mother
board.
PC Card NIC. Installed in PC
Card slot in notebook and some
PDAs.
80
Internal NIC
RJ-45
Jack
PCI Connector Pins
81
Computer Mother Board

Mother Board
PCI Slots
for Expansion Boards
(NICs, etc.)
Slots for RAM
Slot for
Microprocessor
(Pentium 4)
82
Mother Board and Expansion Boards
Expansion Board
(NIC)
Connector
Expansion
Slots
Mother Board
83
Figure 1-20: Unshielded Twisted Pair
(UTP) Cord With RJ-45 Connector (Photo)
4-Pair Unshielded Twisted Pair (UTP)
Industry Standard Pen
8-Pin RJ-45 Connector
UTP Cord
84
Figure 1-21: UTP Cord RJ-45 Connector and
Jack
UTP Cord
--About as thick
as a pencil
--Rugged and
Flexible
RJ-45 Jack
On a Wall
On a Switch
or
On a NIC
RJ-45
Connector
85
Figure 1-23: Logical Functions of the
Access Router
Cable
Modem
Access Router
Router Function
DHCP
Server
Function
NAT
Function
Switch Function
86
Figure 1-24: Ethernet Switch Operation
Switching Table
Port Host
10
A1-44-D5-1F-AA-4C
13
B2-CD-13-5B-E4-65
15
C3-2D-55-3B-A9-4F
16
D4-47-55-C4-B6-9F
Ethernet Switch
UTP
UTP
Frame To C3…
A1-44-D5-1F-AA-4C
UTP
UTP
D4-47-55-C4-B6-9F
Frame To C3…
C3-2D-55-3B-A9-4F
B2-CD-13-5B-E4-65
87
Figure 1-25: Frames and Packets
Cable
Modem
Packet in
DOCIS
Frame
Internal
Router
Access Router
Packet is always
carried (encapsulated)
in a frame
A1-BD-33-6E-C7-BB
IP address = 192.168.0.3
PC in Emily’s Room
Packet in
Ethernet Frame
B2-CD-13-5B-E4-65
IP address = 192.168.0.2
PC in Study
88
Figure 1-26: Dynamic Host Configuration
Protocol (DHCP)
Cable
Modem
ISP
DHCP
Server
1.
IP Address =
60.47.112.6
Access Router
A1-BD-33-6E-C7-BB
PC in Emily’s Room
The ISP only
Gives each home a
Single IP address B2-CD-13-5B-E4-65
PC in Study
A DHCP Server
provides User PCs with
a temporary IP Address
each time the user
connects to the Internet
89
Figure 1-26: Dynamic Host Configuration
Protocol (DHCP), Continued
Cable
Modem
ISP
DHCP
Server
1.
IP Address =
60.47.112.6
Internal
DHCP
Server
Access Router
A1-BD-33-6E-C7-BB
IP address = 192.168.0.3
PC in Emily’s Room
2. IP Address =
192.168.0.3
2. IP Address =
192.168.0.2
The access router’s
Internal DHCP server
Gives private IP
Addresses to each PC
B2-CD-13-5B-E4-65
IP address = 192.168.0.2
PC in Study
90
Figure 1-27: Network Address Translation
(NAT)
2. Packet from
60.47.112.6
Webserver
IP address=
123.7.86.285
Cable
Modem
Internal
NAT
Module
Access Router
The access router’s NAT
module translates between the
private IP addresses and
the single ISP-given IP address
1. Packet from
192.168.0.2
PC in Study
192.168.0.2
91
Figure 1-27: Network Address Translation
(NAT), Continued
3.
Packet
to
60.47.112.6
Webserver
IP address=
123.7.86.285
Cable
Modem
Internal
NAT
Module
Access Router
4. Packet to
192.168.0.2
PC in Study
192.168.0.2
92
Figure 1-28: The Domain Name System
(DNS), Continued
DNS Table
Originating
Host’s DNS
Resolver
Host Name
…
…
Voyager.cba.hawaii.edu
…
IP Address
…
…
128.171.17.13
…
DNS Request Message
“The host name is Voyager.cba.hawaii.edu”
DNS Response Message
“The IP address is 128.171.17.13”
DNS
Host
93
Other XP Command line networking tools

Start -> run -> cmd

nslookup
 Does DNS testing

Try nslookup mail.maine.edu
94
Figure 1-29: Converting Binary IP Addresses to
Dotted Decimal Notation
Binary
IP Address
01111111101010110001000100001101
8-Bit
Segments
01111111 10101011 00010001 00001101
Convert
Segments
to Decimal
Dotted
Decimal
Notation
127
171
17
13
127.171.17.13
95
Figure 1-30: Windows Calculator
1. Open Calculator, which is in
the Program Group Accessories
2. Select View,
Scientific
96
Figure 1-30: Windows Calculator
4. Enter data on keypad
(Limit is 8 bits for Binary)
3. Enter initial
data type here
Dec = Decimal
Bin = Binary
97
Figure 1-30: Windows Calculator
6. Observe answer
5. Enter final
data type here,
observe results
Initial zeros are dropped,
so answer is 0001 0111
98
Topics Covered

The First Bank of Paradise

Networked Applications

Packet switching and Multiplexing

LANs versus WANs

Within a site versus between sites
99
Elements of a Network
Message (Frame)
Application
Application
Client
Station
Switch
Server
Station
Switch
Access
Line
Switch
Mobile Client
Station
Trunk
Line
Switch
Trunk
Line
Outside
World
Router
Mobile Client
Station
100
Topics Covered

Internets



Package
(Packet)
Routers
Packets carried within frames
Truck
(frame)
Categories

Internets

The Internet: ISPs and NATs

Intranets

Extranets
101
Topics Covered

Network Architecture

The Need

Legacy Networks

Scalability

Standards

Need for Efficiency
102
Topics Covered

Security

Firewalls

VPNs

Wireless Communication
103
Topics Covered

Quality of Service (QoS)

Numerical objectives that must be met

Speed and throughput

Latency

Response time

Availability

Error rate
104
Topics Covered: Pat Lee’s Home Network
6.
A1-BD-33-6E-C7-BB
PC in Emily’s Room
2.
Cable
Modem
1.
Coaxial Cable
to ISP
3. UTP Cord
5. UTP
Cord
4.
Access
Router
7. File
Sharing
5. UTP
Cord
6.
B2-CD-13-5B-E4-65
PC in Study
8. Printer
Sharing
105
Topics Covered: Pat Lee’s Home Network

DHCP

NAT

DNS
106