Windows Server 2019 NAT

Question

I want to use Windows Server 2019 as a NAT device. The application works with Linux, but the software I want to run seems to need Windows to work in my setting. I've done everything to set up Routing and Remote Access up to receiving inbound packets but them being rejected from a device on the network. Trouble shooting steps so far: 1. Inbound packet filtering - removed all, then added filter to allow only desired traffic. 2. Firewall - on or off, doesn't seem to matter. 3. Registry Editor - Set enable IP router = 1. Any thoughts on what to try next? Thanks, image of state included. ![73339-whatisdeal.png][1] [1]: /api/attachments/73339-whatisdeal.png?platform=QnA

Answer 1

Hi ,

If you want to deploy NAT on windows server, the server must have two NICs, one configured for the internal network (LAN) and another one configured to access the internet.

If NAT router is working properly, then you will see that packets have been translated as below:

For how to setup Windows Server as a NAT, you can refer to the following article:

Setup Windows Server 2016 as a NAT Router

Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.

Best Regards,

Candy

--------------------------------------------------------------

If the Answer is helpful, please click "Accept Answer" and upvote it.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

I am adding this link as the "why" you need 2 NICs in Windows and not in Linux. Short answer, Windows uses the Strong Host Model, and Linux uses the Weak Host Model. For more details:

https://www.cainetworks.com/support/training/strong-weak-host-oop.html#:~:text=With%20strong%20host%20receive%20model,the%20computer%20will%20receive%20it.

https://help.fortinet.com/fadc/4-1-1/html-e/Content/ServerCx/Weak_and_Strong_Host_Mod.htm