Screen Sharing and ARD broken

Hi,
I have 10.9.4. I had remote management switched on and it was working fine.
I installed ARD 3.7 and started it up fine and it was running fine allowing me to do all what I needed.
I also need to remote to this Mac and so set the preference in ARD to allow control whilst the app was running. Thats when it went pear shaped.
It suddenly stopped allowing remote access to the machine.
I now have to be physically at the unit. I have removed ARD and all the files it has added and switched off all screen sharing and Remote Management in Sys Pref. Restarted and switched on Remote Management again.
I can still not access the machine remotely (i.e. screen sharing).
When trying to use screen sharing on the Mac itself to remote onto another machine I get the following in Console.
20/08/2014 15:08:23.459 Screen Sharing[1422]: unable to get server port
20/08/2014 15:08:23.459 Screen Sharing[1422]: *** -[__NSSetM addObject:]: object cannot be nil
20/08/2014 15:08:23.537 Screen Sharing[1422]: (
  0   CoreFoundation                      0x00007fff93cd525c __exceptionPreprocess + 172
  1   libobjc.A.dylib                     0x00007fff94276e75 objc_exception_throw + 43
  2   CoreFoundation                      0x00007fff93bf4966 -[__NSSetM addObject:] + 790
  3   ScreenSharing                       0x00007fff91f3a0e2 -[SSInputEventSourceCoordinator addSource:] + 69
  4   CoreFoundation                      0x00007fff93ca3e0c __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 12
  5   CoreFoundation                      0x00007fff93b9782d _CFXNotificationPost + 2893
  6   Foundation                          0x00007fff905277ba -[NSNotificationCenter postNotificationName:object:userInfo:] + 68
  7   AppKit                              0x00007fff96fb1cde -[NSApplication finishLaunching] + 440
  8   AppKit                              0x00007fff96fb17f3 -[NSApplication run] + 128
  9   AppKit                              0x00007fff96f9c783 NSApplicationMain + 940
  10  libdyld.dylib                       0x00007fff8f5b55fd start + 1
20/08/2014 15:08:23.622 Screen Sharing[1422]: *** -[NSLock lock]: deadlock (<NSLock: 0x6000000ca330> '(null)')
20/08/2014 15:08:23.622 Screen Sharing[1422]: *** Break on _NSLockError() to debug.
I can ssh to the machine fine, just not screen share (VNC).
Any help to fix allowing VNC to the machine would be greatly appreciated.
Regards
Keith

Further,
I have run a port scan and confirmed that port 5900 is open.
When using COTVNC it sort of sits there trying to connect but doesn't show the screen. If whilst it is trying I switch off Remote Management then COTVNC instantly throws up the error that screen sharing is not enabled.
Thus I am deducing that the actual VNC server of the os is goosed.

Similar Messages

  • Screen sharing and ARD windows to other computers are invisible!

    Hi
    I have been using screen sharing and or ARD with no problem, for some odd reason today when i went to control a iMac in my network, the window opens but is not there, like i hit command W and i noticed it closed windows on the iMac i can not see the screen at all.
    Please advise

    ahhh, thanks you did it!
    forgot to restart after system update!
    cheers

  • Screen Sharing and SSH sessions freeze occasionally on multiple mac minis

    I have 28 Mac Minis at work. With such a large number of minis, I obviously can't have a monitor attached to each of them so I've got them plugged into a network switch and access them via Screen Sharing (both via regular Screen Sharing and ARD) and SSH sessions.
    A few of them seem to suffer from intermittent problems however. I'll be using Screen Sharing when the session freezes. It may unfreeze eventually, but I can also usually just quit out and re-connect and it will be unfrozen. The same thing happens when I'm connected via SSH, it will freeze and I won't be able to type in any more commands.
    I need help troubleshooting (or if anyone knows what could be causing this, that'd be cool too).
    I've tried connecting from both a Mac Pro on the wired network and a MacBook Pro on the wireless network. The freezing seems to only happen on certain Mac Minis as well.
    I've tried switching network cables from a Mac Mini that doesn't suffer from this problem with one that does and nothing changed.
    I also thought it might be a bandwidth issue at first, despite being a gigabit switch connected via cat6 to the rest of our gigabit network, but even when no significant bandwidth is being used, the freezing still occurs.
    One more thing I want to test is the connection between the switch all these Mac Minis is plugged into and one of the other switches that all our other network traffic goes through. I didn't set it up myself so I fear that it might be an old, damaged cable or something. Failing that, I have no idea what the problem could be, which is why I'm posting here.
    So, does anyone have any idea what the problem could be? Or any other ideas for troubleshooting the problem? Thanks.
    (They're all running 10.6.8, and range from Mid-2007 to 2009 models).

    It would be in the system log. However, the next step would be to safe-boot in order to eliminate third-party system modifications. That goes for both client and server. If you can reproduce the problem in safe mode, then you probably have a network issue. Take everything offline except one client and one server, and test.

  • Screen Sharing and VPN functionality with ARD

    Can somebody with ARD tell me if the following setup is going to work? There's no demo version so I can't tell if it's going to be worth 300 dollars.
    I have a number of local machines in a network and a couple external machines in other parts of the state that VPN in to the network. I want to be able to have a local machine that can screen share w/ voice reliably with these guys.
    "Reliably" being the key. iChat screen sharing and VNC alternatives do not work reliably at all. They crash, they are slow, they sometimes disconnect video and keep the audio. Or some days they work perfectly, but that's few and far between. Zero-conf services like MacHelpMate work just fine, but I'm reluctant to pay 600 a year for something like this.
    Is ARD going to be able to be able to fix this problem for me, or am I really just going to end up with more of the same issues?

    ARD uses VNC for observation and control, so if you're having problems with iChat screen sharing and with VNC clients, I would not expect that ARD would be any better. My suspicion is that your network and/or VPN are cutting things off, since most people have found iChat sharing and VNC to be pretty reliable, but without being able to perform reliability tests on your network to VPN clients, I can't say for sure.

  • Screen sharing and remote management no longer working after some uptime

    Server is withoiut monitor.
    Users need to login via screen sharing from time to time.
    "Enable screen sharing and remote management" is ticked in Server.app everything is working fine (for days, weeks).
    ARD reports "Screen Sharing Available", so remote management is not running how it should.
    Screen Sharing.app is "Connecting…" forever.
    Kickstarting ARD (http://support.apple.com/kb/HT2370) does not help.
    Restart fixes it.
    Is there a workaround (over ssh) or a fix?

    seduc wrote:
    Do you know if
    fdesetup authrestart
    works then too?
    Off-hand, no.   I don't.  See this posting, or as would be typical in any case, try it?

  • Screen Sharing and WindowServer processes using 35-45% of CPU!!

    I have recently relocated and reconfigured my Apple network and computers in the house :1) MacBook Air dual display MBA with 20" cinema screen in the office, and 2) and Mac Mini connected to a large LCD TV in the living room.
    The plan now is to use the MBA as a primary computer and connect via wireless screen sharing to the MM so that I can monitor that system, run more intensive apps, watch EyeTV, file server tasks, etc.
    But now this has increased CPU and fan activity on the MBA beyond what I would expect. The activity monitor indicates that the Screen Sharing and WindowServer processes are using combined between 35-45% of the CPU (screen share process is a constant 25%!!).
    This is not good, and I wonder if it will be fixed in a future release. Any ideas or suggestions on how to limit the impact of screen sharing on CPU?

    It seems to be running better with system update, and use of a faster computer (now using the higher end mac book air)

  • Screen Sharing and Drive Sharing

    Hey all!
    I've got a Mac Mini that I am using to share files. I have an external drive attached via FireWire. The SMB and AFP shares only show up for the EXTERNAL drive when someone is logged in. Is this the expected behavior? Does anyone else have this happen?
    This isn't all! I've noticed that when I use Screen Sharing and click "Return to Login" from the upper right corner, that I loose my Screen Sharing connection AND AM UNABLE TO CONNECT AGAIN. I've been able to reproduce this behavior on my Mini, MB, and MBP. Anyone else experience this?
    Thanks in advance!
    Jason

    Thanks for the ideas! I kinda figured drive sharing wouldn't work from the login screen...seems kinda bogus though, but I guess if I want that, then I'd have to get OS X Server.
    As for Screen Sharing, I disagree. When I connect to a Mac via Screen Sharing from the login screen, it lets me choose a logon and login. When I choose to go back to the login screen...the screen freezes. When I hook back up to the Mini from the console, the screen is frozen on a blue screen. No mouse, no keyboard. I believe it worked under a previous version of OS X 10.5...so I'm not sure if 10.5.4 messed it up...
    Thoughts?

  • Screen Sharing and video chats don't work

    I've been searching this forum for awhile and I haven't found a concrete answer to my problem, so if this question has been answered please excuse me. Ok, So here's my situation am running iChat on Mac OS 10.5.1. Whenever I am using my laptop at my school on the network their, I am able to use both screen sharing and video chat. But when I am at home, I am unable to use either one. It begins to try to start the session, but then i receive a message that tells me that a connection could not be established. I know that I have internet access, but I don't know what could be wrong with it.

    After investing far to long in looking at this exact issue on my end, reading the seemingly endless threads on the exact same error, trying all the various tweeks and QT settings, bandwidth limit settings, etc etc. proposed here, I have now solved this problem, and the none of the above were part of the solution.
    I have perhaps one of the the most common routers on the market, Linksys WRT54GL.
    In a totally unrelated network problem (a printing issue), Linksys tech support advised me to reset my router. There is a small button on the bottom. I depressed it for 30 seconds. Rebooted everything and my printer miraculously worked. Yea, I had to reenter my WAP passkey, router admin password etc., but that took 2 secs. So, what does this have to do with iChat?.... The very next time I tried iChat video and turned on and enabled my camera, the recipient immedialty saw me. No connection error.
    Problem solved, for me art least. Not sure if anyone has tried this, but makes sooooo much more sense than the other unApple like suggestions I previous tried. Hope this helps.

  • Screen sharing and yosemite

    I have 2 iMacs running 10.10.1  not on the same LAN. Under Mavericks both screen sharing and file sharing worked fine on both computers
    Since the upgrade to yosemite, i can access file and screen sharing on one computer but only file sharing on the other.
    Both computers have back to my mac activated. Since screen sharing works fine on one computer, I must assume a setting somewhere is incorrect
    Thanks
    Jeff

    Screensharing doesn't require a 'bonjour advertisement'. The advertisement causes other Macs to add it to the sidebar - but that is just to help cut out manual config.
    You could try working out the IP address of the Mac see if Screensharing works that way. Find that in Network Prefernces for the interface that is on the same local network.
    Insert the following into Safari…
    vnc://YOUR-IP-OF-REMOTE-MAC
    That will open the Screensharing app (which is buried in the System folder) and attempt to open the IP of the machine in question. If that works you know sharing is OK but mDNS a.k.a bonjour is failing somewhere. If that fails double check the local IP & retest. It indicates screensharing itself is failing etc.
    You can also try the computer names like 'Macbook.local' instead of the IP address.

  • Screen sharing and file sharing not working on LAN

    This is not a Mavericks specific problem since it existed before I upgraded to Mavericks.  I have a LAN that consists of 3 MBPs and 1 MacPro.
    Local screen sharing and file sharing works fine on all of these computers except for one MBP.  From this MBP I am able to connect to all of the other computers for screen sharing and file sharing.  But I can't connect to this particular MBP for screen sharing or file sharing from any of the other Macs.
    This MBP shows up in the left hand side column under "Shared" on all the other computers.  But I am unable to make a connection from any computer to the problematic MBP.  I get the message, "There was a problem connecting to the server "xxxxxxxx".  The server may not exist or is unavailable at this time".
    I have tried toggling off and on screen sharing and file sharing with no effect.  One probably pertinent strange thing that I notice is that under the Screen Sharing set up the green button next to "Screen Sharing:On" is green.  But the message under it states:
    "Other users can access your computer's screen
    at vnc://johnmacbookproretina/ or by looking for “John MacBook Pro” in the Finder sidebar."
    The problem is that my computer name is "John MacBook Pro" and the LocalHostName is "JohnMBPr.local".  I believe that at some point in the past the computer name and/or LocalHostName was "johnmacbookproretina".
    Similiarly, under File Sharing I am informed:
    "Other users can access shared folders on this computer, and administrators all volumes, at “afp://johnmacbookproretina” or “smb://johnmacbookproretina”."
    I would appreciate any help I could get to resolve this perplexing issue.  Thanks.
    John

    I've finally been able to solve my own problem.
    File sharing and screen sharing on the problematic MBP was being blocked by firewall rules that had been set up several weeks ago when I had installed a trial version of DoorStop X firewall software.  I had previously trashed the app when the 30 day trial ended.  I did not realize that the software had left a set of firewall rules in the Library/StartupItems folder.  Among other things, the rules were set to deny access to the computer on the ports used for file sharing and screen sharing.  Once I trashed the DoorStopStartup folder in the StartUpItems folder all the connection problems resolved with a computer restart.

  • Screen Sharing and Remote Login suddenly stopped working

    I have had Screen Sharing and Remote Login turned on on my iMac for several weeks and they have been working fine up until now. I have been accessing the computer via VNC programs and command-line ssh logins from other computers on the same local network. When I tried to connect today, i was given the following error message.
    ssh: connect to host xxx.xxx.xxx.xxx port 22: No route to host
    I have all of the required settings turned on in System preferences and there are no firewalls or router settings blocking it. I connected the two computers together via ethernet cable and the error message still occurred.
    I can ssh from the machine to 127.0.0.1, so the ssh server is running. I can ssh to other locations from the laptop i am attempting to connect with, so that's not the problem either. I just spent an hour on the phone with the apple tech support line and they couldn't figure anything out either. Can anybody figure something out?

    have you tried the obvious - restarting the computers involved and the router?

  • Screen Sharing and Remote Management

    Is there a way in 10.6 to make both Screen Sharing and Remote Management run at the same time?
    In the past (10.5), you could convince Mac OS to run both Screen Sharing and Remote Management to run simultaneously. I say "convince" because you could not enable them both through System Preferences. You could turn one on, then use Terminal to enable the other. This worked great for me, because I needed remote management for the machines I managed, and the users need screen sharing to work from home.
    However, the work-around for 10.5 no longer seems to work for 10.6. Has any one gotten this to work yet for 10.6? Thanks!

    I figured this out. First enable Remote Management via System Preferences. Then create /private/etc/ScreenSharing.launchd with 'enabled' as it's contents.

  • Screen sharing and video

    Hello all.
    video works fine at my house where I can turn on UPNP. However at work nothing works because UPNP isn't enabled. I have to forward all ports to my laptop. So my question is what ports to forward?

    It is with the Screen Sharing side that we have real problems.
    iChat 3 used
    TCP 5190, 5220, 5222, 5223, 5298
    UDP 5060, 5190, 5297, 5298, 5353, 5678, 16384-16403
    This includes all the Jabber, Bonjour and A/V ports as well as the Login and File sending.
    Leopard/iChat
    Same until we get to that last group or twenty UDP ports
    Port 5060 is dropped and the group becomes just 10 (16393-16402) still inside the iChat range if already done.
    The Screen Sharing I have seen with Little Snitch running suggest this happens on three ports. Two for the Screen Sharing and one for the Audio part.
    The Audio part remains where is does in Normal Audio or Video chats with it's first choice being 16402.
    It's the other two ports.
    Theses seem fairly random in the 50,000 range. They are widely dispersed as well which makes it difficult to suggest a small range that iChat might then use.
    9:26 PM Monday; December 24, 2007

  • How many users using Screen Sharing and Theater?

    I would like to know if the new features Screen Sharing and Theater are just to use face to face or if it is possible to made Theater session with for example 3 members.
    Thanks in advance

    iChat Theatre can be to or from one of the other Buddies in a 3 or 4 way chat.
    Screen Sharing is one on one
    8:59 PM Saturday; December 1, 2007

  • Can connect with Server Admin and Server Prefs, not Screen Sharing or ARD

    Just set up 10.5 server on my G5, and trying to connect from 10.5 on my iMac. I have tried both with the server System Preferences set to allow Screen Sharing via VNC, and with Remote Management enabled for ARD. In both cases, I get authentication errors when trying to connect from home. I have tried with both the full username, and with the short name of the only account on the server. My assumption is that, since this is the administrator account, I don't need to setup explicit privs for it on the server.
    I can authenticate without any trouble with both Server Admin and Server Preferences.
    The Firewall is not enabled on either machine, although I am behind a NAT router at home -- is it necessary to open any special ports to enable screen sharing? Is it possible that having these ports closed would produce an authentication error?
    Thanks for any help.

    Hi
    I'm going to assume you configured your Server in Standard Configuration and not Workgroup or Advanced?
    When using Standard in setting up the server DNS is automatically configured for as well as the Server taking an Open Directory Master Role. The admin account created at the beginning is for administering the Open Directory. Unknown to you and not documented at all - as far as I can see - is the 'Local Administrator' (localadmin) account.
    You only become aware of this account if for some reason you have a problem with the Server which involves demoting to Standalone (ie not an Open Directory Master) once this happens you find you can't log on to the Server anymore or communicate with any of the Server applications because it won't accept any username or password other than root and localadmin for the name and the password defined for the original admin account you created right at the beginning.
    Sometimes it does not even take demotion to find yourself locked out of the Server. Some have experienced this problem when running the Security Update or when some other problem has occured.
    Part of the process of creating an Open Directory Master involves the creation of a 'special' directory administrator account. This account is used for administering the LDAP node. If demotion takes place this account gets blown away along with all users and group accounts that exist in the LDAP node, in fact everything to do with Open Directory is destroyed apart from Users' home folders.
    Why demote if this happens? Sometimes the LDAP database gets damaged/corrupted beyond a point where normal troubleshooting methods fail. This can happen for a whole variety of reasons but more often than not is due to a poorly configured DNS Service. You basically only have two options once you reach that stage. A server reinstall involving a format and rebuild or a demotion to Standalone. Which option would you choose? Prior to demotion you can (if you have the chance) export users and groups or even archive the LDAP database itself for restoration later on. This is a useful option as everything to do with the LDAP Server is retained - passwords, users, groups etc. The other method of saving users etc does not retain passwords.
    As time goes on and you become more familiar with your server you will find more and more of this information out for yourself. Hopefully the simple advice I've given helps you understand Open Directory a little better.
    Hope this helps, Tony

Maybe you are looking for