Brett Serkez wrote:
But now I just realized the obvious: Only X GUIS work and not windows.
Is this correct?
Yes!
I assume I can tunnel rdesktop the same way I tunnel vnc? I guess I'll try
tunneling both vnc and rdesktop next.
I've heard this works, but have not tried personally. If you g
> But now I just realized the obvious: Only X GUIS work and not windows.
>
> Is this correct?
Yes!
> I assume I can tunnel rdesktop the same way I tunnel vnc? I guess I'll try
> tunneling both vnc and rdesktop next.
I've heard this works, but have not tried personally. If you get this
working,
Thanks Dan and Rene! It works.
But now I just realized the obvious: Only X GUIS work and not windows.
Is this correct?
I assume I can tunnel rdesktop the same way I tunnel vnc? I guess I'll try
tunneling both vnc and rdesktop next.
Siegfried
--
Unsubscribe info: http://cygwin.com/ml/#u
Siegfried Heintze wrote:
[snip]
Why does /usr/X11R6/bin/xclock still say "Error can't open display:"?
That looks like an explicit unsetting of DISPLAY, i.e. somewhere, probably
your
.profile/.bashrc/.bash_profile, has a "unset DISPLAY".
Starting in Cygwin:
$ echo $DISPLAY
:0
$ ssh -X [EMAIL
Siegfried Heintze wrote:
>>> [snip]
> echo $DISPLAY
>
> Any other suggestions?
Check /etc/sshd_config on the server, configure it to forward X11:
# X11 tunneling options
X11Forwarding yes
X11DisplayOffset 10
X11UseLocalhost yes
After restarting sshd try:
ssh -X [EMAIL PROTECTED] 'echo $
> > [snip]
> > Why does /usr/X11R6/bin/xclock still say "Error can't open display:"?
>
> That looks like an explicit unsetting of DISPLAY, i.e. somewhere, probably
your
> .profile/.bashrc/.bash_profile, has a "unset DISPLAY".
>
> Starting in Cygwin:
> $ echo $DISPLAY
> :0
> $ ssh -X [EMAIL PROTE
Siegfried Heintze wrote:
> [snip]
> Why does /usr/X11R6/bin/xclock still say "Error can't open display:"?
That looks like an explicit unsetting of DISPLAY, i.e. somewhere, probably your
.profile/.bashrc/.bash_profile, has a "unset DISPLAY".
Starting in Cygwin:
$ echo $DISPLAY
:0
$ ssh -X [EMAIL
[snip]
> > > However, I cannot seem to start an X session from my "ssh -X -p 892
> > > [EMAIL PROTECTED]" session. I tried running "explorer ." and
that
> > > just hung. OK, that was not an X program. Then I tried
> > > /usr/X11R6/bin/xclock and it said it could not open the display.
Having
> >
Siegfried Heintze wrote:
[snip]
> > (2) For reasons I don't understand, there was a conflict between my router's
> > sshd and my cygwin's sshd so I resolved the problem by changing the cygwin's
> > configuration file to start sshd on a different port. Now, using a Red Hat 8
> > client, I can use bo
