Our vBulletin migration is complete.
Welcome vBulletin users! All content and user information from the Micro Focus Forums (vBulletin) site has been migrated to this site. READ MORE.
Anonymous_User Absent Member.
Absent Member.
2491 views

NDPS Problems

Before I can go home I have to get 3 printers installed on a W2k laptop - no
big deal... right?

Steps:

1) add printer drivers to the system...
- Can't do it with C1 because I get "an internal error has occured" -
solution: backrev my iPrint client to 3.12.
Unistall 4.15, reinstall 3.12, C1 says "sorry you need 4.15 or higher"

- Basically the same result when I tried adding XP drivers but that's
another story

- Switch to NWAdmin, try to browse to the driver file, browse button does
nothing - solution: add the /disabletlsmgr switch.... ok, this works so I
add the drivers

- Try to create a new profile on my XP laptop, can't do it - I have to use a
w2k machine
never mind I'll set the settings manually

2) Associate the drivers with the NDPS printer object

3) Install the drivers on the laptop...
- Go thru the add printers wizard, select the printer, install begins,
"Spoolsv.exe has generated errors..." pc blue screens

4) Give up and go home....

My questions for this group are:
Printing seems like it should be pretty simple, does everyone have similar
problems?
Does anyone actually have NDPS working the way it's supposed to work?

Thank you all for the opportunity to vent my frustrations.


0 Likes
9 Replies
Anonymous_User Absent Member.
Absent Member.

Re: NDPS Problems

First of all, are you using NDPS or iPrint? IPrint is a layer atop of
NDPS.

If you are using NDPS then you need to have the NDPS client piece
installed on the WS. You can use NWAdmin32 or iManager to administer.
If using Nwadmin, then use the latest version and start with
-disabletlsmgr

If using iPrint then iManager is preferred and indeed necessary for
some tasks. You also need the iPrint client installed. In this case the
NDPS client piece is not needed.

Yes. There are several people using both NDPS and iPrint and it works
as advertised.

- Anders Gustafsson, Engineer, CNE6, ASE
NSC Volunteer Sysop
Pedago, The Aaland Islands (N60 E20)

Novell does not monitor these forums officially.
Enhancement requests for all Novell products may be made at
http://support.novell.com/enhancement

Using VA 5.51 build 315 on Windows 2000 build 2195

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: NDPS Problems

First of all, I assume that when you are talking about C1, you actually
mean iManager because ConsoleOne does not have any NDPS or iPrint support.
You are leaving a lot of things in the dark which makes it difficult for
us to determine where your problems may lie. The only thing you tell us is
what iPrint client you are using. For more serious troubleshooting, we
need more complete version information about your whole setup:

- the NetWare version you are using (including SP level)
- the iManager version you are using
- the Novell client version you are using (including SP level)
- the web browser you are using with iManager
- the type of printer you are trying to install and the type of driver you
are trying to use for that printer

Some more information for a better understanding between NDPS and iPrint:

iPrint builds on to of NDPS. It uses the same objects for Management, but
it adds a HTTP layer for communication. Most of the functionality between
NDPS and iPrint is the same, though iPrint does not offer some NDPS
features while it adds some other features not found in NDPS.

Here are some of the most important things to know about NDPS and iPrint:

NDPS
- NDPS requires an NDPS client on the workstation. The NDPS client can be
installed as part of the Novell client install. It depends on the Novell
Client for authentication and it it cannot operate without Novell client.
- the default Management too for NDPS is NWADMN32.EXE. NWADMN32.EXE can
only manage NDPS if it is run on a workstation with the NDPS client
installed.
- iManager can also be used to manage NDPS, though you should be aware
that configuring iPrint specific features (like XP only drivers, printer
profiles ...) does not have any effect on NDPS printers.
- the main features included in NDPS but missing in iPrint are:
* seamless integration with the Novell client (e.g. no separate login for printing)
* automatic driver install, update or removal through RPM
* Notification services to notify the client about printer events
- the main iPrint features missing for NDPS are:
* XP specific drivers (with NDPS, XP will use W2K drivers)
* printer profiles
* possibility to operate without Novell client

iPrint
- iPrint requires the iPrint client on the workstation. The iPrint client
is completely independent of the Novell client and can be installed
without Novell client. However at the same time, there is no direct
integration with the Novell client in case you want authentication for
secure printing, though this integration can be achieved indirectly
through the Netindenty agent.
- iPrint can even operate without any iPrint specific client on an OS that
has IPP support. However without iPrint client, you loose the ability of
easy printer install. E.g. you can no longer just click on a link on a web
page to install a printer and you will no longer automatically receive the
driver
- the default management tool for iPrint is iManager. You can manage
certain aspects for iPrint through NWADMN32.EXE, but not all iPrint
aspects are exposed in NWADMN32.EXE.
- to upload drivers through iManager, the iPrint client must be installed.
Also, if I remember correctly, driver upload works only through Internet
Explorer.
- for feature differences between iPrint and NDPS, see the previous section.


In our environment, we are heavily using NDPS and it works very well. One
of the most common problem that one might encounter and that you could be
the victim of is printer drivers that are not NDPS/iPrint compatible. This
may cause problems like the ones you describe.
Solutions to incompatible drivers may typically be the following:
- use a different driver version or driver type for the printer
- if there is a driver for the printer included with Windows 2000 or
Windows XP, use the driver bundled with Windows instead of the vendor
supplied driver. The drivers included with Windows are often more NDPS
friendly then vendor supplied drivers
- sometimes, it is just the driver "packaging" that causes problems. In
this case, it may help to install the driver locally on some workstation,
and then use the printer driver generator to create a new more standard
driver package. The printer driver generator can be found here:
http://www.novell.com/coolsolutions/tools/13952.html

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

Re: NDPS Problems

Couple of questions here. Confused because C1 never really officially
supported NDPS, let alone iPrint..
iPrint only deals with driver profiles, and this is available via
iManager...

Seems like you say you used NWAdmin to add drivers, but that only allows
uploading of Win9x, WinNT and Win2K, not Win XP..

Wondering if C1 really means iManager???

The Spoolsv.exe error and blue screen most of the time is due to a bad
driver...

What is the printer??? What is the driver???



>>> On 12/23/2005 at 1:25 pm, in message

<C2Zqf.780$012.468@prv-forum2.provo.novell.com>, Paul
Sherry<psherry@nospam-varoeng.com> wrote:
> Before I can go home I have to get 3 printers installed on a W2k laptop -


> no
> big deal... right?
>
> Steps:
>
> 1) add printer drivers to the system...
> - Can't do it with C1 because I get "an internal error has occured" -
> solution: backrev my iPrint client to 3.12.
> Unistall 4.15, reinstall 3.12, C1 says "sorry you need 4.15 or higher"
>
> - Basically the same result when I tried adding XP drivers but that's
> another story
>
> - Switch to NWAdmin, try to browse to the driver file, browse button does


>
> nothing - solution: add the /disabletlsmgr switch.... ok, this works so I


>
> add the drivers
>
> - Try to create a new profile on my XP laptop, can't do it - I have to use


> a
> w2k machine
> never mind I'll set the settings manually
>
> 2) Associate the drivers with the NDPS printer object
>
> 3) Install the drivers on the laptop...
> - Go thru the add printers wizard, select the printer, install begins,
> "Spoolsv.exe has generated errors..." pc blue screens
>
> 4) Give up and go home....
>
> My questions for this group are:
> Printing seems like it should be pretty simple, does everyone have
> similar
> problems?
> Does anyone actually have NDPS working the way it's supposed to work?
>
> Thank you all for the opportunity to vent my frustrations.

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: NDPS Problems

Marcel Cox wrote:

> * XP specific drivers (with NDPS, XP will use W2K drivers)


Small correction here.
I've been told that NDPS does use XP specific drivers if available.
However you can only upload those drivers through iManager

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

Re: NDPS Problems

First of all I want to thank you guys for answering my question even after I
spewed my frustration all over my post....

I'm back from a week off and now I'm calm, cool and relaxed and ready to try
again.

Here's some more complete/accurate information:

Yes, I did mean iManager not C1
We're using netware 6.5 sp 4
iManager Version 2.5.20050809
Novell Client 4.91.1.20050819 (sp1)
Internet Explorer 6 - latest sp's from windows update
I'm trying to install a Canon imagerunner c3100.

I've tried the PCL6 drivers and the PCL5 and PCL5e drivers from iManager but
after copying the files I get an Internal Error "Failed to update the
database"

I've also tried an HP1050c driver and it fails with the same error.

What I'd like to accomplish is to be able to load the drivers for my
printers in a central place and be able to either push them to the
workstations (with ZFD?) or load them manually. I was planning on using
profiles to get the proper configurations out when the drivers are pushed
out. Automatic driver updates on the clients would be nice too.

I'm a little grey on the difference between NDPS and iPrint. I have iPrint
enabled for the printers - should I disable it? I don't see any advantage
to iPrint other than internet printing and driver profiles.

Thanks Again,
Paul

"Paul Sherry" <psherry@nospam-varoeng.com> wrote in message
news:C2Zqf.780$012.468@prv-forum2.provo.novell.com...
> Before I can go home I have to get 3 printers installed on a W2k laptop -
> no big deal... right?
>
> Steps:
>
> 1) add printer drivers to the system...
> - Can't do it with C1 because I get "an internal error has occured" -
> solution: backrev my iPrint client to 3.12.
> Unistall 4.15, reinstall 3.12, C1 says "sorry you need 4.15 or higher"
>
> - Basically the same result when I tried adding XP drivers but that's
> another story
>
> - Switch to NWAdmin, try to browse to the driver file, browse button does
> nothing - solution: add the /disabletlsmgr switch.... ok, this works so I
> add the drivers
>
> - Try to create a new profile on my XP laptop, can't do it - I have to use
> a w2k machine
> never mind I'll set the settings manually
>
> 2) Associate the drivers with the NDPS printer object
>
> 3) Install the drivers on the laptop...
> - Go thru the add printers wizard, select the printer, install begins,
> "Spoolsv.exe has generated errors..." pc blue screens
>
> 4) Give up and go home....
>
> My questions for this group are:
> Printing seems like it should be pretty simple, does everyone have similar
> problems?
> Does anyone actually have NDPS working the way it's supposed to work?
>
> Thank you all for the opportunity to vent my frustrations.
>



0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: NDPS Problems

Paul Sherry wrote:

>I'm a little grey on the difference between NDPS and iPrint. I have
>iPrint enabled for the printers - should I disable it? I don't see any
>advantage to iPrint other than internet printing and driver profiles.


It's the client that decides between NDPS and iPrint. On the server side
you just define what kind of server is available, but that will not
automatically make the clients use that service.

As for your actual problem, you might try to generate your own printer
installation files using the printer driver generator available here:

http://www.novell.com/coolsolutions/tools/13952.html

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

Re: NDPS Problems

Thanks for the quick reply Marcel,

I ran a PCL5 driver thru the driver generator and got the same error. The
driver I'm trying to load I had previously loaded on my laptop with NDPS
before we made some server changes and made some changes in order to get
profiles working.

Is there someplace else I can look other than at the driver?

Thanks,
Paul

"Marcel Cox" <cimetmc@myrealbox.com> wrote in message
news:%Sdvf.7011$012.6204@prv-forum2.provo.novell.com...
> Paul Sherry wrote:
>
>>I'm a little grey on the difference between NDPS and iPrint. I have
>>iPrint enabled for the printers - should I disable it? I don't see any
>>advantage to iPrint other than internet printing and driver profiles.

>
> It's the client that decides between NDPS and iPrint. On the server side
> you just define what kind of server is available, but that will not
> automatically make the clients use that service.
>
> As for your actual problem, you might try to generate your own printer
> installation files using the printer driver generator available here:
>
> http://www.novell.com/coolsolutions/tools/13952.html
>
> --
> Marcel Cox (using XanaNews 1.17.6.6)



0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: NDPS Problems

Things are looking up...

I was able to load the XP drivers by starting iManager on another server
that's running iManager ver. 2.5.20050224 but in order to assign them to
printer I had to switch back to the original server and use iManager ver.
2.5.20050809. I was also able to create profiles using the newer version of
iManager.

This brings up another set of questions....

Now that I have the drivers added, assigned to printers and have profiles
created and assigned to the drivers what's the best way to push everything
to the pc's?

If I understand what I've been reading:

RPM will push the drivers out but not the profiles and it will happen
everytime a user logs in? Overwriting any changes they've made to the
printer's config? Doesn't this mean that every user would have to
reconfigure they're printer drivers every time they log in? I must be
missing something.

The other option is iPrint? Associate a driver and profile to a printer,
install the iPrint client on every pc and let the iPrint client handle
installing the driver along with the profile. I can use ZFD to distribute
the client and control it, right? How do I handle driver updates with
iPrint?

Thank you for all your help,
Paul

"Marcel Cox" <cimetmc@myrealbox.com> wrote in message
news:%Sdvf.7011$012.6204@prv-forum2.provo.novell.com...
> Paul Sherry wrote:
>
>>I'm a little grey on the difference between NDPS and iPrint. I have
>>iPrint enabled for the printers - should I disable it? I don't see any
>>advantage to iPrint other than internet printing and driver profiles.

>
> It's the client that decides between NDPS and iPrint. On the server side
> you just define what kind of server is available, but that will not
> automatically make the clients use that service.
>
> As for your actual problem, you might try to generate your own printer
> installation files using the printer driver generator available here:
>
> http://www.novell.com/coolsolutions/tools/13952.html
>
> --
> Marcel Cox (using XanaNews 1.17.6.6)



0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: NDPS Problems

Paul Sherry wrote:

>I was able to load the XP drivers by starting iManager on another server
>that's running iManager ver. 2.5.20050224 but in order to assign them to
>printer I had to switch back to the original server and use iManager ver.
>2.5.20050809. I was also able to create profiles using the newer version
>of iManager.


If I understand you correctly, you tried using different versions of
iManager to administrate the same Broker/Manager combo.
I wonder if your driver management problem might not be partially due to
some corruption and Broker or Manager level, so if you have another server
to try, you might try to create a dummy Broker and Manager on that other
server and see if you have the same problems on that server.

>This brings up another set of questions....
>
>Now that I have the drivers added, assigned to printers and have profiles
>created and assigned to the drivers what's the best way to push everything
>to the pc's?
>
>If I understand what I've been reading:
>
>RPM will push the drivers out but not the profiles and it will happen
>everytime a user logs in? Overwriting any changes they've made to the
>printer's config? Doesn't this mean that every user would have to
>reconfigure they're printer drivers every time they log in? I must be
>missing something.


RPM will push out new printers to users. However unless you use the option
to remove other printers and if the printer does already exist, it should
keep thesettings of the printer. However RPM functionality is currently
only available in NDPS mode. For iPrint, this does currently not exist,
even though the iPrint developers promised they would try to implement
similar functionality in iPrint.

>
>The other option is iPrint? Associate a driver and profile to a printer,
>install the iPrint client on every pc and let the iPrint client handle
>installing the driver along with the profile. I can use ZFD to distribute
>the client and control it, right? How do I handle driver updates with
>iPrint?


iPrint alone currently can't automatically install printers. You can
however do the install by using the iprntcmd command, or if you have a
current version of ZfD, then indeed using ZfD is the easiest way to
install iPrint printers.
Driver updates is something that unfortunately isn't currently supported
in iPrint, but that is also something the developers promised they were
working on.

--
Marcel Cox (using XanaNews 1.17.6.6)
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.