Re: CUPS help
On Tue, 2003-12-09 at 10:36, Dan Coutu wrote: > Well first the direct answer to your last question about username and > password in the URL. Do this: > > http://username:[EMAIL PROTECTED]/path/file > > I'd assume that the ipp syntax would be the same. I thought the same thing. However, it didn't work. CUPS didn't like it. > Secondly, you may find it easier to setup Samba to deal with the printer > installation because it can > be setup so that when a Windows system adds the shared printer the > proper printer drivers can be > downloaded to the Windows system. Pretty cool trick. This was my first method of solving the problem. And it worked nicely. Until I was informed of the actual need ;-) Apparently, what I am doing is setting up a PDF generator so people can just hit "print" and get an e-mail with a URL to their PDF file. (I really wish people would define their needs better before asking for help) I found a system that will work nicely called Alambic (http://alambic.iroise.net/en/index.html). I had to divert from the systems plans and use a different printer driver then the one they say to use (AdobePS driver). Once I used a standard Windows printer driver (HP postscript), I was prompted for the user/passwd. Thanks, Kenny signature.asc Description: This is a digitally signed message part
Re: CUPS help
Kenneth E. Lussier wrote: Hi All, I have started playing around with CUPS (finally). I have one small question about (who wouold have guessed it), Windows clinets. I can point them to http://server:631/printers/foo and everything works fine. The problem starts when I enable basic authentication on the CUPS server. I can add authentication to an existing printer on the Windows side, but I can't install a new printer because access is denied. Does anyone know how to specify the username and password as part of the ipp/http URL? TIA, Kenny Well first the direct answer to your last question about username and password in the URL. Do this: http://username:[EMAIL PROTECTED]/path/file I'd assume that the ipp syntax would be the same. Secondly, you may find it easier to setup Samba to deal with the printer installation because it can be setup so that when a Windows system adds the shared printer the proper printer drivers can be downloaded to the Windows system. Pretty cool trick. Dan ___ gnhlug-discuss mailing list [EMAIL PROTECTED] http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss
CUPS help
Hi All, I have started playing around with CUPS (finally). I have one small question about (who wouold have guessed it), Windows clinets. I can point them to http://server:631/printers/foo and everything works fine. The problem starts when I enable basic authentication on the CUPS server. I can add authentication to an existing printer on the Windows side, but I can't install a new printer because access is denied. Does anyone know how to specify the username and password as part of the ipp/http URL? TIA, Kenny signature.asc Description: This is a digitally signed message part
