Switching from Server Side NAT to Client Side NAT

[Hamza]

Hi All,

I discovered recently that the case "Translate destination on client side" was unchecked :

And its giving me a lot of pain as some incoming NAT are not working 

I want to change this option to NAT on client side by checking this option (which is the default option if i'm not mistaking)

But i don't know if the manuel NAT in place will be impacted or not by this operation ?

Is there something that i have to verify before  activating Client Side NAT  ? routing ? Proxy Arp ? 

Thank You 

[the_rock]

It will not cause any problems, I did this many times before. As a matter of fact, there were times this was done in the middle of the day and it did not even cause any connections to drop at all.

[Hamza]

I did not had any issues when i checked the option 

Now the NAT is hapenning before the routing which is logic and easy to troubleshoot, my issue is now solved 🙂

[PhoneBoy · Accepted solution]

Basically, what this option does is ensures NAT happens before the routing decision takes place.
Without this option, you’d have to have a static route in some cases for NAT to work correctly…if it didn’t work.
It should not break anything to enable this feature.