Hello

I am currently testing a linux client (Fedora Core 6 i386) on one small corner of a large computer network*. There is about an even split of Windows NT4.0 and Apple OS X machines, with printers attatched to each of the two clusters.

Kdeprint (/kprinter) has worked very well for me so far in that it picked up and allowed me to print to all the printers on the Apple side (through the Apple print server) without any configuration whatsoever, with the IPP protocol.

Having not yet set up Samba in order to access the Windows server, I have been attempting to print direct to the printers in the mean time. However, it seems that kdeprint is having problems.

Although it can detect the printers when I try "scan", on both TCP and w/IPP (HTTP/IPP), I get errors when I try to test-print/install them. (NB. some printers are only detected on IPP and not TCP. This is my first experience with networking, so I don't have a clue why)

When I try to test print using kdeprint on both TCP and IPP, I get the error:
After ignoring the message above, when I finish the installation wizard I get this error. The IPP report is the same.


Nonetheless, I did my homework and decided to test it from the command line.
Although it did not print the contents of the file (Only some information regarding the print request, of the form
"Content-Length: 351
User-Agent: CUPS/1.2.5" etc.
...I did actually get the printers to output.


Can anyone advise me on what might be wrong?
Thanks

*yes, I have permission!

First use http://127.0.0.1:631 to configure cups for the printer(s) you want to use.

Choose HPJetDirect and use the actual IP address of i_p.obs.cu.red and the port number 9100 and (of course) select the printer make and model.

Also make sure that the Windows print server has the Unix print services installed and configured;

http://support.microsoft.com/kb/324078

.

Thanks, I didn't know about the CUPS web interface. Link to the Microsoft website about installing unix drivers will also come in handy when I set up samba sometime

Installation was easy; under the Administration tab were all the devices that kdeprint had not been able to handle; waiting to be added.

However, though I've now been able to use the cups interface to pick up and configure the printers, I'm having problems in that nothing comes out of the printer!

Cups has detected the printers and actually brought them out of "sleep" into "ready" mode, but when I send a test page /etc., though cups sends them, and thinks that they have been successfully printed, the printer does not seem to be recieving/processing data, spooling or printing.

I changed the error recording from "info" to "error" in the cups error log, but nothing is recorded: as I said above, it seems cups thinks the print is successful! Where could the problem be?