HP, NDPS, and iPrint - where to from here?

We've been running NDPS since 1999 with pretty good results. Over the
years, more and more HP Laserjet printers fail to come with
NDPS-compatible drivers, we worked around that. Now more and more HP
Laserjet printers fail to work at all with NDPS, at least the version
we're using.

I know we should have moved to the Novell gateway years ago, just never
got around to it. We also meant to have iPrint by now, but, same issue,
never a priority.

The last straw is trying to add a P2035n to NDPS - HP's website said it
was compatible, but the documentation mentions every OS except
NetWare/NDPS. HP Support said [tech 1] 'yes, it's supported and [tech 2]
"No, there are no NetWare drivers, until Novell writes a driver, it
won't work" (I didn't feel like wasting my time arguing *that* one.)

So my question is, does anyone still use NDPS on NetWare exclusively? If
so, should we be able to add HP Laserjet 4014n, 3600n, 1022n, 1320n,
and/or 2035n printers? These have given us trouble and fail to allow a
connection from the NDPS Manager - the print agent says "Error Printing
- I/O Error" even though the address is reachable, ports 9100, LPD, and
snmp are all open.

Knowing that the future of printing for our environment lies in iPrint
on OES/SLES, can anyone point me in the quickest direction to get there?
(Cool solutions article, wiki, etc?)

For what it's worth, our current environment:

NW6.5sp8

NDPSM.nlm v3.02.07

NDPDS.nlm v3.00

HPGate.nlm v3.00.01

Thanks-
Kirt
  • Kirt Sorensen,
    > So my question is, does anyone still use NDPS on NetWare exclusively?
    >

    Yes, but we use the Novell gateway.

    - Anders Gustafsson (Sysop)
    The Aaland Islands (N60 E20)


    Novell has a new enhancement request system,
    or what is now known as the requirement portal.
    If customers would like to give input in the upcoming
    releases of Novell products then they should go to
    http://www.novell.com/rms

  • On Thu, 13 Aug 2009 12:53:22 0000, Kirt Sorensen wrote:

    > The last straw is trying to add a P2035n to NDPS - HP's website said it
    > was compatible, but the documentation mentions every OS except
    > NetWare/NDPS. HP Support said [tech 1] 'yes, it's supported and [tech 2]
    > "No, there are no NetWare drivers, until Novell writes a driver, it
    > won't work" (I didn't feel like wasting my time arguing *that* one.)


    That makes no sense as there is no such thing as NetWare drivers. You
    aren't trying to print from the NW server console. It should work with
    Windows drivers, though it's impossible to say how well they'll work with
    NDPS.

    > So my question is, does anyone still use NDPS on NetWare exclusively?


    We switched to iPrint years ago.

    > Knowing that the future of printing for our environment lies in iPrint
    > on OES/SLES, can anyone point me in the quickest direction to get there?


    Heck you are already at NW65SP8 so you have full iPrint capability now.
    Just log into iManager and check the box to enable iPrint for your
    printers, then install the client. In fact you should be able to use
    iPrint Client Management (ICM) to automate the rollout of the iPrint
    client. I would implement that ASAP and then worry about OES later on
    when you are ready to migrate away from NetWare.




    --
    Joe Marton
    Novell Knowledge Partner
    SUSE Linux Enterprise 11 is ready for action.
  • Kirt Sorensen,

    > We've been running NDPS since 1999 with pretty good results. Over the
    > years, more and more HP Laserjet printers fail to come with
    > NDPS-compatible drivers, we worked around that. Now more and more HP
    > Laserjet printers fail to work at all with NDPS, at least the version
    > we're using.
    >
    > I know we should have moved to the Novell gateway years ago, just never
    > got around to it. We also meant to have iPrint by now, but, same issue,
    > never a priority.


    That's the first thing I would focus on, move to the Novell Gateway.

    Most HP printers do work with the HP Universal printer driver which works
    quite well with iPrint.

    > Knowing that the future of printing for our environment lies in iPrint
    > on OES/SLES, can anyone point me in the quickest direction to get there?
    > (Cool solutions article, wiki, etc?)


    As you're already on NW 6.5 SP8 you already have iPrint.
    Basically what you need to do is make your printers iPrint Enabled.
    Push out the iPrint agent to the clients and have the NDPS client
    removed.


    --
    _________________________________________
    Niclas Ekstedt, CNA/CNE/CNS/CLS
    Systems Engineer
    Atea Sverige AB

  • On Thu, 13 Aug 2009 13:36:03 0000, Niclas Ekstedt wrote:

    > As you're already on NW 6.5 SP8 you already have iPrint. Basically what
    > you need to do is make your printers iPrint Enabled. Push out the iPrint
    > agent to the clients and have the NDPS client removed.


    And actually removing the NDPS client can be done later on as having it
    installed shouldn't interfere with the iPrint client, should it? The
    main thing is enabling the printers for iPrint and pushing out the iPrint
    client.



    --
    Joe
    Does this washcloth smell like chloroform?
  • Joseph Marton,

    > On Thu, 13 Aug 2009 13:36:03 0000, Niclas Ekstedt wrote:
    >
    >> As you're already on NW 6.5 SP8 you already have iPrint. Basically what
    >> you need to do is make your printers iPrint Enabled. Push out the iPrint
    >> agent to the clients and have the NDPS client removed.

    >
    > And actually removing the NDPS client can be done later on as having it
    > installed shouldn't interfere with the iPrint client, should it?


    There was problems with this way back in the past, and it caused a lot of grief
    for administrators. So I guess I still live on old advice.
    It's easy to leave'em both to cooperate and if there are problems, have the NDPS
    client removed.


    --
    _________________________________________
    Niclas Ekstedt, CNA/CNE/CNS/CLS
    Systems Engineer
    Atea Sverige AB

  • Yes, you can have both installed.

    As others have said: iPrint sits on top of NDPS so it is fairly easy to
    implement. Just make sure that you do the homework and use a dedicated
    IP address and domain name for the manager.

    You can easily and automatically convert QMS or NDPS printers on the WS
    to iPrint ones. See the docs.

    - Anders Gustafsson (Sysop)
    The Aaland Islands (N60 E20)


    Novell has a new enhancement request system,
    or what is now known as the requirement portal.
    If customers would like to give input in the upcoming
    releases of Novell products then they should go to
    http://www.novell.com/rms

  • I have had great luck even with troublesome HP (and other vendor drivers)
    via nw65sp8 latest patches, iprint client 5.20, imgr 2.7.3 - by using the
    printer driver generator. Install said driver locally on the workstation,
    then use that app to craft an ndps/iprint friendly driver. Has worked every
    time. You may also want to look into HP's UPD (universal print driver) as
    well, there is a thread not too far down dealing with it
  • Well, most things have already been said here, but let me give a bit of a
    summery answer that clearly emphases the different points:

    1) Gateway.
    The HP NDS gateway has been discontinued some half a dozen years ago. It
    no longer works reliably with recent Novell support packs. You might get
    abends or have communication issues when using the HP gateway with newer
    support packs.
    I'm actually suprised you were still able to printing using the HP gateway
    for so many years.
    The way to go is using the Novell SNMP enabled gateway using the LPR or
    the port 9100 protocol.
    Converting printers from the HP to the Novell gateway can be automated
    with the PACVER.EXE tool available here:
    http://download.novell.com/Download?buildid=NtLoiafBa4Y~

    2) Printer drivers
    NDPS and iPrint rely on pritner drivers that use the standard Windows
    installation procedure for printer drivers. E.g. it is assumed that a
    printer driver consists of a set of files belonging to the driver plus an
    inf file that describes how the driver is to be installed. A normal
    pritner driver does not need an installation program because the
    installation code is in Windows itself. So any driver that follows these
    guidelines should be (almost) automatically be NDPS/iPrint compatible.
    Unfortunately, in the real world, many printer manufacturers have decided
    to deliver much more than just a printer driver. The software they include
    with the printer contains all kinds of additional stuff and comes with an
    installation program that installs the printer driver plus all the extra
    software. Unfortunately, such a printer driver is by default NDPS/iPrint
    unfriendly and often cannot be immediately imported into NDPS/iPrint.
    Fortunately, there is the third party "printer driver generater" utility
    that can take a printer locally installed on a workstation, and use the
    associated driver files to create a neatly packaged pritner driver with an
    INF file that is NDPS/iPrint friendly. This free utility can be found here:
    http://www.novell.com/communities/node/350/printer driver generator 1 3 0 0
    I must say that among the popular printer manufacturers, HP tends to be
    among the more problematic because of the fancy printer software they
    include. What generally works streight away is the printer drivers
    included with Windows itself.

    3) Now regarding HP's unversal printer drivers, HP and Novell have been
    working closely together to make the HP universal printer driver cooperate
    with iPrint. As such, the tech person from HP you have been communicating
    with must not have been well informed regarding Novell environments, or he
    would have known about it.
    If you have a current HP universal printer driver and the current iPrint
    client, then they should work fine together, and the universal printer
    driver should even be able to extract the IP address of the printer in
    order to connect to it and gets its settings. This however does only work
    with an iPrint client, not with an NDPS client.

    --
    Marcel Cox
    http://support.novell.com/forums
    ------------------------------------------------------------------------
    Marcel Cox's Profile: http://forums.novell.com/member.php?userid=8
  • Kirt Sorensen wrote:
    > We've been running NDPS since 1999 with pretty good results. Over the
    > years, more and more HP Laserjet printers fail to come with
    > NDPS-compatible drivers, we worked around that. Now more and more HP
    > Laserjet printers fail to work at all with NDPS, at least the version
    > we're using.
    >
    > I know we should have moved to the Novell gateway years ago, just never
    > got around to it. We also meant to have iPrint by now, but, same issue,
    > never a priority.
    >
    > The last straw is trying to add a P2035n to NDPS - HP's website said it
    > was compatible, but the documentation mentions every OS except
    > NetWare/NDPS. HP Support said [tech 1] 'yes, it's supported and [tech 2]
    > "No, there are no NetWare drivers, until Novell writes a driver, it
    > won't work" (I didn't feel like wasting my time arguing *that* one.)
    >
    > So my question is, does anyone still use NDPS on NetWare exclusively? If
    > so, should we be able to add HP Laserjet 4014n, 3600n, 1022n, 1320n,
    > and/or 2035n printers? These have given us trouble and fail to allow a
    > connection from the NDPS Manager - the print agent says "Error Printing
    > - I/O Error" even though the address is reachable, ports 9100, LPD, and
    > snmp are all open.
    >
    > Knowing that the future of printing for our environment lies in iPrint
    > on OES/SLES, can anyone point me in the quickest direction to get there?
    > (Cool solutions article, wiki, etc?)
    >
    > For what it's worth, our current environment:
    >
    > NW6.5sp8
    >
    > NDPSM.nlm v3.02.07
    >
    > NDPDS.nlm v3.00
    >
    > HPGate.nlm v3.00.01
    >
    > Thanks-
    > Kirt

    Thanks to all who responded. I will try to get said printers running
    with the Novell gateway, perhaps that will eliminate the apparent
    compatibility problem. In the meantime, however, it appears the 2035n is
    not NDPS-compatible, (despite conflicting marketing info) so we've
    ordered a model costing significantly more...

    And yes, iPrint is long overdue here.

    Thanks!
  • Kirt Sorensen,
    > In the meantime, however, it appears the 2035n is
    > not NDPS-compatible, (despite conflicting marketing info) so we've
    > ordered a model costing significantly more...


    I do not know what model printer that is, but often can you get by by
    using a "generic" driver, such as LJ2000.

    - Anders Gustafsson (Sysop)
    The Aaland Islands (N60 E20)


    Novell has a new enhancement request system,
    or what is now known as the requirement portal.
    If customers would like to give input in the upcoming
    releases of Novell products then they should go to
    http://www.novell.com/rms