public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Norman Rieß" <norman@smash-net.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Network printing
Date: Mon, 12 Jan 2009 12:24:25 +0100	[thread overview]
Message-ID: <496B2869.6090700@smash-net.org> (raw)
In-Reply-To: <200901121044.52958.peter@humphrey.ukfsn.org>

Peter Humphrey schrieb:
> Are you telling me that the printers the server knows of should appear in 
> the client's cups web page automatically? That certainly doesn't happen, 
> which is why I've been trying to tell the client where to find its 
> printers.
>
>   
No the webpage only runs on the server which is connected to the printers.
On that page, you should be able to see all printers connected to that
server. If not, then you have to add them.

The only thing you have to tell the clients is the name of your server
the printers are connected to in the client.conf file.
The applications on the client should see all printers on the server
automatically then.
The cupsd doesn't even need to be started on the clients.
> This looks important (trimming time & date etc.):
> cupsdAcceptClient: 8 from 192.168.2.6:631 (IPv4)
> cupsdReadClient: 8 POST / HTTP/1.1
> cupsdAuthorize: No authentication data provided.
> cupsdSendError: 8 code=403 (Forbidden)
> cupsdCloseClient: 8
>
> (The log is taken from the server after running lpstat -a on the client; the 
> IPv4 address shown is the client.)
>
> What kind of authentication data does that mean? User ID confirmation? SSH 
> keys? As far as I know I haven't done anything particular to SSH or SSL. The 
> Gentoo printing guide doesn't mention gnutls or ldap, so I haven't set them 
> up, or even installed them.
>   
>
I assume the printers are not configured correctly on the server.
When i am home from work i will be able to provide some screenshots to
make things clearer.

Regards
Norman




  reply	other threads:[~2009-01-12 11:24 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-06 15:39 [gentoo-user] Network printing Peter Humphrey
2009-01-06 17:04 ` Mark Knecht
2009-01-07 12:08   ` Peter Humphrey
2009-01-07 14:20     ` BRM
2009-01-10 12:15       ` Peter Humphrey
2009-01-10 12:56         ` Norman Rieß
2009-01-12 10:44           ` Peter Humphrey
2009-01-12 11:24             ` Norman Rieß [this message]
2009-01-12 20:12               ` Norman Rieß
2009-01-13 10:38                 ` Peter Humphrey
2009-01-13 14:19                   ` Norman Rieß
2009-01-13 17:46                     ` Peter Humphrey
2009-01-13 18:36                       ` Norman Rieß
2009-01-14  8:58                         ` Mick
2009-01-15 10:39                           ` Peter Humphrey
2009-01-15 14:50                             ` Mick
2009-01-12 14:25             ` BRM
2009-01-13 10:42               ` Peter Humphrey
2009-01-07 15:03     ` Mark Knecht
2009-01-06 18:44 ` BRM
2009-01-19 16:08 ` [gentoo-user] Network printing -- Solved Peter Humphrey
  -- strict thread matches above, loose matches on Subject: below --
2008-12-22 11:25 [gentoo-user] Network printing Peter Humphrey
2008-12-22 18:00 ` BRM
2008-12-23 11:53   ` Peter Humphrey
2008-12-24  0:03     ` Mick
2008-12-24  9:25       ` Peter Humphrey
2008-12-24 10:45         ` Mick
2008-12-24 11:45           ` Peter Humphrey
2008-12-24 19:31             ` Mark Knecht
2008-12-28 12:47               ` Peter Humphrey

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=496B2869.6090700@smash-net.org \
    --to=norman@smash-net.org \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox