bogus "No protocol specified" message

Fri Jan 11 02:03:22 UTC 2013

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/