Hi Willie, On Tue, Dec 16, 2008 at 1:48 PM, Willie Wong <ww...@princeton.edu> wrote: > (Sorry if this one is a dupe... my SSH connection went kaplui and I > wasn't quite sure whether the mail got sent) > > On Tue, Dec 16, 2008 at 01:04:25PM -0800, Mark Knecht wrote: >> I'm looking around for up to date instructions/wikis/howtos on how >> to set up Samba on my CUPS server to allow me to print from Windows. > > Why SAMBA? > > I've recently set up printing for a small home network following this > guide: http://www.owlfish.com/thoughts/winipp-cups-2003-07-20.html > > Basically you just need > > 1) Correct permissions in /etc/cups/cupsd.conf > a) You need the line "Port 631" to allow remote access > b) Maybe (I am not sure about this one) you need "Browsing On" > to allow sharing? > c) You need the section for "<Location />" to have "Allow From > 192.168.0.*" or whatever netmask you use. > 2) Either > a) A working printer that you can print locally from the cups > server via "lpr -P<NAME>". In this case you can just tell > the Windows computers to print to > http://<cups server ip>:631/printers/<NAME> > using a generic postscript driver.
Is this true for non-postscript printers? If so it's a great solution. I can get to the printers page on the server's Cups' GUI: http://192.168.1.59:631/printers It gives me a long, ugly descriptive name for the printer so I tried: lpr -P HP_PSC_1600_series_USB_1 optimize_mythdb.sh which did print correctly so I'm good to go so far. > or > b) A working printer for which you have the Windows drivers. You The Windows driver for this printer does not support network printing so I don't think this is an option. > need to then setup a raw queue (basically a print queue that > does not have a cups driver associated to it so the Windows > boxes can directly send commands to the printer). You tell > the Windows computers to print to > http://<cups server ip>:631/printers/<RAW queue name> > using the Windows drivers for the printer. > OK, so I'm not clear what the <RAW queue name> is. I see it discussed in the link you pointed us at but that was using some Fedora GUI app. Is this something you set up by hand in your cupsd.conf or printers.conf file? I'm curious whether Cups can accept postscript printing info coming across the network from the Windows box and then format it for my HP printer? I'm thinking you're saying it can if I get this RAW queue set up? My printer is available on my network already. All the Linux boxes can see it and print fine so it's shared. Howfully it doesn't need to be 'more' shared to make this work. Off to Google for more answers. The first few I found were your link as well as a few people asking how to set a RAW queue up! Thanks, Mark > Now, I tried setting up linux printing 5 years ago using the CLI and > it sucked. Last week I used the GUI from cups and it was extremely > easy. This is one of the few cases I highly recommend using the GUI: > you are unlikely to fiddle with it much after it is installed, so > the steep learning curve for dealing with the text config files may > not be worth it. Since you mentioned that your server does not have a > GUI, you need to edit /etc/cups/cupsd.conf to allow admin remotely. > Basically you just need to "Allow 192.168.0.*" or whatever appropriate > subnet in the sections for "<Location /admin>" and > "<Location /admin/conf>" in the config file. After that just point a > browser to https://<cups server ip>:631/ and you are set to go. > > Note that the document in the link thinks that it may be necessary to > modify the Windows host files and access the cups server via name, > rather than ip address. For my home network it works fine with just > the ip address. YMMV. > > HTH, > > W > -- > Willie W. Wong ww...@math.princeton.edu > 408 Fine Hall, Department of Mathematics, Princeton University, Princeton > A mathematician's reputation rests on the number of bad proofs he has given. > >
