From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Network printing
Date: Wed, 24 Dec 2008 10:45:58 +0000 [thread overview]
Message-ID: <200812241046.17948.michaelkintzios@gmail.com> (raw)
In-Reply-To: <200812240925.36849.peter@humphrey.ukfsn.org>
[-- Attachment #1: Type: text/plain, Size: 1569 bytes --]
On Wednesday 24 December 2008, Peter Humphrey wrote:
> On Wednesday 24 December 2008 00:03:46 Mick wrote:
> > If you are using SSL certificates you must set up the correct domain
> > name, with regards to what the client machines see on the intranet/LAN.
> > Clearly the IP address is not a FQDN and the certificate check fails.
> > So, you want your common name (CN = serv.ethnet or whatever) to be the
> > same with the name that your server is seen by the client in the LAN and
> > this may involve setting up your router to resolve serv.ethnet to
> > 192.168.2.2, or adding an entry in your client's /etc/hosts file to this
> > effect.
>
> I'm not using SSL certificates, or not as far as I know.
Well, if you are getting security error messages about security certificates
as per your previous email, I would think that you have inadvertently perhaps
configured SSL connections to your CUPS server?
> Every host on the
> LAN has serv.ethnet in its hosts file, and dnsmasq on the gateway also
> knows about it - of course. The problem is not in name resolving. Both the
> cups server and the box running the Web browser are on the same LAN
> segment. I've just checked all the boxes' hosts files and they're all
> correct.
It could still be a machine naming issue if you are pointing your client to
e.g. http://192.168.2.2:631 instead of http://serv.ethnet:631 - which is what
I suspect the SSL certificate's CN record shows. Either way - if you disable
authentication with SSL this problem will go away.
--
Regards,
Mick
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-12-24 10:46 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2008-12-24 11:45 ` Peter Humphrey
2008-12-24 19:31 ` Mark Knecht
2008-12-28 12:47 ` Peter Humphrey
-- strict thread matches above, loose matches on Subject: below --
2009-01-06 15:39 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ß
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
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=200812241046.17948.michaelkintzios@gmail.com \
--to=michaelkintzios@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