John L Fjellstad wrote: > > Tom Pfeifer <[EMAIL PROTECTED]> writes: > > > Thanks for the response, but it's not working. > > > > The docs don't help much. A simple example is needed there. > > Did you check the location entry in the /etc/cups/cupsd.conf? > > I have this as my location entry to allow systems on my network to > print: > > <Location /> > Order Deny,Allow > Deny From All > Allow From 127.0.0.1 > Allow From 192.168.10.* > </Location> > > I think the 127.0.0.1 is the default statement, which would allow the > local system to print
I finally managed to get it working - and very nicely. Thanks for your help, and to the others who responded also. For the benefit of anyone else trying this, you don't have to touch anything on the client machine(s). Just the default install of the basic CUPS packages is needed on the client. The CUPS daemon running on the client will then automatically discover the printer(s) on the local network, and the printcap file for the remote printer will show up at /var/run/cups/printcap on the client. At that point, the remote printer will be available to your applications to print from. The only actual configuration needed to enable printing from a client is to edit the <Location /> section in /etc/cups/cupsd.conf on the server machine (the one the printer is connected to) similar to as shown above. This allows printing from a machine other than just the localhost. Of course, to begin with, the printer has to be properly configured on the server machine. This is covered very well in the CUPS documentation, but basically you just point your web browser to localhost:631, and the configuration is menu driven from there. Tom -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
