We're Sorry, Full Content Access is for Members Only...

If you like to keep on reading, Become a Member Now! Here is Why:

  • Learn any CCNA, CCNP and CCIE R&S Topic. Explained As Simple As Possible.
  • Try for Just $1. The Best Dollar You've Ever Spent on Your Cisco Career!
  • Full Access to our 617 Lessons. More Lessons Added Every Week!
  • Content created by Rene Molenaar (CCIE #41726)

 

375 New Members signed up the last 30 days!

satisfaction-guaranteed

100% Satisfaction Guaranteed!
You may cancel your monthly membership at any time.
No Questions Asked!

Tags:


Forum Replies

  1. Hi Rene,

    Why need for access to web server using the public ip(192.168.2.200) whereas We can access the server locally (Directly).Which special scenario we will use like this ?
    Could you please explain further ?

    br//
    zaman

  2. mismatch configuration -

    just to be sure that i understand what i am reading i think there is a mismatch between the diagram and configuration . instead of the address 192.168.2.220 it has to be 192.168.2.200 in the diagram and i think in the configuration the object network WEB_SERVER it has to be WEB_LOCAL where there is the static nat for INBOUND TRAFFIC .
    Please if i am wrong let me know , Many thanks

  3. Hello Dionisis

    Good catch! You are correct. I will let @ReneMolenaar know of the error and he can fix it.

    Thanks again!

    Laz

  4. Hello Laz

    Its important for me the details of a topic to understand a concept . So thanks for your reply.

    Dionisis

  5. Hi Rene! Great Lesson. Just wanted to point out a typo that may need to be fixed. In the beginning of the lesson I think the webserver IP is supposed to indicate “192.168.1.2” not “192.168.2.2”. Please see below:

    “Above we have a webserver using IP address 192.168.2.2 on our internal LAN. The ASA is configured so that IP address 192.168.2.220 on the outside is translated to IP address 192.168.1.2. This allows users on the Internet to access our webserver.”

13 more replies! Ask a question or join the discussion by visiting our Community Forum