How do I make my Server 2008 (or R2) a router?

I met a partner that said he tried to move his Domain Controller from Windows Server 2003 to Windows Server 2008 and was having problems.  As we talked, it became clear that he was also using this server as a router for his office.  He said that once he replaced his 2003 server with 2008, his users could no longer access the Internet.  He told me he that he has two NICs in this server; one connected to his office network and users, the second NIC is connected to the WAN.  He told me that he did have his DC behind a firewall, but was struggling with getting his users connected to the Internet again.  We talked about configuring RRAS.  It sounded like he needed to setup RRAS to get his users access again, so I dug up the RRAS content for Server 2008 and R2. 

Here’s the best link I found, it’s a great starting point to understanding how to set it up.

Here’s the step-by-step guide that can walk your through setting up RRAS in your lab.

I’ve used RRAS on and off for years in my testing.  For me, I don’t have a dedicated router, so anytime a need a router in my testing, up pops an RRAS server.  Isn’t Hyper-V just awesome??

As an FYI, RRAS is a role that has to be enabled in Server 2008 (and R2).  The thing I couldn’t remember yesterday was that RRAS is included under the Network Policy and Access Services role.  Here is a link that talks specifically about enabling the RRAS role:

Please let me know your thoughts on setting up RRAS.  Has it worked for you?

Until next time!




Comments (1)

  1. Yaser Matar says:

    That’s a very helpful article.
    Thank you Rob!

Skip to main content