Windows Server as a router

[JLogan3o13]

Just curious if anyone has ever used this feature. Try to assist someone setting up a home lab; has no hardware but has licenses as Server 2016. Haven't had a chance to sit in front of the environment yet, just going over his explanation, and it sounds right:

Server #1 LAN routing role installed and RRAS enabled:
   Interface 1:
      IP: 10.0.0.100 /24
      Gateway: 10.0.0.1 (ISP Router)
      DNS: ISP DNS
      
   Interface 2:
      IP 172.25.2.2 /24
      Gateway: Blank
      DNS: 127.0.0.1

Server #2
    Interface 1:
       IP: 172.25.2.4 /24
       Gateway: 172.25.2.2
       DNS: ISP DNS

He states that Server #2 can ping anything on both 10.0.0.x and 172.25.2.x subnets, as well as the internal router gateway (10.0.0.1). He cannot, however, ping the external router interface or get out to the internet.

I am going to take a look at it this weekend; just thought I would throw this out to anyone who have done this configuration with Windows Server as a router in the past. Am looking into whether there are any special caveats, like if he should be creating a static 0.0.0.0 route for his next hop to the internet or some such. 

[mLipok]

Did he try 

Quote

route print

and can give some additional information ?

[JLogan3o13]

I have all the information I am going to get until I get over there this weekend, as he is just starting in IT. As mentioned, I am sure I'll figure it out once I get in and putter about; was just curious if Server 2016 as a router has any known caveats as I have never used it that way.

[jackpeter9051]

Yes, you can use the Windows server as a router, but before that, you have to follow some tips that you can get from <link removed>. You can also consult an expert on the Customer service to get more suggestions. 

 

Edited November 15, 2018 by JLogan3o13

[JLogan3o13]

That makes literally zero sense.

[Skeletor]

Setup Etho Adapters like this:
 

Server #1 LAN routing role installed and RRAS enabled:
   Interface 1:
      IP: 10.0.0.100 /24
      Gateway: 10.0.0.1 (ISP Router)
      DNS: ISP DNS
      
   Interface 2:
      IP 172.25.2.3 /24
      Gateway: 172.25.2.1
      DNS: 

Server #2
    Interface 1:
       IP: 172.25.2.4 /24
       Gateway: 172.25.2.1
       DNS:

Then run on Server #1

route add 172.25.2.3 MASK 255.255.255.0 172.25.2.4 METRIC 1 -P

Edited December 7, 2018 by Skeletor