In this lab.
You need to configure static nat to make the network work.
So on the outside PC I'll open up a web browser and connect to my HTTP dot com.
As you can see, we can access a Cisco Packet Tracer website that says Hello World.
So I was successfully able to connect to the server using HTTP.
Now we could also try and connect to it directly.
And notice that also works.
So just to do that again.
I'll connect to the server via its IP address and I'm able to connect to the server.
Via the IP address on the router show IP net translation.
Notice we have multiple net translations going to this IP address and port 80 and those translations
are being netted to ten one one 100.
So clear IP net translation store will allow us to remove the net translations show IP net translation.
We only see the static net translations.
So let's connect again to my http dot com is enter.
We can see the website show IP net translations.
Here are the net translations.
So as you can see here, there are the dynamic nature translations that are created.
When the client browses to the server.
Here's the static net translation.
Now again, I added a.
You won't see that in your lab if you haven't added SSL.
That just allows me to do this.
HTTPS my http dot com.
That also works.
And when I go back to the net translations notice I see dynamic net translations for the client, a
connection to the SQL Server.
So there's HTTPS or SSL, there is HTTP.
Now what about the FTP server?
I'll open up a command prompt ftp my ftp com.
That's the domain name that we need to use.
Before I do that.
Notice again that there are no FTP translations here.
We don't see Port 21, we see Port 80 and four for three.
I can connect it to the server.
Username of Cisco password is Cisco.
You can see that information by clicking on the server, going to services.
FTP and here is the username and password.
Now there are a bunch of files on the FTP server.
So on the client, if we type draw, we can see those files listed on the FTP client.
And if we have a look at our net translations, so show IP net translations.
Notice we see Port 21 as well as Port 1028.
FTP works differently to HTTP and other protocols.
FTP Control uses port at 21.
So the client is initiating a session to the server on port 21.
But if passive mode is not used.
The server will initiate the connection to the client in this case because passive mode is used.
The client initiates a session to the server on ports that have been negotiated between the server and
the client.
Typically, the server would initiate a session back to the client from Port 20.
So here the port numbers are perhaps a little bit different to what you used to for the exam.
FTP Control Port 21.
FTP Data Port 20.
So show IP net translations.
Once again, we can see net translations for https, http and FTP.
Now the last step is to test connectivity from the inside host.
In this example, we haven't got an internal DNS server, so we're going to connect to the servers directly
using their internal IP addresses so I can connect to the web server directly.
And hopefully I can connect to the FTP server.
And the answer is yes, I can.
And I can log in to the FTP server.
Now the reason why we're using IP addresses is this device is configured to use the external DNS server.
That external DNS server is translating.
My FPTP rt.com.
And my HTTP dotcom to external IP addresses or global inside IP addresses that's going to cause problems
for this client.
So typically what you'd want to do is have a internal DNS server here.
And as an extra now, I'm just going to demonstrate that.
So what you would do is you would have a internal DNS server and you would configure the client to use
the internal DNS server rather than the external DNS server.
So this DNS server would have a default gateway of the router.
It would be its own DNS server.
Or you could point it to Google as the DNS server.
IP address.
All configure is ten 11105 slash 24 subnet and under services.
We'll now configure an a record of my http.
And pointed to the internal IP address of the server, my FTP.
Pointed to the internal IP address.
So we could verify things.
IP config.
Shows us the IP address of the server.
Server can ping the default gateway.
The last step is to enable DNS.
So I need to turn the service on now onto the DNS server.
We can use anice lookup to verify that things are working and let's look up at my http rt.com may not
work here because I made a mistake with the DNS server name needs to be its local IP address.
So let's do that again.
As you can see, it is now resolved.
So ping my http dot com that works in this lookup.
My ftp com.
That works.
Ping my ftp dotcom.
That also works.
So now on the client, this is the internal client.
Rather than using Google will use the internal DNS server.
So on the client, we've changed the DNS server.
Let's verify things.
So can it ping the DNS server?
Yes, it can.
And if look up my http dot com, that works.
And if look up my ftp dot com, that also looks good.
So ftp my ftp dot com.
Let's see if that works.
Now, this may be a problem in packet tracer.
The where it's still using the old DNS server.
I'll check the web browser.
So my htp dot com.
That's timing out.
Let's check whether we can ping the service.
A ping ten one one 100.
Seem to be having an IP connectivity problem here.
So from the DNS server, copying the HTTP server.
Yes, I can and I can ping the FTP server.
So what I'm going to do now is save my configuration and I'll restart packet tracer.
Okay.
So I've restarted packet tracer.
I'll open up the client.
Let's verify connectivity.
Can it ping the router?
Yes, it can.
Can it ping the DNS server?
Yes, it can HTTP server now.
It can.
A FTP server now it works.
So ftp my ftp dot com notice I can now access the ftp server so the internal client is able to access
the FTP server.
Using a different IP address to the external client.
So ftp my FTP dot com external client is able to access the FTP server as well.
But notice please inf lookup my FTP dot com.
This is the IP address returned by the DNS server to the external client.
The internal client, however, is receiving a different IP address, so that's typically what companies
will do.
Internal PCs will use a different DNS server that resolves DNS names to internal IP addresses, whereas
an external DNS server will resolve the domain names to external IP addresses.
So nice lookup my http com.
Notice the IP address.
Now external pc needs lookup my http dot com.
Notice a different IP address is used.
So there you go.
The network is functioning as expected.
How did you do?
Were you able to complete the lab?
Did you get it working?
I'm hoping that you're enjoying these extra pieces of information and the additional content that I've
added in the videos.
Hopefully it teaches you something and you learn how networks actually work.
Thank you for watching.
If you enjoyed this video, please like it and please subscribe to my YouTube channel.
I want to wish you all the very best.