From owner-freebsd-questions@FreeBSD.ORG  Fri Jan 11 02:03:22 2013
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115])
 by hub.freebsd.org (Postfix) with ESMTP id 3CC2B998
 for <freebsd-questions@freebsd.org>; Fri, 11 Jan 2013 02:03:22 +0000 (UTC)
 (envelope-from cyberleo@cyberleo.net)
Received: from paka.cyberleo.net (mtumishi.cyberleo.net [216.226.128.201])
 by mx1.freebsd.org (Postfix) with ESMTP id 1E96C7F2
 for <freebsd-questions@freebsd.org>; Fri, 11 Jan 2013 02:03:21 +0000 (UTC)
Received: from [172.16.44.4] (den.cyberleo.net [216.80.73.130])
 by paka.cyberleo.net (Postfix) with ESMTPSA id B36AC122928;
 Thu, 10 Jan 2013 19:45:19 -0500 (EST)
Message-ID: <50EF609F.1090306@cyberleo.net>
Date: Thu, 10 Jan 2013 18:45:19 -0600
From: CyberLeo Kitsana <cyberleo@cyberleo.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:10.0.11) Gecko/20121201 Thunderbird/10.0.11
MIME-Version: 1.0
To: Perry Hutchison <perryh@pluto.rain.com>
Subject: Re: bogus "No protocol specified" message
References: <50ef3c36.DOThr42hGxWWeg6h%perryh@pluto.rain.com>
In-Reply-To: <50ef3c36.DOThr42hGxWWeg6h%perryh@pluto.rain.com>
X-Enigmail-Version: 1.3.5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: freebsd-questions@freebsd.org
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Jan 2013 02:03:22 -0000

On 01/10/2013 05:09 PM, Perry Hutchison wrote:
> When trying to open an X application on a remote display,
> I am getting
> 
>     No protocol specified
>     Error: cannot open display: 192.168.200.61:0
> 
> The "No protocol specified" message is bogus:  the display is
> specified correctly*, and the same operation -- with exactly
> the same setting of DISPLAY -- was working yesterday.  There's
> no problem with network connectivity between the two systems:
> ping and rlogin both work in either direction, and the specified
> X server is running and accepting connections.
> 
> What does that message actually mean, and how do I fix it?

The error is with regards to the X protocol, not the TCP or UNIX socket
protocol. Check that both sides have compatible and matching X authority
information using xauth(1), or that the connecting host or user was
allowed to connect using xhost(1).

-- 
Fuzzy love,
-CyberLeo
Furry Peace! - http://www.fur.com/peace/