Remote printing trouble on Solaris 2.4

2007-12-25 9:01:00

>Gene Loriot (epl@kodak.com) writes:

>Sun suggest total analiation... here is a script that I built from sun's suggest

>ions. When you are thrown into vi, delete all but the line that that is

>repeated in the comment section that says *don't* delete this line....and

>rebuild the printers. Has worked in every case I can think of.

>

I tried this solution, to no avail, the printers were still faulting

>Michael Ramchand Owner (mpr@relay.fj-icl.com) writes:

>Sun is effectively EOLing the s5 printing model. If you define the remote printer as a bsd host it will work.

>

>i.e. Just do

>

>lpsystem -t bsd <host>

>

>then lpshut, and /usr/lib/lpsched the spooler on both machines, printing should

>then work properly.

I tried this and struck magic, once the print server was defined as bsd and the

print services restarted on both hosts, everything worked fine.

 

Original message:

>After upgrading our machines to Solaris 2.4 the remote printing

>from a 2.4 machine to a 2.4 machine stopped working. The printer

>status returns faulted, system not responding. Printing to bsd

>based remote printers works fine and printing to the local printer

>works fine as well.

>

>I've checked the status of lpNet and lpsched on both machines

>and it makes it look like it should be a listener problem, but

>after checking the listeners via pmadm -l, it looks like they're

>fine too.

>

>Just to check, I've even rebuilt the printers on both the remote

>and local system. It didn't change a thing.

>

>I have applied the lp jumbo patch, 101959-03, on both systems.

>

>Any suggestions or pointers would be highly appreciated.

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

| Michael Baker | Internet: michael.baker@cp.tybrin.com |

| Systems Engineer | Phone : 904.664.6144 |

| Tybrin Corporation | Fax : 904.664.6377 |

| Commercial Division | |

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

Comments

Got something to say?

You must be logged in to post a comment.