Now I'm sure I can't be the only personn whose got problems in trying to use one machine on a LAN to print on another Linux machine on the same LAN where the printer on the remote machine is simply connected via a USB port.

Have a read of this --I agree with it 100%.

http://www.catb.org/~esr/writings/cups-horror.html

Documentation seems to abound on how to connect up to a Windows machine (SAMBA PRINTING) or print servers etc but NOTHING UNDERSTANDABLE on a simple Linux to Linux setup.

The post I made previously had no replies so perhaps this article might explain some of the problems with getting Linux to replace 'Doze as a general Desktop.

And I'm sure I'm not the only person who'se got problems with this.

I've got Wireless to work, compiled kernels, connected NFS and SAMBA up etc) so I'm not a total newbie in this stuff but if I'm having trouble of getting something simple like remote printing to work I can see why as far as the mainstream is concerned Linux is still as far away as ever -- a pity as it DOES offer so much more than Windows.

And BTW I still haven't solved the printing problem. -- I've had to boot the desktop into 'DOZE just to print from my laptop --and I don't want to keep doing this as I want to be rid of 'DOZE as soon as possible.

Cheers

-K

Have you tried configuring your printers using CUPS?

Linux to Linux printing is controlled by CUPS (Common Unix Printing Systems)

Ironically, there's a thread, at this moment, right above you about how a guy just got Linux to Linux printing to work.

http://www.linuxquestions.org/questi...hreadid=365204

Y'ep -- with a LOT of perseverence -- the point of THIS post was to show that in spite of some progress having been made with "seemingly" easier Graphical front ends there's still too much "geek speak" or implied knowledge required for tha average user with limited time to set this sort of stuff up.

Things like Printing should be so simple that ANYBODY should be able to do it without thinking about it.

Linux of course unlike windows can be configured anyway you want -- but to gain more acceptance from typical Windows users these sorts of tasks should be made easier to perform as well.


A typical user just wants to install a printer -- they don't want to know or care what the IP address of the remote machine is, its host name or what the printer queue is called. An Install Printer Wizard should be able to get this info from the newtork or report on what's missing and what needs to be configured.

Cheers

-K