Anonymous_User Absent Member.
Absent Member.
1116 views

Jobs Just Hanging..


We are running iPrint on a NetWare 6.5 server (SP4). NDPS Manager
v3.01n, NDPS Broker v3.0.1, and our users are running iPrint client
v4.05.

Currently I'd say 9/10 users who try to print something via iPrint will
get nothing. I'll check the queue in iManager and see that it is just
sitting there. What are ways to troubleshoot this so that my users can
print?

Thank you in advance.


--
goosed
0 Likes
5 Replies
Marcel_Cox Absent Member.
Absent Member.

Re: Jobs Just Hanging..

Goosed,

> We are running iPrint on a NetWare 6.5 server (SP4). NDPS Manager
> v3.01n, NDPS Broker v3.0.1, and our users are running iPrint client
> v4.05.


You might of course consider moving to a newer SP, like SP6 or SP7 for
instance. For SP6, some extra patches for iPrint would be needed
http://wiki.novell.com/index.php/Nw65sp6

> Currently I'd say 9/10 users who try to print something via iPrint will
> get nothing. I'll check the queue in iManager and see that it is just
> sitting there. What are ways to troubleshoot this so that my users can
> print?


Overall, this looks like a Manager or Gateway problem. What status does
the Manager report for the printers with the stuck jobs?


--
Marcel Cox
Discover the new Novell forums at http://forums.novell.com/

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Jobs Just Hanging..


Thanks for the reply Marcel.

I upgraded the server from SP 4.0a to 6.5 earlier this weekend. And
from there I applied the post SP6 patch for iPrint.

I noticed in NDPS Manager that a few of my printers were showing as
"Needs Attention". I was then getting this error in the logger screen
"BuildBanner() failed, code: FFFFFFF".

I followed TID: 3233501 which resolved the problem, I think. I'm unable
to test it completely as it's Sunday and we are closed.

What the TID had me do was change some settings in the Gateway
configuration. Here is what I had:

NDPSGW PORT=*LPR* HOSTADDRESS=10.10.1.59 PRINTERNAME=9100

and here's what it said to change it to:

NDPSGW PORT=*RAW* HOSTADDRESS=10.10.1.59 PRINTERNAME=9100

This made the error message go away, bu can this really make a
difference?


--
goosed
0 Likes
Marcel_Cox Absent Member.
Absent Member.

Re: Jobs Just Hanging..

goosed wrote:

>NDPSGW PORT=*LPR* HOSTADDRESS=10.10.1.59 PRINTERNAME=9100
>
>and here's what it said to change it to:
>
>NDPSGW PORT=*RAW* HOSTADDRESS=10.10.1.59 PRINTERNAME=9100
>
>This made the error message go away, bu can this really make a
>difference?


Yes. That's a big difference. You change the protocol you use to
communicate to the printer.
Your original gfateway load string doesn't look correct at all. I don't
know any single printer for which the official LPR name is "9100".
When switching to the "raw" protocol, the pritnername is no longer used
and so your probably invalid "PRINTERNAME=9100" parameter is completely
ignored.

If your "port=raw" setting works, just stick with it. Otherwise, use
"port=lpr" with the correct printer name for your type of printer. See the
following list for the correct lpr names to use for a number of printers:

http://www.novell.com/support/search.do?cmd=displayKC&docType=kc&sliceId=&externalId=10080373

--
Marcel Cox
Discover the new Novell forums at http://forums.novell.com
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Jobs Just Hanging..


That's funny that you mention that now. A lot of my users were having
difficulties printing via iPrint. When I logged in with my Domain Admin
account I was able to print. But whenever they would try, even as local
administrators, they were unable to. I'll test this out with a couple
of my users that I know were previously having difficulty in printing.


--
goosed
0 Likes
Marcel_Cox Absent Member.
Absent Member.

Re: Jobs Just Hanging..

goosed wrote:

>That's funny that you mention that now. A lot of my users were having
>difficulties printing via iPrint. When I logged in with my Domain Admin
>account I was able to print. But whenever they would try, even as local
>administrators, they were unable to. I'll test this out with a couple
>of my users that I know were previously having difficulty in printing.


That rather sounds like an iPritn client problem. When the settings for
the gateway are incorrect, it simply doesn't work whoever prints.
If printing works for some users and doesn't work for others, the problem
needs to be searched on the workstation side.

--
Marcel Cox
Discover the new Novell forums at http://forums.novell.com
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.