Anonymous_User Absent Member.
Absent Member.
1912 views

NDPS Print Servicing Queues

I am starting to move all our old print queues over to NDPS. I have set
the NDPS printer up to service the old queue through Jobs -> spooling in
NWAdmin, but the jobs don't seem to be going through the NDPS printer.
What am I missing ? When someone prints to the old queue it does not
increment the number of jobs processed, it is only incremented when a job
is submitted through the NDPS printer, so it is working, but not
processing the jobs from the queue if that makes any sense.
0 Likes
9 Replies
Anonymous_User Absent Member.
Absent Member.

NDPS Print Servicing Queues

> I am starting to move all our old print queues over to NDPS. I have set
> the NDPS printer up to service the old queue through Jobs -> spooling in
> NWAdmin, but the jobs don't seem to be going through the NDPS printer.
> What am I missing ? When someone prints to the old queue it does not
> increment the number of jobs processed, it is only incremented when a

job
> is submitted through the NDPS printer, so it is working, but not
> processing the jobs from the queue if that makes any sense.


Just an update. I think I have it working, but I am not sure if it is
setup correctly. I created the printers with NWADMIN, and when it asked
for the port handler type, the only one available was the Novell Port
Handler, so I chose that one (although according to the help, it doesn't
sound like that is what I want). So on the server in the print manager, I
changed the port handler to Queue based printer and the queue jobs now
appearing to be going the NDPS printer. The printer is an HP 5si
connected to our network through a jetdirect card. What type of port
handler should I be using? Eventually we want to delete the print queues
out of the tree when everything is migrated over. Should I be using
iManager or another program to create the NDPS printers?
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: NDPS Print Servicing Queues

Could you please tell us what NetWare version you are using (including SP
level)?

--
Marcel Cox (using XanaNews 1.18.1.3)
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: NDPS Print Servicing Queues

> Could you please tell us what NetWare version you are using (including
SP
> level)?
>
> --
> Marcel Cox (using XanaNews 1.18.1.3)


Sorry, Netware 6.5 sp5 OES
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: NDPS Print Servicing Queues

> > Could you please tell us what NetWare version you are using (including
> SP
> > level)?
> >
> > --
> > Marcel Cox (using XanaNews 1.18.1.3)

>
> Sorry, Netware 6.5 sp5 OES



Also, I thought it was working changing the port handler, but it doesn't
seem to be sending all the jobs through the ndps printer.
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: NDPS Print Servicing Queues

Well, let's start by explaining some of the concepts you mentioned and how
things should work:

- Port Handler
The port handler is an obsolete concept. It was initially introduced with
NDPS and the output side of NDPS was split up between the gateway and the
output handler. The output handler was only used with the old Novell
gateway. Since Novell introduced the new gateway in NW 5.1, the port
handler is no longer used.

- configuration utilities
Initially, when Novell introduced NDPS, you had 2 ways to configure
pritners. Either from the server console from the NDPS Manager and through
NetWare Administrator (NWADMN32.EXE).
With the introduction of the new NDPS gateway in some support pack for NW
5.1, Novell enahnced the NWADMN32 plugin to support the new gateway, but
unfortunately, the configuration tool in the NDPS Manager was not updated.
This means that since NW 5.1, you should no longer use the server console
to create new printers or change the printer configuration. Otherwise, you
will for NDPS to once again use the old obsolete port handler and gateway
instead of the new enhanced gateway.
Since the introduction of NetWare 6.x and iPrint, Novell created a new
configuration utility as a plugin for iManager and it is now iManager that
should be used to manage NDPS and iPrint. You can still use NWADMN32.EXE
(but make sure you use the one from the 6.5 server and not an old copy you
might have from a different source), but if you use NWADMN32, then you
will not be able to configure new functionality that has been introduced
with iPrint.

- Print queues
Print queues are handled by simply adding them to the NDPS printer under
the spooling options (as you mentioned in your first message). Thzat's all
that is needed. It is the NDPS Manager that takes care of reading the jobs
from the pritn queue and sending them to the NDPS printer. Neither gateway
no port handler are involved in getting the print jobs from a queue. If
for some reason jobs from print qeues are not printed, then there is
indeed some problem which needs to be investigated. However before
investigating that problem, we must make sure that you once again clean up
your NDPS/iPrint configuration and undo the confguration mistakes you made

- sending from NDPS to print queues
NDPS/iPrint has the possibility to send the output to a print queue
instead of to a printer. This option can only be configured through
NWADMN32 or the server console. As I understand your second message, you
configured this option by mistake. E.g. you changed your NDPS pritner
configuration to send the jobs to a print queue instead of sending them to
the printer

So where do we go from here?

Given you probably destroyed your NDPS printer configuration by changing
its configuration from the server console, I guess it is best to delete
the NDPS pritner and created it again from scratch. For the simplicity, we
will use NWADMN32.EXE for now because you seem to be familiar with it
Do so as follows:

- Don't touch your print queues! You don't have to delete them. They
should be OK.

- start NetWare Administrator (NWADMN32.EXE). Use the version from the
public\win32 directory of your NW 6.5 server. Don't use an old version you
might have from an older server as it might have outdated NDPS snapins.

- In NWADMN32 select your NDPS Manager and check it's properties. Go to
the option "Printer Agent List", select your pritner and delete it from
here. It is important that you delete your printer from within the
Manager. If you had only deleted the NDS object corresponding to the
printer, you would have created a "public access" printer

- now move to the container in which your printer is to reside, and use
Object-Create and select to create an NDPS Printer.

- Select a pritner name for creation and continue to the next page. On
this second page, select your NDPS Manager as manager and as gateway
select "Novell Printer Gateway (SNMP)". Make sure the mention SNMP is in
the name ot else you have outdated snpains. Also, don't select the HP
gateway which is obsolete.

- on the next page, select your pritner type (or else use generic PCL) and
accept the default port handler (which is dummy anyway).

- on the next page, check "Novell LPR printer gateway (SNMP)" as
connection type

- on the next page, enter the IP address of your pritner. In the bottom
field, replace the text "PASSTHROUGH" by "raw" (without the quotes). Then
press finish and your pritner will be created.

- next you associate your printer with the appropriate drivers. Note that
if you use NWADMN32 to associate drivers, you don't have any XP specific
drivers. Without XP drivers, the Windows 2000 drivers will be used for XP
as well. In iManager, you could assign XP specific drivers.

- now install the newly created NDPS pritner on a workstation and print a
test page to see if it works.

- if printing works, go back to NWADMN32, select the printer, and in the
spooling configuration, enter your pritn queue to be serviced by the NDPS
printer

- next print to your print queue and in NWADMN32.EXE check your print
queue to see if your print jobs disappear from the queue. If your jobs
disappear, it means that your configuration is correct.

--
Marcel Cox
http://support.novell.com/forums
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: NDPS Print Servicing Queues

If you have not already, you need to remove IPX from the print server.
Look at the print queue in pconsole, you will (should) see only the NDPS
manager attached to the queue (whatever you named it). From there, assuming
the manager is attached to the queue, all jobs will be sent directly from
the queue to the NDPSM and will be printer on the NDPS side. If you have
more than 1 print server attached, that is likely the old IPX print server,
which you need to disable on the printer and/or delete from NDS, as you
dont need it anymore. If the IPX print server is still attached, it will
take priority over NDPS, so in that case, NDPS will be out of the loop.
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: NDPS Print Servicing Queues

> Well, let's start by explaining some of the concepts you mentioned and
how
> things should work:
>
> - Port Handler
> The port handler is an obsolete concept. It was initially introduced

with
> NDPS and the output side of NDPS was split up between the gateway and

the
> output handler. The output handler was only used with the old Novell
> gateway. Since Novell introduced the new gateway in NW 5.1, the port
> handler is no longer used.
>
> - configuration utilities
> Initially, when Novell introduced NDPS, you had 2 ways to configure
> pritners. Either from the server console from the NDPS Manager and

through
> NetWare Administrator (NWADMN32.EXE).
> With the introduction of the new NDPS gateway in some support pack for

NW
> 5.1, Novell enahnced the NWADMN32 plugin to support the new gateway,

but
> unfortunately, the configuration tool in the NDPS Manager was not

updated.
> This means that since NW 5.1, you should no longer use the server

console
> to create new printers or change the printer configuration. Otherwise,

you
> will for NDPS to once again use the old obsolete port handler and

gateway
> instead of the new enhanced gateway.
> Since the introduction of NetWare 6.x and iPrint, Novell created a new
> configuration utility as a plugin for iManager and it is now iManager

that
> should be used to manage NDPS and iPrint. You can still use

NWADMN32.EXE
> (but make sure you use the one from the 6.5 server and not an old copy

you
> might have from a different source), but if you use NWADMN32, then you
> will not be able to configure new functionality that has been

introduced
> with iPrint.
>
> - Print queues
> Print queues are handled by simply adding them to the NDPS printer

under
> the spooling options (as you mentioned in your first message). Thzat's

all
> that is needed. It is the NDPS Manager that takes care of reading the

jobs
> from the pritn queue and sending them to the NDPS printer. Neither

gateway
> no port handler are involved in getting the print jobs from a queue. If
> for some reason jobs from print qeues are not printed, then there is
> indeed some problem which needs to be investigated. However before
> investigating that problem, we must make sure that you once again clean

up
> your NDPS/iPrint configuration and undo the confguration mistakes you

made
>
> - sending from NDPS to print queues
> NDPS/iPrint has the possibility to send the output to a print queue
> instead of to a printer. This option can only be configured through
> NWADMN32 or the server console. As I understand your second message,

you
> configured this option by mistake. E.g. you changed your NDPS pritner
> configuration to send the jobs to a print queue instead of sending them

to
> the printer
>
> So where do we go from here?
>
> Given you probably destroyed your NDPS printer configuration by

changing
> its configuration from the server console, I guess it is best to delete
> the NDPS pritner and created it again from scratch. For the simplicity,

we
> will use NWADMN32.EXE for now because you seem to be familiar with it
> Do so as follows:
>
> - Don't touch your print queues! You don't have to delete them. They
> should be OK.
>
> - start NetWare Administrator (NWADMN32.EXE). Use the version from the
> public\win32 directory of your NW 6.5 server. Don't use an old version

you
> might have from an older server as it might have outdated NDPS snapins.
>
> - In NWADMN32 select your NDPS Manager and check it's properties. Go to
> the option "Printer Agent List", select your pritner and delete it from
> here. It is important that you delete your printer from within the
> Manager. If you had only deleted the NDS object corresponding to the
> printer, you would have created a "public access" printer
>
> - now move to the container in which your printer is to reside, and use
> Object-Create and select to create an NDPS Printer.
>
> - Select a pritner name for creation and continue to the next page. On
> this second page, select your NDPS Manager as manager and as gateway
> select "Novell Printer Gateway (SNMP)". Make sure the mention SNMP is

in
> the name ot else you have outdated snpains. Also, don't select the HP
> gateway which is obsolete.
>
> - on the next page, select your pritner type (or else use generic PCL)

and
> accept the default port handler (which is dummy anyway).
>
> - on the next page, check "Novell LPR printer gateway (SNMP)" as
> connection type
>
> - on the next page, enter the IP address of your pritner. In the bottom
> field, replace the text "PASSTHROUGH" by "raw" (without the quotes).

Then
> press finish and your pritner will be created.
>
> - next you associate your printer with the appropriate drivers. Note

that
> if you use NWADMN32 to associate drivers, you don't have any XP

specific
> drivers. Without XP drivers, the Windows 2000 drivers will be used for

XP
> as well. In iManager, you could assign XP specific drivers.
>
> - now install the newly created NDPS pritner on a workstation and print

a
> test page to see if it works.
>
> - if printing works, go back to NWADMN32, select the printer, and in

the
> spooling configuration, enter your pritn queue to be serviced by the

NDPS
> printer
>
> - next print to your print queue and in NWADMN32.EXE check your print
> queue to see if your print jobs disappear from the queue. If your jobs
> disappear, it means that your configuration is correct.
>
> --
> Marcel Cox
> http://support.novell.com/forums


Thanks for the information. I had everything configured correctly, but I
was using an old version of nwadmin and that seemed to be causing me
problems. Also with the ndps printer pulling from the queue I still had
the old printer and print server objects in the tree. When I printed to
the queue it would not always go through the ndps printer, instead
sometimes it would still go through the old printer object. I turned
notify on to verify this was the case. I then got impatient and started
changing things I shouldn't have thinking I had something wrong when all
I needed to do was delete the old printer objects. Afterwards I did read
that the ndps printer only polls the queue every 6 seconds, which would
explain why with the old printer objects in the tree the jobs only went
to the ndps printer part of the time.

I do have one last question if you don't mind,the majority of our
printers are HP, but we also have a few larger,high volume Canon
printer/copiers. What gateway do I want to use for these, the Novell or
the Canon gateway? I did download it from the Canon website, but have
not tried it yet.

Thanks Again!!!
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: NDPS Print Servicing Queues

jpaul@stfrancis.edu wrote:

>I do have one last question if you don't mind,the majority of our
>printers are HP, but we also have a few larger,high volume Canon
>printer/copiers. What gateway do I want to use for these, the Novell or
>the Canon gateway? I did download it from the Canon website, but have
>not tried it yet.


Always use the Novell gateway. Third party gateways tend to be unstable.
Also, none of the third party gateways provide management plugins for
iManager and iManager is the official management tool to manage
NDPS/iPrint on NW 6.x servers. So sooner or later, you will get into
trouble with your printer management.

One important thing when using the Novell gateway is to use the correct
LPR name. The default "PASSTHROUGH" suggested by the Novell tools is
generally not correct. It happens to work with many printers because they
have a sensible default behaviour. However to be safe, you should use the
official name suggested by the printer manufacturers. A list of names for
many printer types can be found here:

http://support.novell.com/docs/Tids/Solutions/10080373.html

--
Marcel Cox
http://support.novell.com/forums
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: NDPS Print Servicing Queues

On Wed, 07 Jun 2006 00:22:37 +0000, jpaul wrote:

> I do have one last question if you don't mind,the majority of our
> printers are HP, but we also have a few larger,high volume Canon
> printer/copiers. What gateway do I want to use for these, the Novell or
> the Canon gateway? I did download it from the Canon website, but have
> not tried it yet.


We have a Canon copier in one of our offices, and I was using the Canon
gateway for a while. I finally converted it over to the Novell gateway
and it's been working flawlessly.

Joe
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.