Installing and removing RLP

Before installing RLP on your SCO system, be sure first to install TCP/IP. To install RLP:

Enter:

mkdev rlp

You now see the following display:

Remote printing configuration

Do you want to install or delete remote printing (i/d/q)?

You have three options:

To install or reinstall RLP, enter i. Skip to the next step.
To remove RLP after it has been installed, enter d. Once RLP has been removed, your local printing environment is restored and you are returned to the shell prompt.
To quit and return to the shell prompt, enter q.

You now see the following messages:

Installing Remote Line Printing

Creating directories /usr/lpd/remote and /usr/spool/lpd and file /etc/printcap Saving lp, cancel, lpmove and lpstat commands to /usr/lpd/local Installing remote lp, cancel, lpmove and lpstat commands Do you wish to change the remote printer description file /etc/printcap (y/n)?

To define printers available through RLP, enter y. The rlpconf command is then executed. See ``Setting up a client'' and ``Setting up a print server'' later in this chapter for information on rlpconf.

To wait until later to define printers, enter n. You then see the message:

   Run /etc/rlpconf to change the remote printer description file

Remember to run rlpconf at some point before using RLP. Otherwise, you will have no entries in the /etc/printcap file.

If the directories that RLP needs to do the installation already exist, you see the following message:

Remote line printing working directory already exists.

Do you wish to continue installing the remote line printing system (y/n)?

Enter y to continue the installation. Enter n to stop and return to the shell prompt.

You are now asked the following question:

   Do you want to start remote daemon now (y/n)?

To start the lpd(ADMN) daemon, enter y. This daemon must be running for RLP to work. To wait until later to start the daemon, enter n.

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

Installing and removing RLP

Windows Server 2008 editions and NPS

Upgrade from Windows Server 2003

NPS as a role service

NPS server administration