00:04
the last topic of discussion with Napped is your static necked.
00:09
Now let's suppose you have
00:12
a service, a server located on the inside of your network. And in this case, we're gonna pretend PC three is that server that people on the outside or on the Internet need to access for certain needs.
00:28
I have drawn out on the board anthropology I've left out PC 12 and four P C three is connected to switch eight and switch. It is connected
00:37
network 10 to F zero slash 1.10 to Ratter to and Router two is over Outer and Ratter for is your I S P rounder. If I were doing dynamic that
00:50
and let's say, a router for or some user sitting back here on the Internet
00:54
wants to get to the service PC three is providing.
00:58
Let's say it contains a database that people need to access.
01:00
How do people get to PC three
01:06
Let's say people are trying to tell it to P C three
01:10
to remotely log in to PC three to access a certain database. If I were doing Dynamic, Nat
01:17
and I were using the Inside Network as 10 10.
01:22
10 0 slash 24 my Outsider Public
01:27
Network was 1 90 10 10 0 slash 24.
01:34
Well, if my public network is a slash 24 network, I have 240.1
01:41
through 0.254 addresses, which is a total of 254 addresses.
01:49
So I can't very well tell people on the outside
01:53
domain or the public domain, too. Hey, if you want to tell that to PC three, I don't really know the address. 10 10 10.3 got translated to buy router to what 1 90 address
02:09
did. 10 10 10 3 Get translated to buy router tube.
02:14
So how about you try 0.1 through dot to 54 1 of them should work?
02:19
That's just not feasible.
02:21
I need to tie the I P address 10 10 10 3 to 1 address so people on the outside domain can tell that
02:34
For that, we use static net
02:38
and let's see how static not works
