Hello Christian,
No problem for the delay, I myself have been really slow dealing with
this issue. The fact you come back to me, even late, is much appreciated.
At the end of april, as the problem was continuing to occur, I upgraded
this server to 3.4 from backports.org. So when I received your
suggestion, I was already running a more up-to-date version.
Unfortunately, the same problem happens again with this upgrade done.
Following your suggestions, here are the step I took:
1) The printer was configured as "RAW" in Cups. I configured it a second
time (KyoceraBis), now with a proper ppd et al.
The reason I configured the printer a second time aside of the original
config (instead of changing it) is that the current setup is working
properly for most of the lan's workstations, and I do not want to
disrupt service for these other users for testing purposes.
2) In my smb.conf, I added this section:
[KyoceraBis]
comment = Kyocera Mita FS-8008N TESTING
path = /var/spool/samba
valid users = foo, bar
printable = Yes
which is basically the same as in the original setupe, but now lacking
the line "use client driver = yes"
3) I the installed this "new" printer on the client WinXP system using.
As described in smb.conf(5), I know suffer from the "Access Denied;
Unable to connect" message when opening the printer queue window, but
printing works fine so far. I can live with this slight annoyance for now.
We will see if the problem still occurs with that modified setup. If you
have any sugggestion or request please do get in touch.
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
