[opensuse] Linux/CUPS/Samba Printer Configuration - again
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.
If on the client, I open up a command line and do something like this:
print /d:\\
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). -- Hypocrisy is the homage vice pays to virtue. -- François de La Rochefoucauld -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
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:
On 06/19/2007 01:30 AM, Daniel Feiglin wrote:
<snip>
1. You need to ensure that the printer is set up for sharing. SUSE/CUPS does this by default in an openSUSE installation.
From reading the header of /etc/cups/cupsd.conf, I do believe CUPS by default shares all printers, in any distro. There is no comment there to suggest that it has been changed at all by the opensuse team. 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:
:631/printers. This displays the CUPS Web
Actually, you do not need a web server running on the Linux server; those typically won't be listening on port 631 anyway, and even if they were, they would not know what to do with the request. CUPS runs its own mini-http server, which (again by default, though you could change it) listens on port 631 on all interfaces. If you are having problems connecting to the CUPS administration webpage at this point, it is likely that port 631 is closed. Just move opening the IPP port (which you have as point 5) to become point 1.b and this should solve it :-) -- Hypocrisy is the homage vice pays to virtue. -- François de La Rochefoucauld -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Darryl Gregorash wrote:
On 06/19/2007 01:30 AM, Daniel Feiglin wrote:
<snip>
1. You need to ensure that the printer is set up for sharing. SUSE/CUPS does this by default in an openSUSE installation.
From reading the header of /etc/cups/cupsd.conf, I do believe CUPS by default shares all printers, in any distro. There is no comment there to suggest that it has been changed at all by the opensuse team.
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:
:631/printers. This displays the CUPS Web Actually, you do not need a web server running on the Linux server; those typically won't be listening on port 631 anyway, and even if they were, they would not know what to do with the request. CUPS runs its own mini-http server, which (again by default, though you could change it) listens on port 631 on all interfaces.
If you are having problems connecting to the CUPS administration webpage at this point, it is likely that port 631 is closed. Just move opening the IPP port (which you have as point 5) to become point 1.b and this should solve it :-)
Bottom line: It all works, and I'm back on the job instead of futzing around with the system ... I completely forgot about the CUPS web server: Odd, I had a few problems with that a few years ago - solved & forgotten.
participants (2)
-
Daniel Feiglin -
Darryl Gregorash