Hi all,

I usually log in to my machines remotely by typing the following:

	ssh -X host.example.com

(Assuming I'm logged in as me locally.)

This has worked for AGES, but the last weekend I installed the
latest S9 Recommended and Security patch cluster on the server.
(The patch cluster was from June 17 or thereabouts.)

Tonight, trying exactly the same command results in me getting kicked
out, and the following message being put into /var/adm/messages:

[ID 800047 auth.error] error: Failed to allocate internet-domain X11 display socket.

If I get rid of the -X option, I can login OK (hence I can send this message!).
I checked the sshd_config file, and X forwaring is still enabled.
DOes any one have any ideas?

Incidentally, I'm using SUn's ssh server and the ssh client that comes with
build 16 of Nevada.

TIA,

-- 
Rich Teer, SCNA, SCSA, OpenSolaris CAB member

President,
Rite Online Inc.

Voice: +1 (250) 979-1638
URL: http://www.rite-group.com/rich

Rich Teer wrote:

> [ID 800047 auth.error] error: Failed to allocate internet-domain X11 display socket.
> 
> If I get rid of the -X option, I can login OK (hence I can send this message!).
> I checked the sshd_config file, and X forwaring is still enabled.
> DOes any one have any ideas?

Try forcing sshd to have IPV4 support *only* by starting it with " -4"
as a command line argument.

JS

Rich Teer wrote:
> Hi all,
> 
> I usually log in to my machines remotely by typing the following:
> 
> 	ssh -X host.example.com
> 
> (Assuming I'm logged in as me locally.)
> 
> This has worked for AGES, but the last weekend I installed the
> latest S9 Recommended and Security patch cluster on the server.
> (The patch cluster was from June 17 or thereabouts.)
> 
> Tonight, trying exactly the same command results in me getting kicked
> out, and the following message being put into /var/adm/messages:
> 
> [ID 800047 auth.error] error: Failed to allocate internet-domain X11 display socket.
> 
> If I get rid of the -X option, I can login OK (hence I can send this message!).
> I checked the sshd_config file, and X forwaring is still enabled.
> DOes any one have any ideas?
> 
> Incidentally, I'm using SUn's ssh server and the ssh client that comes with
> build 16 of Nevada.
> 
> TIA,
> 
There's a thread in SUN's support forum that discusses this and
indicates that forcing IPV4 will "ssh -4 ..." works around this
problem.

http://supportforum.sun.com/salerts/index.php?t=msg&goto=1963&rid=0