4. On the Properties dialog box of the network adapter, select Internet Protocol Version 4 (TCP/IPv4), and then click Properties. 5. Change the Default Gateway to 192.168.0.100. Leave the all of the other fields unchanged, and then click OK and Close to save your settings. The next step enables IP packet forwarding on MBRSVR1 so that packets arriving at the end of the tunnel are forwarded on to the private network and vice versa. To enable packet forwarding on MBRSVR1 1. On MBRSVR1, at Administrator: command prompt, run the following two commands: netsh interface ipv4 set interface area connection” forwarding = “local enabled netsh interface ipv4 set interface area connection 2” forwarding = “local enabled By default, the ICMP protocol that is used by ping is blocked by the firewall so the next step is to enable ICMP on CLIENT1 and MBRSVR1 so that we can verify connectivity. ICMP is already enabled on DC1 because of the Active Directory that are automatically enabled when the role service is installed. To enable ICMP traffic on MBRSVR1 and CLIENT1 1. On MBRSVR1, start Windows Firewall with Advanced Security. 2. Click Inbound Rules, right-click the rule File and Printer Sharing (Echo Request – ICMPv4-In), and then click Enable Rule. 3. Repeat steps 1 and 2 on CLIENT1 to enable the same rule on that computer. On CLIENT1, there are two versions of the rule one for the Domain profile, and one for the – Public and Private profiles. Enable both rules. 4. Now you can confirm connectivity on your new network. On CLIENT1, at a command prompt, run the command ping 192.168.0.1. Confirm that you receive replies from MBRSVR1. Note You have to use the IP address, because CLIENT1 currently cannot communicate with the DNS server on the private network. 5. On DC1, at a command prompt, run the command ping 131.107.0.101, and confirm that you receive a reply from CLIENT1. Tip You may need to restart CLIENT1 for this to work. Next topic:
4. On the Properties dialog box of the network adapter, select Internet Protocol Version 4 (TCP/IPv4), and then click Properties. 5. Change the Default Gateway to 192.168.0.100. Leave the all of the other fields unchanged, and then click OK and Close to save your settings. The next step enables IP packet forwarding on MBRSVR1 so that packets arriving at the end of the tunnel are forwarded on to the private network and vice versa. To enable packet forwarding on MBRSVR1 1. On MBRSVR1, at Administrator: command prompt, run the following two commands: netsh interface ipv4 set interface “local area connection” forwarding = enabled netsh interface ipv4 set interface “local area connection 2” forwarding = enabled By default, the ICMP protocol that is used by ping is blocked by the firewall so the next step is to enable ICMP on CLIENT1 and MBRSVR1 so that we can verify connectivity. ICMP is already enabled on DC1 because of the Active Directory that are automatically enabled when the role service is installed. To enable ICMP traffic on MBRSVR1 and CLIENT1 1. On MBRSVR1, start Windows Firewall with Advanced Security. 2. Click Inbound Rules, right-click the rule File and Printer Sharing (Echo Request – ICMPv4-In), and then click Enable Rule. 3. Repeat steps 1 and 2 on CLIENT1 to enable the same rule on that computer. On CLIENT1, there are two versions of the rule – one for the Domain profile, and one for the Public and Private profiles. Enable both rules. 4. Now you can confirm connectivity on your new network. On CLIENT1, at a command prompt, run the command ping 192.168.0.1. Confirm that you receive replies from MBRSVR1. Note You have to use the IP address, because CLIENT1 currently cannot communicate with the DNS server on the private network. 5. On DC1, at a command prompt, run the command ping 131.107.0.101, and confirm that you receive a reply from CLIENT1. Tip You may need to restart CLIENT1 for this to work. Next topic: