remote print server

2007-12-25 9:27:00

Thanks to Viet Hoang (vhoang@lucent.com), who reminded

me that I needed to put the new host in the print

server's /etc/hosts.lpd file.

 - Christopher

======================

On Thu, 6 Feb 1997, Christopher M. Chin wrote:

> Date: Thu, 6 Feb 1997 16:40:44 -0800 (PST)

> From: "Christopher M. Chin" <chris@Advent.COM>

> To: Sun Managers Mailing List <sun-managers@ra.mcs.anl.gov>

> Subject: remote print server

>

> Hi fellow sun managers,

>

> Maybe it's the flu I'm just getting over, but I can't

> seem to figure out what I'm missing here.

>

> I have several Solaris machines printing to a SunOS

> 4.1.3 print server, and things work well. I'm adding a

> new Solaris (2.5.1) machine, and can't seem to get

> printing going.

>

> I get the following message (via e-mail) when trying

> to send print jobs to the default printer:

>

> ----------------------

>

> Date: Thu, 6 Feb 1997 16:20:07 -0800

> From: Line Printer Admin <lp@Advent.COM>

> Subject: Status of lp request HP-5

>

> Your request HP-5 destined for HP

>

> The job title was: 5-1

> submitted from: gondor

> at: Thu Feb 6 16:20:07 1997

>

> was canceled by the lpsched daemon.

>

> Reason for failure:

>

> Remote status=5, canceled by remote system

>

>

>

> Reason for being canceled:

>

> Error talking to printer or print server, possibly down

>

> ----------------------

>

> The configuration (via admintool) is identical to that

> of a machine that prints to this server successfully.

>

> I've verified that .rhosts and host file info is

> accurate, and I've also restarted lpsched on the client

> and lpd on the server. No luck. What am I missing?

>

> Thanks,

> - Christopher

>

> ==========================================================================

> Christopher M. Chin (415) 543-7696 (voice)

> Senior Network Administrator (415) 896-1327 (fax)

> Advent Software, Inc.

> 301 Brannan Street chris@Advent.COM

> San Francisco, CA 94107-1849

> ==========================================================================

>

>

>

Comments

Got something to say?

You must be logged in to post a comment.