Home > Articles > Operating Systems, Server

  • Print
  • + Share This
This chapter is from the book

Chapter 12: Routing and Remote Access

Routing and Remote Access Service (RRAS) has often stirred up more controversy in the certification world than in the real world. Plenty have had to learn to deal with common Windows RRAS troubleshooting issues in order to pass the dreaded network infrastructure administration exam, but few have had to apply these concepts in real life.

Many that work in and around enterprise networks would never build a Windows server and then convert it to a router, when they could simply purchase a router that is likely more efficient for far less money than a server. On the other hand, if you support small businesses, there is a likely chance that they are using at least a portion of Routing and Remote Access Service, such as Network Address Translation (NAT), in order to provide routing services and Internet access while keeping costs down. If you find yourself in this boat, then this chapter will be extremely valuable for you, since Routing and Remote Access Service can be fraught with danger.

If routing is not a concern of yours, then don't forget about the other half of the service: remote access. Maybe routing is not important, but you have remote access configured for dial-up connections to a Windows server. If this is the case, then you will find the remote access troubleshooting portion of the chapter very useful.

In addition to the usual quick architectural and fault resolution explanations, this chapter provides descriptions of some hidden treasures in the troubleshooting world by documenting many unknown tools that you will find invaluable when trying to pinpoint the source of an RRAS problem.

  • + Share This
  • 🔖 Save To Your Account