Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #167634 > unrolled thread

cups (sharing network printer)

Back to article view | Back to linux.debian.user

Contents

  cups (sharing network printer) Pol Hallen <deben@fuckaround.org> - 2016-05-09 21:30 +0200
    Re: cups (sharing network printer) Brian <ad44@cityscape.co.uk> - 2016-05-09 21:40 +0200
      Re: cups (sharing network printer) Pol Hallen <deben@fuckaround.org> - 2016-05-09 21:50 +0200
        Re: cups (sharing network printer) Brian <ad44@cityscape.co.uk> - 2016-05-10 00:30 +0200
          Re: cups (sharing network printer) Pol Hallen <deben@fuckaround.org> - 2016-05-10 13:20 +0200
            Re: cups (sharing network printer) Brian <ad44@cityscape.co.uk> - 2016-05-10 14:20 +0200
      Re: cups (sharing network printer) Brian <ad44@cityscape.co.uk> - 2016-05-09 21:50 +0200
    Re: cups (sharing network printer) Dutch Ingraham <stoa@gmx.us> - 2016-05-09 21:40 +0200
      Re: cups (sharing network printer) Pol Hallen <deben@fuckaround.org> - 2016-05-09 22:00 +0200
        Re: cups (sharing network printer) deloptes <deloptes@gmail.com> - 2016-05-09 23:50 +0200
          Re: cups (sharing network printer) Brian <ad44@cityscape.co.uk> - 2016-05-10 00:30 +0200
            Re: cups (sharing network printer) David Wright <deblis@lionunicorn.co.uk> - 2016-05-10 03:10 +0200
              Re: cups (sharing network printer) Brian <ad44@cityscape.co.uk> - 2016-05-10 12:40 +0200
            Re: cups (sharing network printer) deloptes <deloptes@gmail.com> - 2016-05-10 10:30 +0200
            Re: cups (sharing network printer) Pol Hallen <deben@fuckaround.org> - 2016-05-10 13:00 +0200
              Re: cups (sharing network printer) Brian <ad44@cityscape.co.uk> - 2016-05-10 14:30 +0200

#167634 — cups (sharing network printer)

Hi all :)

I've a cups printer server (192.168.1.10) with a network printer 
connected (192.168.1.200). From that server I can print.

how I have to configure the clients to print by that server?

thanks for help!

Pol

[toc] | [next] | [standalone]

#167635

On Mon 09 May 2016 at 21:15:50 +0200, Pol Hallen wrote:

> Hi all :)
> 
> I've a cups printer server (192.168.1.10) with a network printer connected
> (192.168.1.200). From that server I can print.
> 
> how I have to configure the clients to print by that server?

Set up the clients to discover the server. Print.

[toc] | [prev] | [next] | [standalone]

#167637

> Set up the clients to discover the server. Print.

ehm... not it so easy: from client I see network printer (shared by 
server) but after installed it I can't print.

On client I see "printer not connected" and on the server no logs file.

I also checked iptables rules but I've same problem :-/

thanks for help!

PS: on server I use debian wheezy (testing on clients)

Pol

[toc] | [prev] | [next] | [standalone]

#167644

On Mon 09 May 2016 at 21:49:17 +0200, Pol Hallen wrote:

> >Set up the clients to discover the server. Print.
> 
> ehm... not it so easy: from client I see network printer (shared by server)
> but after installed it I can't print.
> 
> On client I see "printer not connected" and on the server no logs file.
> 
> I also checked iptables rules but I've same problem :-/
> 
> thanks for help!
> 
> PS: on server I use debian wheezy (testing on clients)

Please post the outputs of 'lpstat -t' on the server and a client.

[toc] | [prev] | [next] | [standalone]

#167666

> Please post the outputs of 'lpstat -t' on the server and a client.

scheduler is running
system default destination: T640
device for PDF: cups-pdf:/
device for T640: socket://192.168.1.220:9100
PDF accepting requests since Mon 09 May 2016 07:25:03 PM CEST
T640 accepting requests since Tue 10 May 2016 01:00:30 PM CEST
printer PDF is idle.  enabled since Mon 09 May 2016 07:25:03 PM CEST
printer T640 is idle.  enabled since Tue 10 May 2016 01:00:30 PM CEST


Pol

[toc] | [prev] | [next] | [standalone]

#167669

On Tue 10 May 2016 at 13:12:14 +0200, Pol Hallen wrote:

> >Please post the outputs of 'lpstat -t' on the server and a client.
> 
> scheduler is running
> system default destination: T640
> device for PDF: cups-pdf:/
> device for T640: socket://192.168.1.220:9100
> PDF accepting requests since Mon 09 May 2016 07:25:03 PM CEST
> T640 accepting requests since Tue 10 May 2016 01:00:30 PM CEST
> printer PDF is idle.  enabled since Mon 09 May 2016 07:25:03 PM CEST
> printer T640 is idle.  enabled since Tue 10 May 2016 01:00:30 PM CEST

Two outputs were asked for. Would you post the one for a client.

[toc] | [prev] | [next] | [standalone]

#167638

On Mon 09 May 2016 at 20:30:28 +0100, Brian wrote:

> On Mon 09 May 2016 at 21:15:50 +0200, Pol Hallen wrote:
> 
> > Hi all :)
> > 
> > I've a cups printer server (192.168.1.10) with a network printer connected
> > (192.168.1.200). From that server I can print.
> > 
> > how I have to configure the clients to print by that server?
> 
> Set up the clients to discover the server. Print.

That was bad piece of advice. Your Jessie server will broadcast its
printers if they are shared. Your Jessie clients will automaticlly
pick them up.

[toc] | [prev] | [next] | [standalone]

#167636

On Mon, May 09, 2016 at 09:15:50PM +0200, Pol Hallen wrote:
> Hi all :)
> 
> I've a cups printer server (192.168.1.10) with a network printer connected
> (192.168.1.200). From that server I can print.
> 
> how I have to configure the clients to print by that server?
> 
Unless I am misunderstanding the question, first go to the CUPS web
interface, click "add printer," choose (if your networked printer(s) are
not automatically detected) "AppSocket,", then in the "Connection" box
insert the printer's IP (e.g., socket://192.168.1.200).  Click 
"continue" to finish up.

[toc] | [prev] | [next] | [standalone]

#167639

> Unless I am misunderstanding the question,

I need to print using 192.168.1.10 (server) not directly by network printer

thanks!


Pol

[toc] | [prev] | [next] | [standalone]

#167641

Pol Hallen wrote:

>> Unless I am misunderstanding the question,
> 
> I need to print using 192.168.1.10 (server) not directly by network
> printer
> 
> thanks!
> 
> 
> Pol

Hi

In /etc/cups/client.conf

set the ServerName

ServerName 192.168.1.10

try lpstat -a

$  lpstat -a
HP_LaserJet_5L accepting requests since Wed 04 May 2016 10:31:02 PM CEST

regards

[toc] | [prev] | [next] | [standalone]

#167645

On Mon 09 May 2016 at 23:45:18 +0200, deloptes wrote:

> Pol Hallen wrote:
> 
> >> Unless I am misunderstanding the question,
> > 
> > I need to print using 192.168.1.10 (server) not directly by network
> > printer
> > 
> > thanks!
> > 
> > 
> > Pol
> 
> Hi
> 
> In /etc/cups/client.conf
> 
> set the ServerName
> 
> ServerName 192.168.1.10
> 
> try lpstat -a
> 
> $  lpstat -a
> HP_LaserJet_5L accepting requests since Wed 04 May 2016 10:31:02 PM CEST

The OP talks about *"clients"*. Would your advice stay the same if there
was a 1000 of them?

[toc] | [prev] | [next] | [standalone]

#167649

On Mon 09 May 2016 at 23:22:44 (+0100), Brian wrote:
> On Mon 09 May 2016 at 23:45:18 +0200, deloptes wrote:
> > Pol Hallen wrote:
> > >> Unless I am misunderstanding the question,
> > > I need to print using 192.168.1.10 (server) not directly by network printer

> > In /etc/cups/client.conf
> > 
> > set the ServerName
> > 
> > ServerName 192.168.1.10
> > 
> > try lpstat -a
> > 
> > $  lpstat -a
> > HP_LaserJet_5L accepting requests since Wed 04 May 2016 10:31:02 PM CEST
> 
> The OP talks about *"clients"*. Would your advice stay the same if there
> was a 1000 of them?

Your first and last comments were too terse for me to understand. I
think you might be implying here that the solution doesn't scale well.
Can you explain the difference between the purported solution above
and your earlier "Set up the clients to discover the server. Print.",
ie how "Set up"?

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#167662

On Mon 09 May 2016 at 20:01:28 -0500, David Wright wrote:

> On Mon 09 May 2016 at 23:22:44 (+0100), Brian wrote:
> > On Mon 09 May 2016 at 23:45:18 +0200, deloptes wrote:
> > > Pol Hallen wrote:
> > > >> Unless I am misunderstanding the question,
> > > > I need to print using 192.168.1.10 (server) not directly by network printer
> 
> > > In /etc/cups/client.conf
> > > 
> > > set the ServerName
> > > 
> > > ServerName 192.168.1.10
> > > 
> > > try lpstat -a
> > > 
> > > $  lpstat -a
> > > HP_LaserJet_5L accepting requests since Wed 04 May 2016 10:31:02 PM CEST
> > 
> > The OP talks about *"clients"*. Would your advice stay the same if there
> > was a 1000 of them?
> 
> Your first and last comments were too terse for me to understand. I
> think you might be implying here that the solution doesn't scale well.

The advice is fine as far as it goes and should work. It is a technique
I use myself on a machine or two when I do not want a local cupsd or
prefer not to have avahi-daemon on a print server with limited
resources.

Scaling is an issue and I do not know how one efficiently adopts to
adding large number of clients or a change in the server's IP. The
assumption is also being made that the server is online and available.

Visitors on a network would have to be informed of the IP; this may be a
hassle for them, particularly if they are unfamiliar with the device
they are using or not comfortable with altering its settings. Visiting
Big Company Boss would likely not be amused having to take a lesson in
network configuration just to print.

The reality is that mobile devices (laptops, phones etc) are probably
more numerous than desktops. Linking them with a single infrastructure
and pointing to a single server negates the advantages they have for
printing. Devices using AirPrint should immediately be at home with
Debian CUPS and really have no need of a client.conf.

Also, if the network is down or there are network errors or the server
is not available, the application may not retry and printing will be
prevented. A user closing the lid on a laptop before an application has
finished submitting a job is to be avoided; the job isn't going
anywhere.

> Can you explain the difference between the purported solution above
> and your earlier "Set up the clients to discover the server. Print.",
> ie how "Set up"?

With a local cupsd a job can be queued and recovery from temporary
issues is much easier. The local cupsd can coordinate with the OS to
keep the system (and network stack) up long enough to send the job
remotely. The client software can adapt to the network/location more
easily (for example, when roaming). What is displayed in print
dialogues of applications is what is actually online, not what may
have disappeared a week ago and which you now have to re-locate.

The "Set up" on a Jessie client consists of

  apt-get install cups

The default for the installation is for print queues on a remote server
to be offered by applications or displayed by 'lpstat -a'. Immediate
printing capability, in other words.

[toc] | [prev] | [next] | [standalone]

#167651

Brian wrote:

> On Mon 09 May 2016 at 23:45:18 +0200, deloptes wrote:
> 
>> Pol Hallen wrote:
>> 
>> >> Unless I am misunderstanding the question,
>> > 
>> > I need to print using 192.168.1.10 (server) not directly by network
>> > printer
>> > 
>> > thanks!
>> > 
>> > 
>> > Pol
>> 
>> Hi
>> 
>> In /etc/cups/client.conf
>> 
>> set the ServerName
>> 
>> ServerName 192.168.1.10
>> 
>> try lpstat -a
>> 
>> $  lpstat -a
>> HP_LaserJet_5L accepting requests since Wed 04 May 2016 10:31:02 PM CEST
> 
> The OP talks about *"clients"*. Would your advice stay the same if there
> was a 1000 of them?

I do not have any better solution - this autodiscovery did not work for me
and setting the ServerName in client.conf works.
If he has 1000 - he has to manage them automatically anyway - or what do you
do in such a case?
Anyway I'll be glad to have better solution

regards

[toc] | [prev] | [next] | [standalone]

#167664

>> try lpstat -a

T640 accepting requests since Mon 09 May 2016 07:29:09 PM CEST

Pol

[toc] | [prev] | [next] | [standalone]

#167671

On Tue 10 May 2016 at 12:58:13 +0200, Pol Hallen wrote:

> >>try lpstat -a
> 
> T640 accepting requests since Mon 09 May 2016 07:29:09 PM CEST

Please test from your client with

  lp -d T640 ~/.profile

Does the file print?

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web