Features of the Routing and Remote Access Service

  • Article

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:

  • Static IP routing With this inherent function of the TCP/IP protocol for Windows 2000, you can manage static routes using the Routing and Remote Access snap-in rather than the Route tool.

  • Routing Information Protocol (RIP) versions 1 and 2 A distance vector-based routing protocol commonly used in small and medium IP internetworks.

  • Open Shortest Path First (OSPF) A link state-based routing protocol commonly used in medium to large IP internetworks.

  • DHCP Relay Agent An agent that relays Dynamic Host Configuration Protocol (DHCP) messages between DHCP clients and DHCP servers on different network segments.

  • Network address translation A network address translator component that creates a translated connection between privately addressed networks and the Internet.

  • IP packet filtering The ability to define what traffic is allowed into and out of each interface based on filters defined by the values of source and destination IP addresses, TCP and UDP port numbers, ICMP types and codes, and IP protocol numbers.

  • ICMP router discovery The ability to periodically advertise and respond to host router solicitations to support ICMP router discovery by hosts on a network segment.

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

IP Multicast Support

IP multicast support consists of the following:

  • Multicast forwarding With this inherent function of the TCP/IP protocol for Windows 2000, you can view the multicast forwarding table using the Routing and Remote Access snap-in.

  • Internet Group Management Protocol (IGMP) versions 1 and 2 The TCP/IP protocol to track multicast group membership on attached network segments.

  • Ability to support limited multicast forwarding and routing When you use the IGMP routing protocol and configure interfaces for IGMP router mode and IGMP proxy mode, the Windows 2000 router can support multicast forwarding and routing for specific configurations.

  • Multicast boundaries Multicast boundaries (barriers to the forwarding of IP multicast traffic) can be based on the IP multicast group address, the Time-To-Live (TTL) in the IP header, or on the maximum amount of multicast traffic in kilobytes per second.

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

IPX Support

IPX support consists of the following:

  • IPX packet filtering The ability to define what traffic is allowed into and out of each interface based on filters defined by the values of source and destination IPX network, node, socket numbers, and packet type.

  • RIP for IPX A distance-vector-based routing protocol commonly used on IPX internetworks. The Routing and Remote Access service also provides the ability to configure static IPX routes and RIP route filters.

  • SAP for IPX Service Advertising Protocol (SAP) is a distance-vector-based advertising protocol commonly used on IPX internetworks to advertise services and their locations. The Routing and Remote Access service also provides the ability to configure static SAP services and SAP service filters.

  • NetBIOS over IPX NetBIOS over IPX is used by Microsoft networking components to support file and printer sharing components. The Routing and Remote Access service can also forward NetBIOS over IPX broadcasts and configure static NetBIOS names.

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:

  • IP Forwarding Table MIB Objects in the IP Forwarding Table MIB are documented in RFC 1354, "IP Forwarding Table MIB."

  • Microsoft RIP version 2 for Internet Protocol MIB

  • Wellfleet-Series7-MIB for OSPF

  • Microsoft BOOTP for Internet Protocol MIB

  • Microsoft IPX MIB

  • Microsoft RIP and SAP for IPX MIB

  • Internet Group Management Protocol MIB Objects in the Internet Group Management Protocol MIB are documented in the Internet draft titled "Internet Group Management Protocol MIB."

  • IP Multicast Routing MIB Objects in the IP Multicast Routing MIB are documented in the Internet draft titled "IP Multicast Routing MIB."

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 https://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.