WEBVTT

00:00.000 --> 00:01.545
>> Networking concepts.

00:01.545 --> 00:03.449
Make sure everybody understands

00:03.449 --> 00:04.500
the terms are going to use in

00:04.500 --> 00:06.300
networking and just answer

00:06.300 --> 00:09.795
questions about what it takes
to make a network function.

00:09.795 --> 00:12.630
Let's take a look
at the objectives.

00:12.630 --> 00:14.820
We're going to talk
about the basics.

00:14.820 --> 00:16.110
Here's where we'll define

00:16.110 --> 00:18.535
those terms that we hear
and take for granted.

00:18.535 --> 00:21.770
For example, the OSI
reference model,

00:21.770 --> 00:23.450
a framework, a node,

00:23.450 --> 00:26.455
a host, a protocol, and a port.

00:26.455 --> 00:29.975
Even though these may seem
like very basic terms,

00:29.975 --> 00:31.685
as you're getting
into networking,

00:31.685 --> 00:32.780
you want to make sure you have

00:32.780 --> 00:35.065
a strong understanding of them.

00:35.065 --> 00:38.240
As I mentioned, the
OSI reference model

00:38.240 --> 00:40.985
isn't something people
just know automatically.

00:40.985 --> 00:43.805
It's a really important
foundational idea

00:43.805 --> 00:45.550
as it applies to networking.

00:45.550 --> 00:48.140
We'll talk about what it
is to have a framework

00:48.140 --> 00:50.755
and what the purpose
of that framework is.

00:50.755 --> 00:52.940
We'll be looking
at two frameworks,

00:52.940 --> 00:57.035
the OSI reference model
and the TCP/IP model.

00:57.035 --> 00:58.790
These will help us understand

00:58.790 --> 01:01.790
networking at a bit
of a deeper level.

01:01.790 --> 01:05.065
Then we'll move on to
protocols and ports.

01:05.065 --> 01:07.250
Protocols are
necessary in order to

01:07.250 --> 01:09.440
enable communication
between hosts.

01:09.440 --> 01:11.780
They're basically a set
of rules and regulations

01:11.780 --> 01:14.150
about how that communication
is going to happen.

01:14.150 --> 01:15.620
It's important to
look at some of

01:15.620 --> 01:17.305
the more common protocols.

01:17.305 --> 01:20.875
Some of those you may have
heard of and some may be new.

01:20.875 --> 01:23.390
We'll also take a look
in an upper level of

01:23.390 --> 01:27.080
network services, DHCP and DNS.

01:27.080 --> 01:29.480
We'll get into what some
of these ideas are on

01:29.480 --> 01:32.330
a much deeper level as we
move forward in the course,

01:32.330 --> 01:35.275
but to start, we just want
to lay out the groundwork.

01:35.275 --> 01:37.280
We'll also talk
about storage and

01:37.280 --> 01:39.650
our data and where it
lives, so to speak.

01:39.650 --> 01:41.435
We can have storage
on the network,

01:41.435 --> 01:42.950
we can have storage
in the Cloud,

01:42.950 --> 01:44.975
we can have storage on
a different network,

01:44.975 --> 01:47.425
and we'll look at some
of those options.

01:47.425 --> 01:49.460
Then we're going to
wrap up this section

01:49.460 --> 01:51.095
with remote access.

01:51.095 --> 01:53.630
Most of what we'll talk about
in the class is going to

01:53.630 --> 01:55.250
reference you're
physically connected

01:55.250 --> 01:56.905
to a local area network.

01:56.905 --> 01:58.985
But in the case
of remote access,

01:58.985 --> 02:00.200
you might be connecting from

02:00.200 --> 02:02.930
a VPN or some other
external source.

02:02.930 --> 02:05.360
How that works and the
materials, equipment,

02:05.360 --> 02:06.560
and tools we need to make that

02:06.560 --> 02:09.990
operate will all be
covered in this section.

02:11.990 --> 02:14.935
Jumping into network basics,

02:14.935 --> 02:17.525
the first question
we have to ask is,

02:17.525 --> 02:19.100
what is a network?

02:19.100 --> 02:21.155
We take some of these
things for granted,

02:21.155 --> 02:24.080
but I just want to be clear
when we talk about a network,

02:24.080 --> 02:26.660
we're looking at a group
of interconnected systems,

02:26.660 --> 02:28.340
and usually they're connected

02:28.340 --> 02:30.415
together for the
purpose of sharing.

02:30.415 --> 02:33.199
Sharing data or
sharing resources

02:33.199 --> 02:37.010
like maybe a printer or some
other tools on the network.

02:37.010 --> 02:40.160
It's all about bringing
these systems together and

02:40.160 --> 02:43.580
allowing them to access
some of the same resources.

02:43.580 --> 02:45.740
In order to do that, we have to

02:45.740 --> 02:47.465
have the systems themselves,

02:47.465 --> 02:48.950
a framework that provides

02:48.950 --> 02:50.255
the structure for
how we're going to

02:50.255 --> 02:52.040
communicate and the clients and

02:52.040 --> 02:54.685
the servers that both
need operating systems.

02:54.685 --> 02:57.440
We'll have to think about
protocols and how the data,

02:57.440 --> 02:59.900
like media, will
traverse the network.

02:59.900 --> 03:02.585
The easy answer for
media is cable.

03:02.585 --> 03:04.825
But we have to think
about the airwaves too,

03:04.825 --> 03:06.785
because of wireless
connectivity.

03:06.785 --> 03:09.460
Then we have our network
connectivity devices

03:09.460 --> 03:10.540
like our hubs,

03:10.540 --> 03:11.890
switches, and routers.

03:11.890 --> 03:13.720
Then we have network
services that

03:13.720 --> 03:16.430
put it all together
and make it work.

03:17.930 --> 03:20.610
Starting out, the first thing to

03:20.610 --> 03:23.500
define after defining
a network is a system.

03:23.500 --> 03:25.075
When we talk about a system,

03:25.075 --> 03:26.140
there are different elements

03:26.140 --> 03:28.075
working together
for a common goal,

03:28.075 --> 03:30.489
which is a very
broad definition.

03:30.489 --> 03:31.990
You can see I have a bit more of

03:31.990 --> 03:34.075
an in-depth definition
on the slide.

03:34.075 --> 03:37.734
Interconnected components
which transform, store,

03:37.734 --> 03:39.865
transport, or
control data and or

03:39.865 --> 03:42.575
information for a
particular purpose.

03:42.575 --> 03:44.450
I don't like to read
definitions for

03:44.450 --> 03:46.610
you as I know you can
read for yourselves,

03:46.610 --> 03:48.065
but if you think about that,

03:48.065 --> 03:50.795
systems is a very
inclusive term.

03:50.795 --> 03:53.450
We've even got different
types of systems.

03:53.450 --> 03:55.580
Honestly, I don't want
you to worry too much

03:55.580 --> 03:57.830
about someone saying
node versus host

03:57.830 --> 04:00.110
or host versus client because

04:00.110 --> 04:02.885
a lot of these terms are
used interchangeably.

04:02.885 --> 04:05.420
For instance, if
you look at node,

04:05.420 --> 04:08.435
it's defined as any addressable
device on the network.

04:08.435 --> 04:11.285
That's your laptops
or desktop computers,

04:11.285 --> 04:12.920
but it's also your routers,

04:12.920 --> 04:16.385
storage devices, or network
attached storage devices.

04:16.385 --> 04:18.935
A cluster or all
of these things.

04:18.935 --> 04:20.900
If you can address it or access

04:20.900 --> 04:22.940
it on the network, it's a node.

04:22.940 --> 04:25.250
A host is a type of node and

04:25.250 --> 04:27.800
that generally indicates
a computer system.

04:27.800 --> 04:31.120
Types of hosts are
servers or clients.

04:31.120 --> 04:33.155
Servers are computer systems,

04:33.155 --> 04:35.000
generally speaking, that provide

04:35.000 --> 04:37.715
a service like data or
access to a printer.

04:37.715 --> 04:40.670
Any sort of service on
the network like DNS and

04:40.670 --> 04:41.930
the clients are the ones that

04:41.930 --> 04:44.845
access the resources
of that server.

04:44.845 --> 04:47.300
You can see there's
not a huge difference

04:47.300 --> 04:48.560
between these terms,

04:48.560 --> 04:50.960
and people will
say node or host.

04:50.960 --> 04:52.760
But for the most
part, we're generally

04:52.760 --> 04:55.830
just referring to
network devices.

04:56.110 --> 04:58.880
The one you will hear
that we do usually make

04:58.880 --> 05:01.490
a discrepancy with is
clients and servers.

05:01.490 --> 05:03.515
Think of clients
for the most part,

05:03.515 --> 05:05.930
as end-user workstations
when you're sitting at

05:05.930 --> 05:07.760
your desk and think of server

05:07.760 --> 05:09.980
as where you log
on to the domain,

05:09.980 --> 05:13.800
access DNS, or your
database or file server.

05:15.370 --> 05:17.840
What makes a network a network

05:17.840 --> 05:19.705
is often the operating system.

05:19.705 --> 05:21.710
I can have 15 client computers

05:21.710 --> 05:24.515
connected and running Windows
10 and I have a network,

05:24.515 --> 05:26.390
but I have what we used to call

05:26.390 --> 05:28.520
back in the olden days
or as my son says,

05:28.520 --> 05:30.095
anything prior to 2010,

05:30.095 --> 05:32.060
a peer to peer network.

05:32.060 --> 05:34.820
We didn't have a formal
domain environment.

05:34.820 --> 05:37.355
We just had a group of
connected computers.

05:37.355 --> 05:40.520
We can do that with a
client-based operating system,

05:40.520 --> 05:43.165
and those will be what
you're most familiar with.

05:43.165 --> 05:46.040
When I say client-based
operating system,

05:46.040 --> 05:47.660
I'm talking about Windows 10,

05:47.660 --> 05:49.070
Red Hat for Linux,

05:49.070 --> 05:52.315
basically just the client
operating systems.

05:52.315 --> 05:55.580
When we move to a client server
environment where we need

05:55.580 --> 05:58.880
a domain or VM created and
we want centralized control,

05:58.880 --> 06:01.340
central login, and
central security to have

06:01.340 --> 06:04.370
a true network environment
that we see in the workplace,

06:04.370 --> 06:05.900
we need at least one.

06:05.900 --> 06:07.700
But likely, multiple servers

06:07.700 --> 06:09.575
running a network
operating system,

06:09.575 --> 06:11.240
and that network
operating system

06:11.240 --> 06:12.410
might be the latest version

06:12.410 --> 06:15.470
of Windows Server 2016 or 2020,

06:15.470 --> 06:17.980
Unix, or Oracle Solaris.

06:17.980 --> 06:20.360
Back in the day we had Novell,

06:20.360 --> 06:22.370
which is even in the
olden days for me,

06:22.370 --> 06:25.915
but those are all network-based
operating systems.

06:25.915 --> 06:29.330
Ultimately, with your network
based operating systems,

06:29.330 --> 06:31.190
they create this virtual

06:31.190 --> 06:32.780
logical grouping
of computers and

06:32.780 --> 06:34.550
clients that come on
to the network and

06:34.550 --> 06:36.740
access the
authentication server,

06:36.740 --> 06:38.975
which allows them
onto the network.

06:38.975 --> 06:42.650
Usually, that authentication
server passes out policy,

06:42.650 --> 06:44.750
manages access
requirements to join

06:44.750 --> 06:47.950
the network, and
validates credentials.

06:47.950 --> 06:49.850
The environments
we're going to be

06:49.850 --> 06:51.530
working in today and focusing on

06:51.530 --> 06:54.730
throughout the class are
domain based environments.

06:54.730 --> 06:56.955
You'll have client
operating systems

06:56.955 --> 06:58.400
and you'll have a server that's

06:58.400 --> 06:59.780
the domain controller that's

06:59.780 --> 07:02.820
running the network
operating system.