In this lab.
You need to configure static nat to make the network work.
In this topology, we have multiple internal servers that need to be accessed from the outside.
In other words, this PC outside PC one needs to be able to access the HTTP server and FTP server in
the internal network.
This router is our internet facing router.
This interface gigabyte 001 is connected to the internet and this interface is connected to a switch
on the inside of our network.
Here are the router details that you need to configure and then you need to configure a static net so
that the PC on the outside can access the internal HTTP and FTP servers.
To see the internal IP addresses of the servers, click on the server in packet tracer and go to config
interface and you'll be able to see the IP addresses of the internal servers.
So one has an IP address of ten one one 100.
The other 110 one one 101.
However, those are not internet readable addresses.
They are RF C 1918 addresses.
In other words, private IP addresses.
So to allow this PC on the outside to access the servers, you are going to have to configure static
net on the router and use public IP addresses.
The HTTP server has been allocated.
IP address 8.8.8. 200 and the FTP server.
8.82.8.21.
For the HTTP or web server, you're going to configure it to only net the required port number.
So when a user here opens up a web browser and connects to my HTTP dot com, the DNS server will resolve
the IP address to 8.8.8 200, and the router needs to do a static net translation to translate that
to the internal server IP address.
The same is true for FTP, but in this example you're going to do a full net translation using the domain
name my ftp.
Com.
So when the PC opens up an FTP client and connects to my ftp com the DNS server.
Will resolve my FTP.
Welcome to a 2.8.8.201.
The router needs to be configured with that IP address to nat, the IP address to the internal server.
Now, as always, don't just configure.
Verify.
And make sure that things are working the way that you think they working.
Routers and other network devices do what you tell them to do, not what you think they should do.
So verify that you've configured the devices in the way that you think you have.
So verify that both the inside PC, this PC here and outside PC this one here can access the internal
servers because we don't have an internal DNS server in our network.
You need to configure the inside host to use internal IP addresses to connect to the servers.
So in other words, open up a web browser and connect to the IP address of the HTTP server using its
internal or inside IP address on the outside.
Verify that the outside host can connect to these servers using DNS names.
So there you go.
Can you complete this lab?
Can you configure the lab and verify that it's working as it should?
Download the attached packet, trace a file and see if you can complete the lab yourself.
In the next video I'm going to show you how to do this.
But as always, try it yourself first.
These kind of labs are great for verifying that, you know, the CCNA topics and that you are ready
for the CCNA exam.