Displaying the routing information table (drouter)

All hosts that are capable of acting as NetWare routers maintain a routing information table. This allows the routers to forward packets by the best possible route. SCO IPX/SPX can be configured to act as a router , and thus all SCO IPX/SPX servers maintain a routing information table. For more information about the routing information table, see ``Packet delivery''. For more information about configuring an SCO system as a router, see NPSConfig(SFF) for more information.

In a NetWare network, routers periodically emit broadcasts containing their routing information tables, as specified by the NetWare RIP (Routing Information Protocol) standard.

The NetWare RIP Monitor and its command-line alternatives, drouter(PADM) and rrouter(PADM), display the current routing information tables and allow the superuser to reset and update the routing tables. Both of these features can be used to highlight potential problems in a network's configuration.

A useful feature of the NetWare RIP Monitor is automatic screen refresh which updates the routing information display at a regular, user-specified interval. The refresh interval can be controlled using a slider for the amount of time in minutes and seconds between refreshes. Automatic screen refresh can be set using the Set Auto Refresh cascade menu, which is available under the View menu.

If information about known nodes is missing from the routing information table, then there may be problems with the routing information broadcasts. See ``Router operation'' for procedures to remedy this situation.

The NetWare RIP Monitor's output looks like this:

The NetWare RIP Monitor displays the following:

Network

The IPX network number of the network segment or host.

Hops

The number of hops required to reach the routing destination.

Time

The time in ticks required to reach the network segment or host, as defined by RIP.

Node

IPX node number (MAC address) of the host, or the node number through which packets to the given network number (or host) are routed (6 octets)

This information reflects the knowledge that a given SCO server has gathered from its own configuration file as well as other nodes on the network. It presents a snapshot of the current operation of the internetwork.

Using this information, it is possible to detect the following situations:

One of the most common errors when adding a host to a network is choosing an internal network number or network number that is not unique. If you have a situation where a host is visible to only a portion of your network, it is likely that the network number(s) have been misconfigured. In this case, compare the output from the NetWare RIP Monitor on a number of different hosts on your network. You should be able to trace the same path to the new host from all the different hosts on your network. This is possible because the network and node number information in the routing information table will either be that of a router, the local host, a host on the network, or the network the host is connected to.

From the command line, a combination of rrouter and drouter can monitor the operation of routing information broadcasts: rrouter clears and updates the routing information table. A command-line user can periodically run drouter to monitor the status of the routing information table as it is updated by routing information broadcasts, updating the tables with rrouter if required.

Network Access Protection Design Guide

Updated: October 6, 2008

Applies To: Windows 7, Windows Server 2008, Windows Server 2008 R2, Windows Vista

Network Access Protection (NAP) is one of the most anticipated features of the Windows Server� 2008 operating system. NAP is a new platform that allows network administrators to define specific levels of network access based on a client�s identity, the groups to which the client belongs, and the degree to which the client complies with corporate governance policy. If a client is not compliant, NAP provides a mechanism for automatically bringing the client into compliance (a process known as remediation) and then dynamically increasing its level of network access. NAP is supported by Windows Server 2008 R2, Windows Server 2008, Windows 7, Windows Vista�, and Windows� XP with Service Pack 3 (SP3). NAP includes an application programming interface that developers and vendors can use to integrate their products and leverage this health state validation, access enforcement, and ongoing compliance evaluation. For more information about the NAP API, see Network Access Protection (http://go.microsoft.com/fwlink/?LinkId=128423).

The following are key NAP concepts:

NAP Agent. A service included with Windows Server 2008, Windows Vista, and Windows XP with SP3 that collects and manages health information for NAP client computers.
NAP client computer. A computer that has the NAP Agent service installed and running, and is providing its health status to NAP server computers.
NAP-capable computer. A computer that has the NAP Agent service installed and running and is capable of providing its health status to NAP server computers. NAP-capable computers include computers running Windows Server 2008, Windows Vista, and Windows XP with SP3.
Non-NAP-capable computer. A computer that cannot provide its health status to NAP server components. A computer that has NAP agent installed but not running is also considered non-NAP-capable.
Compliant computer. A computer that meets the NAP health requirements that you have defined for your network. Only NAP client computers can be compliant.
Noncompliant computer. A computer that does not meet the NAP health requirements that you have defined for your network. Only NAP client computers can be noncompliant.
Health status. Information about a NAP client computer that NAP uses to allow or restrict access to a network. Health is defined by a client computer's configuration state. Some common measurements of health include the operational status of Windows Firewall, the update status of antivirus signatures, and the installation status of security updates. A NAP client computer provides health status by sending a message called a statement of health (SoH).
NAP health policy server. A NAP health policy server is a computer running Windows Server 2008 with the Network Policy Server (NPS) role service installed and configured for NAP. The NAP health policy server uses NPS policies and settings to evaluate the health of NAP client computers when they request access to the network, or when their health state changes. Based on the results of this evaluation, the NAP health policy server instructs whether NAP client computers will be granted full or restricted access to the network.