My wife has an HP 1210 printer/scanner/copier/wok/bidet/whatever all I want to do is print to it from my PC. I am running Slack 10.1 with the 2.4 kernel. I can see her machine and see the printer share with LinNeighborhood and all, but I cannot for the life of me print to it.

Where do I even start?

It's pretty much the same as adding a local printer in CUPS, but you just point it to the remote printer instead.

First thing, look at http://www.linuxprinting.org/show_pr...um=HP-PSC_1210 You're in luck, as it looks like HP provide an open source driver for the printer. Download and install the relevant PPD file from that page (basically, grab the PPD file and put it in the /usr/share/cups/model/ directory)

(I don't know how much experience you have with CUPS, so I'm assuming 'none but learns quickly')

Then, go to http://localhost:631 in your browser and select 'Manage Printers', then click the 'Add Printer' button - username and password are 'root' and root's password.

Fill in the first boxes, and then click continue. From the drop down box in the next screen, pick the last option, 'Windows Printer via SAMBA'. In the next screen, enter the device location. LinNeighbourhood, I imagine, should give this to you - if not, it will be something like (off the top of my head):

smb://<wife's machine name>/<printer share name>

Then continue as a normal printer - select HP from the next menu, and then the driver you downloaded and installed, and you should be ready to go.

OK, thank you so much! I am much further now, however now on her PC, the spooler is saying that it has a "Remote Downlevel Document" and it will only spool 63k of any job, and it will never print.

CUPS marks the job as complete, but it never prints. Any ideas?

you have to go to the windows printer configurator thingy
you know -- right click properties
then on the tab "ports"
uncheck "Enable bidirectional support"

it literally took me years to figure that one out

it doesn't seem to have any effect accept now cups -> windows works

yipeee

That was it! Thank you.

I am surprised I didn't check that. I had that issue a few weeks ago on an all-Windows network.