9:01 a.m.
I recently upgraded (clean install) my wife to F15 and noticed that
even after I opened up the firewall for printing that it did not auto
detect my printers like it had in F14. Am I missing something or is
this intentional?
The Gnome 3 printer settings GUI is, uh, interesting. Manually adding
a printer seemed to work.
Thanks,
Richard
10:14 a.m.
On Thu, Aug 4, 2011 at 9:33 AM, Tim Waugh <twaugh(a)redhat.com> wrote:
On Thu, 2011-08-04 at 09:08 -0500, Richard Shaw wrote:
> It's one physical printer connected to my desktop and shared by CUPS
> from there. I've got 3 queues on it, two of which are shared (normal,
> and photo for the photo tray). They are on a flat network
> (192.168.0.x)
There's no intention behind it not currently working for you. I would
expect altering the firewall to do the trick.
What's in /etc/sysconfig/system-config-firewall? Hopefully there's a
line saying "--service=ipp-client".
Good catch! I did open s-c-firewall and check and apply printing
client but apparently it didn't update
/etc/sysconfig/system-config-firewall... Strange
Richard
3:06 p.m.
Tim Waugh ha scritto / said the following il giorno/on 04/08/2011 16:04:
On Thu, 2011-08-04 at 09:01 -0500, Richard Shaw wrote:
> I recently upgraded (clean install) my wife to F15 and noticed that
> even after I opened up the firewall for printing that it did not auto
> detect my printers like it had in F14. Am I missing something or is
> this intentional?
Could you give a bit more detail? What printers were you expecting to
be auto-detected... are they hosted on CUPS instances on the network, or
are they actual network printers?
Tim.
*/
I have exactly the same problem, printer is not auto-detected, and it is
detected only if I insert the remote IP.
I insert the correct driver, but at a certain step when verifying
printer, I get the message that printer is not available!!
Firewall is disabled on all network machines.
What is the starting point to decode the problem (Printer is a HP2350
all in one)?? Same printer with same driver is working fine if directed
connected to computer
Tnx
--
Antonio M
Skype: amontag52
Linux Fedora F15 (Lovelock) on Acer 5720
http://lugsaronno.altervista.org
http://www.campingmonterosa.com
http://www.studiodacolpaloschi.it
3:13 p.m.
On Sat, 2011-08-06 at 09:12 +0930, Tim wrote:
Theoretically, all you need to do to get it to work is:
1. Set up the server so that it can do its own printing (get the right
printer driver, test print through CUPS, test print through any
program that prints its output). Then configure its CUPS server to
share itself to the LAN.
2. Set up the server's firewall so that it can act as a CUPS *server*
(probably called IPP, for internet printing protocol, in your firewall
configuration).
3. Set up your client's firewall so they can be a CUPS *client*
(again, it may be called IPP).
I don't know if, since the last time I set up network printing,
there's any options that need setting with SELinux configuration, as
well. There didn't used to be.
To be complete, I should add that you do need the CUPS services running
on both the server and the clients.
--
[tim@localhost ~]$ uname -r
2.6.27.25-78.2.56.fc9.i686
Don't send private replies to my address, the mailbox is ignored. I
read messages from the public lists.
6:42 p.m.
On Fri, 2011-08-05 at 23:16 +0200, antonio montagnani wrote:
Not clear what you mean by saying that printer must be configured
only
on the attached machine: I understand that it should be configured
also on the remote machine (or you mean that it should be left as Raw
printer??)
On the computer that the printer is directly plugged into, that computer
is configured as the printer server. It does the driving for the
printer, and makes itself available to the network.
The clients should automatically find the server, without you doing
anything, at all, to the CUPS configuration on the client. And it'll
make that printer available to any program that wants to print.
Theoretically, all you need to do to get it to work is:
1. Set up the server so that it can do its own printing (get the right
printer driver, test print through CUPS, test print through any program
that prints its output). Then configure its CUPS server to share itself
to the LAN.
2. Set up the server's firewall so that it can act as a CUPS *server*
(probably called IPP, for internet printing protocol, in your firewall
configuration).
3. Set up your client's firewall so they can be a CUPS *client* (again,
it may be called IPP).
I don't know if, since the last time I set up network printing, there's
any options that need setting with SELinux configuration, as well.
There didn't used to be.
--
[tim@localhost ~]$ uname -r
2.6.27.25-78.2.56.fc9.i686
Don't send private replies to my address, the mailbox is ignored. I
read messages from the public lists.
6:20 p.m.
On Fri, 2011-08-05 at 23:16 +0200, antonio montagnani wrote:
Aaron Konstam ha scritto / said the following il giorno/on
05/08/2011
23:03:
> On Fri, 2011-08-05 at 22:06 +0200, antonio montagnani wrote:
>> Tim Waugh ha scritto / said the following il giorno/on 04/08/2011 16:04:
>>> On Thu, 2011-08-04 at 09:01 -0500, Richard Shaw wrote:
>>>> I recently upgraded (clean install) my wife to F15 and noticed that
>>>> even after I opened up the firewall for printing that it did not auto
>>>> detect my printers like it had in F14. Am I missing something or is
>>>> this intentional?
>>>
>>> Could you give a bit more detail? What printers were you expecting to
>>> be auto-detected... are they hosted on CUPS instances on the network, or
>>> are they actual network printers?
>>>
>>> Tim.
>>> */
>>>
>>>
>>>
>>>
>> I have exactly the same problem, printer is not auto-detected, and it is
>> detected only if I insert the remote IP.
>> I insert the correct driver, but at a certain step when verifying
>> printer, I get the message that printer is not available!!
>> Firewall is disabled on all network machines.
>> What is the starting point to decode the problem (Printer is a HP2350
>> all in one)?? Same printer with same driver is working fine if directed
>> connected to computer
>>
>> Tnx
> There are 2 secrets that you need to be aware of with printer browsing.
> Only configure the printer on the machine to which it is attached (the
> server)
> Browsing only works if the printers are on the same LAN
>
>
printers are on the same LAN.
Not clear what you mean by saying that printer must be configured only
on the attached machine: I understand that it should be configured also
on the remote machine (or you mean that it should be left as Raw printer??)
No configuring of printers should be done on the client machines, only on the server.
Just do no configuration of printers on the clients.
--
=======================================================================
Sanity is the trademark of a weak mind. -- Mark Harrold
=======================================================================
Aaron Konstam telephone: (210) 656-0355 e-mail: akonstam(a)sbcglobal.net
4:16 p.m.
Aaron Konstam ha scritto / said the following il giorno/on 05/08/2011
23:03:
On Fri, 2011-08-05 at 22:06 +0200, antonio montagnani wrote:
> Tim Waugh ha scritto / said the following il giorno/on 04/08/2011 16:04:
>> On Thu, 2011-08-04 at 09:01 -0500, Richard Shaw wrote:
>>> I recently upgraded (clean install) my wife to F15 and noticed that
>>> even after I opened up the firewall for printing that it did not auto
>>> detect my printers like it had in F14. Am I missing something or is
>>> this intentional?
>>
>> Could you give a bit more detail? What printers were you expecting to
>> be auto-detected... are they hosted on CUPS instances on the network, or
>> are they actual network printers?
>>
>> Tim.
>> */
>>
>>
>>
>>
> I have exactly the same problem, printer is not auto-detected, and it is
> detected only if I insert the remote IP.
> I insert the correct driver, but at a certain step when verifying
> printer, I get the message that printer is not available!!
> Firewall is disabled on all network machines.
> What is the starting point to decode the problem (Printer is a HP2350
> all in one)?? Same printer with same driver is working fine if directed
> connected to computer
>
> Tnx
There are 2 secrets that you need to be aware of with printer browsing.
Only configure the printer on the machine to which it is attached (the
server)
Browsing only works if the printers are on the same LAN
printers are on the same LAN.
Not clear what you mean by saying that printer must be configured only
on the attached machine: I understand that it should be configured also
on the remote machine (or you mean that it should be left as Raw printer??)
--
Antonio M
Skype: amontag52
Linux Fedora F15 (Lovelock) on Acer 5720
http://lugsaronno.altervista.org
http://www.campingmonterosa.com
http://www.studiodacolpaloschi.it
4:03 p.m.
On Fri, 2011-08-05 at 22:06 +0200, antonio montagnani wrote:
Tim Waugh ha scritto / said the following il giorno/on 04/08/2011
16:04:
> On Thu, 2011-08-04 at 09:01 -0500, Richard Shaw wrote:
>> I recently upgraded (clean install) my wife to F15 and noticed that
>> even after I opened up the firewall for printing that it did not auto
>> detect my printers like it had in F14. Am I missing something or is
>> this intentional?
>
> Could you give a bit more detail? What printers were you expecting to
> be auto-detected... are they hosted on CUPS instances on the network, or
> are they actual network printers?
>
> Tim.
> */
>
>
>
>
I have exactly the same problem, printer is not auto-detected, and it is
detected only if I insert the remote IP.
I insert the correct driver, but at a certain step when verifying
printer, I get the message that printer is not available!!
Firewall is disabled on all network machines.
What is the starting point to decode the problem (Printer is a HP2350
all in one)?? Same printer with same driver is working fine if directed
connected to computer
Tnx
There are 2 secrets that you need to be aware of with printer browsing.
Only configure the printer on the machine to which it is attached (the
server)
Browsing only works if the printers are on the same LAN
--
=======================================================================
I'm not under the alkafluence of inkahol that some thinkle peep I am.
It's just the drunker I sit here the longer I get.
=======================================================================
Aaron Konstam telephone: (210) 656-0355 e-mail: akonstam(a)sbcglobal.net
9:33 a.m.
On Thu, 2011-08-04 at 09:08 -0500, Richard Shaw wrote:
It's one physical printer connected to my desktop and shared by
CUPS
from there. I've got 3 queues on it, two of which are shared (normal,
and photo for the photo tray). They are on a flat network
(192.168.0.x)
There's no intention behind it not currently working for you. I would
expect altering the firewall to do the trick.
What's in /etc/sysconfig/system-config-firewall? Hopefully there's a
line saying "--service=ipp-client".
Next would be to take a look at the TCP traffic using wireshark, and
check that you are receiving UDP packets on port 631.
After that, ramp up the debugging (with "cupsctl LogLevel=debug2") and
take a look at what gets written to /var/log/cups/error_log when a
packet comes in.
Tim.
*/
9:08 a.m.
On Thu, Aug 4, 2011 at 9:04 AM, Tim Waugh <twaugh(a)redhat.com> wrote:
On Thu, 2011-08-04 at 09:01 -0500, Richard Shaw wrote:
> I recently upgraded (clean install) my wife to F15 and noticed that
> even after I opened up the firewall for printing that it did not auto
> detect my printers like it had in F14. Am I missing something or is
> this intentional?
Could you give a bit more detail? What printers were you expecting to
be auto-detected... are they hosted on CUPS instances on the network, or
are they actual network printers?
Duh, that probably would help.
It's one physical printer connected to my desktop and shared by CUPS
from there. I've got 3 queues on it, two of which are shared (normal,
and photo for the photo tray). They are on a flat network
(192.168.0.x)
Thanks,
Richard
9:04 a.m.
On Thu, 2011-08-04 at 09:01 -0500, Richard Shaw wrote:
I recently upgraded (clean install) my wife to F15 and noticed that
even after I opened up the firewall for printing that it did not auto
detect my printers like it had in F14. Am I missing something or is
this intentional?
Could you give a bit more detail? What printers were you expecting to
be auto-detected... are they hosted on CUPS instances on the network, or
are they actual network printers?
Tim.
*/
4655
days inactive
4657
days old
12 comments
7 participants
participants (7)
-
Aaron Konstam -
antonio montagnani -
Arthur Dent -
Patrick O'Callaghan -
Richard Shaw -
Tim -
Tim Waugh