Lion broke screen sharing, VNC?

RealVNC Server will indeed reconnect as Apple used to up to 10.6.8, but the keystrokes don't match. On iOSProApps Custom Keypad app for example under Apple VNC, it works perfectly while still connected, but under RealVNC, Cmd+Shift+i is sent as just 'i'

What is a fantastic and powerful tool (still) under MacOS 10.6.8 becomes Roadkill from Lion 10.7 onwards.

Apple HQ is a mess these days, VNC is but one of the symptoms.

Is that it then, are Apple just ignoring it?

Computers NEED a cross-platform interface with multiple remote dektops. This is a fundamental part of a business network. Why has it been so badly executed and whats going on to fix it??

Apple apparently fixed the issue in Mountain Lion 10.8. For me it works as it should. It's a $20 upgrade, well worth the investment to alleviate the hassle.

Thanks William. Is there any official word on this? I'm yet to find anything. Where did you find this out, can you link me there? This is a no go without evidence as the buck will stop with me, not Apple. I'm not about to go there!

Also I hear Mountain Lion breaks existing Wikis and Users, something I'm keen to disprove, as my client has a wiki on Snow Leo at the moment.

In a corporate enviroment, where there are older machines, that wont be able to upgrade to Mountain Lion.

An 20$ upgrade is not going to solve this problem. There should be a fix to this rdm problem. We upgraded to

Lion, and some of the clients cant upgr to ML ...

So no remote desktop support for Lion clients without hassle?

This screen is quite often what you get when connecting to a client computer:

Sorry Enthususast.

I too work in a large enviroment, but it is primarily Windows. The few Macs i support are upgradable to ML. The issue with Lion has been onging and in my opinion Apple wiil not address it as another means of encouraging upgrades to ML. Apple has never been sensitive to backwards compatibily and that is why we shy away from it in my organization. just wanted to put out there that it works on ML.

William,

Is this from experience? If so, how many concurrent clients have you successfully connected to one share in ML? We had a nightmare testing Lion - so much so we might be forced to buy a PC for the server and use Terminal Services..even though they are 99% Mac users. Really blows, doesn't it!

Someone needs to start an Apple lobby group so those of a mind to, can bring the power of our numbers to bear against Apple when it breaks things and doesn't fix them afterwards. We expect more from a child than we are expecting from the world's biggest Wall St success.

There are millions of us, against a handful of board members, drowning in gold, so how has it come to pass that they can they repeatedly win against us like this? It's time for us to get emails going to the board members, and faxes to make them sit up and take notice.

If we work together, we can force Apple listen to us.

A fix on Mountain Lion ? WOW .. that would be great. BUT, my Quad Core Intel Xeon Mac Pro is not able to upgrade to ML. Considering it's more powerful than half the machines that are able to upgrade, it's clear Apple is restricting ML for arbitrary (and not entirely technical) reasons.

Can someone confirm what the "fix" is and if it might be a binary (or something) that can be added/run on Lion or do I have to continue to deal with a third party VNC server workaround (which happened to also crash on me so now this system is completely inaccessible to manage until I get back in town and can physically touch it later this week) 😟

I have Mountain Lion (10.8.1) installed, and still have intermittent but regular issues connecting remotely, either via Mocha VNC on iPhone/iPad using the "Mac OS X Lion sign on" over 3G, or UltraVNC for Windows at work (on a big fat pipe).

For me, it appears data gets garbled during the authentication process, according to a quick glance at a recent console log (if you can see the gist of what’s happening in this tiny screenshot)…

I just tried LogMeIn, after struggling with VNC login issues, and it works great. Thanks for the suggestion!

DW, just a thought but try wyse pocketcloud app for your iPad -- while I haven't tried against mac os x lion machines, I have used consistently against windows on my iPhone. (I know different animal, but might be worth a shot).

http://www.pocketcloud.com/remotedesktop#tab-video

http://itunes.apple.com/us/app/pocketcloud-remote-desktop/id326512817?mt=8

Keeping an eye on this thread though, as I'm looking to get a mac os x lion desktop for remoting into.

-Steve

Could this be due to the fact that the password length has changed from 10+ characters to only 8. I try typing in a new password but as soon as I hit the 8 one it doesn't let me type any further.

I have some users which were not granted permissions to do remote management, while one of their accounts was open I noticed an error stating that they were not authorized to use Ardagent. This occured even though under Remote Management the option to permit all users was selected. I have revoked the general permission and now explicitly granted each known user permission. I need to observe the machine longer to see if this helped the vnc issue I am having. I am mac to mac vnc with Jolly Fast Home from the app store or screen sharing.

-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... ?