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


319 New Members signed up 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. Twice NAT means you configure a source and destination in a single rule so yes, that's pretty much what we do here. We specify the source (host) and the destination (webserver).

  3. 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 it has to be 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

  4. Hello Dionisis

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

    Thanks again!


  5. Hello Laz

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


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