You are configuring the network for a small branch office. Currently, the branch office does not connect directly to the Internet.
In the branch office, you deploy a new server named Server1 that has a server Core installation of Windows Server 2016. Server1 has two network adapters configured as shown in the following table.
You plan to use Server1 to provide Internet connectivity for the branch office.
Routing and Remote Access (RRAS) in installed and configured for VPN remote access on Server1.
You need to configure RRAS on Server1 to provide network address translation (NAT).
Which command or cmdlet should you use first?
A. netsh.exe routing ip nat install
B. New-NetNat NAT1 -ExternalIPInterfaceAddressPrefix 131.107.10.1/29
C. route.exe add 192.168.1.1 255.255.255.0 131.107.10.1 metric 1
D. Enable-NetNatTranstionConfiguration
A is wrong .
the answer should be B. New-NetNat NAT1 -ExternalIPInterfaceAddressPrefix 131.107.10.1/29.
Explanation/Reference:
https://technet.microsoft.com/en-us/itpro/powershell/windows/netnat/new-netnat
The New-NetNat cmdlet creates a Network Address Translation (NAT) object that translates an internal network address to an external network address.
NAT modifies IP address and port information in packet headers.
Seems Coleman is right.
Answer should be B.
Not getting any documents on ” netsh.exe routing ip nat install ” …
But B seems legit according to his provided link.
A is right. The answer is “netsh.exe routing ip nat install”
Once the Routing and Remote Access role and its PowerShell cmdlets are added (Step 1: Configuring the internal NIC
Step2: Install the Routing and Remote Access role), you can now configure it. In this scenario you set up a simple NAT gateway
https://deploymentresearch.com/install-a-virtual-router-based-on-windows-server-2012-r2-using-powershell/