Highlighted
Absent Member.
Absent Member.
2179 views

CIFS distribution of print drivers

I am running NetWare 6.5 and ZEN 3.2. I would like to distribute print
drivers using a CIFS path.
server - theserver
CIFS server - theserver-w

In order for the drivers to be distributed using CIFS I need to specify
theserver-w as the server name.

I am uing NDPS and I don't see a way to change this. Is this correct?
Will IPP printing allow me to do this?
Will iPrint allow me to do this?

Thanks in advance
0 Likes
8 Replies
Highlighted
Absent Member.
Absent Member.

Re: CIFS distribution of print drivers

j.r.trimark@aurora.org wrote:

>I am uing NDPS and I don't see a way to change this. Is this correct?
>Will IPP printing allow me to do this?
>Will iPrint allow me to do this?


NDPS and iPrint use their proper communication method to download the
printer driver to the workstation. In none of these the client gets the
ddriver directly from a network drive.
In the case of NDPS, you need a Novell client with the NDPS client
installed. For iPrint, you can install the iPrint client alone without
Novell client.
IPP is the protocol used by iPrint for printing. You can address an iPrint
printer without iPrint client through some other IPP client (like for
example the IPP functionality built into windows). However if you use
"bare" IPP, you completely loose the capability to distribute printer
drivers.

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

Re: CIFS distribution of print drivers

Marcel,

> However if you use "bare" IPP, you completely loose the capability to
> distribute printer drivers.


Very true and quite tedious to manage! However, if you're using iPrint, you
can deploy IPP printers with batch scripts using KIX32 script engine without
having any polices in the "bare" IPrint world. This works with and without
Client32. What I've done is create a per-workstation print script in a
shared CIFS folder, with the name of the computer as the name of the file:

Kix32.exe \\Server1\SYS\PUBLIC\SCRIPTS\ %COMPUTERNAME%.KIX

The %COMPUTERNAME%.KIX would be a two-line script that looks something like
this for adding and removing a printer:
iprntcmd http://printing.mycompany.com/ipp/Colorprinter /add /default
iprntcmd http://printing.mycompany.com/ipp/OLD-Colorprinter /delete

(Taken from this page:
http://support.novell.com/techcenter/search/Docs/ProductDoc/NetWare/NetWare%206.5/iprint/iprint.html#Akuji88 )

That's it. It's easy to teach any LAN person how to create one of these
scdripts, as per computername, then drop it in the Read-Only folder. This
method is simple and easy to use. If you use Zenworks, just have the batch
file run at user login time.

Then, as Marcel said, the printer driver download is completely automatic as
a built-in function of the iPrint/NDPS back-end environment.

Good Luck!
Mike



0 Likes
Highlighted
Absent Member.
Absent Member.

Re: CIFS distribution of print drivers

> IPP is the protocol used by iPrint for printing. You can address an
> iPrint printer without iPrint client through some other IPP client (like
> for example the IPP functionality built into windows). However if you
> use "bare" IPP, you completely loose the capability to distribute
> printer drivers.


Any way to get it not to make the printer name huge on that? When you
do a "bare" install you get http://server/ipp/printer on
http://server/ipp/printer

Actuate crashes when trying to build a printer list because the name is
too long.



0 Likes
Highlighted
Absent Member.
Absent Member.

Re: CIFS distribution of print drivers

Patrick Farrell wrote:

>Actuate crashes when trying to build a printer list because the name is
>too long.


Honestly, if an application crashes because it just allocates a too small
static buffer for enumerating printers, that is a serious application
fault and should be fixed at application level.

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

Re: CIFS distribution of print drivers

Marcel Cox wrote:
> Patrick Farrell wrote:
>
>> Actuate crashes when trying to build a printer list because the name
>> is too long.

>
>
> Honestly, if an application crashes because it just allocates a too
> small static buffer for enumerating printers, that is a serious
> application fault and should be fixed at application level.
>


Ok now lets move to the real world where you deal with a large company
that doesn't even have a knowledge base on the web, and this company
makes a reporting system that is bundled with an accounting system and
thus we have no direct support with said company. What are the odds
that I can get them to fix their software when I tell them what I'm
doing when they can just as easily say, we don't support Novell? 😞

I totally agree with you. Unfortunately it is, what it is.

That being said, it's still a really ugly printer name for even a user
to look at.
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: CIFS distribution of print drivers

Since you stepped into this thread, could you tell me what your
environment looks like?
What NetWare version are you using? Are you using iPrint? If yes, what
iPrint client? Are you use Novell clients on your workstation?

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

Re: CIFS distribution of print drivers

Marcel Cox wrote:
> Since you stepped into this thread, could you tell me what your
> environment looks like?
> What NetWare version are you using? Are you using iPrint? If yes, what
> iPrint client? Are you use Novell clients on your workstation?
>


Basically I have a 2003 server with the iprint 4.12 client. When I
install printers with that, Actuate doesn't see them (it's similar to
crystal reports enterprise). If I install with the windows add printer
and point at a url, the name is so long Actuate ****'s itself. So I saw
this thread about bare installs so to speak and said ok that can
possibly work if I can get the name shorter so I chimed in 🙂
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: CIFS distribution of print drivers

Marcel Cox wrote:

> Since you stepped into this thread, could you tell me what your
> environment looks like?
> What NetWare version are you using? Are you using iPrint? If yes, what
> iPrint client? Are you use Novell clients on your workstation?
>


Success!

Ok the problem as touched on by someone else was a system vs user
printer. I went into the iprint client and told it to install
workstation printers only and now it works.
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.