Listen mode for vnc client to accept in bound connectio

[GoogleCodeExporter]

What steps will reproduce the problem?
1. No way to start/instruct client to listen for connections rather than 
connecting directly to a 
server.

What is the expected output? What do you see instead?
1. Maybe an option in the connect area to listen?

What version of the product are you using? On what operating system?
1. Connect with ultravnc on win xp

Please provide any additional information below.
1. I would consider a small bounty for implemnting this feature/

Original issue reported on code.google.com by goy...@gmail.com on 3 Feb 2009 at 5:29

[GoogleCodeExporter]

Need a little more information about how this would work--

Do you do something else from your phone to get the server to connect to you?  
How is
this configured on the server end?

Original comment by googlec...@antlersoft.com on 3 Feb 2009 at 6:06

• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

It's a reverse connection...control/see the phone UI from the computer

Original comment by mikela...@gmail.com on 14 Mar 2009 at 11:43

[GoogleCodeExporter]

It's a reverse connection...control/see the phone UI from the computer

Original comment by mikela...@gmail.com on 14 Mar 2009 at 11:44

[GoogleCodeExporter]

You are asking to implement a VNC SERVER for the phone.

1) this will depend on having ROOT ACCESS,
2) this program is a VNC CLIENT. Implementing a server is a little beyond the 
scope
of this project. Try this instead: http://code.google.com/p/android-vnc/

Original comment by andr...@tastemycity.com on 20 Oct 2009 at 4:53

[GoogleCodeExporter]

Note: the reason that this requires root is that it requires a patched kernel. 
The
kernel patch is available in the SVN. Don't use the kernel they provide -- it 
is a
very old M3 kernel and won't boot a dream. Apply the kernel patch against a 
modern
kernel source.

For viewing only, just copy the fbvncserver binary and run it. I don't think it
requires root by itself.

Original comment by andr...@tastemycity.com on 20 Oct 2009 at 5:38

[GoogleCodeExporter]

It seems that two different concepts are being discussed here:

1) goyuix wants the client (viewer) to listen on a specific port for a server
(machine that is to be controlled) to connect back to it. This is done by 
programs
such as UltraVNC SC and it's what most people would consider a "Reverse VNC
connection". This is very useful when you're helping a not-so-tech-savvy user 
who's
behind a firewall or NAT router since you don't have to walk them through 
setting up
a port forward. I've only just downloaded this app and it's definitely a 
feature I'd
love to see in it. Most VNC clients support this and call it "Listen Mode". 
Most VNC
servers have a "Connect to client" option to support this, but some (like 
UltraVNC SC
or gsvncj) automate the entire process and have the client's IP address and
destination port hardcoded for ease of use.

2) Mikelague wants to control the phone's UI from a PC, what most people would
consider a "VNC Server" - that seems beyond the scope of this project but Adam 
seems
to have pointed him in the right direction.

Original comment by rass...@gmail.com on 29 Nov 2009 at 6:01

[GoogleCodeExporter]

I have to agree with rassiej on his 1st point a reverse vnc like UltraVNC SC 
would 
be a great feature.  

Original comment by m.soh...@site-electrical.co.uk on 9 Dec 2009 at 4:47

[GoogleCodeExporter]

I am interested in rassiej's #1 as well.  With the desktop client, it's a 
simple switch

Original comment by amat...@gmail.com on 18 Dec 2009 at 10:17

[GoogleCodeExporter]

I think what goyuix is asking for is a reverse connection, not a VNC Server in 
the 
sense that Android can be controlled by a desktop.  It gets kind of confusing 
because 
typically a Server sends information to a Client about the screen contents.  By 
definition a Server is always Listening for a Client to Connect.  So, if 
android-vnc-
viewer is Listening, then it is a Server.  However, in the case of a Reverse 
Connection, it is still a Viewer (Listening Viewer, Server Viewer).  Android is 
NOT 
being controlled.  

Now, we all know that Android will allow this to happen, easily, but the 
question 
arises: will Verizon?  I will start off by saying I am highly uneducated about 
the 
architecture of Verizon's (or any) 3G network.  It is quite possible that many 
phones 
are attached to a single NAT hub, and so a single public IP address.  This 
would 
likely include an SPI Firewall (much like the one on your home router) that 
would 
prevent incoming connections.  Unlike your home router, you would not have 
permission 
to edit the settings to allow an incoming connection.  If either of these (NAT 
hub or 
Firewall) are the case, then reverse connection functionality would be 
impossible.  
It could be entirely true that each phone gets it's own IP that isn't protected 
at 
all by a firewall; it could even vary by network; I simply just do not know.  

If the developers can conclude that any networks would support it by their 
infrastructure, I would say it would be a great addition to the 
android-vnc-viewer.  
Like rassiej said, it would be a good idea for viewing recipients' computers 
who 
don't know how or do not have access to port forwarding settings (such as 
corporate 
networks).  

Thanks for reading, 
Zach

Original comment by ZacharyL...@gmail.com on 11 Apr 2010 at 5:41

[GoogleCodeExporter]

I am all in For a reverse/listening client also.

Original comment by talibb...@gmail.com on 17 Jun 2010 at 5:26

[GoogleCodeExporter]

I am all in For a reverse/listening client also.

Original comment by talibb...@gmail.com on 17 Jun 2010 at 5:26

[GoogleCodeExporter]

ditto. this is a necessity. i have clients that will initiate a support 
request. they'll connect to my repeater using the uvnc server. my vnc viewer in 
listen mode, connected to the same repeater, will find that connection and ill 
be able to see their desktop. this would be very useful from the android os. 
use the device as a viewer, but have it connect to the repeater and wait on the 
client.

Original comment by doomd...@gmail.com on 14 Jul 2010 at 4:01

[GoogleCodeExporter]

Remote VNC Pro has this feature:
http://www.toremote.com/ (see table of features) 3rd from bottom.

I'm interested in using this feature with UltraVNC:
http://forum.xda-developers.com/showthread.php?t=704812

Original comment by kwmer...@gmail.com on 23 Aug 2010 at 10:48

[GoogleCodeExporter]

I agree with everyone on the reverse connection. If I could set the VNC viewer 
to listen I can connect back to my repeater as well. Please add this feature. 
It would be VERY useful.

Original comment by casey.ch...@gmail.com on 20 Mar 2011 at 4:13

[GoogleCodeExporter]

I am all in For a reverse/listening client also.
Listening to port 5500 is the only easy way to help Madame Michu with her VNC 
server "add new client" or "-connect" option.

Original comment by azertyhg...@gmail.com on 7 Jun 2011 at 12:55

[GoogleCodeExporter]

+1, would be great if reverse/listening gets implemented

Original comment by Georg.Sc...@gmail.com on 30 Aug 2011 at 3:10

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

I'm also looking for this --listen option to for instance to do a remote 
installation of OS (Linux). Would be very much appreciated :)

Original comment by chesu...@gmail.com on 19 Oct 2011 at 6:41

[GoogleCodeExporter]

+100 for listening viewer! Would use it for ultravnc sc. 

Original comment by mitch.sh...@gmail.com on 8 Nov 2011 at 12:58

[GoogleCodeExporter]

TightVNC also does this. I vote for this feature. Should not be hard to add.

Original comment by timeband...@gmail.com on 19 Feb 2012 at 2:23

[GoogleCodeExporter]

It has been almost a year now, any progress on this one? I'd really like to see 
it.

Original comment by azelp...@azelphur.com on 31 Dec 2013 at 8:14

[GoogleCodeExporter]

Hi. I would like an android listening VNC viewer too.

Original comment by treyalle...@gmail.com on 25 Feb 2015 at 11:21