Has anyone looked to see if j2ssh client talks to the local X server via TCP?
Most X servers (outside of standalone X terminals) don't listen for TCP
connections anymore, by default. Instead they either use shared memory
or Unix domain sockets.
OpenSSH will connect to the local X server by what ever works, and the
OpenSSH server emulates a TCP based X server.
I have some applications that do not run via OpenSSH X forwarding. The
X server emulation is not complete and I get bad X calls reported. They work
fine localy. PerlTK seems to be this way. (Invalid Atoms reported.)
On 5/13/05, Andre Charbonneau <andre.charbonneau@nrc-cnrc.gc.ca> wrote:
Hi,
If I connect to a openssh server (SSH-1.99-OpenSSH_3.8p1, running on
SuSE Linux 9.1 (i586)) using a openssh client (OpenSSH_3.9p1, OpenSSL
0.9.7d 17 Mar 2004, running on SuSE Linux 9.2 (i586)), then X11
forwarding works fine.
But, if I use j2ssh as a ssh client to connect to the same sshd, then I
get the following error in the sshd debug output:
debug1: channel 3: new [X11 connection from 127.0.0.1 port 36470]
channel 3: open failed: connect failed: Connection refused
I've been trying to find what might be the problem for a few days now
but with no success.
I understand that this is not the place to ask questions about j2ssh.
But what I would like to know is the following: In general, is there a
well known condition, either at the client or server side, which would
cause such a 'connection refused'?
Thanks,
Andre
--
Andre Charbonneau
100 Sussex Drive, Rm 2025
Research Computing Support, IMSB
National Research Council Canada
Ottawa, ON, Canada K1A 0R6
613-993-3129 Fax: 613-993-3127
--
END OF LINE
-MCP
