>> Hi, everybody,
this is Katie.
Welcome to Network+.
We are gonna cover Chapter 1
in this short video.
Now, I'm gonna go
through these things,
the main points in this
chapter pretty quick
because I know that
attention spans
are kind of not very high
when you're just listening
and reading
the chapter.
But I wanna read through
it together with you
so that it will help
you open the chapter.
A lot of us won't
do that otherwise.
So I'll try to keep
it under 20 minutes.
This is Chapter 1, "An
Introduction to Networks."
We'll have some assignments
at the end of this,
or with this chapter, that
are out of Chapter 1.
The objectives-- identify an
application and protocol,
looking at client-servers,
various network hardware,
a little introduction
to the OSI,
best practices for safety,
and troubleshooting models.
Now, before we go
into the book--
uh, into the PowerPoint
presentation,
and cover the
main things,
I wanna talk for a
second about CompTIA
and the changes
to this textbook.
Whoop...
bum, bum, bum.
Let's go over there,
uploading video, CompTIA.
Now, I met the author of the
book this summer, in 2015,
and I loved her.
She was dynamic, I loved
the way she wrote the book,
and I loved the new edition
because it lays things out,
one, that follow the
Net+ certification exam,
but two, in a way where
it's easy to read.
The author, Jill West
and Jean Andrews,
if you look at the
front of the book,
I met both of
those this summer.
Tamara Dean is
our previous author,
so she's also
still on the book
because they kept some
of the legacy things.
But Jill-- the way that
this book is structured
is so much better
than before.
I think you're
going to like it
and it's going to
really help you
to prepare for the
Net+ certification.
Now, I'll make another
video on that,
because if there's
anything in this chapter
that we need
more focus on,
I will make a different
video for that
so that they're short videos
and not super long.
But I do want you to
go to comptia.org,
go to their
certification site,
and I want you to register
and create an account there,
because one of the main
goals of this course
is to get you
certified.
And without getting
their information,
or without getting
their study guides
and their Net+
objectives,
we are not going to be
able to get certified.
So go through this process,
create a username and password,
or you can-- from here,
we can cross that off,
and click on
comptia.org,
and then do the
"Register" option here.
Then, once you
register...
"Register User"-- once you
fill out this information,
you just create a
username and password,
and then you're
able to log in.
Let me log into
mine real quick.
I'm just a normal
person, like you.
I don't have any
special privileges.
You can use your
student email account.
Save my password.
That, it doesn't know.
Maybe not.
Well, we'll go back
to that later.
I have to, apparently,
fix my account.
I don't wanna waste my
precious 20 minutes doing that.
Create an
account anyway.
On the CompTIA website,
one of the things
we're going to do with
the assignments is,
we're going to
look at the Net+.
So you can go to the
Net+ site-- Network+--
without logging in.
Or if you don't wanna create
an account yet, that's fine.
It does cover
the exam objectives.
This is also part
of Chapter 1.
I don't like to go through
the PowerPoint slide by slide,
so I'm jumping around.
And then, at the end, we'll
skim through the PowerPoint
and see what
we missed.
It goes through the
exam objectives.
Oh, I guess we gotta
put in this information.
All right, fine.
Even though I've done
this a million times.
Professor-- you
can put "student."
You could call yourself
a chef if you want,
they don't really care.
You could be
whatever.
United States.
Exam Objectives.
I am...
"Currently Training,"
and I plan to take the exam
in three to six months.
I want to get
a job-- bam!
CompTIA is the best site
to get our most up-to-date
and current
objectives.
They're not
going to change.
The new test-- the 006
is what it is--
was released
just this summer.
That is why we have a new
edition to the textbook
and why we're learning
these new objectives.
Come on.
I have everything
filled out.
Ah, name required.
See?
Slow going--
there we go.
One of the links
I have in Blackboard
is a link to where you
can go to take the test.
But I'll cover that
in another video.
We have the
N10-006.
Those are the objectives
that we're covering.
The 005 is the one that's
just recently expired.
So we want to go to here, and
I will download that, too,
so you have that, and
throw it in Blackboard.
But you should create
a copy of it, too,
or keep a copy
of it, as well.
One of your assignments is
going to look through this.
Also, we have required
Transcender for this class.
And you can see the five topics
that CompTIA tests you on.
One of the other people I
met in the summer of 2015
was the Transcender
test writer.
She explained to me
how she writes the test
to get people to pass from
the CompTIA certification.
That was also
really useful.
Once we get into Transcender,
which is required,
I will teach you
how to use that
through a
different video.
And that will be our
main tool for cramming in
and studying and passing
this certification test
at the end of
the semester.
But it's broken down into
five different categories.
Again, that's kind of
how our book is laid out
and the structure of where
we're going with the textbook.
But here are a list
of the objectives
from CompTIA
directly.
Now, the reason I like
this as a secondary tool
to the textbook is
that it is just a list
of things that
you need to know
and doesn't include
all the explanation.
So it's very long, but it's
shorter than the textbook,
and then it doesn't
explain it.
So you'll have to go,
"Okay, what is evil twinning
"on a wireless network," or
"What does brute force mean?"
And then, you have to be
able to define those.
So these are all
of the objectives.
Acronym list--
holy acronyms!
Transcender is
going to help us
know all of
these objectives
that are on this
document from CompTIA.
Don't worry
about that now.
We're just in
Chapter 1.
But you wanna keep
that and save it.
Some of the other things
from this CompTIA site
that you'll see--
study materials,
you don't need to
buy anything else.
I think with-- well, I know
with just this textbook,
your commitment,
and Transcender,
you can pass
the test.
Finding a testing center
and paying for the test,
you don't wanna buy
a voucher from here.
You wanna buy a voucher
from Davenport...
or...
or GRCC.
But at this particular
time, we don't have
our testing center and our
vouchers purchased yet.
But Davenport sells
their vouchers to us
at a discounted price.
I have this information
in Blackboard, as well.
I'll also list it
as part of this video.
So, "Purchase
a Voucher"--
you can purchase any one
of these from Davenport.
We are setting up our own
system here at the college.
But I don't know
if it'll be ready
by the time you're
ready to test.
You can do the Net+
for 163.24 right now.
That price fluctuates
sometimes.
But if you bought
that voucher here,
it is $277.
No way.
$110 or
$13 cheaper,
or $100-and-some-odd-dollars
cheaper if you bought it here.
So, much better option
and place to go.
I'll share that
link with you.
But that's, for now,
what you need to know
about the CompTIA
and the Net+ cert.
That-- in the back of the
chapter, the hands-on projects
that start on page 43--
we'll look at, like, 1.4
as part of
our assignments
that has you looking at
some of those things--
what are certifications,
what degrees are required?
It does a little
job search.
It's a good way to
kind of get an idea
of what the CompTIA
Network+ exam is.
So that is a big portion of
what Chapter 1 is about.
Now, going back to the
chapter from the beginning.
If I look at--
I'm on page 2,
so I'm just starting
at the beginning.
Some of these things
you're gonna read
as you go through
the quiz,
so I won't go on and on and on
about how networks are used
or how computers are used,
because this is something,
even though we're in a
"Intro to Networking Class,"
you should probably
already know.
We use them to
share printers,
and we use them
to share Internet,
and use them
to share files.
Everything we do is
on a computer network.
The Internet is
a huge network.
WAN-- a huge, wide-area
network that we access.
Popular client-server
applications that are used
on networks and
the Internet,
things that you've probably
heard-- web services,
email services, FTP
for transferring files,
Telnet to connect
to remote areas,
remote desktop,
remote applications.
These are all types of
services that we connect with
in a client-server
environment.
So client-server, on page 3,
shows you a little picture--
not sure if it's in here--
yeah, right here--
where here's the client,
you wanna do something,
so you ask the server if
you could do something.
It sends back to the client
and says, "Sure, here you go.
"You can do that."
Same thing
when you print.
I hit the "Print" button,
I ask the print server
if I can print, the print
server says "yes" or "no,"
and then sends a
message back to me.
So that's a client-server
environment.
That's what we're
learning in this class.
When we talk about
Local Area Networks,
that's what
we're learning.
We're not talking about
setting up networks at home.
That kind of, not confuses
people in the beginning,
but people wanna know how
to configure Microsoft
so that they can
share services at home
and set up
a network.
And that's not what we're
doing in this course.
That's the
Windows class.
We're learning
big environments--
medium to large size
network environments
where we have a server
and we have clients
and we have this
huge network set-up
that we're used to
in any business.
Some of the
other services--
file services,
I'm sharing files,
print services, email or
communication services--
you can read
about these.
Voice and video, phone
networks are now set up
to the computer
network.
Some terms here--
topology.
Topology.
I wonder if
I missed that.
Oh no, it's
coming up.
Topology-- we have
two types of topology
you should look at.
Now, topology--
think of the landscape.
The topology of
northern Michigan
is very woodsy
and hilly.
You look at the
design of it.
Topology of Indiana
is very flat.
A topology of a network
could be very different.
In most types of
computer networks,
the type of physical
topology that we work with
is some sort of
star topology,
where the server's
at the center,
and then your clients
all connect to a server
via a router.
But we'll get into
that in depth
with the future chapters
when we talk about topology.
But that's a
physical topology.
A logical topology is
how data's transferred,
so that's like
Ethernet.
Operating systems-- this is
like-- not an operating system.
There's a very big difference
between a NOS and a OS.
An NOS is like a
Windows server,
or Linux OS, a Linux network
operating system, I should say.
Windows 10, which is
what I'm using now--
that's an operating system.
It operates
one computer.
A Network Operating System
is where you have users
and groups, and it's
a client-server model.
That is what you learn in
this course and future courses
when you learn about
network administration.
You're learning
how to administer
a client-server
environment.
Peer-to-peer, that's
what I was talking about,
what we're not going
to learn in this class.
We're not gonna
learn Windows
and how to set up
local, shared resources.
That's a peer-to-peer
network,
where you're just connecting
with one other or two others,
but not in a centralized
server-type way.
This is a big mess,
but you can see
there's no server that's
connecting everything.
They're all directly
connected to one another.
Not a good way to set up
multiple computers
in a business--
it's just not feasible.
For one, we don't have
Ethernet connections
to connect to
another computer,
and then to this computer,
and another printer,
and a scanner.
We don't have all of
those ports to connect.
The client-server model
is much more--
it's just what's used
in the industry.
Client-server model.
Active directory-- this
is a term that's used
to be a centralized directory
for users-- our users,
and licenses and applications
that are on a network.
I'm only on slide 16--
I better speed it up.
Client-server network model--
okay, we talked about that.
There's our server,
we're all connected.
You see the
star topology?
It's like a star--
ding, ding, ding, ding, ding.
NOSes-- they are responsible for
letting the client do things.
Popular examples-- Windows
Server 2012 Release 2,
that's what we teach
in CIS 234 and 235.
Ubuntu Server, Red Hat
Linux, those are taught
in our Server Administration
classes, as well.
Back in the day, we used
to have Novell servers.
But those are not
as popular anymore.
(humming)
Physical hardware is
touched on in this chapter,
and LANs and
their hardware.
So page 13, it shows
you a couple switches.
That's probably
up here.
We'll cover
these in depth.
So, type of typical
network hardware,
you have Ethernet ports,
you have switches,
you have routers, you
have network printers
that you
connect to.
Network interface card, or
NICs, as they're often called.
These are the ports--
you probably have one
on your laptop.
Some laptops don't.
You connect them
with a USB now.
But you probably have
one on your desktop,
where you can plug in a RJ45
to connect to the network.
But again, we'll cover
that more in depth later.
For now, the term "backbone"
is the part of the network
that supports a large
number of computers.
So it's usually
run on fiber.
It is the backbone
of the network.
This part here.
So here's one subnet,
here's another subnet,
here's another subnet.
And then, this line here
supports all of these computers.
So that would be
called the "backbone."
Now, the purpose--
this image right here
is also an example
of daisy chaining,
which is not a good way
to set up your design,
because if this
thing goes down,
this subnet can't
talk to this subnet.
But that is the backbone
of the network.
Routers route
traffic.
For now, that's what
you need to know.
They route packets.
Switches and routers
are very similar,
but a router can also be a
gateway between networks,
so a gateway between
your internal network
and the Internet,
or between two different
types of networks
within your
Local Area Network.
This is a
better design.
This would be the backbone,
this would be a backbone,
and this would
be a backbone.
But here's
subnet A, B, and C,
and they all connect
to one router.
So one switch isn't
dependent on, you know,
this switch or
that switch.
Hopefully, you can see
my mouse moving around.
A couple other terms--
MANs and WANs and PANs,
you can read
about those.
Really trying to--
how many--
I'm really trying--
oh, I'm out of time.
I'm gonna keep going,
'cause we're gonna get--
we're not covering
58 slides,
but we're getting the
gist of this chapter.
And then, like I said,
anything we need to cover
more in depth, I will make
another video that's shorter.
OSI model-- OSI-- you need
to know the OSI model.
We'll cover this
all semester.
There used to be chapters
and chapters and chapters
on the OSI model, and that's
why I like this book better,
because there's not
chapters and chapters
and chapters of it.
But read
about it.
It starts on page--
uh, seven-layer--
not a seven-layer
taco or burrito--
page 18, the seven-layer
OSI model,
created by ISO.
You need to know
all the layers--
physical, data, network,
and transport.
As network people,
those are the four
that we're concerned
about the most--
physical, data link,
network, and transport.
Then, session, presentation,
and application--
those we don't interact
with as much.
But they're also
part of the OSI.
And what the OSI model is
is a very basic--
it's a system for packaging
up our packets of data.
So I'm a user-- I don't
know what's coming up here.
You know, I'm not gonna
go through all of these,
'cause you wanna
read these
and we'll cover them
more in depth later.
But if you're a sender
on a computer,
I'm on my computer and I
wanna send to my printer,
I am here and
I hit "Send."
So I make the seven-layer,
and my packet goes down
seven, six,
five, four--
it goes through all of
these layers of the OSI
and it builds
my packet.
So here, in the transport layer,
it says, "Send it via TCP."
Then, it says, "Okay,
here's my IP address,"
and then it adds
on the MAC address
and then converts
it to binary.
So it packages your
data as it goes down.
Then, it goes
through the network,
so duh-duh-duh-duh-duh,
going through the network.
It hits my receiver and then
it goes up and unencapsulates.
So it goes down,
encapsulates,
goes to the receiver, and
unencapsulates the data.
The OSI model
is just rules.
Networks and network devices
follow these rules
so that we can have
one company make a NIC
and another company make a
NIC, but they all send data.
That's a brief introduction
to the OSI model.
Read about it.
There's all these slides...
give you a brief definition
of what each
layer does.
We'll talk about it more
and more in the textbook
because it is an important
part of networking.
These are questions that
will come up in interviews
and certainly on the
certification exam,
what packets are,
or PDUs, all of that,
how it all works
together.
Here's what I was talking
about, with wanting to print.
You start here, you go
through the network,
some things are added,
you go through,
and then you hit
the destination,
and then it
unpackages it.
So, data, adds,
adds, adds, adds,
travels, travels,
da-da-da-da,
and then takes off,
takes off, takes off,
and then there's
my data again.
So that's explained in the book,
and then some definitions.
Staying safe on
the computer.
Hmmm....
There is a fire extinguisher
somewhere in here.
This is just--
read about this.
The reason it's
in the book
is because it's on the
certification test.
So, you know,
know what type of wire,
what plenum rate it is,
for example,
when we talk about wire and
material safety data sheets
for cleaning solutions and how
is your HVAC system set up?
Protecting against
static electricity.
Running cables over fluorescent
lights is a bad idea
'cause it causes
interference.
So these are things
that are all important
that you need to know
on a high level
for network
administration.
Kind of common sense,
but you need to--
okay, keep your
back straight,
bend your knees,
and grip your load.
Okay.
Don't bend with your back,
people-- bend with your knees.
Is that what
they tell you?
I have back and knee problems,
so I don't know. (chuckling)
I try not to lift
heavy things, period.
But it happens.
Installation,
safety.
I've cut myself so many times
on the inside of a computer.
Oh, motherboard.
Memory is kinda sharp,
too, by the way.
Okay, get it?
Get that pun?
"Memory is sharp"?
Ha, ha, ha.
Troubleshooting
network problems--
there's a quick flowchart
and a quick--
(child squealing,
distantly)
sorry, if you can hear my son
screaming in the background.
Hey, people with children,
school starts tomorrow.
Yay!
Troubleshooting network
problems-- there is a--
it must not be in
these PowerPoints,
but on page 33, there
is a quick flowchart.
Determining your problem,
a lot of it is experience,
common sense,
but there's things
that you wanna check
first, certainly,
especially if you're
on help desk
and you're in your answering
phone calls from people
who literally don't know
how to shut down a computer.
I'm sorry, that
is your future.
You'll have to tell them how
to find Start and Shut Down
and help them
out that way.
So that is a little introduction
to what networking is about.
Then, as we go on
with this semester,
all of these things we'll
cover much more in depth.
But that's just an
intro to Chapter 1.
So I'm sorry I went
over a little bit,
and I hope you stayed
through the end.
Some discussion topics--
things that you might
wanna think about before
you start the exercises,
or the labs
that I'll post--
differences and
similarities
between peer-to-peer
networks,
differences between physical
and logical topology.
I'm afraid to Google that
here while I'm recording.
But Google that-- physical
versus logical topology.
So that's super, super
important, too,
knowing how networks
are designed.
And that's it
for now.
When I post this video,
I'll leave a couple
of resources for you
to check out.
Expect to be doing a
couple of the exercises
or the labs, the activities
from the back of the chapter.
It's an intro chapter--
it's kinda fluff,
but it also is a good intro
to what we're learning.
So thanks for listening,
and have a great day.
