I am running Slackware 10.2, I recently purchased a network print sever. My windows machine works fine. Linux box on the other hand will recognize the printer and send data to it, the indicator on the server blinks, however the printer does nothing. I am using cups, it worked great for the USB, Wanted to offload the file server. Thanks in advance.

What brand and model of printer?

The printer is a HP Deskjet 932C

I am running SlackWare 10.2, cups 1.1.23, Zonet ZPS1000 usb print server and a HP932C DeskJet. I have configured the printer in cups as socket://192.168.1.8:9100. When I attempt to test the printer, the indicator on the printer server blinks, telling me that data is being received. I looked at the cups error log and there are no errors.
Does anybody have a clue?
Going on 3 weeks of frustration.

If windoze can doit why not Linux???

I bought a Zonet PrintServer, and only after I'd purchased it did I find that it will print very slowly if the printer attached to it doesn't have sufficient memory. I couldn't ever get it working for anything.

Anyways, does CUPS really put that much load on your file server?

No, it was not that much of a load, nothing significant, however it is now a desire to make something that should work, work. How is linux going to win users over when something as basic as printing over a network is not possible.

I had no problem printing in Linux when printing to Windows, or to another Linux box, so it is possible.

After reading about Zonet's print servers, it really is something you'd use more for printers with enough internal RAM to spool the print jobs properly.

Anyways, try using the HPIJS or HPLIP drivers for your printer. If the print server shows activity, though, things are probably working properly. Try putting your printer on a Windows box instead and see what happens.

I have used a windows box and it works fine (argh!)

http://www.linuxprinting.org/show_pr...P-DeskJet_932C

According to Linux printing, it is supported using the proper drivers. As I suggested, take your print server out of the equation since you seemed to imply it worked before. The reviews I've read of those things say they're useless unless you have sufficient RAM in your printer. I've worked with a similar print server on Windows and Linux; it sucks, plain and simple. [edit]After re-reading your first post, you even said it worked attached locally. That means the printer works, plain and simple. It is your print server or the device URI that is causing the screw up.