Routing and Remote Access Service

Previous Topic Next Topic

Features of the Routing and Remote Access Service

The Routing and Remote Access service for Windows 2000 includes a wide variety of features for unicast and multicast IP routing, IPX routing, AppleTalk routing, remote access, and VPN support.

Unicast IP Support

Unicast IP support consists of the following:

For more information, see "Unicast IP Support" in this book.

IP Multicast Support

IP multicast support consists of the following:

For more information, see "IP Multicast Support" in this book.

IPX Support

IPX support consists of the following:

For more information, see "IPX Routing" in this book.

AppleTalk

AppleTalk consists of supporting the forwarding of AppleTalk packets as an AppleTalk router and the use of the Routing Table Maintenance Protocol (RTMP). For more information about AppleTalk routing, see "Services for Macintosh" in this book.

Demand-Dial Routing

IP and IPX traffic can be forwarded over demand-dial interfaces over persistent or over on-demand WAN links. For on-demand connections, the Routing and Remote Access service automatically creates a PPP-based connection to the configured endpoint when traffic matching a static route is received.

For more information, see "Demand-Dial Routing" in this book.

Remote Access

The Routing and Remote Access service enables a computer to be a remote access server, accepting remote access connections from remote access clients using traditional dial-up technologies such as analog phone lines and ISDN.

For more information, see "Remote Access Server" in this book.

VPN Server

The Routing and Remote Access service enables a computer to be a virtual private network (VPN) server, supporting both PPTP and L2TP over IPSec and accepting both remote access and router-to-router (demand-dial) VPN connections from remote access clients and calling routers.

For more information, see "Virtual Private Networking" in this book.

RADIUS Client

The Routing and Remote Access service can be configured as a Remote Authentication Dial-In User Service (RADIUS) client for authentication, authorization, and accounting. Parameters of all PPP-based connection attempts are sent to the configured RADIUS server for authentication and authorization. Information about connections is sent to the configured RADIUS server for accounting.

Windows 2000 also includes the Internet Authentication Service (IAS), an implementation of a RADIUS server. For more information, see "Internet Authentication Service" in this book.

SNMP MIB Support

Windows 2000 and the Routing and Remote Access service provide Simple Network Management Protocol (SNMP) version 1 agent functionality with support for Internet MIB II as documented in RFC 1213. SNMP management stations can be used to manage a Windows 2000 remote access router. Beyond Internet MIB II support, the Routing and Remote Access service also provides MIB dynamic-link libraries (DLLs) for the following:

Extensive LAN and WAN Support

The Routing and Remote Access service can run over any of the network adapters supported by Windows 2000 Server, including WAN cards from Eicon, Cisco, SysKonnect, Allied and US Robotics. For more information about supported network adapters, see the Windows 2000 Hardware Compatibility link at http://windows.microsoft.com/windows2000/reskit/webresources.

Graphical and Command-Line Management Utilities

The Routing and Remote Access service includes the Routing and Remote Access snap-in, a Windows 2000 administrative utility that provides easy viewing and configuration of local or remote Windows 2000 remote access routers, and Netsh.exe, a command-line utility that can also run scripts for local automated configuration. For more information, see "Routing and Remote Access Service Tools and Facilities" later in this chapter.

API Support for Third-Party Components

The Routing and Remote Access service has fully published API sets for unicast and multicast routing protocol and administration utility support. Routing protocol developers can write additional routing protocols and interface directly into the Routing and Remote Access service architecture. Other software vendors can also use Routing and Remote Access service administration APIs to provide their own management utilities.

© 1985-2000 Microsoft Corporation. All rights reserved.