On Tue, 2003-10-07 at 19:14, Colin Watson wrote:
> On Tue, Oct 07, 2003 at 05:13:18PM -0400, Shaun ONeil wrote:
> > I know I've done this plenty of times before, but this time it's just
> > not playing ball. Any hints?
> > [EMAIL PROTECTED]:~$ dpkg --get-selections | grep ^x
> > xfree86-common
On Tue, Oct 07, 2003 at 05:13:18PM -0400, Shaun ONeil wrote:
> I know I've done this plenty of times before, but this time it's just
> not playing ball. Any hints?
>
> "desktop" Is Debian sid, with a display running on :0
> "server" is Debian woody, and headless (hence using ssh)
>
> I've tried w
I know I've done this plenty of times before, but this time it's just
not playing ball. Any hints?
"desktop" Is Debian sid, with a display running on :0
"server" is Debian woody, and headless (hence using ssh)
I've tried with and without passing -X to ssh, and I understand my
entries in ssh_confi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
I'm running the latest unstable here on my computer with the Debian 2.4.8-k7
Kernel, but now I got a big problem: For quite a few days, X-forwarding no
longer works with ssh. It is enabled, and everything should be fine, but for
some reason t
Tom Cook wrote:
Vineet Kumar wrote:
[snip]
Also, please, please, PLEASE! DON'T do this:
local$ ssh remote
remote$ export DISPLAY=local:0 # DON'T EVER DO THIS!!!
remote$ xterm
As others have already explained. You might as well be using telnet.
This defeats the entire purpose of tunneling. Wha
Vineet Kumar wrote:
[snip]
> Also, please, please, PLEASE! DON'T do this:
>
> local$ ssh remote
> remote$ export DISPLAY=local:0 # DON'T EVER DO THIS!!!
> remote$ xterm
>
> As others have already explained. You might as well be using telnet.
> This defeats the entire purpose of tunneling. What yo
* steve downes ([EMAIL PROTECTED]) [020305 01:10]:
> debug1: Requesting X11 forwarding with authentication spoofing.
that looks good.
> [EMAIL PROTECTED]:~$ xterm
> xterm Xt error: Can't open display:
> [EMAIL PROTECTED]:~$ vncviewer
> Error: Can't open display:
> [EMAIL PROTECTED]:~$
Tha
On Wed, 6 Mar 2002, Tom Cook wrote:
> My 2 bits worth of experience:
> [EMAIL PROTECTED]:~$ xterm
> xterm Xt error: Can't open display:
This shouldn't be happening; my results:
nujoma:~> ssh -v -X geingob
SSH Version OpenSSH-1.2.3, protocol version 1.5.
...
[EMAIL PROTECTED]:~$ xterm
debug: Re
steve downes wrote:
>
> Tried the -v option & all seemd OK. (listed below) It seems to be
> allowing X.
>
> However it still isn't functioning.
>
> Sorry for the delay, I decided it might be policy to upgrade the
> server to Woody before carrying on but the only difference in this
> context is t
Tried the -v option & all seemd OK. (listed below) It seems to be
allowing X.
However it still isn't functioning.
Sorry for the delay, I decided it might be policy to upgrade the
server to Woody before carrying on but the only difference in this
context is the error message now no longer says er
Try the -v flag to ssh to see what it's trying to do:
ssh -v -X remote.host
this will let you watch the steps ssh is going through to try to debug the
connection.
If the remote host is configured correctly to allow X forwarding, you will
not have to set DISPLAY. Setting DISPLAY to local:0.0 will
Tried everything in this thread (& more besides)but the closest I get
is:-
[EMAIL PROTECTED]:~$ xterm &
[1] 19419
[EMAIL PROTECTED]:~$ _X11TransSocketINETConnect: Can't connect: errno = 101
xterm Xt error: Can't open display: fileserver:10.0
I have opened X11 in ssh_config & sshd_config in both
On Fri, 1 Mar 2002, Tom Cook wrote:
>> Currently when I try to run X apps via an ssh login I get the error message
>>
>> xterm Xt error: Can't open display:
>desk.host: # xhost +remove.host.domain.com
>desk.host: # ssh -X remote.host.domain.com -l myaccount
>[EMAIL PROTECTED]'s password: **
Tom Cook <[EMAIL PROTECTED]> writes:
> It doesn't sound like a problem with ssh to me, it sounds like you
> haven't set the DISPLAY variable correctly, and therefore probably
> haven't run xhost either.
If ssh X forwarding is enabled, the sshd on the remote end should
automatically set a correct (
Nick Wright wrote:
> Hi there.
>
> Currently when I try to run X apps via an ssh login I get the error message
>
> xterm Xt error: Can't open display:
>
> Is this a problem with ssh and my x-forwarding?
> if so, how do you change the x-forwarding options in ssh?
> if not, what is the problem and
A couple of comments.
1. If you have root access on the server machine, you can edit the ssh_config
and sshd_config files to turn on X11Forwarding. You should also do that on your
machine.
If this is done, I have had it the case that X forwarding has not required
setting up the DISPLAY variab
Nick Wright <[EMAIL PROTECTED]> writes:
> Hi there.
>
> Currently when I try to run X apps via an ssh login I get the error message
>
> xterm Xt error: Can't open display:
>
> Is this a problem with ssh and my x-forwarding?
> if so, how do you change the x-forwarding options in ssh?
> if not
Ok, I was actually running ssh with the -X option and it wasn't working then
either.
I've noticed that when I ssh to the box in question I get this message:
Warning: Remote host denied X11 forwarding.
The display variable is not being set either.
Exporting the display variable manually does wo
The default doesn't do X-forwarding.
ssh -X remote.machine
does. I never bothered to track down the config file where -X could be
made default but I'm pretty sure there is one.
On Fri, 1 Mar 2002, Nick Wright wrote:
> Currently when I try to run X apps via an ssh login I get the error message
>
Nick Wright wrote:
>
> Hi there.
>
> Currently when I try to run X apps via an ssh login I get the error message
>
> xterm Xt error: Can't open display:
>
> Is this a problem with ssh and my x-forwarding?
> if so, how do you change the x-forwarding options in ssh?
> if not, what is the proble
Probably.
Try
ssh -X (remote host)
If it still doesn't work, then either your X server is screwed up or the
remote host isn't allowing X packets to be forwarded.
--
Andrew J Perrin - [EMAIL PROTECTED] - http://www.unc.edu/~ape
Hi there.
Currently when I try to run X apps via an ssh login I get the error message
xterm Xt error: Can't open display:
Is this a problem with ssh and my x-forwarding?
if so, how do you change the x-forwarding options in ssh?
if not, what is the problem and how do I fix it? :)
thanks,
Nic
For people who care: I figured it out.
It seems that since I upgraded to testing lo (loopback interface) isn't
broadup at boottime. I don't understand why by the way. I have a line
saying 'auto lo' in my /etc/network/interfaces.
Further more I had to make a line 'ALL : 127.0.0.1' in my
etc/
Tim Dijkstra, 2001-Nov-16 23:52 +0100:
> nate wrote:
>
> >Tim Dijkstra said:
> >
> >
> >>debug1: Requesting pty.
> >>debug1: Requesting X11 forwarding with authentication spoofing.
> >>debug1: Requesting shell.
> >>debug1: Entering interactive session.
> >>
> >>Is that enough? Does anybody with X-
nate wrote:
Tim Dijkstra said:
debug1: Requesting pty.
debug1: Requesting X11 forwarding with authentication spoofing.
debug1: Requesting shell.
debug1: Entering interactive session.
Is that enough? Does anybody with X-forw working correctly gets the
same output?
pretty much. how bout w
Tim Dijkstra said:
> debug1: Requesting pty.
> debug1: Requesting X11 forwarding with authentication spoofing.
> debug1: Requesting shell.
> debug1: Entering interactive session.
>
> Is that enough? Does anybody with X-forw working correctly gets the
> same output?
pretty much. how bout when yo
Hi,
I posted something about this problem a while ago, but I'am still stuck.
The problem is that X-forwarding stopt working when I upgraded from
potato to testing. I tried downgrading ssh and the x-server, but didn't
help. I now even tried ssh-nonfree, still nothing.
OK, what is supposed to
27 matches
Mail list logo
