Anonymous_User Absent Member.
Absent Member.
1531 views

iPrint Driver issues

Nw6.5 SP3. Trying to get drivers uploaded to iPrint/NDPS.

So what do you do when iManager just errors on you?

I failed the cluster resource to a second node today, and I was able to
assign an XP and Mac/Linux driver to one printer. Then after that, all
I get is NDPS Library Errors: 7000001h when I go to the broker, and now
when I go to a printer, I get told there are no available drivers in the
list even though I know I succeeded in uploading XP and Mac drivers.

So looks like communication between iManager and Broker is an issue.
How does one troubleshoot this one? I have restarted the RMS and that
does not seem to help.


0 Likes
2 Replies
Anonymous_User Absent Member.
Absent Member.

Re: iPrint Driver issues

Okay,

I assume you have looked at doc:
http://www.novell.com/products/netware/printing/iprintcluster.pdf
that talks about cluster services and printing...

The NDPS Library error is indicative of communication problems. You can
look in the directory, sys:\ndps\resdir\english\prndrv on the server that is
hosting the broker/RMS. This is the directory structure containing the
"repository" of drivers for the various platforms...

Also, the directory sys:\ndps\xfer is a temporary transfer directory ( if
uploading using the old method in iManager). Starting with NW 6.5 sp3,
there is a new method of uploading.

The old method employed HTTPSTK (Novells own HTTP web server) as the web
server to transfer the driver file to the sys:\ndps\xfer temporary
directory. From here, a request was made to the RMS to process this driver
file from the temporary location and incorporate it into its normal
repository directories..

The new method employs APACHE2 to talk directly to the RMS and have it
upload directly to the repository directories.

Based on the errors you are getting, I suspect that the new APACHE2 method
is failing, because even after the fact, trying to access a printer you are
told there are no available drivers. SO, using the following document(s)
you can begin to trouble shoot the problem..
SEE:
http://www.novell.com/products/netware/printing/debug_display.pdf This
document outlines debug switches you can set to see communications with the
NDPS Manager. Look at the +CHECK_SERVICES switch to see if the NDPS Manager
is even talking to a RMS...

You can also look at:
http://www.novell.com/products/netware/printing/ipp_server_debug.pdf to
see about the driver upload. Use +DRIVER with this..

You might also look at the different nodes in the cluster, as well as the
server (if different from the others) that is running iManager. Check the
following modules to make sure that they are the same. JNDPS.NLM,
DPLSV386.NLM, DPRPCNLM.NLM, RMANSRVR.NLM, and naturally, the Winsock
Modules WS2_32, WSPIP, WSPSSL, etc...

It really sounds like a configuration module problem. You have to remember,
if running iManager from another server, it is possible that modules are out
of sync with each other...


>>> On 8/15/2005 at 8:25:38 am, in message

<CB1Me.5697$RK5.1359@prv-forum2.provo.novell.com>, Geoffrey
Carman<geoffc@yorku.ca> wrote:
> Nw6.5 SP3. Trying to get drivers uploaded to iPrint/NDPS.
>
> So what do you do when iManager just errors on you?
>
> I failed the cluster resource to a second node today, and I was able to
> assign an XP and Mac/Linux driver to one printer. Then after that, all
> I get is NDPS Library Errors: 7000001h when I go to the broker, and now
> when I go to a printer, I get told there are no available drivers in the
>
> list even though I know I succeeded in uploading XP and Mac drivers.
>
> So looks like communication between iManager and Broker is an issue.
> How does one troubleshoot this one? I have restarted the RMS and that
>
> does not seem to help.
>
>

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: iPrint Driver issues

Bunch of questions in here. Lots of gold in your message! Thanks
tons!!! I wish other Novell products were as well debuggable as
iPrint/NDPS is!!!


iprint wrote:
> Okay,
>
> I assume you have looked at doc:
> http://www.novell.com/products/netware/printing/iprintcluster.pdf
> that talks about cluster services and printing...


I have now. Thanks! These docs are great! They are somewhat out of
date... (No new references to NW6.5 or OES, some commands syntax are
minorly different (I.e. /ENS or /RMS is now /SETENS and /SETRMS))

Couple of good points in there.
1) RO files. I had some in my ndps\resdir structure, fixed that. Don't
think that was it, but good point.

This raises the issue of what rights (File system) does the
broker/manager need to the ndps/resdir structures? Are they implicit or
explicit? I.e. Should I grant them, if they are missing?

2) /SETRMS was a good one! I was wondering how to force it to use a
specific Broker for info.

3) NSS /transaction=volumename. Do we still need that in NW6.5? Or at
all?

> The NDPS Library error is indicative of communication problems. You can
> look in the directory, sys:\ndps\resdir\english\prndrv on the server that is
> hosting the broker/RMS. This is the directory structure containing the
> "repository" of drivers for the various platforms...


i have been looking. Interesting structure. I used this and the info
from a past email to update a PPD file (just a single file inside the
ZIP file) because the one I chose was a bad choice. And I deleted the
TOC file, stopped and then restarted the RMS service. Interesting!

> Also, the directory sys:\ndps\xfer is a temporary transfer directory ( if
> uploading using the old method in iManager). Starting with NW 6.5 sp3,
> there is a new method of uploading.


I noticed the /XFER dir, I see on the logger screen a reference to it
each time I try to upload. (NW65 sp3!). Interestingly, or annoyingly,
it has [Public] granted RWECMF to that dir. Bad security guys! Our
students go trolling for file space that they have rights too! Can't
really quota it, since i need to add files!

4) Can we change it so the Broker or Manager has full rights, instead of
[Public]?

> The old method employed HTTPSTK (Novells own HTTP web server) as the web
> server to transfer the driver file to the sys:\ndps\xfer temporary
> directory. From here, a request was made to the RMS to process this driver
> file from the temporary location and incorporate it into its normal
> repository directories..


I get the first part done, the second seems to be the failing part.

Also, if iManager is showing for Manage Broker, only the Windows driver
options, how do I get it to add the Linux/Mac option? I have tried
installing the 1.6, 1.8, and 1.9 iprint NPM files, with no luck.

I am now cross tree authing from a NW65SP3 server with the 1.8 snapin.
But now the REALM on the iPrint client is goofed, since it has the
tree name wrong for some reason. (Y-NOT is the tree, Realm is Y-NOT-TMP
which has never been the tree name, as far as I know!). SLP sees the
tree as Y-NOT.

5) This is a real issue, as I see it, from the iPrint client! How do I
switch the Realm? I can see two simple models. a) Make the field
editable! 🙂 I.e. Let me change the realm, when it is wrong. Right
now it is NOT! b) Add an Authenticate button on the Passwords page of
the iprint client settings that lets me specify the tree name. Heck
make it require an ip address of a eDir replica, or LDAP server that is
running IPPSRVR and Apache2. That is fine with me! Then I can auth to
any tree I want, whenever I want.

Right now, if I try to cross tree auth, and in my world, I work in 3 or
more trees every day, it causes real pain and suffering!


> The new method employs APACHE2 to talk directly to the RMS and have it
> upload directly to the repository directories.
>
> Based on the errors you are getting, I suspect that the new APACHE2 method
> is failing, because even after the fact, trying to access a printer you are
> told there are no available drivers. SO, using the following document(s)
> you can begin to trouble shoot the problem..
> SEE:
> http://www.novell.com/products/netware/printing/debug_display.pdf This
> document outlines debug switches you can set to see communications with the
> NDPS Manager. Look at the +CHECK_SERVICES switch to see if the NDPS Manager
> is even talking to a RMS...
>
> You can also look at:
> http://www.novell.com/products/netware/printing/ipp_server_debug.pdf to
> see about the driver upload. Use +DRIVER with this..


Another up date to this is syntax is that there does not seem to be a
+DRIVER option. 🙂 My ippsrvr.nlm is 4.00.04 (4.0d) Jan 25/05.

Watching with +CLIENT I see....

But


GetInstallFiles End, Time used: 0:00:00.0001 Apache_Worker 1
Error: successful-ok-ignored-or-substituted-attributes
GetPrtAttrs Start 8-15-05 3:24:06 pm Apache_Worker 2
Printer: pa-cns-pmo-colour
GetPrtAttrs End, Time used: 0:00:24.8853 Apache_Worker 2
GetPrtAttrs Start 8-15-05 3:24:32 pm Apache_Worker 2
Printer: pa-cns-pmo-colour
GetPrtAttrs End, Time used: 0:00:00.0002 Apache_Worker 2
Error: client-error-not-authorized
GetPrtAttrs Start 8-15-05 3:25:00 pm Apache_Worker 2
Printer: pa-cns-pmo-colour
GetPrtAttrs End, Time used: 0:00:00.0003 Apache_Worker 2
Error: client-error-not-authorized
GetPrtAttrs Start 8-15-05 3:25:16 pm Apache_Worker 22
Printer: pa-cns-pmo-colour
GetPrtAttrs End, Time used: 0:00:00.0003 Apache_Worker 22
Error: client-error-not-authorized
GetPrtAttrs Start 8-15-05 3:25:20 pm Apache_Worker 7
Printer: pa-cns-pmo-colour
GetPrtAttrs End, Time used: 0:00:00.0003 Apache_Worker 7
PrintJob Start 8-15-05 3:25:26 pm Apache_Worker 7
Printer: pa-cns-pmo-colour

I keep getting asked to authorize... But in this case, I am using the
iPrint plugin from NW6.5 SP4 beta, and it is a high security/SSL
configured iPrint IPP printer. Against a production non-SP4 server.
Let me test against an SP4 beta server and see if that works!

Except that SSL seems broken on this server. More work to do!

> You might also look at the different nodes in the cluster, as well as the
> server (if different from the others) that is running iManager. Check the
> following modules to make sure that they are the same. JNDPS.NLM,
> DPLSV386.NLM, DPRPCNLM.NLM, RMANSRVR.NLM, and naturally, the Winsock
> Modules WS2_32, WSPIP, WSPSSL, etc...
>
> It really sounds like a configuration module problem. You have to remember,
> if running iManager from another server, it is possible that modules are out
> of sync with each other...


So what needs to be in sync? Each module on each server involved?
iManager server, Broker server, NDPS Manager server? (That starts to
get a bit unwieldly! I checked, and for the one with the broker
disappearing, it appears to be the same on both!
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.