Setting up a client

The printer description file /etc/printcap on the client machine provides routing and other information about printers.

NOTE:

``Setting up a print server''

/etc/hosts.equiv

/etc/hosts.lpd

For a full description of the /etc/printcap file format, see the printcap(SFF) manual page.

Here is an example of an entry in the /etc/printcap file, followed by an explanation of each field. Note that fields are separated by colons.

laser::lp=:rm=ohio:rp=sunlaser:sd=/usr/spool/lpd/laser

The first field, laser, is the name by which the client knows the printer. For a remote printer, the name that the client uses need not be the same as that used by the print server. In this example, laser is an alias for the printer named sunlaser on ohio.

The second field (before the first colon on the second line) is empty by default. When used, it defines the name of the error log file.

The third field, starting with lp=, must be empty (that is, followed immediately by a colon) for remote printing. This field specifies the device name for a local printer.

The fourth field, starting with rm=, specifies the network name of the print server. In this example, the print server is called ohio.

The fifth field, starting with rp=, specifies the name that the print server uses for the printer.

The last field, starting with sd=, is the name of the spooling directory on the client. It is in this directory that print jobs are stored before being sent over the network to the print server. This directory is always located in /usr/spool/lpd and bears the name of the printer. In this example, the spool directory is called /usr/spool/lpd/laser.

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

Setting up a client

Windows Server 2008 editions and NPS

Upgrade from Windows Server 2003

NPS as a role service

NPS server administration