I'd be most grateful for any advice on the following:

  We are finding that X11 forwarding works only about 1 times out of 10,
apparently at random, (between an Alpha [local machine] and another Alpha or a
Solaris machine).  Using "ssh2 -v" (see examples of unsuccessful and successful
connections below) indicates that the local xauth data is not being found when
X11 forwarding fails.

  We are using ssh2.3.0, by the way.

--
Rex Godby                             Tel. (+44) (0)1904 432231
Department of Physics                 Fax  (+44) (0)1904 432214
University of York                    E-mail [EMAIL PROTECTED]
York YO10 5DD, U.K.                   http://www-users.york.ac.uk/~rwg3/

===

ssh2 -v host (*unsuccessful* X11 forwarding, happens 9 times out of 10)
-----------------------------------------------------------------------
Authentication successful.
debug: Ssh2Common/sshcommon.c:686: num_channels now 1
debug: Requesting X11 forwarding with authentication spoofing.  [SEE NOTE BELOW]
debug: Failed to get local xauth data.
debug: ssh_sigchld_real_callback
...
> xterm&
[1] 2540
> debug: Ssh2Common/sshcommon.c:686: num_channels now 2
debug: Ssh2Common/sshcommon.c:660: num_channels now 1
X connection to xxxx.york.ac.uk:10.0 broken (explicit kill or server shutdown).

NOTE: using the higher debug level "-d 99" gives the following additional
information after this line:
debug: SshEventLoop/sshunixeloop.c:248: Got signal number: 20


ssh2 -v host (*successful* X11 forwarding, happens 1 times out of 10)
---------------------------------------------------------------------
Authentication successful.
debug: Ssh2Common/sshcommon.c:686: num_channels now 1
debug: Requesting X11 forwarding with authentication spoofing.
debug: ssh_sigchld_real_callback
debug: ssh_sigchld_process_pid: no handler for pid 1982 code 0
...
> xterm&
[1] 2236
> debug: Ssh2Common/sshcommon.c:686: num_channels now 2

Reply via email to