<div>
Single NIC, single subnet 10.0.0.0/16 is correct. Everything else calls for trouble. Only if you want the networks to be physically separate, i.e. using different switches, the two NIC setup makes sense. More, your &quot;main network&quot; network mask should match on all devices. 
 
Having said that, it is probably not the culprit. 
Re first hop being the VPN client IP, that is correct or not, depening on the definition, but it is better this way, to account for additional &quot;cost&quot; to transfer data via a slow/high latency link. So nothing to worry about. 
I'm expecting tracert to show exactly two nodes only: Source and target. It doesn't help hence. You do not know if the target does not reply, or reply using a route, or whatsoever. To know that for sure you have to use MS NetMon or WireShark or another network capturing application on the RRAS server and the target machine with an IP address filter set to the VPN client IP, then perform a ping from your VPN client to the target, and see what is captured.
</div>

<div>
Thank you very much for your feedback and advice! 
 
To make the environment less complex I installed a new copy of 2012R2 and RRAS using just one NIC. &nbsp;Naturally, the issue is still present. &nbsp;:-( 
 
I think the problem is that VPN, or DHCP, is not providing the proper network mask. &nbsp;On my server and in DHCP the network mask is 255.255.255.0. &nbsp;But my VPN connection always gives me 255.255.255.255. 
 
I can RDP and access the VPN host while on the VPN connection, but I cannot access any other resources in the subnet. 
 
How can I force VPN to give the client a different network mask? 
 
Here’s the ipconfig of each: 
SERVER -&gt; PPP adapter RAS (Dial In) Interface: 
&nbsp; &nbsp;Connection-specific DNS Suffix &nbsp;. : 
&nbsp; &nbsp;Description . . . . . . . . . . . : RAS (Dial In) Interface 
&nbsp; &nbsp;Physical Address. . . . . . . . . : 
&nbsp; &nbsp;DHCP Enabled. . . . . . . . . . . : No 
&nbsp; &nbsp;Autoconfiguration Enabled . . . . : Yes 
&nbsp; &nbsp;IPv4 Address. . . . . . . . . . . : 10.1.0.210(Preferred) 
&nbsp; &nbsp;Subnet Mask . . . . . . . . . . . : 255.255.255.255 
&nbsp; &nbsp;Default Gateway . . . . . . . . . : 
&nbsp; &nbsp;NetBIOS over Tcpip. . . . . . . . : Enabled 
 
SERVER -&gt; Ethernet adapter Ethernet: 
&nbsp; &nbsp;Connection-specific DNS Suffix &nbsp;. : 
&nbsp; &nbsp;Description . . . . . . . . . . . : AWS PV Network Device #0 
&nbsp; &nbsp;Physical Address. . . . . . . . . : &lt;removed&gt; 
&nbsp; &nbsp;DHCP Enabled. . . . . . . . . . . : No 
&nbsp; &nbsp;Autoconfiguration Enabled . . . . : Yes 
&nbsp; &nbsp;Link-local IPv6 Address . . . . . : &lt;removed&gt;(Preferred) 
&nbsp; &nbsp;IPv4 Address. . . . . . . . . . . : 10.1.0.200(Preferred) 
&nbsp; &nbsp;Subnet Mask . . . . . . . . . . . : 255.255.255.0 
&nbsp; &nbsp;Default Gateway . . . . . . . . . : 10.1.0.1 
&nbsp; &nbsp;DNS Servers . . . . . . . . . . . : 10.1.0.200 
&nbsp; &nbsp;NetBIOS over Tcpip. . . . . . . . : Enabled 
 
CLIENT -&gt; PPP adapter vpn: 
&nbsp; &nbsp;Connection-specific DNS Suffix &nbsp;. : mydomain.net 
&nbsp; &nbsp;Description . . . . . . . . . . . : vpn 
&nbsp; &nbsp;Physical Address. . . . . . . . . : 
&nbsp; &nbsp;DHCP Enabled. . . . . . . . . . . : No 
&nbsp; &nbsp;Autoconfiguration Enabled . . . . : Yes 
&nbsp; &nbsp;IPv4 Address. . . . . . . . . . . : 10.1.0.209(Preferred) 
&nbsp; &nbsp;Subnet Mask . . . . . . . . . . . : 255.255.255.255 
&nbsp; &nbsp;Default Gateway . . . . . . . . . : 
&nbsp; &nbsp;DNS Servers . . . . . . . . . . . : 10.1.0.200 
&nbsp; &nbsp;NetBIOS over Tcpip. . . . . . . . : Enabled 
 
Thanks! 
--Joe
</div>

<div>
It is normal that you have that netmask on the dial-in client. More important is the routing table (route print 10.1.*).
</div>

<div>
Thanks very much for your help Qlemo! 
 
Here is the route print for 10.1.* on both the client and the server. &nbsp;If you would kindly review this and see if it is telling, I would sure appreciate it. &nbsp;:-) &nbsp;I'm afraid I'm really stumped here. 
 
CLIENT-&gt; route print 10.1.* 
=========================================================================== 
Interface List 
&nbsp; 5...f8 16 54 06 49 6b ......Microsoft Wi-Fi Direct Virtual Adapter 
&nbsp; 3...fa 16 54 06 49 6a ......Microsoft Hosted Network Virtual Adapter 
&nbsp;43...........................vpn 
&nbsp; 2...f8 16 54 06 49 6a ......Intel(R) Dual Band Wireless-AC 7260 
&nbsp; 1...........................Software Loopback Interface 1 
&nbsp; 6...00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface 
&nbsp;20...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #2 
&nbsp;22...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #4 
=========================================================================== 
 
IPv4 Route Table 
=========================================================================== 
Active Routes: 
Network Destination &nbsp; &nbsp; &nbsp; &nbsp;Netmask &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Gateway &nbsp; &nbsp; &nbsp; Interface &nbsp;Metric 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;10.1.0.0 &nbsp; &nbsp;255.255.255.0 &nbsp; &nbsp; &nbsp; &nbsp; On-link &nbsp; &nbsp; &nbsp; &nbsp;10.1.0.209 &nbsp; &nbsp; 11 
&nbsp; &nbsp; &nbsp; &nbsp;10.1.0.209 &nbsp;255.255.255.255 &nbsp; &nbsp; &nbsp; &nbsp; On-link &nbsp; &nbsp; &nbsp; &nbsp;10.1.0.209 &nbsp; &nbsp;266 
&nbsp; &nbsp; &nbsp; &nbsp;10.1.0.255 &nbsp;255.255.255.255 &nbsp; &nbsp; &nbsp; &nbsp; On-link &nbsp; &nbsp; &nbsp; &nbsp;10.1.0.209 &nbsp; &nbsp;266 
=========================================================================== 
Persistent Routes: 
&nbsp; None 
 
IPv6 Route Table 
=========================================================================== 
Active Routes: 
&nbsp; None 
Persistent Routes: 
&nbsp; None 
*************************************************************************** 
 
SERVER-&gt; route print 10.1.* 
=========================================================================== 
Interface List 
&nbsp;26...........................RAS (Dial In) Interface 
&nbsp;12...0e ac 9d 71 09 f3 ......AWS PV Network Device #0 
&nbsp; 1...........................Software Loopback Interface 1 
&nbsp;13...00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface 
&nbsp;15...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #2 
&nbsp;16...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #3 
=========================================================================== 
 
IPv4 Route Table 
=========================================================================== 
Active Routes: 
Network Destination &nbsp; &nbsp; &nbsp; &nbsp;Netmask &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Gateway &nbsp; &nbsp; &nbsp; Interface &nbsp;Metric 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;10.1.0.0 &nbsp; &nbsp;255.255.255.0 &nbsp; &nbsp; &nbsp; &nbsp; On-link &nbsp; &nbsp; &nbsp; &nbsp;10.1.0.200 &nbsp; &nbsp;266 
&nbsp; &nbsp; &nbsp; &nbsp;10.1.0.200 &nbsp;255.255.255.255 &nbsp; &nbsp; &nbsp; &nbsp; On-link &nbsp; &nbsp; &nbsp; &nbsp;10.1.0.200 &nbsp; &nbsp;266 
&nbsp; &nbsp; &nbsp; &nbsp;10.1.0.209 &nbsp;255.255.255.255 &nbsp; &nbsp; &nbsp; 10.1.0.209 &nbsp; &nbsp; &nbsp; 10.1.0.210 &nbsp; &nbsp; 31 
&nbsp; &nbsp; &nbsp; &nbsp;10.1.0.210 &nbsp;255.255.255.255 &nbsp; &nbsp; &nbsp; &nbsp; On-link &nbsp; &nbsp; &nbsp; &nbsp;10.1.0.210 &nbsp; &nbsp;286 
&nbsp; &nbsp; &nbsp; &nbsp;10.1.0.255 &nbsp;255.255.255.255 &nbsp; &nbsp; &nbsp; &nbsp; On-link &nbsp; &nbsp; &nbsp; &nbsp;10.1.0.200 &nbsp; &nbsp;266 
=========================================================================== 
Persistent Routes: 
&nbsp; None 
 
IPv6 Route Table 
=========================================================================== 
Active Routes: 
&nbsp; None 
Persistent Routes: 
&nbsp; None
</div>

<div>
As I expected, the client gets a 10.1.0.0/24 route. With that you should be able to reach any machine in that subnet (10.1.0.x).
</div>

<div>
I don 't know what to try next... 
 
The problem is clearly routing. &nbsp;I can connect to the VPN server and also RDP to it just fine, but no matter what I cannot route to any other system in the subnet. &nbsp;My tracert goes to the VPN host and that's it. 
 
It is unclear if I need to add a static route in RRAS on the VPN server, or on the VPN client. &nbsp;But it is pretty clear that I need to add the route(s) somewhere.
</div>

<div>
If someone would please take a look at my routing again, I'd sure appreciate it! 
 
Here is the IPv4 Route Table from my existing OpenVPN client connection, which I am trying to replace with the new Windows 2012R2 RRAS VPN server. 
=========================================================================== 
Active Routes: 
Network Destination &nbsp; &nbsp; &nbsp; &nbsp;Netmask &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Gateway &nbsp; &nbsp; &nbsp; Interface &nbsp;Metric 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 0.0.0.0 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;0.0.0.0 &nbsp; &nbsp; &nbsp;192.168.1.1 &nbsp; &nbsp; 192.168.1.18 &nbsp; &nbsp; 20 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;10.0.0.0 &nbsp; &nbsp; &nbsp; &nbsp;255.0.0.0 &nbsp; &nbsp; &nbsp; 10.255.0.1 &nbsp; &nbsp; &nbsp;10.255.0.12 &nbsp; &nbsp; 20 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;10.1.0.0 &nbsp; &nbsp; &nbsp;255.255.0.0 &nbsp; &nbsp; &nbsp; 10.255.0.1 &nbsp; &nbsp; &nbsp;10.255.0.12 &nbsp; &nbsp; 20 
&nbsp; &nbsp; &nbsp; &nbsp;10.255.0.0 &nbsp; &nbsp; &nbsp;255.255.0.0 &nbsp; &nbsp; &nbsp; &nbsp; On-link &nbsp; &nbsp; &nbsp; 10.255.0.12 &nbsp; &nbsp;276 
&nbsp; &nbsp; &nbsp; &nbsp;10.255.0.0 &nbsp; &nbsp; &nbsp;255.255.0.0 &nbsp; &nbsp; &nbsp; 10.255.0.1 &nbsp; &nbsp; &nbsp;10.255.0.12 &nbsp; &nbsp; 20 
&nbsp; &nbsp; &nbsp; 10.255.0.12 &nbsp;255.255.255.255 &nbsp; &nbsp; &nbsp; &nbsp; On-link &nbsp; &nbsp; &nbsp; 10.255.0.12 &nbsp; &nbsp;276 
&nbsp; &nbsp;10.255.255.255 &nbsp;255.255.255.255 &nbsp; &nbsp; &nbsp; &nbsp; On-link &nbsp; &nbsp; &nbsp; 10.255.0.12 &nbsp; &nbsp;276 
&nbsp; &nbsp; &nbsp; &nbsp; 127.0.0.0 &nbsp; &nbsp; &nbsp; &nbsp;255.0.0.0 &nbsp; &nbsp; &nbsp; &nbsp; On-link &nbsp; &nbsp; &nbsp; &nbsp; 127.0.0.1 &nbsp; &nbsp;306 
&nbsp; &nbsp; &nbsp; &nbsp; 127.0.0.1 &nbsp;255.255.255.255 &nbsp; &nbsp; &nbsp; &nbsp; On-link &nbsp; &nbsp; &nbsp; &nbsp; 127.0.0.1 &nbsp; &nbsp;306 
&nbsp; 127.255.255.255 &nbsp;255.255.255.255 &nbsp; &nbsp; &nbsp; &nbsp; On-link &nbsp; &nbsp; &nbsp; &nbsp; 127.0.0.1 &nbsp; &nbsp;306 
&nbsp; &nbsp; &nbsp; 192.168.1.0 &nbsp; &nbsp;255.255.255.0 &nbsp; &nbsp; &nbsp; &nbsp; On-link &nbsp; &nbsp; &nbsp;192.168.1.18 &nbsp; &nbsp;276 
&nbsp; &nbsp; &nbsp;192.168.1.18 &nbsp;255.255.255.255 &nbsp; &nbsp; &nbsp; &nbsp; On-link &nbsp; &nbsp; &nbsp;192.168.1.18 &nbsp; &nbsp;276 
&nbsp; &nbsp; 192.168.1.255 &nbsp;255.255.255.255 &nbsp; &nbsp; &nbsp; &nbsp; On-link &nbsp; &nbsp; &nbsp;192.168.1.18 &nbsp; &nbsp;276 
&nbsp; &nbsp; &nbsp; &nbsp; 224.0.0.0 &nbsp; &nbsp; &nbsp; &nbsp;240.0.0.0 &nbsp; &nbsp; &nbsp; &nbsp; On-link &nbsp; &nbsp; &nbsp; &nbsp; 127.0.0.1 &nbsp; &nbsp;306 
&nbsp; &nbsp; &nbsp; &nbsp; 224.0.0.0 &nbsp; &nbsp; &nbsp; &nbsp;240.0.0.0 &nbsp; &nbsp; &nbsp; &nbsp; On-link &nbsp; &nbsp; &nbsp; 10.255.0.12 &nbsp; &nbsp;276 
&nbsp; &nbsp; &nbsp; &nbsp; 224.0.0.0 &nbsp; &nbsp; &nbsp; &nbsp;240.0.0.0 &nbsp; &nbsp; &nbsp; &nbsp; On-link &nbsp; &nbsp; &nbsp;192.168.1.18 &nbsp; &nbsp;276 
&nbsp; 255.255.255.255 &nbsp;255.255.255.255 &nbsp; &nbsp; &nbsp; &nbsp; On-link &nbsp; &nbsp; &nbsp; &nbsp; 127.0.0.1 &nbsp; &nbsp;306 
&nbsp; 255.255.255.255 &nbsp;255.255.255.255 &nbsp; &nbsp; &nbsp; &nbsp; On-link &nbsp; &nbsp; &nbsp; 10.255.0.12 &nbsp; &nbsp;276 
&nbsp; 255.255.255.255 &nbsp;255.255.255.255 &nbsp; &nbsp; &nbsp; &nbsp; On-link &nbsp; &nbsp; &nbsp;192.168.1.18 &nbsp; &nbsp;276 
=========================================================================== 
Persistent Routes: 
&nbsp; None 
=========================================================================== 
 
 
And here is the IPv4 Route Table from my new Windows 2012R2 RRAS VPN client connection, which won't route anywhere beyond the host I connect to. 
=========================================================================== 
Active Routes: 
Network Destination &nbsp; &nbsp; &nbsp; &nbsp;Netmask &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Gateway &nbsp; &nbsp; &nbsp; Interface &nbsp;Metric 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 0.0.0.0 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;0.0.0.0 &nbsp; &nbsp; &nbsp;192.168.1.1 &nbsp; &nbsp; 192.168.1.18 &nbsp; &nbsp; 20 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;10.0.0.0 &nbsp; &nbsp; &nbsp; &nbsp;255.0.0.0 &nbsp; &nbsp; 10.255.0.201 &nbsp; &nbsp; 10.255.0.202 &nbsp; &nbsp; 11 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;10.1.0.0 &nbsp; &nbsp; &nbsp;255.255.0.0 &nbsp; &nbsp; &nbsp; &nbsp; On-link &nbsp; &nbsp; &nbsp;10.255.0.202 &nbsp; &nbsp; 11 
&nbsp; &nbsp; &nbsp;10.1.255.255 &nbsp;255.255.255.255 &nbsp; &nbsp; &nbsp; &nbsp; On-link &nbsp; &nbsp; &nbsp;10.255.0.202 &nbsp; &nbsp;266 
&nbsp; &nbsp; &nbsp; &nbsp;10.255.0.0 &nbsp; &nbsp; &nbsp;255.255.0.0 &nbsp; &nbsp; &nbsp; &nbsp; On-link &nbsp; &nbsp; &nbsp;10.255.0.202 &nbsp; &nbsp; 11 
&nbsp; &nbsp; &nbsp;10.255.0.202 &nbsp;255.255.255.255 &nbsp; &nbsp; &nbsp; &nbsp; On-link &nbsp; &nbsp; &nbsp;10.255.0.202 &nbsp; &nbsp;266 
&nbsp; &nbsp;10.255.255.255 &nbsp;255.255.255.255 &nbsp; &nbsp; &nbsp; &nbsp; On-link &nbsp; &nbsp; &nbsp;10.255.0.202 &nbsp; &nbsp;266 
&nbsp; &nbsp; 52.71.137.102 &nbsp;255.255.255.255 &nbsp; &nbsp; &nbsp;192.168.1.1 &nbsp; &nbsp; 192.168.1.18 &nbsp; &nbsp; 21 
&nbsp; &nbsp; &nbsp; &nbsp; 127.0.0.0 &nbsp; &nbsp; &nbsp; &nbsp;255.0.0.0 &nbsp; &nbsp; &nbsp; &nbsp; On-link &nbsp; &nbsp; &nbsp; &nbsp; 127.0.0.1 &nbsp; &nbsp;306 
&nbsp; &nbsp; &nbsp; &nbsp; 127.0.0.1 &nbsp;255.255.255.255 &nbsp; &nbsp; &nbsp; &nbsp; On-link &nbsp; &nbsp; &nbsp; &nbsp; 127.0.0.1 &nbsp; &nbsp;306 
&nbsp; 127.255.255.255 &nbsp;255.255.255.255 &nbsp; &nbsp; &nbsp; &nbsp; On-link &nbsp; &nbsp; &nbsp; &nbsp; 127.0.0.1 &nbsp; &nbsp;306 
&nbsp; &nbsp; &nbsp; 192.168.1.0 &nbsp; &nbsp;255.255.255.0 &nbsp; &nbsp; &nbsp; &nbsp; On-link &nbsp; &nbsp; &nbsp;192.168.1.18 &nbsp; &nbsp;276 
&nbsp; &nbsp; &nbsp;192.168.1.18 &nbsp;255.255.255.255 &nbsp; &nbsp; &nbsp; &nbsp; On-link &nbsp; &nbsp; &nbsp;192.168.1.18 &nbsp; &nbsp;276 
&nbsp; &nbsp; 192.168.1.255 &nbsp;255.255.255.255 &nbsp; &nbsp; &nbsp; &nbsp; On-link &nbsp; &nbsp; &nbsp;192.168.1.18 &nbsp; &nbsp;276 
&nbsp; &nbsp; &nbsp; &nbsp; 224.0.0.0 &nbsp; &nbsp; &nbsp; &nbsp;240.0.0.0 &nbsp; &nbsp; &nbsp; &nbsp; On-link &nbsp; &nbsp; &nbsp; &nbsp; 127.0.0.1 &nbsp; &nbsp;306 
&nbsp; &nbsp; &nbsp; &nbsp; 224.0.0.0 &nbsp; &nbsp; &nbsp; &nbsp;240.0.0.0 &nbsp; &nbsp; &nbsp; &nbsp; On-link &nbsp; &nbsp; &nbsp;192.168.1.18 &nbsp; &nbsp;276 
&nbsp; &nbsp; &nbsp; &nbsp; 224.0.0.0 &nbsp; &nbsp; &nbsp; &nbsp;240.0.0.0 &nbsp; &nbsp; &nbsp; &nbsp; On-link &nbsp; &nbsp; &nbsp;10.255.0.202 &nbsp; &nbsp;266 
&nbsp; 255.255.255.255 &nbsp;255.255.255.255 &nbsp; &nbsp; &nbsp; &nbsp; On-link &nbsp; &nbsp; &nbsp; &nbsp; 127.0.0.1 &nbsp; &nbsp;306 
&nbsp; 255.255.255.255 &nbsp;255.255.255.255 &nbsp; &nbsp; &nbsp; &nbsp; On-link &nbsp; &nbsp; &nbsp;192.168.1.18 &nbsp; &nbsp;276 
&nbsp; 255.255.255.255 &nbsp;255.255.255.255 &nbsp; &nbsp; &nbsp; &nbsp; On-link &nbsp; &nbsp; &nbsp;10.255.0.202 &nbsp; &nbsp;266 
=========================================================================== 
Persistent Routes: 
&nbsp; None 
=========================================================================== 
 
 
If it helps, here is the IPv4 Route Table from the new Windows 2012R2 RRAS Server itself. 
=========================================================================== 
Active Routes: 
Network Destination &nbsp; &nbsp; &nbsp; &nbsp;Netmask &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Gateway &nbsp; &nbsp; &nbsp; Interface &nbsp;Metric 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 0.0.0.0 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;0.0.0.0 &nbsp; &nbsp; &nbsp; &nbsp; 10.1.0.1 &nbsp; &nbsp; &nbsp; 10.1.0.200 &nbsp; &nbsp;266 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;10.1.0.0 &nbsp; &nbsp;255.255.255.0 &nbsp; &nbsp; &nbsp; &nbsp; On-link &nbsp; &nbsp; &nbsp; &nbsp;10.1.0.200 &nbsp; &nbsp;266 
&nbsp; &nbsp; &nbsp; &nbsp;10.1.0.200 &nbsp;255.255.255.255 &nbsp; &nbsp; &nbsp; &nbsp; On-link &nbsp; &nbsp; &nbsp; &nbsp;10.1.0.200 &nbsp; &nbsp;266 
&nbsp; &nbsp; &nbsp; &nbsp;10.1.0.255 &nbsp;255.255.255.255 &nbsp; &nbsp; &nbsp; &nbsp; On-link &nbsp; &nbsp; &nbsp; &nbsp;10.1.0.200 &nbsp; &nbsp;266 
&nbsp; &nbsp; &nbsp; &nbsp; 127.0.0.0 &nbsp; &nbsp; &nbsp; &nbsp;255.0.0.0 &nbsp; &nbsp; &nbsp; &nbsp; On-link &nbsp; &nbsp; &nbsp; &nbsp; 127.0.0.1 &nbsp; &nbsp;306 
&nbsp; &nbsp; &nbsp; &nbsp; 127.0.0.1 &nbsp;255.255.255.255 &nbsp; &nbsp; &nbsp; &nbsp; On-link &nbsp; &nbsp; &nbsp; &nbsp; 127.0.0.1 &nbsp; &nbsp;306 
&nbsp; 127.255.255.255 &nbsp;255.255.255.255 &nbsp; &nbsp; &nbsp; &nbsp; On-link &nbsp; &nbsp; &nbsp; &nbsp; 127.0.0.1 &nbsp; &nbsp;306 
&nbsp; 169.254.169.250 &nbsp;255.255.255.255 &nbsp; &nbsp; &nbsp; &nbsp; 10.1.0.1 &nbsp; &nbsp; &nbsp; 10.1.0.200 &nbsp; &nbsp; 10 
&nbsp; 169.254.169.251 &nbsp;255.255.255.255 &nbsp; &nbsp; &nbsp; &nbsp; 10.1.0.1 &nbsp; &nbsp; &nbsp; 10.1.0.200 &nbsp; &nbsp; 10 
&nbsp; 169.254.169.254 &nbsp;255.255.255.255 &nbsp; &nbsp; &nbsp; &nbsp; 10.1.0.1 &nbsp; &nbsp; &nbsp; 10.1.0.200 &nbsp; &nbsp; 10 
&nbsp; &nbsp; &nbsp; &nbsp; 224.0.0.0 &nbsp; &nbsp; &nbsp; &nbsp;240.0.0.0 &nbsp; &nbsp; &nbsp; &nbsp; On-link &nbsp; &nbsp; &nbsp; &nbsp; 127.0.0.1 &nbsp; &nbsp;306 
&nbsp; &nbsp; &nbsp; &nbsp; 224.0.0.0 &nbsp; &nbsp; &nbsp; &nbsp;240.0.0.0 &nbsp; &nbsp; &nbsp; &nbsp; On-link &nbsp; &nbsp; &nbsp; &nbsp;10.1.0.200 &nbsp; &nbsp;266 
&nbsp; 255.255.255.255 &nbsp;255.255.255.255 &nbsp; &nbsp; &nbsp; &nbsp; On-link &nbsp; &nbsp; &nbsp; &nbsp; 127.0.0.1 &nbsp; &nbsp;306 
&nbsp; 255.255.255.255 &nbsp;255.255.255.255 &nbsp; &nbsp; &nbsp; &nbsp; On-link &nbsp; &nbsp; &nbsp; &nbsp;10.1.0.200 &nbsp; &nbsp;266 
=========================================================================== 
Persistent Routes: 
&nbsp; Network Address &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Netmask &nbsp;Gateway Address &nbsp;Metric 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 0.0.0.0 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;0.0.0.0 &nbsp; &nbsp; &nbsp; &nbsp; 10.1.0.1 &nbsp;Default 
===========================================================================
</div>

<div>
After several different configuration attempts the only way I could get it to work in my environment was to also enable NAT on RRAS. &nbsp;It just wouldn't work in my environment without NAT. 
 
Thanks for the help Qlemo.
</div>

<div>
I've requested that this question be closed as follows: 
 
Accepted answer: 0 points for JOE-BULLITT's comment <a href="https://www.experts-exchange.com/questions/28911260/Need-help-properly-configuring-RRAS-on-Server-2012R2-It-won't-route.html?anchorAnswerId=41483238#a41483238" rel="ugc">#a41483238</a> 
 
for the following reason: 
 
I've configured VPN before without NAT, but this time it was the only way to get it to work.
</div>

<div>
<div class="content wysiwyg-content">
Hello Experts! 
 
Thank you for your kind assistance. 
 
I am trying to deploy a Windows 2012R2 server with RRAS VPN and am having a bit of trouble and cannot figure out what is wrong. &nbsp;I searched the threads and I see others that had similar issues, but the solutions did not work for me. 
(<a href="https://www.experts-exchange.com/questions/28480617/LAN-Routing-over-RRAS-VPN.html" rel="ugc nofollow">https://www.experts-exchange.com/questions/28480617/LAN-Routing-over-RRAS-VPN.html</a>) 
(<a href="https://www.experts-exchange.com/questions/26798399/RRAS-VPN-Routing-Problem.html" rel="ugc">https://www.experts-exchange.com/questions/26798399/RRAS-VPN-Routing-Problem.html</a>) 
 
The server is running and everything installed fine. &nbsp;The VPN client can connect, but it will not route anywhere in the same LAN as the Windows RRAS server. &nbsp;Through VPN, I can ping and RDP to the RRAS server via its private IP, but I cannot access any other servers in the same destination network. 
 
My server installation has two NIC’s in two subnets and is running RRAS/VPN and DNS. &nbsp;I also tried with just one NIC and one subnet, another time using two NIC’s and one subnet, and now two NIC’s and two subnets. &nbsp;All unsuccessful. 
 
Here is what I have so far… 
 
Server Public IP: 10.1.0.100/24 
Server Private IP: 10.1.1.100/24 
Public Subnet: 10.1.0.0/24 
Private Subnet: 10.1.1.0/24 
Main Network: 10.1.0.0/16 
 
DNS IP: 10.1.1.100/24 (DNS also listening on 10.1.0.100/24) 
RRAS Server External IP: 10.1.0.100/24 
RRAS Server Internal IP: 10.1.1.100/24 
IPv4 address assignment using RRAS static pool: &nbsp;10.1.1.101 – 10.1.1.120 
IPv4 forwarding is enabled 
Lan and Demand Dial routing is enabled 
 
I can connect fine via VPN and I get an IP address, but I am unable to reach anything in the 10.1.1.x or 10.1.0.x network except the RRAS/VPN host itself. 
 
Here are the results from the ipconfig on the client VPN adapter 
PPP adapter vpn: 
&nbsp; &nbsp;Connection-specific DNS Suffix &nbsp;. : 
&nbsp; &nbsp;Description . . . . . . . . . . . : vpn 
&nbsp; &nbsp;Physical Address. . . . . . . . . : 
&nbsp; &nbsp;DHCP Enabled. . . . . . . . . . . : No 
&nbsp; &nbsp;Autoconfiguration Enabled . . . . : Yes 
&nbsp; &nbsp;IPv4 Address. . . . . . . . . . . : 10.1.1.102(Preferred) 
&nbsp; &nbsp;Subnet Mask . . . . . . . . . . . : 255.255.255.255 
&nbsp; &nbsp;Default Gateway . . . . . . . . . : 
&nbsp; &nbsp;DNS Servers . . . . . . . . . . . : 10.1.0.100 
&nbsp; &nbsp;NetBIOS over Tcpip. . . . . . . . : Enabled 
 
Here is the result from a tracert to the Public and Private NIC’s on the RRAS server itself: 
&gt;tracert 10.1.1.100 
Tracing route to VPN [10.1.1.100] over a maximum of 30 hops: 
&nbsp; 1 &nbsp; &nbsp;86 ms &nbsp; &nbsp;88 ms &nbsp; &nbsp;84 ms &nbsp;VPN [10.1.1.101] 
&nbsp; 2 &nbsp; &nbsp;87 ms &nbsp; &nbsp;90 ms &nbsp; &nbsp;91 ms &nbsp;VPN [10.1.1.100] 
 
&gt;tracert 10.1.0.100 
Tracing route to VPN [10.1.0.100] over a maximum of 30 hops: 
&nbsp; 1 &nbsp; 101 ms &nbsp; &nbsp; * &nbsp; &nbsp; &nbsp; 89 ms &nbsp;VPN [10.1.1.101] 
&nbsp; 2 &nbsp; &nbsp;98 ms &nbsp; &nbsp;97 ms &nbsp; &nbsp;86 ms &nbsp;VPN [10.1.0.100] 
 
I found it curious that my first hop was to the IP 10.1.1.101. &nbsp;Is this normal, or should it be configured somewhere? 
 
Here is the result from a tracert to an IP in the subnet 
&gt;tracert 10.1.0.10 
Tracing route to 10.1.0.10 over a maximum of 30 hops 
&nbsp; 1 &nbsp; &nbsp;92 ms &nbsp; &nbsp; * &nbsp; &nbsp; &nbsp; 90 ms &nbsp;VPN [10.1.1.101] 
&nbsp; 2 &nbsp; &nbsp; * &nbsp; &nbsp; &nbsp; &nbsp;* &nbsp; &nbsp; &nbsp; &nbsp;* &nbsp; &nbsp; Request timed out. 
&nbsp; 3 &nbsp; &nbsp; * &nbsp; &nbsp; &nbsp; &nbsp;* &nbsp; &nbsp; &nbsp; &nbsp;* &nbsp; &nbsp; Request timed out. 
&nbsp; 4 &nbsp; &nbsp; * &nbsp; &nbsp; &nbsp; &nbsp;* &nbsp; &nbsp; &nbsp; &nbsp;* &nbsp; &nbsp; Request timed out. 
 
Can someone please advise what I am missing, or what I should check? &nbsp; Thank you!!!
</div>
</div>

Hello Experts!

Thank you for your kind assistance.

I am trying to deploy a Windows 2012R2 server with RRAS VPN and am having a bit of trouble and cannot figure out what is wrong.  I searched the threads and I see others that had similar issues, but the solutions did not work for me.
(http://www.experts-exchange.com/questions/28480617/LAN-Routing-over-RRAS-VPN.html)
(http://www.experts-exchange.com/questions/26798399/RRAS-VPN-Routing-Problem.html)

The server is running and everything installed fine.  The VPN client can connect, but it will not route anywhere in the same LAN as the Windows RRAS server.  Through VPN, I can ping and RDP to the RRAS server via its private IP, but I cannot access any other servers in the same destination network.

My server installation has two NIC’s in two subnets and is running RRAS/VPN and DNS.  I also tried with just one NIC and one subnet, another time using two NIC’s and one subnet, and now two NIC’s and two subnets.  All unsuccessful.

Here is what I have so far…

Server Public IP: 10.1.0.100/24
Server Private IP: 10.1.1.100/24
Public Subnet: 10.1.0.0/24
Private Subnet: 10.1.1.0/24
Main Network: 10.1.0.0/16

DNS IP: 10.1.1.100/24 (DNS also listening on 10.1.0.100/24)
RRAS Server External IP: 10.1.0.100/24
RRAS Server Internal IP: 10.1.1.100/24
IPv4 address assignment using RRAS static pool:  10.1.1.101 – 10.1.1.120
IPv4 forwarding is enabled
Lan and Demand Dial routing is enabled

I can connect fine via VPN and I get an IP address, but I am unable to reach anything in the 10.1.1.x or 10.1.0.x network except the RRAS/VPN host itself.

Here are the results from the ipconfig on the client VPN adapter
PPP adapter vpn:
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : vpn
   Physical Address. . . . . . . . . :
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv4 Address. . . . . . . . . . . : 10.1.1.102(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.255
   Default Gateway . . . . . . . . . :
   DNS Servers . . . . . . . . . . . : 10.1.0.100
   NetBIOS over Tcpip. . . . . . . . : Enabled

Here is the result from a tracert to the Public and Private NIC’s on the RRAS server itself:
>tracert 10.1.1.100
Tracing route to VPN [10.1.1.100] over a maximum of 30 hops:
  1    86 ms    88 ms    84 ms  VPN [10.1.1.101]
  2    87 ms    90 ms    91 ms  VPN [10.1.1.100]

>tracert 10.1.0.100
Tracing route to VPN [10.1.0.100] over a maximum of 30 hops:
  1   101 ms     *       89 ms  VPN [10.1.1.101]
  2    98 ms    97 ms    86 ms  VPN [10.1.0.100]

I found it curious that my first hop was to the IP 10.1.1.101.  Is this normal, or should it be configured somewhere?

Here is the result from a tracert to an IP in the subnet
>tracert 10.1.0.10
Tracing route to 10.1.0.10 over a maximum of 30 hops
  1    92 ms     *       90 ms  VPN [10.1.1.101]
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4     *        *        *     Request timed out.

Can someone please advise what I am missing, or what I should check?   Thank you!!!

Need help properly configuring RRAS on Server 2012R2.  It won't route!

A virtual private network (VPN) is a network that uses a public telecommunication infrastructure, such as the Internet, to provide remote offices or travelling users access to a central organizational network securely. VPNs encapsulate data transfers using secure cryptographic methods and other security mechanisms to ensure that only authorized users can access the network and that the data cannot be intercepted.

Windows Server 2012 is the server version of Windows 8 and the successor to Windows Server 2008 R2. Windows Server 2012 is the first version of Windows Server to have no support for Itanium-based computers since Windows NT 4.0. Windows Server 2012, now in its second release (Windows Server 2012 Release 2) includes Foundation, Essentials, Standard and Datacenter, and does not support IA-32 or IA-64 processors.

Windows Server 2012

The Windows operating systems have distinct methodologies for designing and implementing networks, and have specific systems to accomplish various networking processes, such as Exchange for email, Sharepoint for shared files and programs, and IIS for delivery of web pages. Microsoft also produces server technologies for networked database use, security and virtualization.

Windows Networking

Networking is the process of connecting computing devices, peripherals and terminals together through a system that uses wiring, cabling or radio waves that enable their users to communicate, share information and interact over distances. Often associated are issues regarding operating systems, hardware and equipment, cloud and virtual networking, protocols, architecture, storage and management.

Networking

Transmission Control Protocol/Internet Protocol (TCP/IP) is the set of networking protocols that define end-to-end connectivity specifying how data should be packeted, addressed, transmitted, routed and received at the destination. This functionality is organized into four abstraction layers which are used to sort all related protocols according to the scope of networking involved.