On 24 Feb 2023 at 1:21, Reon Beon via users wrote:
Subject:Re: vncviewer to new tightvnc 2.8.75
To: users@lists.fedoraproject.org
Date sent: Fri, 24 Feb 2023 01:21:05 -
Send reply to: Community support for Fedora
users
From
Have you tried tigervnc?
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: ht
x27;t work, can't just reinstall old version?
2.8.75 just came out. Have sent messages to both
Tigervnc and Tightvnc lists.
Tried strace vncviewer but didn't notice an error
message other than resource not available and fonts not
found?? But didn't seem to
On 25 Jan 2020 at 7:00, Ed Greshko wrote:
From: Ed Greshko
Subject:Re: F8 key not workingwith vncviewer??
To: Fedora
Date sent: Sat, 25 Jan 2020 07:00:56 +0800
Send reply to: Community support for Fedora users
>
to a windows machine, and nothing
>> happens. Then tried it on one of my other Fedora machines, and from a
>> terminal window it puts out a ~ each time the key was pressed, but no menu.
>> Connected to the same machines using a windows machine with tightvnc's
>> v
d it on one of my other Fedora machines, and from a
> terminal window it puts out a ~ each time the key was pressed, but no menu.
> Connected to the same machines using a windows machine with tightvnc's
> vncviewer, and the F8 key works perfectly.
> I'v seen a similar proble
out a ~ each time the key was pressed, but no menu.
Connected to the same machines using a windows machine with tightvnc's
vncviewer, and the F8 key works perfectly.
I'v seen a similar problem with something in the past, where the files where
using the DOS CR/LF instead of the linux LF. In
OK,
Very good, it works now
> On 03/02/14 21:56, Patrick Dupre wrote:
> >
> >> - Original Message -
> >> From: Ed Greshko
> >> Sent: 03/02/14 02:47 PM
> >> To: Community support for Fedora users
> >> Subject: Re: vncviewer
> >
On 03/02/14 21:56, Patrick Dupre wrote:
>
>> - Original Message -
>> From: Ed Greshko
>> Sent: 03/02/14 02:47 PM
>> To: Community support for Fedora users
>> Subject: Re: vncviewer
>>
>> On 03/02/14 21:06, Ed Greshko wrote:
>>
> - Original Message -
> From: Ed Greshko
> Sent: 03/02/14 02:47 PM
> To: Community support for Fedora users
> Subject: Re: vncviewer
>
> On 03/02/14 21:06, Ed Greshko wrote:
> > nmap -v -n -P0 -p5900-5906 192.168.0.101
>
> typo
>
> n
On 03/02/14 21:06, Ed Greshko wrote:
> nmap -v -n -P0 -p5900-5906 192.168.0.101
typo
nmap -v -n -P0 -p5900-5906 192.168.1.101
--
Getting tired of non-Fedora discussions and self-serving posts
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription option
On 2 Mar 2014 at 13:38, Patrick Dupre wrote:
Date sent: Sun, 02 Mar 2014 13:38:32 +0100
From: "Patrick Dupre"
Subject: vncviewer
To: "Community support for Fedora users"
> Hello,
>
> When I try to c
On 03/02/14 20:38, Patrick Dupre wrote:
> When I try to connect to a fedora 20 machine (192.168.1.101) through
> vncviewer (both machine
> are on the same lan), I get
> TigerVNC Viewer for X version 1.1.0 - built Nov 22 2011 14:21:13
> Copyright (C) 1999-2011 TigerVNC Team and m
Hello,
When I try to connect to a fedora 20 machine (192.168.1.101) through vncviewer
(both machine
are on the same lan), I get
TigerVNC Viewer for X version 1.1.0 - built Nov 22 2011 14:21:13
Copyright (C) 1999-2011 TigerVNC Team and many others (see README.txt)
See http://www.tigervnc.org for
On 02/28/14 05:49, Patrick Dupre wrote:
> It appears that every time I have to change the owner of /run/user/1000/user!
> I need to do something for that.
If you have to do that, then something is very wrong on either your system or
the user account.
That is why I suggested you create a new user
>
> On 2/27/2014 15:37, Patrick Dupre wrote:
> > OK, I restarted it:
>
> If you look below, I have removed all the chains that didn't reference
> SSH. Notice that the VNC ports you were trying to access are not listed
> in these chains. That's why you aren't getting access to them remotely.
>
On 2/27/2014 15:37, Patrick Dupre wrote:
OK, I restarted it:
If you look below, I have removed all the chains that didn't reference
SSH. Notice that the VNC ports you were trying to access are not listed
in these chains. That's why you aren't getting access to them remotely.
Now that we h
On 2/27/2014 15:58, Ed Greshko wrote:
FWIW, if you have ssh working and you use VNC over an SSH Tunnel you do not
need ports 590X or any other ports open!
Agreed. I mentioned at the outset that encryption was not present in
vanilla vnc but it is extremely desirable. In fact, I would go so f
02/27/2014 12:37 PM, Patrick Dupre wrote:
OK, I restarted it:
Chain INPUT (policy ACCEPT)
target prot opt source destination
ACCEPT all -- anywhere anywhere ctstate
RELATED,ESTABLISHED
ACCEPT all -- anywhere anywhere
INPUT_direc
FWIW, if you have ssh working and you use VNC over an SSH Tunnel you do not
need ports 590X or any other ports open!
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: ht
> - Original Message -
> From: Tom Rivers
> Sent: 02/27/14 09:11 PM
> To: Community support for Fedora users
> Subject: Re: vncviewer
>
> On 2/27/2014 14:47, Patrick Dupre wrote:
> > iptables -L
> > Chain INPUT (policy ACCEPT)
> > target prot opt s
On 02/28/14 04:16, Patrick Dupre wrote:
> Progress, but still:
>
> the log file:
>
> Xvnc TigerVNC 1.2.80 - built Mar 14 2013 18:53:14
> Copyright (C) 1999-2011 TigerVNC Team and many others (see README.txt)
> See http://www.tigervnc.org for information on TigerVNC.
> Underlying X server release 11
not
compatible with current GNOME Shell and/or GJS version
** Message: applet now embedded in the notification area
(mc2:25045): Gdk-CRITICAL **: IA__gdk_window_thaw_toplevel_updates_libgtk_only:
assertion `private->update_and_descendants_freeze_count > 0' failed
> - Original Message -
> From: Ed Greshko
> Sen
On 2/27/2014 14:47, Patrick Dupre wrote:
iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination
Chain FORWARD (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destinat
On 02/27/14 22:29, Patrick Dupre wrote:
> Should I just not change the righths on
> /run/user/1000/dconf/
>
> drwx--. 2 root root 60 Feb 26 23:10 dconf
It is very, very odd that this directory is owned by root. I would like to see
what you get for.
NOTE, use 1000 for your user id.
Sorry,
after vncserver
ps -eaf | grep -i vnc
pdupre 22520 1 0 20:43 pts/2 00:00:00 /usr/bin/Xvnc :1 -desktop
Homere:1 (pdupre) -auth /home/pdupre/.Xauthority -geometry 1024x768 -rfbwait
3 -rfbauth /home/pdupre/.vnc/passwd -rfbport 5901 -fp
catalogue:/etc/X11/fontpath.d -pn
pdupre
On 2/27/2014 14:06, Jon Ingason wrote:
2014-02-27 19:03, Patrick Dupre skrev:
Hello,
For me
iptables -F
does not display anything!
That is because option -F means flushing the iptable, deleting all
rules. You should use option -L as Tom suggested.
While the rules are gone, you can try conne
2014-02-27 19:03, Patrick Dupre skrev:
> Hello,
>
> For me
> iptables -F
>
> does not display anything!
That is because option -F means flushing the iptable, deleting all
rules. You should use option -L as Tom suggested.
>
>> On 2/26/2014 17:13, Patrick Dupre wrote:
>>> How i do it? vncserver
Hello,
For me
iptables -F
does not display anything!
> On 2/26/2014 17:13, Patrick Dupre wrote:
> > How i do it? vncserver is not helpfull, Is it a file that I need to edit?
>
> It depends on how you configure your firewall settings. I manage mine
> using a script that builds the iptables ent
On 2/26/2014 18:57, Ed Greshko wrote:
FYI, it is the telnet server that is not installed by default. The
client is
Thanks Ed!
Tom
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedo
On 2/26/2014 17:13, Patrick Dupre wrote:
How i do it? vncserver is not helpfull, Is it a file that I need to edit?
It depends on how you configure your firewall settings. I manage mine
using a script that builds the iptables entries I need. There are also
other products that can perform the
vncserver
New 'Homere:1 (pdupre)' desktop is Homere:1
Starting applications specified in /home/pdupre/.vnc/xstartup
Log file is /home/pdupre/.vnc/Homere:1.log
then:
ps -eaf | grep -i vnc
pdupre 5266 1 2 15:26 pts/0 00:00:00 /usr/bin/Xvnc :1 -desktop
Homere:1 (pdupre) -auth /home/
Also, one thing you need to know is this
If you run vncserver a second time without killing a previous instance of
vncserver it will run and increment the display. This means you can have
multiple vncservers running for a user each on a different tcp port.
[egreshko@f20f ~]$ vncserver
New
On 02/27/14 18:15, Patrick Dupre wrote:
> There is an issue
> Here is the ls
> -rw-rw-r--. 1 pdupre 1000 38590005 Feb 27 11:00 Homere:8.log
> -rw-rw-r--. 1 pdupre 10006 Feb 27 01:25 Homere:8.pid
> -rw-rw-r--. 1 pdupre 100010091 Feb 26 19:12 Homere:2.log
> -rw-rw-r--. 1 pdupre 1000 35988
> - Original Message -
> From: Ed Greshko
> Sent: 02/27/14 03:04 AM
> To: Community support for Fedora users
> Subject: Re: vncviewer
>
> On 02/27/14 09:55, Patrick Dupre wrote:
> > I am trying by vnc uisng ssh tunnelin,
> > It does ask me for the passwo
On 02/27/14 09:55, Patrick Dupre wrote:
> I am trying by vnc uisng ssh tunnelin,
> It does ask me for the password, and then wait
> connectiong to 196.49. through ssh tunnel for ever.
On the server side. Your user should have a ~/.vnc directory and there should
be a "log" file.
Does that f
> - Original Message -
> From: Ed Greshko
> Sent: 02/27/14 02:38 AM
> To: Community support for Fedora users
> Subject: Re: vncviewer
>
> On 02/27/14 09:36, Patrick Dupre wrote:
> >
> >> - Original Message -
> >> From: Ed Greshko
&g
On 02/27/14 09:36, Patrick Dupre wrote:
>
>> - Original Message -
>> From: Ed Greshko
>> Sent: 02/27/14 02:24 AM
>> To: Community support for Fedora users
>> Subject: Re: vncviewer
>>
>> On 02/27/14 09:13, Patrick Dupre wrote:
>>&g
> - Original Message -
> From: Ed Greshko
> Sent: 02/27/14 02:24 AM
> To: Community support for Fedora users
> Subject: Re: vncviewer
>
> On 02/27/14 09:13, Patrick Dupre wrote:
> >
> >> - Original Message -
> >> From: Ed Greshko
&g
On 02/27/14 09:13, Patrick Dupre wrote:
>
>> - Original Message -
>> From: Ed Greshko
>> Sent: 02/27/14 02:10 AM
>> To: Community support for Fedora users
>> Subject: Re: vncviewer
>>
>> On 02/27/14 09:06, Patrick Dupre wrote:
>>&g
On 02/27/14 09:13, Patrick Dupre wrote:
>
>> - Original Message -
>> From: Ed Greshko
>> Sent: 02/27/14 02:10 AM
>> To: Community support for Fedora users
>> Subject: Re: vncviewer
>>
>> On 02/27/14 09:06, Patrick Dupre wrote:
>>&g
On 02/27/14 09:13, Patrick Dupre wrote:
> I just get a text window
> how can I get a graphics window?
The protocol you want is "VNC - Virtual Network Computing".
See
https://drive.google.com/file/d/0B2H9v1dYNcvpY2VJdTNYcVZpc2M/edit?usp=sharing
and
https://drive.google.com/file/d/0B2H9v1d
> - Original Message -
> From: Ed Greshko
> Sent: 02/27/14 02:10 AM
> To: Community support for Fedora users
> Subject: Re: vncviewer
>
> On 02/27/14 09:06, Patrick Dupre wrote:
> >
> >> - Original Message -
> >> From: Ed Greshko
&g
On 02/27/14 09:06, Patrick Dupre wrote:
>
>> - Original Message -
>> From: Ed Greshko
>> Sent: 02/27/14 01:56 AM
>> To: Community support for Fedora users
>> Subject: Re: vncviewer
>>
>> Oh
>>
>> You said ssh works.
>&
> - Original Message -
> From: Ed Greshko
> Sent: 02/27/14 01:56 AM
> To: Community support for Fedora users
> Subject: Re: vncviewer
>
> Oh
>
> You said ssh works.
>
> You should use vncviewer over an ssh tunnel in that case.
>
> T
Oh
You said ssh works.
You should use vncviewer over an ssh tunnel in that case.
The "easiest" way to do that would be to use a graphical client such as
"remmina".
Ed
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscri
On 02/27/14 08:45, Patrick Dupre wrote:
>
>> - Original Message -
>> From: Ed Greshko
>> Sent: 02/27/14 01:36 AM
>> To: Community support for Fedora users
>> Subject: Re: vncviewer
>>
>> On 02/27/14 08:33, Patrick Dupre wrote:
>>> Are
On 02/27/14 08:33, Patrick Dupre wrote:
> telnet connections are not accepted on the machine.
> telnet machine x (x=0,1) gives No route to host
In your example x should be 5901 not 0 or 1.
In "telnet" the last number is the Port.
In "vncviewer" the last nu
> - Original Message -
> From: Ed Greshko
> Sent: 02/27/14 01:36 AM
> To: Community support for Fedora users
> Subject: Re: vncviewer
>
> On 02/27/14 08:33, Patrick Dupre wrote:
> > Are you sure?
> >
> > telnet connections are not accepted on t
On 02/27/14 08:33, Patrick Dupre wrote:
> Are you sure?
>
> telnet connections are not accepted on the machine.
> telnet machine x (x=0,1) gives No route to host
>
> vncviewer 193.49.194.196:0
> or
> vncviewer 193.49.194.196:1
> give
>
> main:unable co
> - Original Message -
> From: Ed Greshko
> Sent: 02/27/14 01:15 AM
> To: Community support for Fedora users
> Subject: Re: vncviewer
>
> On 02/27/14 08:13, Patrick Dupre wrote:
> > telnet: connect to address 193.49.194.1xx: No route to host
> > (with
> - Original Message -
> From: Pittigher, Raymond - ES
> Sent: 02/27/14 12:47 AM
> To: Community support for Fedora users
> Subject: RE: vncviewer
>
> Just do a iptables -F at a command line to see if that is the problem before
> you go crazy with tryin
On 02/27/14 08:13, Patrick Dupre wrote:
> telnet: connect to address 193.49.194.1xx: No route to host
> (with the correct IP)
> ssh works OK!
> why no route again!
Because you are int specifying the PORT NUMBER!
--
Getting tired of non-Fedora discussions and self-serving posts
--
users maili
> - Original Message -
> From: Ed Greshko
> Sent: 02/27/14 01:05 AM
> To: Community support for Fedora users
> Subject: Re: vncviewer
>
> On 02/27/14 07:41, Patrick Dupre wrote:
> > PORT STATE SERVICE
> > 5900/tcp closed vnc
> > 5901/tcp open vnc-1
One more thing.
When using vncviewer make sure you specify the display #.
vncviewer 192.168.1.227 would attempt to connect to 0 which is port 5900 .
on which you don't have a server running.
You want.....
vncviewer 192.168.1.227:1 to connect to port 5901 !
Use the proper IP ad
On 02/27/14 07:41, Patrick Dupre wrote:
> PORT STATE SERVICE
> 5900/tcp closed vnc
> 5901/tcp open vnc-1
> 5902/tcp closed vnc-2
> 5903/tcp closed vnc-3
> 5904/tcp closed unknown
> 5905/tcp open unknown
> 5906/tcp open unknown
"closed" means the port is not blocked/filtered by the firew
On 02/27/14 05:43, Tom Rivers wrote:
> I'm not sure telnet is the way to go because if memory serves it isn't
> installed by default.
FYI, it is the telnet server that is not installed by default. The client
is
--
Getting tired of non-Fedora discussions and self-serving posts
--
users ma
:41 PM
To: Community support for Fedora users
Subject: Re: vncviewer
>
> OK, the ports 5905 and 5906 are open and in use locally. Unfortunately,
> your previous scan results didn't show the status of those same ports
> from the remote machine. Try the following command on t
>
> OK, the ports 5905 and 5906 are open and in use locally. Unfortunately,
> your previous scan results didn't show the status of those same ports
> from the remote machine. Try the following command on the remote machine:
>
> nmap -v -n -P0 -p5905-5906 193.49.194.19
>
> If the ports aren't s
> - Original Message -
> From: Tom Rivers
> Sent: 02/26/14 11:08 PM
> To: Community support for Fedora users
> Subject: Re: vncviewer
>
> On 2/26/2014 17:01, Patrick Dupre wrote:
> > # nmap -v -n -P0 -p5900-5910 localhost
> >
> > Starting Nmap 6.
On 2/26/2014 17:01, Patrick Dupre wrote:
# nmap -v -n -P0 -p5900-5910 localhost
Starting Nmap 6.40 ( http://nmap.org ) at 2014-02-26 23:00 CET
Initiating SYN Stealth Scan at 23:00
Scanning localhost (127.0.0.1) [11 ports]
Discovered open port 5905/tcp on 127.0.0.1
Discovered open port 5906/tcp o
> - Original Message -
> From: Tom Rivers
> Sent: 02/26/14 10:56 PM
> To: Community support for Fedora users
> Subject: Re: vncviewer
>
> On 2/26/2014 16:49, Patrick Dupre wrote:
> > Starting Nmap 6.01 ( http://nmap.org ) at 2014-02-26 22:47 CET
> > Ini
On 2/26/2014 16:49, Patrick Dupre wrote:
Starting Nmap 6.01 ( http://nmap.org ) at 2014-02-26 22:47 CET
Initiating SYN Stealth Scan at 22:47
Scanning 193.49.194.19 [4 ports]
Completed SYN Stealth Scan at 22:47, 3.01s elapsed (4 total ports)
Nmap scan report for 193.49.194.19
Host is up.
PORT
5900-5910 in the example above because you can
> configure the vnc service to listen on a number of different ports. That
> what the ":1" or ":2" mean when you set up the entries in the
> /etc/sysconfig/vncserver file. This also means that to connect to a v
at the ":1" or ":2" mean when you set up the entries in the
/etc/sysconfig/vncserver file. This also means that to connect to a vnc
server set up for ":2" on the example IP address above you need to use
"192.168.1.10:2" in the vncviewer and the nmap outp
> - Original Message -
> From: Mark Haney
> Sent: 02/26/14 10:20 PM
> To: users@lists.fedoraproject.org
> Subject: Re: vncviewer
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
>
> On 02/26/14 16:07, Patrick Dupre wrote:
> >
> &g
> > Hello,
> >
> > vncviewer gives me:
> > unable connect socket: No route to host (113) fedora
> >
> > I browsed the web, and tried sevral options without succes!
> >
>
> It is probable a firewall issue on the machine running the server. I ha
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/26/14 16:07, Patrick Dupre wrote:
>
>> Turn it off and see if it works.
>
> It does not change anything, still unable connect to socket: No
> route to host (113)
>
> ssh works fine
>
Can you telnet to the VNC port on the server?
- --
Mark
behalf of Patrick Dupre
> [pdu...@gmx.com]
> Sent: Wednesday, February 26, 2014 2:57 PM
> To: Community support for Fedora users
> Subject: RE: vncviewer
>
> Subject: RE: vncviewer
> >
> > Is the firewall running?
&g
On 26 Feb 2014 at 19:46, Patrick Dupre wrote:
Date sent: Wed, 26 Feb 2014 19:46:59 +0100
From: "Patrick Dupre"
Subject: vncviewer
To: fedora
Send reply to: Community support for Fedora users
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/26/14 14:57, Patrick Dupre wrote:
> Subject: RE: vncviewer
>>
>> Is the firewall running?
>
> Yes, but I checked public/vnc-server (and ssh)
>
>>
Since you're not really giving us much to go on, here&#x
: RE: vncviewer
Subject: RE: vncviewer
>
> Is the firewall running?
Yes, but I checked public/vnc-server (and ssh)
>
>
> From: users-boun...@lists.fedoraproject.org
> [users-boun...@lists.fedoraproject.org] on behalf of Mark Haney
> [
Subject: RE: vncviewer
>
> Is the firewall running?
Yes, but I checked public/vnc-server (and ssh)
>
>
> From: users-boun...@lists.fedoraproject.org
> [users-boun...@lists.fedoraproject.org] on behalf of Mark Haney
> [mha...@p
: vncviewer
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/26/14 13:46, Patrick Dupre wrote:
> Hello,
>
> vncviewer gives me: unable connect socket: No route to host (113)
> fedora
>
> I browsed the web, and tried sevral options without succes!
>
Could you be slightly less spec
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/26/14 13:46, Patrick Dupre wrote:
> Hello,
>
> vncviewer gives me: unable connect socket: No route to host (113)
> fedora
>
> I browsed the web, and tried sevral options without succes!
>
Could you be slightly l
Hello,
vncviewer gives me:
unable connect socket: No route to host (113) fedora
I browsed the web, and tried sevral options without succes!
Thank
===
Patrick DUPRÉ | | email: pdu...@gmx.com
On 12/11/2011 04:29 PM, Robert Moskowitz wrote:
>
> On 12/11/2011 03:51 PM, mike cloaked wrote:
>> On Sun, Dec 11, 2011 at 8:15 PM, Robert Moskowitz
>> wrote:
>>
>>> $ vncviewer
>>>
>>> TigerVNC Viewer for X version 1.1.0 - built Nov 22 2011
On 12/11/2011 03:51 PM, mike cloaked wrote:
> On Sun, Dec 11, 2011 at 8:15 PM, Robert Moskowitz
> wrote:
>
>> $ vncviewer
>>
>> TigerVNC Viewer for X version 1.1.0 - built Nov 22 2011 14:21:13
>> Copyright (C) 1999-2011 TigerVNC Team and many ot
On Sun, Dec 11, 2011 at 8:15 PM, Robert Moskowitz wrote:
> $ vncviewer
>
> TigerVNC Viewer for X version 1.1.0 - built Nov 22 2011 14:21:13
> Copyright (C) 1999-2011 TigerVNC Team and many others (see README.txt)
> See http://www.tigervnc.org for information on TigerVNC.
> ^C
On 12/11/2011 02:43 PM, Marko Vojinovic wrote:
> On Sunday 11 December 2011 14:33:42 Robert Moskowitz wrote:
>> When I first installed f16, I tried out VNCViewer and it started up, but
>> the address I was using was blocked from my VNCServer; no problem really
>>
>>
On Sunday 11 December 2011 14:33:42 Robert Moskowitz wrote:
> When I first installed f16, I tried out VNCViewer and it started up, but
> the address I was using was blocked from my VNCServer; no problem really
>
> So I move my new notebook to the proper VLAN and copied all the
When I first installed f16, I tried out VNCViewer and it started up, but
the address I was using was blocked from my VNCServer; no problem really
So I move my new notebook to the proper VLAN and copied all the files
from the old notebook, including .ssh, .subversion, and .vnc
Now when I
Hi,
I have a fedora15 system with a win7 KVM guest and connect to it using
tigervnc to a RealVNC Enterprise server on the win7 guest. Is this the
recommended vnc client?
Is there a way to keep the client connected so it doesn't timeout and
exit on its own?
Thanks for any ideas.
Best,
Alex
--
us
83 matches
Mail list logo
