Windows 2000 Routing: AppleTalk and IPX/SPX

Microsoft Windows 2000 Server incorporates native multi-protocol routing through its integrated Routing and Remote Access Service (RRAS). While the operating system was engineered during the industry's broad migration toward pure TCP/IP, it maintained comprehensive backward compatibility for enterprise networks still relying on legacy architectures. This article explores how Windows 2000 processes, routes, and manages network traffic across both Novell IPX/SPX and AppleTalk environments using built-in software routers.

The Routing and Remote Access Service (RRAS)

In Windows 2000, multi-protocol routing is centralized within RRAS, an administrative framework accessed via the Microsoft Management Console (MMC). RRAS allows a multi-homed Windows 2000 Server—a machine equipped with two or more network interface cards (NICs)—to function as a software router. Instead of treating network traffic uniformly, RRAS maintains independent routing tables, forwarding engines, and management rules for each supported protocol stack: IPv4, IPX/SPX, and AppleTalk.

IPX/SPX Routing in Windows 2000

Windows 2000 routes Internetwork Packet Exchange/Sequenced Packet Exchange (IPX/SPX) traffic using the NWLink protocol stack. The architecture relies on three primary components:

  • Routing Information Protocol (RIP) for IPX: RRAS implements RIP over IPX to exchange network reachability and hop-count metrics with other Novell NetWare servers and IPX routers. It supports both static route configuration and dynamic updates via periodic RIP broadcasts.
  • Service Advertising Protocol (SAP): To allow clients to locate servers, printers, and network services without manual configuration, the Windows 2000 IPX router manages SAP tables. RRAS listens for SAP broadcasts, builds a local service directory, and relays these advertisements across different network segments.
  • NetBIOS over IPX: For legacy Windows clients communicating across IPX segments, RRAS provides NetBIOS over IPX routing (Type 20 packet forwarding) to facilitate computer name resolution and browsing.

Administrators configure specific frame types (such as Ethernet 802.2, 802.3, Ethernet II, or SNAP) and assign unique IPX internal network numbers to prevent routing collisions between attached segments.

AppleTalk Routing in Windows 2000

Routing for Macintosh clients is provided through the AppleTalk routing module within RRAS, which works in conjunction with Services for Macintosh (SFM).

Windows 2000 handles AppleTalk routing through distinct operational roles:

  • Seed vs. Non-Seed Routing: A Windows 2000 Server can act as an AppleTalk "seed router," which actively defines the network range (a range of network numbers) and the available AppleTalk Zones for a physical network segment. Alternatively, it can act as a "non-seed router," where it discovers network ranges and zone information from an existing seed router during startup.
  • Routing Table Maintenance Protocol (RTMP): Windows 2000 uses RTMP to dynamically learn network topology, calculate shortest paths based on hops, and maintain an AppleTalk routing table.
  • Zone Information Protocol (ZIP) and Name Binding Protocol (NBP): When Macintosh clients request services across network boundaries, the Windows 2000 AppleTalk router queries and responds using ZIP to map networks to zones, while passing NBP packets across interfaces to enable device lookup.

Multi-Protocol Traffic Forwarding

When forwarding data across heterogeneous networks, the Windows 2000 kernel inspects the Layer 3 protocol header of incoming frames. Traffic designated for IPX is passed directly to the NWLink forwarding engine, while AppleTalk datagrams (DDP packets) are handed to the AppleTalk stack. Each protocol is processed concurrently without interference:

  1. Frame Demultiplexing: The network adapter driver identifies the frame type and passes the payload to the corresponding protocol stack.
  2. Routing Table Lookup: The protocol engine checks its independent routing table (IPX routing table or AppleTalk RTMP table) to determine the next-hop interface.
  3. Encapsulation and Transmission: The packet is re-encapsulated into the appropriate Layer 2 frame format of the destination network interface and transmitted.

By handling routing at the operating system level, Windows 2000 Server eliminated the need for dedicated third-party hardware routers in mixed environments containing NetWare file servers, Apple Macintosh workstations, and PC networks.