How to configure and enable NAT with server core installation
Solution 1
It isn't all that pretty, but take a look at this: https://windowsmasher.wordpress.com/2013/03/02/scripting-the-build-of-a-server-2008-r2-test-domain/ After this either call "Start-Service RemoteAccess" or "net start remote access". This script assumes the public interface is named "Public Interface" and the private interface is named "Private Network".
Solution 2
The PowerShell Network Address Translation (NAT) Cmdlets are only available in Server 2012 R2, even using PowerShell 4 or copying the NetNat module does not help. So you're stuck with the netsh commands.
Related videos on Youtube
Kevin Mangold
I am a Computer Scientist at a US Federal research center working primarily with human factors and usability research. Formerly, I worked closely with biometrics and identity management technologies. Languages: Python, Java, C#, C/C++, VB.Net, HTML / CSS / JavaScript IDE: Eclipse, Visual Studio, PyCharm, VS Code Operating Systems: Windows 7/8/8.1/10, Windows Server 2008/2012/2012 R2, CentOS 5/6/7/8, Mac OS X
Updated on September 18, 2022Comments
-
Kevin Mangold over 1 year
Using Microsoft Server 2012 Core:
What is the equivalent core/Powershell command to enable and configure NAT. I have configured NAT on servers with the following GUI steps:
Server Manager, Tools, Routing and Remote Access, Right click on machine, "Configure and Enable Routing and Remote Access"
Select "Network address translation (NAT)" radio box,
Pick public interface.
I found "Install-RemoteAccess" but I'm stuck on the prompting for ConnectToAddress. It needs to be public or something but the GUI does not seem to have this requirement.
Thanks, Kevin
-
Ryan Ries over 10 yearsGod speed. That sounds difficult. I'd be using the MMC snapin on another machine to remotely administer the RRAS server.
-
Kevin Mangold over 10 yearsYeah, that's what I have been doing. The goal is to fully automate installation/configuration of certain services.
-