Does samba modify print queues?

[Jack Downes-2]

I have the following situation at the hospital I work at.
we are a windows shop (not my fault), and as such use windows 2k3 file
and print servers.
Recently passing 400 printers has apparently put too much strain on our
main printserver - called ntprn (been a windows shop for a while).
Okay, so now we are going to split the load amongst two or more
printservers... ntprn1 and ntprn2.  Our users have decided that this is
most inconvenient - remembering which server their printer resides on.  
The windows admins looked for a while for a solution, but found nothing
easy to implement, and handed it down to me.  I thought "Cups can do
this - be a front for those windows servers" and I'm right.  it does a
great job of being a face in front of one or more w2k3 server - just
using raw queues, everything is perfect.  Again, the issues of the user
rears it head - they don't want to change their printers to this foreign
idea of IPP.  Okay, so samba can front for this and pass the print
request to Cups and cups passes it to windows, all should be fine.  
Except it isn't.  the prints are changing now.
So somewhere in the line of windowsXPclient -> samba ->cups
->Win2k3printserver -> printer, we are changing the output.  I'm trying
to use "raw" queues in cups and just printers=cups in samba.

Prints from WinXPclients directly to Win2k3printserver are the "control"
Prints from WinXPClients to Cups To Win2k3printserver are exact match
Prints from WinXPClients to Samba to Cups to Win2k3 are different -
fonts are usually smaller, things are bold that are not on the control,
some italics are sometimes missing.  I've checked and rechecked the
drivers on the WinXPClients and the Win2k3 server .. tried making more
generic, etc.  No difference.

Can someone tell me if this is expected behavior or not?  If this is a
known issue, is there a work around?

thanks,
Jack
--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba

[Gerald (Jerry) Carter]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jack Downes wrote:

> So somewhere in the line of windowsXPclient -> samba ->cups
> ->Win2k3printserver -> printer, we are changing the output.

smbd does not modify any bits in the print job itself.  My guess is
that the Windows drivers are operating differently when using RAW
vs. EMF printing modes.






cheers, jerry
- --
=====================================================================
Samba                                    ------- http://www.samba.org
Likewise Software          ---------  http://www.likewisesoftware.com
"What man is a man who does not make the world better?"      --Balian
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFIKaTpIR7qMdg1EfYRAlGzAJwOsF7M18gdb3VL6hLd+t2FTUf1MACgvhup
r2ayevYCF9SwZjHEG5dRIh8=
=QdLw
-----END PGP SIGNATURE-----
--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba

[Jack Downes-2]

Dang... apparently I was not specific enough.  I'm not using RAW drivers on
the windows clients - ONLY in cups. My intention is for the users to change
nothing and to just have the samba/cups combo do routing.  It would seem
easy, however everyone I've tried to talk with has given some linux-centric
answer or whatever.  Okay, well, guess I'll just do this without samba as
it's the culprit.  without samba, all works fine, with samba things go
wrong.  I'm not sure how you came to the conclusion that it must be the
windows client.  Poor writing on my part I must presume.  Well thanks for
the effort.

On Tue, 13 May 2008 09:25:45 -0500, "Gerald (Jerry) Carter"
<jerry@...> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Jack Downes wrote:
>
>> So somewhere in the line of windowsXPclient -> samba ->cups
>> ->Win2k3printserver -> printer, we are changing the output.
>
> smbd does not modify any bits in the print job itself.  My guess is
> that the Windows drivers are operating differently when using RAW
> vs. EMF printing modes.
>
>
>
>
>
>
> cheers, jerry
> - --
> =====================================================================
> Samba                                    ------- http://www.samba.org
> Likewise Software          ------

--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba

[Lukasz Szybalski]

On Tue, May 13, 2008 at 12:26 PM,  <jax@...> wrote:

>
>  Dang... apparently I was not specific enough.  I'm not using RAW drivers on
>  the windows clients - ONLY in cups. My intention is for the users to change
>  nothing and to just have the samba/cups combo do routing.  It would seem
>  easy, however everyone I've tried to talk with has given some linux-centric
>  answer or whatever.  Okay, well, guess I'll just do this without samba as
>  it's the culprit.  without samba, all works fine, with samba things go
>  wrong.  I'm not sure how you came to the conclusion that it must be the
>  windows client.  Poor writing on my part I must presume.  Well thanks for
>  the effort.
>
>

Doesn't samba/cups printing happens this way?

So from winxp (pcl6 or pcl5 or ps) -> to samba (cups) -> to printer
using PPD to raw?
--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba

[Gerald (Jerry) Carter]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jax,

> Dang... apparently I was not specific enough.  I'm not using RAW drivers on
> the windows clients - ONLY in cups. My intention is for the users to change
> nothing and to just have the samba/cups combo do routing.  It would seem
> easy, however everyone I've tried to talk with has given some linux-centric
> answer or whatever.  Okay, well, guess I'll just do this without samba as
> it's the culprit.  without samba, all works fine, with samba things go
> wrong.  I'm not sure how you came to the conclusion that it must be the
> windows client.  Poor writing on my part I must presume.  Well thanks for
> the effort.

Understand there are two different ways to generate print jobs on Windows
clients.  Raw (client side rebdered) and EMF which is basically
encapsulated GDI calls (server side rendered).  When using EMF it is
possible that certain Windows print drivers do not pass the job through
the local Win32 print processor for that driver and hence generate
different output.  That is what I was referring to when I said RAW vs.
EMF printing.  Has nothing to do with cups.






cheers, jerry

- --
=====================================================================
Samba                                    ------- http://www.samba.org
Likewise Software          ---------  http://www.likewisesoftware.com
"What man is a man who does not make the world better?"      --Balian
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFIKdmdIR7qMdg1EfYRAtfeAKDZysCLk/WAgYmeHRGwBDBfgg0/6gCfZwu3
pCJzeGY1zC/j8roHfSI7bYA=
=zXFx
-----END PGP SIGNATURE-----
--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba

[Jack Downes-2]

Oddly enough I wrote back once to this list, but it's not yet shown up. Now
I'm here to say I was wrong, and that Jerry is right...
Setting the print driver on the windows XP client side to NT EMF enables
perfect prints.
thanks for the patient assistance!  you rock.

On Tue, 13 May 2008 13:10:37 -0500, "Gerald (Jerry) Carter"
<jerry@...> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Jax,
>
>> Dang... apparently I was not specific enough.  I'm not using RAW drivers
> on
>> the windows clients - ONLY in cups. My intention is for the users to
> change
>> nothing and to just have the samba/cups combo do routing.  It would seem
>> easy, however everyone I've tried to talk with has given some
> linux-centric
>> answer or whatever.  Okay, well, guess I'll just do this without samba
> as
>> it's the culprit.  without samba, all works fine, with samba things go
>> wrong.  I'm not sure how you came to the conclusion that it must be the
>> windows client.  Poor writing on my part I must presume.  Well thanks
> for
>> the effort.
>
> Understand there are two different ways to generate print jobs on Windows
> clients.  Raw (client side rebdered) and EMF which is basically
> encapsulated GDI calls (server side rendered).  When using EMF it is
> possible that certain Windows print drivers do not pass the job through
> the local Win32 print processor for that driver and hence generate
> different output.  That is what I was referring to when I said RAW vs.
> EMF printing.  Has nothing to do with cups.
>
>
>
>
>
>
> cheers, jerry
>
> - --
> =====================================================================
> Samba                                    ------- http://www.samba.org
> Likewise Software          ------

--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba