NAT for the Lab to expand subnets
-
On both esxi1 and esxi2, change the network Label from NAT to 192.168.255-Port Group on the NAT Properties
-
DC1, install second NIC and assigned to 192.168.255-Port Group
-
Rename the NIC to 192.168.255 NIC and assigned IP to 192.168.255.1
-
Add Network Policy and Access Services Role
-
Select Routing and add required role services
-
Install
Setup DHCP Server
-
On DC1, install DHCP Server role
-
Select 192.168.255.1 network
-
Valid
-
No WINS
-
Add Scope as below and set Default Gateway to 192.168.255.1
-
Next
-
Disable DHCPv6
-
Use Current Cred
-
Confirm and install
NAT setup on DC1
-
Since we setup NAT and Tested on subca (Win Server 2003 R2), please disable it.
- Back to DC1, open Routing and Remote Access Console
-
Configure and Enable Routing and Remote Access
-
Select NAT
-
Select 172.20.255 NIC for Public interface to connect to the internet
-
Finish
-
On DC1 Properties>IPv4 Tab>check the DHCP is on and Allow RAS to select adapter for broadcast name resolution
Test with a Client if it connects to the internet (an external network)
- I have already built out a client1 VM with Win81e template and joined to domain with a static IP, 172.20.254 port group for testing.
-
Edit Settings Client1 VM properties> Change Network Adapter to 192.168.255-Port Group
-
Log on to client1, change to obtain IP address automatically with DHCP server
-
And open CMD and run ipconfig command to confirm to get IP from DHCP Server (192.168.255 subnet)
-
Ping to www.google.com
-
Open IE to browse msn.com