It is probably an ssh1 vs. ssh2 issue. The two versions have almost nothing in common.
The ssh2 server can be configured to call an ssh1 server if it sees a ssh1 client, but
that's all there is. After that initial call they never talk to each other again.
Check that your ssh2 environment can make X forwarding. You will need proper configure
parameters and include libraries when compiling both client and server, and you have
to check the run time config files as well. Try running the server with debug logging
and the client with the verbose option.
Amanda.
On Mon, 22 May 2000, Phil Hurvitz wrote:
> I'm having trouble with X forwarding using SSH Secure Shell 2.1.0 (Build
> 111).
>
> There is nothing in any of my UNIX startup scripts that set a DISPLAY env.
> var. After I make a successful ssh connection, the ssh client does not
> automatically set the DISPLAY var. I get errors when I attempt to start
> an X app. The errors indicate that the DISPLAY variable is undefined, or
> the Xt error "Can't open display:"
>
> I do have "Tunnel X11 connections" checked, and I did quit and restart the
> ssh client.
>
> However, when I use TeraTerm to connect to the same servers, the DISPLAY
> variable is set properly, and X apps forward correctly.
>
> After looking at what TeraTerm has set the DISPLAY to, I can manually set
> this in the ssh client, and get an X display. However, I thought this was
> supposed to happen automatically. It seems strange that a 3rd party
> client software works better in this instance than client software written
> by the same folks who wrote the server.
>
> Or is this perhaps an ssh1 vs. ssh2 issue? One of the servers I'm
> connecting to only runs ssh1, therefore only TeraTerm , and, not the SSH
> Secure Shell client will make a connection. I'm assuming that TeraTerm
> uses ssh1?
