Currently Being ModeratedOct 7, 2012 8:21 AM (in response to Geordon)
-This thread has 90000 views but still no solution for Lion?
-Is it true that Lion incorporated a secure non standard VNC protocol to increase safety that broke all non VNC clients from connecting to it or could there be another reason?
-Can anyone else confirm that Mountain Lion's builtin VNC server is working when connecting from a windows VNC client like realvnc , uvnc , tightvnc etc... ?
Currently Being ModeratedOct 9, 2012 3:31 AM (in response to Geordon)
I can confirm that upgrading a Mac mini from Lion to Mountain Lion fixed the VNC issue: I can now connect to the Mac's VNC server with the UltraVNC 126.96.36.199.2 client running on Windows XP.
Currently Being ModeratedOct 9, 2012 5:49 AM (in response to fsalve)
So from this we can deduce that Lion DID in fact break screen sharing, and there is no fix for Windows users wanting to connect. Buy Mountain Lion is not a fix IMHO, it's issue avoidance. Where does that leave the lower spec users who cannot run it?
Currently Being ModeratedOct 9, 2012 8:47 PM (in response to john lewis)
John et al ....
While there's no update from anyone official here, I did notice that on October 4 there was a "Remote Desktop Client Update" (version 3.6.1) for Lion. It made some references in the text that gave me "hope" that it may finally fix this problem .... and after seeing your post I was reminded to try it out.
So -- some promising results .... I was just able to connect back to my Mac that is running Lion (and this recent software update) using UltraVNC on my Windows laptop. This same process failed miserably after moving from Lion from Snow Leopard. I will still give it a few more attempts before declaring success (particularly trying when I'm out of town) ... but this is the best progress I've seen on this problem since Lion came out and broke this basic capability.
BTW: I agree with you .. Mountain Lion is NOT an acceptable fix considering many of us (like me with a 2008 64-bit capable quad-core Xeon) cannot upgrade to Mountain Lion because of the 32-bit EFI .... even though our systems have plenty more power than a whole set of more current boxes that are upgradable..... but that's another gripe all together
Currently Being ModeratedNov 19, 2012 5:50 AM (in response to NelsonPunch)
Its possible to view the login screen. but good luck getting any further.
You will find the account buttons are actually disabled, so you cannot click to enter a password. After months of trying there is still no solution, other than upgrading to mountain Lion (paying Apple bucks to avoid Apple bugs).
Aaaand its up to
99172 Views 171 Replies
With still no word on a fix.
Currently Being ModeratedNov 27, 2012 7:26 AM (in response to mhren)
Same thing for me, the last update for "Remote Desktop Client Update" broke the ability to do any remote access from Tight VNC, Real VNC, etc. Can see the login screen just fine, but can't type anything. Is it going to take another update to access our Lion Server or should we just give it to a school and switch OS?
Currently Being ModeratedNov 27, 2012 7:39 AM (in response to KnightMB)
I think the general idea with Apple is they have swept this bug under the carpet and moved on to Mountain Lion. AFAIK that doesn't change much. They have basically made their screen sharing over VNC proprietary, either intentional or not. The fact is it doesn't help anyone out in a mixed OS environment though.
You could always opt for a third party VNC client such as Vine, which is capable of multiple sessions over multiple ports.
See this for a quick message regarding this configuration:
And see here for the actual software:
At least they have some active support, which is a major plus over this situation.
Currently Being ModeratedNov 27, 2012 11:04 AM (in response to Geordon)
I was able to confirm, the last update broke this. Basically, you have to screen share from another Mac system for it to work. Any other software for other operating systems is broke.
I loaded up Mac OS X in virtual box and used this to get to my Lion server, hope this helps anyone else until things are either fixed, changed, or marked as "too bad" I guess.
In finder, choose "Connect to Server"
Then use vnc://ipaddress.to.the.mac
Put in username and password, and like magic, it works again, but only on another Mac.
Currently Being ModeratedNov 27, 2012 11:40 AM (in response to Geordon)
I havent read all the posts, but would like to share a workaround to this corrupted vnc screen issue.
1. When u connect to a client machine, that shows corrupted/broken screen:
2. Push cmd + shift + 4 and and release these 3 keys, then push space bar, u get screenshot camera tool
3. When moving the camera tool, it starts to RE render the windows and bars and desktop etc..
4. Now u have fixed ur VNC screen connection
This has workded for us.
"Keyboard Shortcuts of taking pictures of screen"
Currently Being ModeratedNov 27, 2012 12:47 PM (in response to enthusuast)
Once I used another Mac to restart for the latest update, screen sharing started to work again for TightVNC, so I guess the problem was fixed? How confusing, but I'm glad it works again.
More Like This
- Retrieving data ...
- This solved my question - 10 points
- This helped me - 5 points