Darryl Gregorash wrote:
On 2007-06-18 08:35, Daniel Feiglin wrote:
Hello!
This issue has been done to death on the Web, but I'm not sure where the following derivative problem belongs:
I have an openSUSE 10.2 "vanilla" installation with Samba set up as a server for my Windows work group, with all Win 2K clients. The Linux system is fully patched. I have a parallel port HP printer attached to the Linux box - which works fine, locally. CUPS operates as expected, without problems.
When I try to print something from a Win 2K client, say a browser page - there is a flurry of activity on the net (from the blinking lights on the hub) - and then, nothing.
As of Win2K, I believe you do not need to use Samba to print to a Linux network printer. Configure the printer in CUPS to allow network connections (this should actually be the default behaviour), and configure the printers in Windows to use a Unix-style (IPP) connection. If you are running a firewall on the server, you may need to open the IPP port (name ipp or number 631).
Right on!
That solved the problem - actually bypassing it.
There are a few details Darryl did not include, which I offer, for
anyone else with the same problem:
1. You need to ensure that the printer is set up for sharing. SUSE/CUPS
does this by default in an openSUSE installation.
2. In Win 2K (and presumably later) you set up the printer as a network
printer with its own URL.
3. You get the URL this way:
If you have your Linux box set up as a Web server (say with Apache):
a. From Win, enter the following URL in a browser: