From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([69.77.167.62] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1LFSBv-0001su-Fn for garchives@archives.gentoo.org; Wed, 24 Dec 2008 11:46:19 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id ADEB4E05C1; Wed, 24 Dec 2008 11:46:16 +0000 (UTC) Received: from mail.ukfsn.org (mail.ukfsn.org [77.75.108.10]) by pigeon.gentoo.org (Postfix) with ESMTP id 82738E05C1 for ; Wed, 24 Dec 2008 11:46:16 +0000 (UTC) Received: from localhost (smtp-filter.ukfsn.org [192.168.54.205]) by mail.ukfsn.org (Postfix) with ESMTP id E1748DEE2F for ; Wed, 24 Dec 2008 11:46:17 +0000 (GMT) Received: from mail.ukfsn.org ([192.168.54.25]) by localhost (smtp-filter.ukfsn.org [192.168.54.205]) (amavisd-new, port 10024) with ESMTP id XfRD5MoFKt53 for ; Wed, 24 Dec 2008 10:51:41 +0000 (GMT) Received: from wstn.ethnet (unknown [78.32.181.186]) by mail.ukfsn.org (Postfix) with ESMTP id B99D0DED72 for ; Wed, 24 Dec 2008 11:46:17 +0000 (GMT) From: Peter Humphrey Organization: at home To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Network printing Date: Wed, 24 Dec 2008 11:45:04 +0000 User-Agent: KMail/1.9.9 References: <200812221125.39755.peter@humphrey.ukfsn.org> <200812240925.36849.peter@humphrey.ukfsn.org> <200812241046.17948.michaelkintzios@gmail.com> In-Reply-To: <200812241046.17948.michaelkintzios@gmail.com> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200812241145.04996.peter@humphrey.ukfsn.org> X-Archives-Salt: 4a498688-d55f-4f11-a6cc-0b4a28c4749b X-Archives-Hash: 4c7bda565e7dfc81aac0afe0cd65dbfa On Wednesday 24 December 2008 10:45:58 Mick wrote: > 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. (There's always one more detail that gets forgotten.) I am pointing my client to serv.ethnet, not any IP address. It decides for itself, part-way through setting-up the printer, that it's now connected to a different host from before. > Either way - if you disable authentication with SSL this problem will go > away. - but remain unsolved. Thanks anyway. -- Rgds Peter