Skip navigation

Lion broke screen sharing, VNC?

158692 Views 200 Replies Latest reply: Mar 18, 2014 5:56 AM by dwmusic RSS
  • Ricky Yu Calculating status...
    Currently Being Moderated
    Jul 24, 2011 6:36 PM (in response to Laurent Drion)

    Turning it off and on, and turning Remote Management on and off DID NOT work for me.  The client VNC still shows the login window and nothing you do can make you login.  The keyboard is frozen, you just see the pointer move around. VNC/SCREEN SHARING IS BROKEN with Remote Management (ran ARD 3.5.1).

  • MixedUp Calculating status...
    Currently Being Moderated
    Jul 25, 2011 4:15 PM (in response to Ricky Yu)

    not working for me either from XP via VNC - tried ""Only use protocol 3.3"" but this didn't solve anything

     

    interestingly in the system log, after I try to connect with VNC (nothing else) I see the following - there are some logmein lines in there for some reason (also noting logmein is busted under Lion for the moment too...)

     

     

     

     

     

    loginwindow[768]: Login Window Application Started

    loginwindow[768]: **DMPROXY** Found `/System/Library/CoreServices/DMProxy'.

    com.logmein.logmeinguiagent[758]: 2011-07-26 09:02:46.434 - Debug     - LMIGUIAgent - SessionManager - sessionTerminating

    com.logmein.logmeinguiagent[758]: 2011-07-26 09:02:46.434 - Debug     - LMIGUIAgent - SessionManager - DisplayServer stop

    com.logmein.logmeinguiagent[758]: 2011-07-26 09:02:46.434 - Debug     - LMIGUIAgent - SessionManager - DisplayServer close

    com.logmein.logmeinguiagent[758]: 2011-07-26 09:02:46.434 - Debug     - LMIGUIAgent - GUIAgent - DisplayServerStopped.Sent[758]

    com.logmein.logmeinguiagent[758]: Session - Error occured:read errno: (9) Bad file descriptor

    com.logmein.logmeinguiagent[758]: 2011-07-26 09:02:46.437 - Debug     - LMIGUIAgent - SessionManager - Connection closed

    com.logmein.logmeinguiagent[758]: 2011-07-26 09:02:46.437 - Debug     - LMIGUIAgent - SessionManager - Closing DisplayServer

    com.logmein.logmeinguiagent[758]: 2011-07-26 09:02:46.437 - Debug     - LMIGUIAgent - SessionManager - DisplayServer close

    com.logmein.logmeinguiagent[758]: 2011-07-26 09:02:46.437 - Debug     - LMIGUIAgent - SessionManager - Exiting

    com.apple.launchd[1] (com.logmein.logmeinguiagent): Unknown key for boolean: UseLMILaunchAgentFixer

    com.apple.launchctl.LoginWindow[770]: com.apple.findmymacmessenger: Already loaded

    com.logmein.logmeinguiagent[774]: 2011-07-26 09:02:46.511 - Info      - LMIGUIAgent - Main - starting...

    com.logmein.logmeinguiagent[774]: 2011-07-26 09:02:46.511 - Info      - LMIGUIAgent - Main - started:774 uid:0 (parent:1 launchd)

    com.logmein.logmeinguiagent[774]: 2011-07-26 09:02:46.512 - Info      - LMIGUIAgent - Main - waiting for window server connection

    com.logmein.logmeinguiagent[774]: 2011-07-26 09:02:46.531 - Info      - LMIGUIAgent - Main - waiting for window server session

    com.logmein.logmeinguiagent[774]: 2011-07-26 09:02:46.532 - Info      - LMIGUIAgent - Main - connecting to session manager

    ManagedClient[776]: MCX.createConnection bootstrap_register failed = 1100

    loginwindow[768]: Login Window Started Security Agent

    loginwindow[768]: kCGErrorFailure: CGSPackagesGetWorkspaceType: couldn't get workspace type

    loginwindow[768]: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.

    SecurityAgent[777]: Echo enabled

    com.logmein.logmeinguiagent[774]: 2011-07-26 09:02:47.178 - Debug     - LMIGUIAgent - SessionManager - SessionAgentStarted

    com.apple.launchd[1] (com.logmein.logmeinguiagent[758]): Exited with code: 1

    SecurityAgent[777]: kCGErrorFailure: CGSPackagesGetWorkspaceType: couldn't get workspace type

    SecurityAgent[777]: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.

  • JaseOD Calculating status...
    Currently Being Moderated
    Jul 25, 2011 7:42 PM (in response to MixedUp)

    Here's my sample log. Some similarities to yours excluding the logmein stuff.

     

    21/07/11 9:54:57.343 AM screensharingd: Authentication: SUCCEEDED :: User Name: N/A :: Viewer Address: 192.168.183.12 :: Type: VNC DES

    21/07/11 9:54:57.434 AM loginwindow: Login Window Application Started

    21/07/11 9:54:57.445 AM loginwindow: **DMPROXY** Found `/System/Library/CoreServices/DMProxy'.

    21/07/11 9:54:57.558 AM com.apple.launchctl.LoginWindow: com.apple.findmymacmessenger: Already loaded

    21/07/11 9:54:57.610 AM com.apple.SecurityServer: Session 100027 created

    21/07/11 9:54:57.613 AM loginwindow: Login Window Started Security Agent

    21/07/11 9:54:57.646 AM loginwindow: kCGErrorFailure: CGSPackagesGetWorkspaceType: couldn't get workspace type

    21/07/11 9:54:57.646 AM loginwindow: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.

    21/07/11 9:54:57.782 AM SecurityAgent: Echo enabled

    21/07/11 9:54:57.782 AM SecurityAgent: Echo enabled

    21/07/11 9:54:58.016 AM sandboxd: ([743]) applepushservice(743) deny file-read-data /private/etc/master.passwd

    21/07/11 9:54:58.164 AM SecurityAgent: kCGErrorFailure: CGSPackagesGetWorkspaceType: couldn't get workspace type

    21/07/11 9:54:58.164 AM SecurityAgent: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.

    21/07/11 9:56:38.881 AM SecurityAgent: (ipc/send) invalid destination port: CGSGetNextEventRecord (Inline) connection 0x1a34f, 16384 bytes

    21/07/11 9:56:38.881 AM SecurityAgent: CGSShutdownServerConnections: Detaching application from window server

  • JaseOD Level 1 Level 1 (0 points)
    Currently Being Moderated
    Jul 25, 2011 11:45 PM (in response to JaseOD)

    Thought I'd give Screens for iOS a try since it specifies Lion compatibility.

     

    Everythingwentbetterthanexpected.jpg

     

    It works perfectly. I imagine I'll need to play around a little to work out all the gestures etc. In terms of pure VNC functionality it's perfect. Seems that sending username/password in the VNC connect does the trick. This isn't an option in the other clients I've been testing with. Screens might be doing other things under the hood as well, I dont know.

     

    It's not the cheapest option for remote control, but it's a very polished app. There are versions for iOS and Mac available, all $20.

  • Ricky Yu Level 1 Level 1 (0 points)
    Currently Being Moderated
    Jul 26, 2011 7:38 AM (in response to JaseOD)

    This does not work in REAL VNC from a PC.  What's the point of controlling a Mac from another Mac if Screen Sharing DOES work? In iOS is perfectly understandable, but no point of paying $20 for a Mac App.  VNC IS BROKEN FROM PC!

  • Ricky Yu Level 1 Level 1 (0 points)
    Currently Being Moderated
    Jul 26, 2011 7:40 AM (in response to Geordon)

    Here is an official response from REAL VNC:

     

    VNC Enterprise Edition is currently not compatible with OS X Lion...

    To ensure you continue to have the best experience when using VNC Enterprise Edition on a Mac we recommend that you refrain from updating to OS X Lion until Enterprise Edition version 4.6.2 is available.

     

    http://www.realvnc.com/company/press/news/lion-information.html

  • don\'t mind the maggots Calculating status...
    Currently Being Moderated
    Jul 26, 2011 10:49 AM (in response to Ricky Yu)

    They are perhaps correct in the sense of achieving FULL compatibility, but I was able to get it working.

     

    "VNC/SCREEN SHARING IS BROKEN with Remote Management"

     

    That's a correct statement - I think.

     

    I was able to connect from the Real VNC viewer on a win7 box, via lan to my mini, via Screen Sharing.

     

    I went through a ton of possible configurations, but what finally worked was closing the ARD app on the mini.

     

    Then I was able to connect without issue.

     

    After I connect via VNC, I can then start ARD and it works fine as well.

     

    I think the problem is that while they can both use the same port, either the app or the os is having a hissy fit over it.

  • Sven-Goran Ljungholm1 Calculating status...
    Currently Being Moderated
    Jul 26, 2011 4:03 PM (in response to don\'t mind the maggots)

    I had the same issue. What I did.

    Created new admin account using System Preferences.

    Logged out of current account

    Connected using screen sharing with new admin name and pass.

    Disconnected

    Logged in to machine as "old" user

    Screen sharing with "old" user works now

  • Reubania Level 1 Level 1 (0 points)
    Currently Being Moderated
    Jul 27, 2011 5:14 AM (in response to Geordon)

    OK! Following advice from another thread:

     

    1. DELETE ARDAgent 3.5.1 (HDD > System > Library > CoreServices > Remote Management)

     

    2. Copied ARDAgent 3.4 (available through Apple's own Support Download section)

     

    3. Restart machine

     

     

    AND Screen Sharing WORKS between my OS X Lion machines! NO WAY will I be installing ANY update of Remote Desktop Client Update from Apple EVER again!

  • boymilo Calculating status...
    Currently Being Moderated
    Jul 27, 2011 8:52 AM (in response to Reubania)

    Thank you for sharing this, I would like to give it a try. Where can I find ARDAgent 3.4? I am unable to locate it at http://support.apple.com/downloads/.

  • MixedUp Level 1 Level 1 (0 points)
    Currently Being Moderated
    Jul 27, 2011 3:57 PM (in response to boymilo)

    I've already reverted back to Leopard - will wait until there are obvious fixes in place before trying the upgrade to Lion again...

  • Reubania Level 1 Level 1 (0 points)
    Currently Being Moderated
    Jul 28, 2011 1:21 AM (in response to boymilo)

    Here is the link mate. Enjoy!

     

    http://support.apple.com/kb/DL1350

     

     

    Instructions by tchaga:

     

    1. Download ARD 3.4 (RemoteDesktopClient.dmg), mount it, look inside the package/Contents, copy the Archive.pax.gz to the desktop.

     

    2. Expand the Archive.pax.gz and navigate inside the resulting folder Archive to /System/Library/CoreServices/RemoteManagement

     

    3. Navigate to the same folder at the root of your HD (i.e. HD/System/Library/CoreServices/RemoteManagement)

     

    4. Copy ARDAgent from your HD/System/Library/CoreServices/RemoteManagement to the Desktop and then delete it from the HD/System/Library/CoreServices/RemoteManagement folder (you need admin password).

     

    5. Copy ARDAgent from Archive/System/Library/CoreServices/RemoteManagement to HD/System/Library/CoreServices/RemoteManagement (you need admin password again).

     

    6. Restart

     

    Message was edited by: Reubania

  • Andreas Yankopolus Calculating status...
    Currently Being Moderated
    Jul 28, 2011 9:11 AM (in response to Reubania)

    Did these steps allow you to connect from a VNC client on Windows to the Lion box?

     

    —Andreas

  • G.C.Thompson Calculating status...
    Currently Being Moderated
    Jul 28, 2011 10:52 PM (in response to Reubania)

    Thanks for the info; just applied the changes and restarted, unfortunately iTap VNC still has the same problem.

     

    I raised a support ticket with them a week ago, but no response as yet.

  • williamfromstudio city Calculating status...
    Currently Being Moderated
    Jul 31, 2011 11:59 AM (in response to Ricky Yu)

    You may have already  discovered this --- vnc is broken in ARD, but does work with :Screen Sharing".  Uncheck Remote Management and check Screen Sharing.

1 2 3 4 ... 14 Previous Next

Actions

More Like This

  • Retrieving data ...

Bookmarked By (10)

Legend

  • This solved my question - 10 points
  • This helped me - 5 points
This site contains user submitted content, comments and opinions and is for informational purposes only. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.