Setting Up Microsoft Windows LPD for Easy Printing on the Solaris OS

Matt Hatley, August 2006

This Tech Tip walks through the configuration and connection of a host using the Solaris OS to a Windows server running Windows LPD. Generally for the Solaris OS to print using the following techniques, the printers need to support PostScript, that is, the printer needs a built-in PostScript (PS) engine.

1. If you've got a network printer...

From your Solaris system, do this (assumes printer IP is 192.168.1.99):

# lpadmin -p hp3200m -s 192.168.1.99 -I any

Type the following to set the default printer (assuming the printer is hp3200m):

# lpadmin -d hp3200m

You need to be sure that print services are started (/usr/lib/lpsched or the equivalent command using Service Management Facility [SMF] in the Solaris 10 OS).

2. If you don't have a network printer...

Windows 2000, Windows XP, and Windows Server 2003 support an optional LPD print server. This enables the Solaris OS to use its normal lp capability with Windows running LPD and should cause minimal impact to an existing enterprise. Here's how to do it:

Locate the Windows system that is serving as the print server or that has a direct connected printer.

Assume, for this example, a Windows server at 192.168.1.99 and printer hp3200m.

Here's how to install and start LPD on a Windows XP or Windows Server 2003 host:

• Select Start->Control Panel->Add or Remove Programs. (Add or Remove Programs dialog box pops up.)
• Click Add or Remove Windows Components. (Windows Components Wizard pops up.)
• Select Other Network File and Print Services. (Other Network File and Print Services box pops up.)
• Select Print Services For Unix and Click OK. Follow the prompts that ask for the Win2003 CD.

This installs LPD on Windows. Next you need to start the service and ensure that it starts at boot:

• Menu: Select Start->Programs->Administrative Tools->Services. (Services dialog pops up.)
• Scroll down and double click on TCP/IP Print Server Properties. (Dialog box pops up.)
• Set Startup type: Automatic.
• Click Start button.
• Click OK.
• Close Services Dialog.

Repeat step 1 on each Solaris host to access the new printer hp3200m.

3. Verify the install of Windows LPD...

I run Windows LPD at home, and it works perfectly. When you've successfully installed and started Windows LPD, on a Solaris system you should see output like the following. Note: This is from a Solaris system at home connecting to a Windows XP system (grouper @ 192.168.1.99) and printer hp3200m (which supports PS):

sharkscove{10} lpstat -t
scheduler is not running
system default destination: hp3200m
system for hp3200m: 192.168.1.99
system for _default: 192.168.1.99 (as printer hp3200m)
hp3200m accepting requests since Apr 15 12:07 2006
_default accepting requests since Apr 15 12:07 2006
printer hp3200m unknown state. enabled since Apr 15 12:07 2006. available.

                        Windows XP LPD Server
                              Printer \\192.168.1.99\hp3200m

Owner       Status         Jobname          Job-Id    Size   Pages  Priority
----------------------------------------------------------------------------
printer _default unknown state. enabled since Apr 15 12:07 2006. available.
sharkscove{11}

4. If lpstat -t hangs and/or fails to connect...

• Select Start->Control Panel->Security Center.
• Click Manage Security Settings for Windows Firewall.
• Click the Exceptions tab.
• Ensure LPD is selected and click the OK button.

This tells the firewall not to block LPD IP traffic.

Unless otherwise licensed, code in all technical manuals herein (including articles, FAQs, samples) is provided under this License.