Testing dedicated link connectivity

Verify host-to-host connectivity on the link as follows:

Turn on the PPP driver and PPP daemon logging. See ``Logging PPP information''.

Execute the following command:

ping remote_host_IP_address

ping

ping send: Network is unreachable

Configuring Network Connections

If ping hangs with no response, make sure that the IP address used on the command line is correct. It should be the value assigned to the machine connected to the other end of the dedicated serial line. If the IP address appears to be correct, look in the logfile where the PPP driver and PPP daemon log information has been collected. By default, this file is /usr/adm/syslog. The following example logfile and the description below the example show the steps PPP uses to achieve host-to-host connectivity. You can view the logfile to see if these steps have been successful.

1 Mar 14 09:31:54 127.0.0.1 pppd[318]: ppp_add_inf: 132.147.118.6 --> 132.147.118.9 2 Mar 14 09:31:58 127.0.0.1 pppd[318]: Set static PPP on tty4d 3 Mar 14 09:31:58 127.0.0.1 pppd[318]: ppp_add_conn 4 Mar 14 09:31:59 127.0.0.1 pppd[318]: Assigned link id for dedicated link (132.147. 5 118.6->132.147.118.9) is 84

line 1

the PPP daemon (shown as ``pppd'' in the logfile) builds the PPP network interface for the link

line 2

the PPP daemon links the tty specified in the PPP endpoint configuration under the PPP driver

line 4,5

the PPP daemon assigns a link ID (84) to the dedicated link

/usr/adm/syslog

If ping is successful when using the IP address of the remote host, you may wish to test whether one can reach the remote host using the host names by which it should be reachable. See ``Using ping to test reachability using host names'' for the command, possible error message, and resolutions.

NPS Fast Facts

Updated: February 18, 2009

Applies To: Windows Server 2008

In Windows Server� 2008, Network Policy Server (NPS) replaces Internet Authentication Service (IAS).

NPS is:

The Microsoft implementation of the Remote Authentication Dial-In User Service (RADIUS) protocol.
Configurable as a RADIUS server.
Configurable as a RADIUS proxy that forwards connection requests to other RADIUS servers for processing.
A required component of Network Access Protection (NAP). When you deploy NAP, NPS functions as a NAP health policy server.
Configurable to perform all three functions (RADIUS server, RADIUS proxy, NAP health policy server) at the same time.
Compatible with user account databases in Active Directory Domain Services (AD DS).

Windows Server 2008 editions and NPS

NPS provides different functionality depending on the edition of Windows Server 2008 that you install:

Windows Server 2008 Enterprise and Windows Server 2008 Datacenter. These server editions include NPS. With NPS in Windows Server 2008 Enterprise and Windows Server 2008 Datacenter, you can configure an unlimited number of RADIUS clients and remote RADIUS server groups. In addition, you can configure a group of RADIUS clients by specifying an IP address range.
Windows Server 2008 Standard. This server edition includes NPS. With NPS in Windows Server 2008 Standard, you can configure a maximum of 50 RADIUS clients and a maximum of two remote RADIUS server groups. You can define a RADIUS client by using a fully qualified domain name or an IP address, but you cannot define groups of RADIUS clients by specifying an IP address range. If the fully qualified domain name of a RADIUS client resolves to multiple IP addresses, the NPS server uses the first IP address returned in the Domain Name System (DNS) query.
Windows Web Server 2008. This server edition does not include NPS.

For more information, see Windows Server 2008 Overview of Editions at http://go.microsoft.com/fwlink/?LinkId=111845.

Upgrade from Windows Server 2003

You can upgrade a server running Windows Server 2003 and IAS to Windows Server 2008 and NPS. During the upgrade process, the server configuration is preserved, including the RADIUS client, connection request policy, accounting, and remote access policy configurations. In NPS, however, remote access policies are renamed to network policies.

MCITP Boot camp USA : MCITP CCNA Boot camp UK, MCITP MCSE CCNA Boot camp Asia, MCITP CCNA MCSE Bootcamp, MCITP MCSE RHCE Training

In addition, you can export the configuration of an IAS server in Windows Server 2003, and then import the configuration to an NPS server in Windows Server 2008 by following the instructions in the following article:

NPS servers in Windows Server 2008 systems cannot import configuration settings that were exported from IAS servers in Windows Server 2003 systems

NPS as a role service

NPS is a role service of the Network Policy and Access Services (NPAS) server role. Other role services of NPAS are the Routing and Remote Access service, Health Registration Authority (HRA), and Host Credential Authorization Protocol (HCAP). For information about how to install NPS, see the NPS Operations Guide.

NPS server administration

After you install NPS, you can administer NPS servers:

Locally, by using the NPS Microsoft Management Console (MMC) snap-in, the static NPS console in Administrative Tools, or the network shell (Netsh) commands for NPS.
From a remote NPS server, by using the NPS MMC snap-in, the Netsh commands for NPS, or Remote Desktop Connection.
From a remote workstation, by using Remote Desktop Connection.

Our Microsoft Boot Camp Training Exclusives

Testing dedicated link connectivity

Windows Server 2008 editions and NPS

Upgrade from Windows Server 2003

NPS as a role service

NPS server administration