Monitoring current NVT connections (dnvt)

SCO IPX/SPX hosts act as NVT servers on the network; any client on the network that is capable of running the NVT protocol can connect to these servers. The NetWare NVT Monitor and its command-line equivalent, dnvt(PADM), are useful in determining which machines on the network are connected to a given NVT server. dnvt also displays information about each connection, can be used to determine the amount of activity performed by the user of the connection or to highlight any potential network connectivity problems.

A useful feature of the NetWare NVT Monitor is automatic screen refresh which updates the NVT connection 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.

The NetWare NVT Monitor's output looks like this:

The NetWare NVT Monitor displays the following:

Client Name / Address

If the client is a DOS client, a NetWare address will be displayed. If the connection is from a client that also advertises services on the network (such as another SCO host running IPX/SPX), the host name is displayed.

Sequence#

The current packet sequence number in use for the connection.

Retries

The current packet retry count. In normal situations, the retry count should always be zero. However, if there is traffic congestion or the server or client are slow, it is possible to see a non-zero retry count.

KeepAlives

The current number of keep alive packets sent to the client. Keep alive packets are sent when the server thinks the client is no longer on the network or when the connection is inactive.

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.