5.2 Flashcards
You are adding a new Internet connection to connect your private network to the Internet. A server running
Windows Server 2012 R2 with Routing and Remote Access and NAT connects the private network to the
Internet.
The ISP currently hosts your Web server, but you want to move that server into your private network. You
want all Web traffic sent to 135.74.16.86 to be redirected to the server on your private network with address
10.1.1.3.
What should you do?
In Routing and Remote Access, edit the properties of the NAT/Basic Firewall object. Redirect HTTP to 10.1.1.3.
In Routing and Remote Access, edit the properties of the public network interface running the NAT protocol. Create a reservation for 135.74.16.86 that redirects all incoming requests to 10.1.1.3.
In Routing and Remote Access, edit the properties of the NAT/Basic Firewall object. Create a reservation for 135.74.16.86 that redirects all incoming requests to 10.1.1.3.
In Routing and Remote Access, edit the properties of the public network interface running the NAT protocol. Redirect HTTP to 10.1.1.3.
In Routing and Remote Access, create an input filter on the private interface to redirect all HTTP traffic to 10.1.1.3.
In Routing and Remote Access, edit the properties of the public network interface running the NAT protocol. Redirect HTTP to 10.1.1.3.
You want to let clients on your private network connect to the Internet through Serverl. Serverl connects to
the Internet using a dial-up connection.
On Serverl, you enable the Routing and Remote Access Service and install the NAT routing protocol. All
computers in your network use Automatic Private IP addressing. There is no DHCP server on the network.
You want to use the private IP address range 172.16.65.1 to 172.16.65.250.
How would you configure Serverl? (Select two. Each choice is a required part of the solution.)
Assign an IP address of 172.16.65.1 to the LAN interface of Serverl.
Configure the NAT routing protocol to automatically assign addresses in the range of 172.16.65.2 through 172.16.65.250 to computers on the private interface.
Configure the NAT protocol to disable APIPA.
Configure Serverl to use APIPA.
Assign an IP address of 172.16.65.1 to the dial-up interface of Serverl.
Assign an IP address of 172.16.65.1 to the LAN interface of Serverl.
Configure the NAT routing protocol to automatically assign addresses in the range of 172.16.65.2 through 172.16.65.250 to computers on the private interface.
The Portland site in your company network has the only connection to the Internet. To allow all Windows 8
computers on the network to access the Internet through the Portland connection, you install and configure
the NAT routing protocol on a server in Portland.
You decide to use IP addresses in the range of 192.168.40.1 through 192.168.40.50 for the network. The
Portland server is configured to use an IP address of 192.168.40.1.
Webl is a Web server configured with an IP address of 192.168.40.2 and a default gateway of 192.168.40.1.
Your Internet service provider has allocated two IP addresses, 207.46.179.16 and 207.46.179.17, to your
network. You want to allow Internet users from outside your internal network to use an IP address of
207.46.179.17 to access the resources on the Webl server through the NAT service on Portland.
What should you do?
Configure Portland with a static route on the private interface of the NAT routing protocol. Use a destination address of 207.46.179.17, a network mask of 255.255.255.255, and a gateway of
192.168.40.2.
Configure Seattle with a static route on the WAN interface. Use a destination address of 192.168.40.1, a network mask of 255.255.255.255, and a gateway of 207.46.179.17.
Configure the network interface of the Web1 server to use multiple IP addresses. Assign the additional IP address of 207.46.179.17 to the interface.
Configure the public interface of the NAT routing protocol to use an address pool with a starting address of 207.46.179.16 and a mask of 255.255.255.254. Reserve a public IP address of 207.46.179.17 for the private IP address of 192.168.40.2.
Configure the public interface of the NAT routing protocol to use an address pool with a starting address of 207.46.179.16 and a mask of 255.255.255.254. Reserve a public IP address of 207.46.179.17 for the private IP address of 192.168.40.2.
You are implementing NAT on a Windows Server 2012 system using Routing and Remote Access. You
installed two network interfaces in the server:
The Ethernet connection is connected to external network that uses registered IP addresses.
The Ethernet1 connection is connected to the internal network where private IP addressing is used.
The Ethernet connection is assigned an IP address of 137.65.1.23/16, while the Ethernet1 connection is
assigned an IP address of 172.17.1.1/16. You enabled Routing and Remote Access on the server and
configured it for NAT. You defined the Ethernet connection as the private interface and the Ethernet1
connection as the public interface with NAT enabled.
When you test the configuration, it doesn’t work correctly. What should you do to fix it?
Assign an IP address from the 172.17.0.0/16 range to the Ethernet connection.
Add the IGMP Router and Proxy routing protocol to RRAS.
Use a valid private IP addressing scheme on the private network, such as 192.168.1.0/24.
Configure the Ethernet interface as the public interface and enable NAT on it.
Configure the Ethernet interface as the public interface and enable NAT on it.
You are implementing NAT on a Windows Server 2012 system using Routing and Remote Access. You
installed two network interfaces in the server:
The Ethernet connection is connected to the external network that uses registered IP addresses.
The Ethernet1 connection is connected to the internal network where private IP addressing is used.
The Ethernet connection is assigned an IP address of 137.65.1.23/16, while the Ethernetl connection is
assigned an IP address of 172.17.1.1/16. You enabled Routing and Remote Access on the server and
configured it for NAT. You defined the Ethernetl connection as the private interface and the Ethernet
connection as the public interface with NAT enabled.
Which of the following is true regarding this implementation?
The NAT router can forward DNS requests to the DNS servers on the public network.
A DNS server must be implemented on the private network to enable name resolution.
A DHCP server must be implemented on the private network to enable dynamic addressing of hosts.
Hosts on the private network should be configured with a default gateway address of 137.65.1.23.
The NAT router can forward DNS requests to the DNS servers on the public network.
You are implementing NAT on a Windows Server 2012 system using Routing and Remote Access. You
installed two network interfaces in the server:
The Ethernet connection is connected to the external network that uses registered IP addresses.
The Ethernet1 connection is connected to the internal network where private IP addressing is used.
The Ethernet connection is assigned an IP address of 137.65.1.23/16 while the Ethernetl connection is
assigned an IP address of 172.17.1.1/16. You enabled Routing and Remote Access on the server and are
using the Custom Configuration option in the Routing and Remote Access Server Setup Wizard to configure
NAT.
What options must be selected to enable NAT on the server.
VPN access
Dialup access
Demanddial connections
NAT
LAN routing
NAT
LAN routing
