David responded:

>Then you specify a lpd URI in CUPS from the CUPS server, not from the
>clients. You want the server to do the actual I/O to the printer, not
>the clients. The clients should need to speak only IPP. Your device URI
>in CUPS for the printer should look something like this:
>
>lpd://<hostname>/raw
>
>Replace <hostname> with the actual hostname of the printer.
>
>It helps if you think about it this way:
>
>There are three parts here:
>
>1) LPD server in the printer (speaks LPR/LPD only)

First I apologize for the length of this email.

We have printing working from the Linux System z guest and printing from
the Win/XP desktops to SAMBA/Cups on Linux System z.

We found a printer that did not support IPP so we had to define the printer
on the Win/XP desktop as an LPR. It works fine as an LPR.
We also found a printer that only partially supported IPP and that one we
had to define as LPR.

We have about 8-10 various printer models defined and all working
correctly.

Now the final part of this is to setup the ability to easily add these
SAMBA printers to Win/XP desktops.
If I understand correctly anyone should be able to open a browser to the
SAMBA Linux guest and be presented with a display of the known
printers on SAMBA/Cups point to one and click. A ppd file will be created
and the printer added to the Win/XP desktop.

I have followed the IBM Redpiece redp3864, 'Printing with Linux on zSeries
using Cups & SAMBA'  I find that on page 17
the install/extract of winsteng.exe and aps426eng.exe do not complete
successfully. I am guessing that these work fine for Win/NT
but have problems with Win/XP ?.

I was given four files to use instead of trying to run the winsteng.exe or
aps426eng.exe.

These four files are placed on the SAMBA/Cups Linux guest.

ADOBEPS5.DLL,
ADOBEPSU.DLL,
ADOBEPSU.HLP,
DEFPRTR2.PPD,

The SAMBA/CUPS userid for admin is cupsadm for both. Password has been set
using smbpasswd for samba. The cupsadm is also created as a user account on
Linux with the same password. On the Win/XP work station we also have the
Windows logged on as cupsadm with the same password.

We then run cupsaddsmb to populate the SAMBA drivers directory.

We have a couple of errors messages but are stumped on how to resolve:

"samba1:/var/lib/samba/drivers/W32X86 # cat 'password for cupsadm required
to access localhost via SAMBA:'
WARNING: The "printer admin" option is deprecated
SetPrinter call failed!
result was WERR_ACCESS_DENIED
WARNING: The "printer admin" option is deprecated
failed session setup with NT_STATUS_LOGON_FAILURE
Cannot connect to server.  Error was NT_STATUS_LOGON_FAILURE
Running command: rpcclient localhost -N -U'cupsadm%samba' -c 'setdriver
AUDIT01-HP-136.020 AUDIT01-HP-136.020'

Running command: rpcclient localhost -N -U'cupsadm%' -c 'setdriver
AUDIT01-HP-136.020 AUDIT01-HP-136.020'."

Also we have seen:
"Password for cupsadm required to access localhost via SAMBA:
WARNING: The "printer admin" option is deprecated
Password for cupsadm required to access localhost via SAMBA: SetPrinter
call failed!
result was WERR_ACCESS_DENIED

WARNING: The "printer admin" option is deprecated
cupsaddsmb: Unable to set Windows printer driver (256)!
failed session setup with NT_STATUS_LOGON_FAILURE
Cannot connect to server.  Error was NT_STATUS_LOGON_FAILURE
Running command: rpcclient localhost -N -U'cupsadm%samba' -c 'setdriver
AUDIT01-HP-136.020 AUDIT01-HP-136.020'

Running command: rpcclient localhost -N -U'cupsadm%' -c 'setdriver
AUDIT01-HP-136.020 AUDIT01-HP-136.020'"

Any thoughts would be greatly appreciated.

TIA ...............

Terry L. Spaulding
[email protected]
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Reply via email to