Windows Server 2012, two NICs, only rras role installed.
-
PC2 can PING anything at 192.168.2.xx by IP, but not by name.
-
PC2 in Network Neighborhood has only itself and mserver, but can access anything at \\192.168.2.xx (by IP, but not by name).
-
PC2 has Internet.
-
PC1 cannot see, nor PING anything beyond NIC1.
I'm kind of stuck trying to figure out why routing doesn't work proper for local traffic between the two LANs while internet routing works fine.
Best Answer
You're most likely missing routes for the 10.0.0.0/8 network on the gateway 192.168.2.1.
You see, when packets from PC1 try to reach PC2, first PC1 checks:
So, by all rights this setup shouldn't work at all, without a route for 10.0.0.0/8 setup in the 192.168.2.1 router, because even requests to the internet shouldn't be able to find a way back.
The reason this is working at all is because you've set up RRAS to do NAT of the traffic from your 10.0.0.0/8 network. Any outbound traffic from PC2 will have its address translated, first by MSERVER, so that its source IP on the 192.168.2.0/24 LAN will be 192.168.2.101.
So in this scenario, when PC2 sends out a ping, PC1 will see it as coming from 192.168.2.101 and will know to send the response there as well.
In this scenario, you add a route for 10.0.0.0/8 via 192.168.2.101 on your 192.168.2.1 router, and then disable NAT in RRAS.
Network browsing will still probably not work since it will only work within one broadcast domain unless special measures are taken. Hostnames will also require a specific setup to work properly.