Hi, The <user> part should be the same as the username you use to connect to the filesystem shares. On my samba config [print$] relates to the share where the Windows drivers live, so when you connect a new Windows machine to the network, it doesn't ask you for a printer driver disk. I can't undertand why so many people are having problems with CUPS. Every machine I've set up over the apst 4 years has had cups installed and it just works for me. If you want something really hard to make work first time, try using asterisk :-) Chris -- Chris ---------------------------------- E Mail: chris@glovercc.clara.co.uk SIP: 101@glovercc.claranet.co.uk IAXTEL: 17003366726 On Wed, 5 May 2004, Graham Trott wrote:
On Wednesday 05 May 2004 12:14, Chris Glover wrote:
Two commands are your friend lpq and lprm
lpq -P<printername>
will list all the jobs in the queue and show their job number. You don't need the -P if you only have one printer installed.
lprm -P<printername> <jobno>
will remove offending job from the queue.
As for not being able to access the printer from a windows machine, it's a windows bug. W2K and XP need to have admin rights on a remote printer before they will print to it.
In the [printers] section of your smb.conf add the line
printer admin = <user1> <user2> etc then restart samba.
HTH
Chris
Thanks for the info, but the printer is still listed as access denied. I assume <user> has to be named in smbpasswd. Note: There are two sections in smb.conf: [printers] and [print$]. What do these mean?
-- G
_______________________________________________ main@lists.alug.org.uk http://www.alug.org.uk/ http://lists.alug.org.uk/mailman/listinfo/main Unsubscribe? See message headers or the web site above!