Thanks to all who responded. After going as far as removing the
lp subsystems and reinstalling the packages, the culprit turned out
to be an incorrect digit in a few reverse DNS entries. I examined
the file more than once previously but missed the errors. Funny how
the eyes play tricks on you.
Thanks again.
The original problem:
> >I'm perplexed by the following printing problem. Here is the
senario:
> >
> >A few 2.5.1 clients are set to send all print jobs to f3W_svr, an
> >HPUX print server running HPJetDirect. When the two were on the
same
> >subnet, printing worked fine. The client was recently moved to
> >another subnet and now every time a job is queued, I get the
following
> >error:
> >
> ># lpstat -p
> >printer floor3_W faulted. enabled since Fri Apr 24 13:56:02 PDT
1998.
> >available.
> > system not responding
> >
> >/var/spool/lp/logs/LPNet reports the following:
> >
> >04/28 10:52:52 c 7761 f3W_svr floor3_W: lost connnection
> >04/28 10:53:02 p 188 <none> Started child for f3W_svr, pid = 7762
> >04/28 10:53:03 c 7762 f3W_svr floor3_W: lost connnection
> >04/28 10:53:12 p 188 <none> Started child for f3W_svr, pid = 7765
> >04/28 10:53:12 c 7765 f3W_svr floor3_W: lost connnection
> >04/28 10:53:14 p 188 <none> Started child for f3W_svr, pid = 7767
> >
> >I can print from other clients on both subnets, so I know the
problem
> >isn't the HP print server. The only thing I can think of is that
> >the print request is timing out some how. The clients that don't
> >print, are connected to a remote wiring closet so I thought the
cause
> >might be a connectivity problem, but the only thing that has
changed
> >is the subnet.
---- Jeff Newton Unix Systems Administrator PMC-Sierra Inc.
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:12:39 CDT