I remember that there was a bug in the printing part when using XP SP2
clients. This has been fixed in 2.2.11.
First, you could use a more recent release of samba (wether 2.2.x or 3.0.x).
In all samba-printing-problem-cases I've seen, *nothing* came out of the
printer. So you could increase the loglevel of your cups-daemon and see,
if there are any errors logged. Perhaps you have a problem with your
cupsd (enable raw printing in /etc/mime.confs or something like that...)
bye,
Martin
Jason wrote:> do I not have enough info for someont to take a crack at this?
>
> hey folks. got cups set up and working on a freebsd 4.11
> box running samba 2.2.10. I can print
> locally from the freebsd box just fine.. when I try to print from remote
> windows boxes on the network, I only get blank pages (may be empty banner
> or form feeds). but I jacked up the logging and the only "error"
i see in there
> is
>
>
> [2005/07/01 10:37:55, 5] rpc_parse/parse_prs.c:prs_uint32(588)
> 86c4 buffer_size2: 000086a9
> [2005/07/01 10:37:55, 4]
> rpc_server/srv_lsa_hnd.c:find_policy_by_hnd_internal(168)
> Policy not found: [000] 00 00 00 00 10 02 00 00 00 00 00 00 B8 4C C5 42
> ........ .....L.B
> [2005/07/01 10:37:55, 4] lib/util.c:dump_data(1549)
> [010] D2 06 01 00 ....
> [2005/07/01 10:37:55, 2]
> rpc_server/srv_spoolss_nt.c:find_printer_index_by_hnd(263)
> find_printer_index_by_hnd: Printer handle not found:
_spoolss_writeprinter:
> Invalid handle (OTHER:6728
> 2:67612)
>
>
> I have the following in my smb.conf
>
> [global]
> printing = cups
> printcap name = cups
> hosts allow = 192.168.1. 127.
>
> and
>
> [designjet]
> comment = DesignJet 450C
> path = /var/spool/samba
> writeable = Yes
> guest ok = Yes
> printable = Yes
> printer = designjet
>
>
> any ideas what else to look at?
>
--
Martin Zielinski mz@seh.de
Software Development
SEH Computertechnik GmbH www.seh.de