Ismael Valladolid Torres wrote:
-
Make an ssh connection to the remote machine with the -X option. Echo
$DISPLAY and if you don't see something like "localhost:10.0" then
the ssh daemon is not configured for tunneling X.
The ssh daemon allocates local virtual displays 10 and up
El lunes 27 de enero de 2003 a las 20:56:32, Thomas Schweikle escribió:
> Not that this is sure to solve your problem, but it's a possibility:
> ssh daemons can be configured to prohibit X forwarding.
Make an ssh connection to the remote machine with the -X option. Echo
$DISPLAY and if you don't s
Hi!
> Not that this is sure to solve your problem, but it's a possibility:
> ssh daemons can be configured to prohibit X forwarding. Try
>
> ssh -v -l
Use the above if your sure you enabled x-forwarding in your ~/.ssh/config
or in /etc/ssh/ssh_config. If not, a better idea would be to use
Patrick Nelson wrote:
-
My other Linux systems can connect to the remote sshd. Here is the output
of a call:
---snip--
debug1: Sending command: evolution
debug1: channel request 0: exec
debug1: channel 0: open confirm rwindow 0 rmax 32768
debug1: channel 0: rcvd e
[EMAIL PROTECTED] wrote:
-
Not that this is sure to solve your problem, but it's a possibility:
ssh daemons can be configured to prohibit X forwarding. Try
ssh -v -l
to see what ssh reports regarding whether X forwarding was actually
established, and/or check the sshd_co
Not that this is sure to solve your problem, but it's a possibility:
ssh daemons can be configured to prohibit X forwarding. Try
ssh -v -l
to see what ssh reports regarding whether X forwarding was actually
established, and/or check the sshd_config file on the remote machine
(if you have p
6 matches
Mail list logo