public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Mark Knecht" <markknecht@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Sharing a CUPS printer
Date: Mon, 18 Sep 2006 18:38:08 -0700	[thread overview]
Message-ID: <5bdc1c8b0609181838j4dfbc7bv9685bce698734b5b@mail.gmail.com> (raw)
In-Reply-To: <b69857cf0609181719n661af42dl242ddfa7828131a5@mail.gmail.com>

On 9/18/06, Sarpy Sam <sarpy.sam@gmail.com> wrote:
<SNIP>
>
> Maybe port 631 will work here, I have it set to Listen *.631

Changed it to

Listen *:631

and restarted CUPS on the server.

<SNIP>
>
> On the client mahines you want to comment out the listen localhost:631
> line in cupsd.conf.  Then you want to make a file in /etc/cups called
> client.conf.  Insert in it
>
> ServerName  *****

Ah! OK, that makes sense. I changed it appropriately, restarted CUPS
on the client machine and now I get this far:

mark@dragonfly ~ $ lpq
HP is ready
no entries
mark@dragonfly ~ $ lpstat -a
HP accepting requests since Jan 01 00:00
mark@dragonfly ~ $

So far this looks OK. However, if I go into the CUPS manager on the
client and try to print a test page it's telling me the printer is not
available.

Any ideas? I guess you can print a test page from within the CUPS
manager on the client?

Thanks a lot for this much. It's helpful.

- Mark
-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2006-09-19  1:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-18 23:48 [gentoo-user] Sharing a CUPS printer Mark Knecht
2006-09-19  0:19 ` Sarpy Sam
2006-09-19  1:38   ` Mark Knecht [this message]
2006-09-19  2:06     ` Sarpy Sam
2006-09-19 16:37       ` Mark Knecht
     [not found]     ` <7573e9640609181943j640398bev63dfaa831a992842@mail.gmail.com>
2006-09-19  7:49       ` [gentoo-user] " Stefan Wimmer
2006-09-19 10:46     ` [gentoo-user] " Sarpy Sam
2006-09-19  8:26 ` Mick
2006-09-19 11:05   ` Nick Rout

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=5bdc1c8b0609181838j4dfbc7bv9685bce698734b5b@mail.gmail.com \
    --to=markknecht@gmail.com \
    --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