antlersoft / android-vnc-viewer

Automatically exported from code.google.com/p/android-vnc-viewer
68 stars 26 forks source link

Getting "VNC Connection Failed! null" error immediately on trying to connect to RealVNC #281

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Get androidVNC version 0.5.0
2. Get RealVNC 4.1.3
3. Set up RealVNC as a service on Windows 7 and androidVNC on a Rezound.
4. Try to connect the Rezound to the PC and get this error.  I've tried 
everything I can think of, so I think this is all you really need to do.

What is the expected output? What do you see instead?
I see an error message that pops up right away when trying to connect.  It just 
says:
Error!
VNC Connection Failed!
null

What version of android-vnc-viewer are you using?
0.5.0

Which VNC server/version are you using?  On which platform?
RealVNC 4.1.3 service mode on Windows 7

What is the size of the desktop you are trying to access (i.e. 1024x768, 
1920x1080...)?
1920x1200

What device are you using?
HTC Rezound

Are you using a custom ROM?  If so, which?
None

Please provide any additional information below.
I've tried to connect with and without password authentication, both failed.  
My router is configured to open the ports needed for VNC and my firewall has 
been disabled, still no luck.  Sorry if this is a duplicate issue, I couldn't 
find a ticket that was quite like this issue.

Original issue reported on code.google.com by nwas...@gmail.com on 3 Dec 2011 at 3:40

GoogleCodeExporter commented 9 years ago
same problem, need help asap please

Original comment by matthew....@gmail.com on 3 Apr 2012 at 12:01

GoogleCodeExporter commented 9 years ago

I have the same problem when using realVNC service mode. However in user mode
i manage to connect from my galaxy note. So i suspect the error to be somewhere 
in 
(in my case) windows 7.

Original comment by Tobx...@gmail.com on 10 Apr 2012 at 9:08

GoogleCodeExporter commented 9 years ago
having same problem on galaxy tab 2. setting the Color Format to 24-bit color(4 
bpp) fix it.

Original comment by 45g...@gmail.com on 3 May 2012 at 10:41

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
Have the same problem on my Motorola Defy+, connecting to a VNC running on 
Debian. Changing the colour settings does not fix it.
Can connect to VNC from other hardware fine.
Tried with wifi and it works, but not through mobile network.

Original comment by mail.ton...@gmail.com on 13 Jul 2012 at 3:22

GoogleCodeExporter commented 9 years ago
Received this identical error when I used the wrong port, 5800 instead of 5900 
from my android VNC client - to my (Windows) VNC Server. 

Once I corrected the port, I then ran into this issue: 
http://code.google.com/p/android-vnc-viewer/issues/detail?id=232

See my notes there. In the end, I successfully connect to my VNC Server from my 
android VNC client. VERY Nice!!

Original comment by RSWel...@gmail.com on 1 Dec 2012 at 5:09

GoogleCodeExporter commented 9 years ago
seriously, since 2012 no solution posted?

Original comment by volatili...@gmail.com on 21 Jan 2015 at 9:07