Shows "Establishing Handshake. Please wait.." forever

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Enable Apple Remote Desktop on Mac OS X 10.4.11
2. Try to connect from T-Mobile G1 through wifi
3. It shows the error

What is the expected output? What do you see instead?
It should connect to the mac machine and show the desktop.

What version of the product are you using? On what operating system?
Android-VNC-Viewer: Build 090307
Android: Build Number: dream_devphone-userdebug 1.0 UNLOCKED 116222 test-keys
Mac OS X: 10.4.11

Please provide any additional information below.

When I am trying to establish a connection to my macbook (Mac os 10.4), it
keeps showng "Establishing Handshake. Please wait.."

Original issue reported on code.google.com by sandeepg...@gmail.com on 28 Mar 2009 at 7:47

[GoogleCodeExporter]

In the step 3, instead of "It shows the error" it should be "It displays the
"Establishing Handshake. Please wait.." forever.

Original comment by sandeepg...@gmail.com on 28 Mar 2009 at 7:49

[GoogleCodeExporter]

Yeah. When I use Mac OS X 10.5.6's built-in VNC stuff, it always says "VNC 
connection failed!" after it does the "Establishing handshake" stuff.

If I use Vine (an alternative VNC server for Mac OS X) it hangs on 
"Establishing 
handshake"

I would really like to be able to use this VNC app, but it doesnt seem to work. 
I've 
read that the default Mac VNC server doesn't work with things like changing the 
colors (to grayscale or 8bits or whatever) so maybe that's causing the issue.

Original comment by amgupt01 on 9 May 2009 at 5:50

[GoogleCodeExporter]

Check your firewall, make sure that port 5900 is open, and if that doesn't 
work, make
sure that your router is set up to forward port 5900 as well

Original comment by shshc...@gmail.com on 23 Nov 2009 at 8:55

[GoogleCodeExporter]

What A pile of shit for the MAC community. And no help from anyone to make it 
work.Not mac-like at all

Original comment by Spooling...@gmail.com on 18 Dec 2009 at 4:43

[GoogleCodeExporter]

@Spoolingturbo6 I understand your frustrations which I share... that's why Mac 
users will keep buying iPhones 
and will never turn to Nexus or DROID. It is a shame that although Android 
(*NIX Based) is an OS that has 
more in common with OS X (FreeBSD based), it apparently works with Windows, 
according to user who 
reported successful connection. I have not tried myself on Windows, but in all 
fairness the failing connection 
may be due to the VNC running natively on OS X, or a minor problem in the 
android client that could be 
solved easily... I don't know and unfortunately I am not an advanced developer 
hence can't look into it myself.

One thing is sure though these issues better get fixed before mac user who 
chose a DROID will change their 
mind and go with iPhone after all. There is talk about the iPhone coming to 
Verizon (though may just be 
rumors). At that point there would be no reason to keep a DROID if it doesn't 
deliver in conjunction with a 
Mac.

 I tried all possible permutations, IPs, Bonjour domain (like "mymac.local"), reconfigured DHCP on router to 
assign a static IP to the DROID, tried to access via Dynamic DNS coming in from 
the WAN to my mac (port 
5900 gets forwarded to the static IP of my mac), I made sure the mac was 
listening on port 5900.... You name 
it!

The huge frustration is that I can vnc-control my mac from my Mac laptop and 
PCs without a hitch, when it 
comes to the DROID and the VNC client it's a big forgeddaboutit! The Android 
VNC constantly ends up 
returning a "Error, VNC Connection Failed" and the button "Acknowledged". Damn 
this thing is driving me 
nuts! My conclusion as of now is that the Android VNC does not work with the 
Apple's built-in VNC server. I'll 
give a shot at an alternative server if I find any and test if that solves the 
problem.  Otherwise until someone 
in the dev community or at Google will read our posts and will be kind enough 
to look into why OS X can't be 
VNC'ed from Android, we'll be out of luck and stuck with the current situation.

If anyone finds a workaround to the problem, please share it... thanks in 
advance, much appreciated.

Original comment by freak...@gmail.com on 8 Jan 2010 at 4:43

[GoogleCodeExporter]

Quick update to all Mac Users who encountered the same problem I described in 
my previous post.
Finally I got my motodroid to connect to my mac via VNC and Apple's built in 
VNC server has nothing to do 
with the Android VNC client issues.
When I previously said "I tried all possible permutations" I did not realize I 
left out a few other problem-
causing possibilities. 

The Android VNC client DOES NOT work when you try to connect to your mac using 
something other than a 
"24-bit color" profile therefore that's rule#1 and can't be ignored! (also make 
sure you selected "Local Mouse 
Pointer"). That's just one side of the problem...

Being spoiled by technology, sometimes prevents me from thinking about the 
obvious! 
My Mac Pro drives a 2560x1600 30" monitor and although I have ZERO issues when 
I VNC-in from my 
Macbook Pro or other PCs with smaller screens, it turns out that the Android 
client completely craps itself and 
chokes to death because it can't handle properly anything above 1280x800 (at 
least on my MotoDroid). 
At resolutions higher than 1280x800 the Android VNC client starts having a real 
hard time refreshing the tiles 
that make the replica of the mac screen on the droid and do not even think 
about checkin the checkbox 
"Force full-screen bitmap" because the result would be that you will find 
yourself stuck on a black screen and 
your sole options will be to:
A) press the "back" button to exit, but that will be unresponsive and will do 
nothing;
B) press the "menu" button used to access the preferences (on motodroid at 
least) which will simply yield a 
Force Close... although when you will click on the "Force Close" button, the 
application will just return to the 
VNC client's main screen.

So here is the recap to connect to a mac using the Android VNC client:
1) Make sure your mac screen resolution is not larger than 1280x800 (that a 
huge limitation but for now there 
is no other option unless some nice developer comes to our rescue ;D hint-hint!)
2) Type in all the required info such as Password, IP and port in your Android 
VNC client
3) Select "24-bit color (4 bpp)" in the "Color Format" drop-down menu
4) Hit connect

et voilá... you are remote-managing your mac from your DROID.

Despite the successful connection and the "viability" of this VNC client, when 
it comes to mac you will soon 
realize that the VITAL "Command" key has been left out from the "Send Special 
Key" therefore you will be 
unable to use any shortcut that will require the Command Key, but that's not 
too bad.. who would want to 
open a send key and go through that hassle to just Copy, Paste or Select All, 
for instance? I sure wouldn't 
want to :)
The only way that mac shortcuts can become usable in the Android VNC client is 
if the user was able to map 
shortcuts to key combinations using something that can put in place of the 
command key... that's when I 
would have loved if Motorola instead of removing them, would have added those 2 
keys next to the "alt" 
button (that presently are just blank non-functional dead pads), and allowed 
the users to assign to them 
custom functionalities. But for now maybe the "search" key (the one with a 
magnifying lens icon) could be 
used as a replacement for "Command"  key. After all what are the odds that 
someone would want to use that 
key to trigger a search when connecting via VNC to a remote computer? ;)

I hope the info above will help some of my fellow Mac Users who went DROID 
instead of iPhone ;P

Peace.

Original comment by freak...@gmail.com on 8 Jan 2010 at 6:34

[GoogleCodeExporter]

Password when connecting to a mac is REQUIRED and there are limits on what 
characters can be used in the 
pasword, although I have not tested to see what they all are

Original comment by lividchi...@gmail.com on 24 Mar 2010 at 9:11

[GoogleCodeExporter]

thank you 
for his. i had to pick 24-bit colour and it works all fine. 

Original comment by marksavi...@gmail.com on 24 Apr 2010 at 1:21

[GoogleCodeExporter]

Yes!

Thank you for this thread.  It describes the problem completely.

Once I switched to 24 bit color, and enabled "local mouse pointer" I was able 
to acess my Imac which has a 1680x1050 display without a problem.  Perhaps this 
problem has been fixed?  Still the correct settings are absolutely required.

Thanks,

Bill

Original comment by bqg...@gmail.com on 17 Jun 2011 at 4:52