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 644 Lessons. More Lessons Added Every Week!
  • Content created by Rene Molenaar (CCIE #41726)

482 Sign Ups in the last 30 days

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


Forum Replies

  1. Hi Rene,

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


  2. Hello Dionisis

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

    Thanks again!


  3. Hello Laz

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


  4. 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 “” not “”. Please see below:

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

  5. Rene, you are doing a great job. A very difficult topic explained in simple way.

    Just to add, one reason why we need hairpining is that there are some applications in the DC which need to create control channels on the public IP in order to communicate hence they need inside to inside NAT.

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