We use static NAT for servers in a LAN. But using dynamic NAT doesn't have any effect, then why is it a standard? Is it because of the overhead faced by the server, to map each connection/request to it's local ip and vice-versa. Please help.

  • 1
    Why do you want to use dynamic NAT? I don't see what your issue is. More information would also help.
    – HAL
    Jun 12 '14 at 15:10
  • It's just a doubt. Is it feasible to use dynamic NAT for a server in a LAN? (It was my first post, sorry for any mistakes.)
    – Josh
    Jun 12 '14 at 15:17
  • Could you clarify your question? Specifically, what do you mean by the statement "using dynamic NAT doesn't have any effect" and to which standard are you referring?
    – YLearn
    Jun 12 '14 at 17:32

I think you're confused about the usual uses of static- and dynamic NAT.

Static is used on the outside router/firewall to expose a server/service located inward which wouldn't normally be reachable from the outside. (static: nailed in place, permanently mapped inward.)

Dynamic is used to enable inward transportation of return traffic for outgoing connections; so a web browser on a system with a private IP is dynamically mapped to a public address as the packets egress, and then the return traffic is mapped back for ingress. (dynamic: the inside end points change so the mappings are changing too.)

  • For those companies with few public addresses, generally private IP's are dynamic NAT or PAT. PAT (Port Address Translation) assigns each public PC a port then translates their traffic back to the private IP during ingress traffic.
    – HAL
    Jun 12 '14 at 15:39

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.