Hot Downloads

Welcome, Guest
Username: Password: Remember me

TOPIC: Static Nat Requirement

Static Nat Requirement 5 years 2 months ago #37186

  • Nevins
  • Nevins's Avatar
  • Offline
  • Expert Member
  • Posts: 438
  • Thank you received: 9
  • Karma: 4



I'm using the same topology I used to ping from private host to public server (4.4.4.2) in this case. Now I want to be able to ping from private host to private host. Knowing that 192.168.x is private and does not get passed over wan links there is a requirement for some sort of translation to take place. I know static nat will do the job but I'm wondering if it is the ONLY method to get PC0 to ping PC1.


Essentially I'm wondering if I have correctly identified a need for static nat addressing in this case.
Useful Threads
================================
www.firewall.cx/forum/2-basic-concepts/3...e-resource-page.html
The administrator has disabled public write access.

Re: Static Nat Requirement 5 years 2 months ago #37192

  • TheBishop
  • TheBishop's Avatar
  • Offline
  • Moderator
  • Posts: 1719
  • Thank you received: 8
  • Karma: 5
Another way would be to set up a site-to-site VPN
The administrator has disabled public write access.
Time to create page: 0.073 seconds

CCENT/CCNA

Cisco Routers

  • SSL WebVPN
  • Securing Routers
  • Policy Based Routing
  • Router on-a-Stick

VPN Security

  • Understand DMVPN
  • GRE/IPSec Configuration
  • Site-to-Site IPSec VPN
  • IPSec Modes

Cisco Help

  • VPN Client Windows 8
  • VPN Client Windows 7
  • CCP Display Problem
  • Cisco Support App.

Windows 2012

  • New Features
  • Licensing
  • Hyper-V / VDI
  • Install Hyper-V

Linux

  • File Permissions
  • Webmin
  • Groups - Users
  • Samba Setup