Routing and Remote Access Service
 | This is an article recently created by a new user at Louisiana State University for a class project. More editing may be needed to meet standards, but please be courteous and assume good faith, and consider leaving a constructive message on the creator's talk page if large changes need to be made. This template should be removed once the page has been reviewed by someone other than its creator. If you are the article's creator, you can seek feedback on your new article. (May 2011) |
Routing and Remote Access Service (RRAS) is a Microsoft API and server software make it possible to create applications to administer the routing and remote access service capabilities of the operating system, to function as a network router, and developers can also use RRAS to implement routing protocols. The RRAS server functionality follows and builds upon the Remote Access Service (RAS).[1]
- Multiprotocol Router - The computer running RRAS can route IP,IPX, and AppleTalk simultaneously. All routable protocols are configured from the same administrative utility.
- Demand-Dial Router - IP and IPX can be routed over on-demand or persistent WAN links such as analog phone lines or ISDN, or over VPN connections.
- Remote Access Server - provides remote access connectivity to dial-up or VPN remote access clients that use IP,IPX, AppleTalk, or NetBEUI.
Routing services and remote access services used to work separately. Point-to-Point Protocol (PPP), the protocol suite commonly used to negotiate point-to-point connections, has allowed them to be combined.
Abstract
Routing and Remote Access Service (RRAS) can be used to create client applications. These applications display RAS common dialog boxes, manage remote access connections and devices, and manipulate phone-book entries.[2]
Routing and Remote Access Service Management Pack
The Routing and Remote Access Service Management Pack helps an network administrator monitor the status and availability of computers running Windows Server 2008 R2.[3]