RRAS LAN and demand-dial routing (IPv6)

    General discussion

  • I was having lots of problems with Server 2012R2's RRAS not acting as the gateway for IPv6 traffic on the subnet assigned to remote access clients. After hours of troubleshooting I've found that while RRAS configures the router advertisement and prefix information to send to the LAN, it does NOT enable router advertisements on the LAN interface. This causes remote access clients to be able to get to the LAN but the servers on the LAN do not know how to send (and so do not send) traffic back to the RRAS server as the router it is.

    Running the following powershell enabled the router advertisements on the LAN side and let the servers learn the route, and they now use the RRAS server as the gateway to the remote client subnet.

    netsh interface ipv6 set interface "Ethernet" routerdiscovery=enabled advertise=enabled

    Mediocre Access 2010 | (Baby) Beginner C Sharp | OK at Active Directory (2012 R2) | Fragmented understanding of DNS/DHCP | Laughable experience with Group Policy | Expert question asker on MSDN Forums

    Thursday, October 26, 2017 5:35 PM