I misunderstood your intent, because your previous message suggested
that you were trying to connect to port 5901 (Display :1). If you need
to connect to Display :1001, then do:
/opt/TurboVNC/bin/vncviewer -loglevel 110 -extssh -via
uek8desktop01 localhost:1001
or
/opt/TurboVNC/bin/v
Sorry it took so long to get back to you.
The first command does not work possibly because the display requested (1)
does not match the display expected (1001)
The second one, however, does work:
libjawt.so path:
/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.312.b07-2.el8_5.x86_64/jre/lib/amd64
Log se
Try
/opt/TurboVNC/bin/vncviewer -loglevel 110 -extssh -via
uek8desktop01 localhost:1
or
/opt/TurboVNC/bin/vncviewer -loglevel 110 -extssh -via
uek8desktop01 localhost::5901
You have to use two colons if you are specifying a TCP port rather than
a display number.
DRC
On 11/14/21
Afraid not. I tried a few variation then turned up the logging level.
$ /opt/TurboVNC/bin/vncviewer -loglevel 110 -extssh -via uek8desktop01
localhost:1001
libjawt.so path:
/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.312.b07-1.el8_4.x86_64/jre/lib/amd64
Log setting: 110
main: start called
Tunnel:
Ah, OK. The built-in SSH client in the TurboVNC Viewer won't support
that, but you should still be able to use OpenSSH by passing -extssh to
/opt/TurboVNC/bin/vncviewer. That will mimic the behavior of TigerVNC,
since it also uses the external SSH client.
DRC
On 11/11/21 5:33 PM, Stephen Ca
Sure. I use a bastion host with ProxyJump. (I hope the formatting comes
out OK)
Host ovpn
Hostnamebastion.lereta.com
Userstephen
Protocol2
Port8022
ControlMaster auto
ControlPath ~/.ssh/master-%r@%h:%p
ControlPersist 3600
Host uek
I can't reproduce the issue. If I add, for example:
Host my_fake_server_name
HostName {my_server_ip_address_or_real_server_name}
User drc
to ~/.ssh/config, then executing
/opt/TurboVNC/bin/vncviewer -via my_fake_server_name
localhost:{my_display_number}
works as expected. Can you pos
I am out of the office right now but will double check our support of the
OpenSSH config file when I get back. What you describe should work with
TurboVNC 2.2.6.
> On Nov 6, 2021, at 8:47 AM, Stephen Carville
> wrote:
>
> That worked. Thank you.
>
>> On Saturday, November 6, 2021 at 1:14:5
That worked. Thank you.
On Saturday, November 6, 2021 at 1:14:57 AM UTC-7 osmark wrote:
> For Mate windows manager please use:
>
> vncserver -geometry 1920x1080 -wm mate-session
>
> sob., 6 lis 2021 o 05:37 Stephen Carville
> napisał(a):
>
>> I started testing TurboVNC on OL8 this weekend. I
For Mate windows manager please use:
vncserver -geometry 1920x1080 -wm mate-session
sob., 6 lis 2021 o 05:37 Stephen Carville
napisał(a):
> I started testing TurboVNC on OL8 this weekend. Immediately I noticed it
> seem to start up gnome exclusively, Hoiw can I get it to start MATE or
> Xfce?
I started testing TurboVNC on OL8 this weekend. Immediately I noticed it
seem to start up gnome exclusively, Hoiw can I get it to start MATE or
Xfce? I did this readily with TigerVNC and ~/.vnc/xstartup but TurboVNC
seems to use a different approach. Even a link to some documentation would
b
11 matches
Mail list logo
