Screen Sharing Failure from Admin 3.72 to Yosemite Clients 3.8

My Yosemite classroom Macs have ARD Version 3.8. My Admin version is 3.72. I can do everything with the clients except share my screen, which I use every day for teaching and demonstrating. I discovered I can still share my screen with the remaining clients using ARD 3.71 or earlier. So, is there a solution, an Admin upgrade or a downgrade available for my clients back to 3.7.1.

I have talked to two of the specialist in the Apple Service Center and they didn't even know this was an issue.
I wanted him to do exactly same environment that I am having in my iMac lab. This guy was keep saying that it is me who is having a network problem. So he was telling me to install Yosemite again. And it did not solve my problem of sharing screen.
The other guy that I talked to was patient enough to do as I have explained. If the Admin was upgraded to Yosemite and clients are still in Mavericks then screen sharing is working just fine. But if you upgrade client computers to Yosemite, then screen sharing is not working as it should be.
It has been already a month now that I told him what I am experiencing, and it is not still solved yet. He told me he was gonna report it to the relevant department. I really need to get things ready before March, otherwise my class will have to go back to the stone age again....... watching on projector screen.....

Similar Messages

  • Remote Screen Sharing (VNC) from outside of my LAN

    I often have to connect to my parents' Macs to help them out with various things. I commute between two cities and stay with them when I'm there.
    (I set up a dynamic hostname with DynDNS to point to our router, which defaults to port 443, which on the home network is reserved for the QNAP NAS that's set up. I set the router up to be reachable at port 455 but I'm not sure if it is successfully sending IP address updates to DynDNS. I don't see a way to check if it is. DynDNS seems to require a paid account for that functionality and my routers log is also not very helpful. In short, I'm having trouble getting the whole dynamic DNS thing to work reliably with our router, which is otherwise a great little box: a Fritz!Box Fon WLAN 7390).
    I use Jolly's Fast VNC (http://goo.gl/UmllQ) to connect to a personal server and that works wonderfully, but then there the details are taken care of for me by my provider and I just have to type in the details.
    What I'd really love is something like Edovia's Screens (http://www.edovia.com/)... except for the Mac rather than the iPhone/iPad (though I do own an iPhone copy of it and it's wonderful).
    We do share a MobileMe subscription in the family, but that's not very helpful here either.
    So far, we've used iChat, Skype screen sharing and I often end up using TeamViewer because of its speed and near non-existant setup.
    My goal is to find a way to connect to my parents' Macbooks even when they are not around so I can help them out with problems while they may not even be around. The key here is that I want to be able to control their screens without needing any action on their part.
    Suggestions for the simplest possible way to do this are very welcome.

    I didn't know TeamViewer could be set up to be accessible without a second user having to be around to give me the session ID and password. I wonder if it's worth looking into that if LogMeIn Free with its server always running is a perfectly acceptable solution? Any advantages to using TeamViewer's solution?
    The free LogMeIn account does NOT allow file transfer. The free for personal use TeamViewer does.
    LogMeIn server hides in the background, so it is less likely your parents will Quit LogMeIn.com, were as TeamViewer looks like just another app, so they might Quit from it to get it out of the way.
    Of course if you need to transfer a file (or 2), you could use DropBox.com for that, and it is a very easy way to transfer files between systems. Or you could store the file on your MobileMe account in a public place, then via LogMeIn copy the file from your public space into your Parent's Mac(s). Or your could use LogMeIn to start TeamViewer, and then use TeamViewer to transfer the file.
    Basically once you can start applications on your Parent's Mac(s), you can use any number of utilities for transferring data.
    We do have MobileMe. I was under the impression that the way Back to my Mac works is that it will show you YOUR remote Macs in the Finder's sidebar. You know, ones that you're also logged in with YOUR MobileMe credentials. We all use our own, unique MobileMe accounts. Am I missing something?
    Yes, all the Macs would need to use the same MobileMe account. Do you all really need separate accounts? Maybe a Family account.
    I could deal with the port forwarding and DynDNS but I'll have to set that up to remotely administer my router and NAS, which is turning out to be quite the pain. So if I can simplify, I will. LogMeIn or TeamViewer will do the trick just fine.
    Port forwarding is a once and done thing for your parent's router. It allows you to get to their Macs from outside their home. It should have nothing to do with remote admin, or your router and NAS. Also once you can Screen Share your parent's Mac, you can then use that Mac to talk from the inside to their router. Although one must be very careful about making router config changes as one "Oops" and you could loose your remote access, and have to visit Mom and Dad to get physical access
    By the way, I've been using VNC/Screen Sharing and AFP file sharing over ssh tunnels in conjunction with port forwarding on the destination router for years. I do this, even though it is more work, because it was available long before most of the above services were available, and because it has a lot more flexibility once you know how to use it. Oh yea, I'm also a Unix software developer and spend a lot of time using ssh anyway

  • I accidentally deleted Screen Sharing app from my Macbook Pro (Mountain Lion). Can I download it again?

    Any chance of finding this as a download?

    Hi Carolyn;
    Well it seems like I wasn't as stupid as I thought. I initially thought I'd deleted an app called Screen Sharing from my applications folder, as after I'd finished my session of deleting unused apps, the availablity of the "Share Screen" button in the Finder window (under the "Connect" button) when you click on a shared computer in the home network was gone.
    Now it seems it's back.
    Problem solved!

  • Screen sharing works from home to work but can't type shifted characters

    hi
    i can successfully connect to from my home (using macbook or macmini) to my work mac using screen sharing but it seems that i can't type shifted characters like
    @ or _
    i can type these characters using screen sharing within the network at work so. any reason why this might be?
    best wishes
    max

    I'm having exactly the same keyboard issue.  Certainly nothing has ever enhanced my concentration while coding like suddenly becoming unable to type.
    I'm seeing a great many devicemgr and rake errors in my system log.  I don't know if they're related.  How 'bout you?
    If you're unfamiliar with the system log…
    Open /Applications/Utilities/Console.
    If necessary, choose View > Show Log List.
    system.log is at the top of the FILES section.
    Try searching it for hot words like DEBUG, FATAL, and aborted.
    I've found some discussions that would tend to indicate my errors are postGres related – I'm running OS X server.
    -Bryan

  • Screen Sharing won't work, but every other VNC client will

    I have been trying to resolve this for months, and nothing has worked so far. I can connect to my Mac Mini Server (Snow Leopard Server) from LogMeIn, from Chicken of the VNC, from JollyFastVNC, and from VNC clients on my iPad and iPhone. However, I cannot connect using OSX's own Screen Sharing service. I'm really frustrated, and I've posted here before without any sort of help. Is there ANYONE that can solve this problem for me?

    To restate your issues and your question and your concern, you're frustrated, you're using a WiFi connection, you're not attempting remote access, it's not working for some protocols, and you're receiving unspecified error message(s).
    Start by posting the diagnostics and messages received when this "doesn't work".
    Then reconfigure the network, and (for testing) specifically move the screen sharing client box onto (and add one if needed) the same network switch as the server. Remove the WiFi device (a router) from the network connection. (Unmanaged gigabit network switches are cheap, too.)
    In addition to and in parallel with reconfiguring the network (for testing), also confirm that all of the network port connections on the WiFi are established on the correct physical ports, if you're using that device as a network gateway and NAT device in addition to using it as a router.
    Also ensure the firmware on the WiFi device is current.
    Drop the firewall on the client.
    Given you're probably on a NAT-based network and (guessing) using the WiFi device is configured as a gateway, post up some DNS or mDNS information, and a forward and reverse dig of the IP address. (I haven't seen issues such as this with local screen sharing via the Apple tools, but other Apple tools are known to be sensitive to incorrect DNS configurations.) From the same client you're attempting the screen-sharing:
    dig -x your.target.ip.address.

  • Screen Sharing and Wake from Sleep

    Hi,
    I'd like to know if there's any way a Screen Sharing request from a remote vnc client can wake a Leopard machine from sleep. I've opened the vnc port on firewall, tested screen sharing while its awake... all good. When the target machine is asleep though it doesn't see the request as "Wake for Ethernet Administrator Access" I guess ?
    Has anybody found a way to do this? I spoke to Apple support but they suggested I try Discussions.
    Cheers.

    None of the file sharing or screen sharing apps actually send the WOL packet. You can have launchd watch the screen sharing app and then send the WOL signal when you use it. There will be a slight delay but it does work. You need to download and install wol as it does not ship with osx. You will also probably want to get "lingon" so you can set up launchd easily.
    Commentary: I find it ridicules that this stuff isn't already built into the apps. Electric costs money and using it unnecessarily is a waste. Yet not one of the apps or tools designed to work over ethernet with another computer sends the wol command. Its like the developers expect you to have your computer on 24/7.

  • Screen sharing from Mtn Lion to Lion?

    Currently I'm on a Mountain Lion system and I have a system that is remote which uses Lion, I am able to use Back to My Mac to connect and browse files but Screen Sharing (Lion system on the Mtn Lion system) will never connect.
    Should this be expected to work?

    Jim, I may have solved the problem. Don't know if it is a permanent fix yet though.
    On the Lion computer, on the Sharing Control Panel, I turned on "Remote Management" rather than screen sharing.
    When I did this, Screen Sharing was disabled. I then turned off Remote Management and re-activated Screen Sharing.
    From this point Share Screen seems to work and I am now able to see the screen from the Lion computer on the Mountain Lion computer.
    Throughout the day I have been able to share screen the other way (displaying the Mountain Lion computer's screen on the Lion computer) without any problems.
    No idea why this would work, but seems to have done the trick for me!

  • Back to My Mac / Screen Sharing

    I am trying to (and have had sporadic success with) controlling my desktop computer (at home, iMac, OS X 10.10) with my laptop (via Internet, Macbook Pro, OS X 10.10.1) through connecting through Screen Sharing from the Finder window's "Shared" computers. It's really hit or miss whether the iMac shows up in the Finder window, and I can't figure out why.
    I've been all over websites and forum posts for information, and have learned a lot of things, but many of them are outdated. Here are some things I've done/learned about:
    I can always log into my iMac through Chrome Remote Desktop, but I want the functionality of Screen Sharing.
    I cannot simply start the Screen Sharing app and type in my icloud id, because that only allows viewing and not controlling the screen.
    SSH through the terminal is hit or miss; it works more often than Screen Sharing does, but still not 100% of the time. I use it to copy files, but most of the time I need to be using the GUI.
    A couple times the iMac showed up in Shared computers right after I did something, i.e. trace route to icloud.com or initiate a Screen Sharing session from the iMac, via Chrome Remote Desktop. Other times I've tried to jumpstart it like that and it doesn't work.
    I've tried a variety of networks (home networks, workplace, mobile tethering) and I get different results every time, on every network. I might see my iMac in the Finder at work one day, and the next day it doesn't show up now matter what I do. So it must not be blocked ports in every case.
    I've been taking notes almost every time I successfully connect, and I have documented cases where I can get it to work by (once again) going into my iMac via Chrome, disabling Back to My Mac and/or Screen Sharing, then re-enabling them. But of course, this hasn't worked consistently.
    Any help or insight is appreciated. Again, this is all purely done over the internet, as accessing my home computer over a local network is of no use to me; I'm physically separated from it most of the time. (Most articles and walkthroughs teach people how to do it with their 192.168.x.x addresses, and they assume that your computers are always in your Shared section in Finder. This is not the case for me.)

    That means that the Remote Management is turned on.
    All you have to do is turn the Remote Management off if its not in use.
    You may want to investigate how the Remote Management is being used to make sure you are not turning something off that needs to be on.

  • Screen sharing- not showing who is on my mac

    i've got screen sharing setup on all our macs and works great- HOWEVER, on occasion, a number of things can happen:
    1- i am unable to access a computer even though i accessed it earlier; i need to restart the computer and then it works
    2- when i shut down the computer, a message pops up that 2users are accessing the computer though there is only one or even none on the network that can do so and the remote computer icon shows only 1computer address or no icon present (does that mean someone is hacking my computer?)
    3- when i shut down the computer, a message pops up that there is a user and there is no remote computer icon visible (again, is someone hacking my computer?)
    2 and 3 above concern me the most especially since at times i don't see the screen sharing icon, so don't know who's accessing the computer... and no one knows how to access my main computer which is where this problem occurs. 1 happens on the other macs when trying to access the main computer.
    i've got my network running on a timecapsule with WPA2 personal security, password for timecapsule disk, password for computers, screen sharing set to admin only with no other people listed for access so a bit concerned about this would GREATLY appreciate the help/information anyone has!
    thanks
    ps- i also had this problem in snow leopard

    The upgrade just showed up for me when the criteria was met. Try reindexing your Mac.
    Spotlight: How to re-index folders or volumes -
    http://support.apple.com/kb/ht2409

  • Screen sharing in Mountain Lion

    The apple creen sharing app is no longer working in Mountain Lion. How can i now screen share remotly to nother mac without physically being at that computer to accept it (hence why i cant use iChat)?

    I found the problem. I was using an old version of Screen Sharing either from lion or snow leopard which doesnt work on Mountain Lion, you either type vnc://***.***.***.*** in Connect to Server in finder and it will automatically open screen sharing, or you can find the new screen sharing app in System/Libraby/CoreServices.

  • Yosemite Messages Screen Sharing Router Type: Port Restricted

    I want to do Screen Sharing via Messages as newly enabled in Yosemite (through Messages...not the Buddy List).  Unfortunately, it fails.  I run Connection Doctor under Video in Messages and see that I have an issue with the message "Router Type: Port Restricted".  I would like to see "Full Cone".
    What do I need to do?
    I am on AT&T U-Verse running a Motorola NVG589 modem. I have the wireless disabled on the NVG589.  The NVG589 is connected via ethernet to my Apple Airport Time Capsule (the tower model that is 802.11ac).  The Airport Time Capsule is set up in Bridge Mode - so as not to create Double NAT but to offer 802.11ac wifi speeds and to provide Time Machine backups.
    I have connected directly to the NVG589 modem and gotten the same "Router Type: Port Restricted" message.  I assume I must open a port/ports on the NVG589. If so...what are those ports?
    Any help would be greatly appreciated!

    Hi,
    The Messages app in all versions up to Mavericks only Screen Shares with AIM to AIM and Jabber to Jabber contacts as well as Bonjour connections on your LAN.
    It is based on those accounts that do Video and Audio Chats within the app.
    The iMessages invokes FaceTime to do Video and will not do Screen Sharing.
    However as you say there is this info:-
    Share a conversation —
    and your screen.
    Now you can share your screen with the person you’re chatting with. Then you can go from iMessage conversation to screen sharing with just a click. You can easily do things like collaborate on a presentation with a colleague, browse the web with a friend, or select airplane seats with your spouse. And Messages automatically initiates an audio chat when you start a screen sharing session, so you can talk things through while you’re at it.
    On checking the icon to Screen Share does appear in iMessages conversation Details option
    Notice the slightly diminished ("greyed out") quality to the Screen Sharing icon.
    It appears it only works to other Macs.
    The Buddies menu also has the option greyed out.
    Routers
    My Network Status looks like this.
    The Bandwidth Limit is set in Messages > Preferences > Video/Audio pane > Bandwidth Limit.
    Setting it to 500kbps is over what it needs to do 4 Way Video chat as Host.
    When it is a really fast connection to a much slower Buddy it can help  and also with higher speeds come higher variances which and cause havoc.
    There are four main type of Router  type as this refers to them.
    http://en.wikipedia.org/wiki/Network_address_translation#Methods_of_port_transla tion
    Port Restricted is just as effective as Full Cone.
    I have had it show up this way on a  Thompson-Alcatel 510v4 when I was first On line in iChat 2 and Netgear device I forget the number of, a Sagem Fast2504 from Sky my current internet provider when I had DLS and the current Fibre Hub that they supply.
    I have UPnP set as the method to open the ports needed.
    This allows the computer (apps) to tell the router which ports to open.
    They will also close after periods on Non use.
    Router that do UPnP advertise the fact.
    You can reduce the number of devices that happens through (Hops). The default setting is normally 4.  Router to computer counts as 1 Ethernet hubs don't count. But large LANs with more routers (Subnets to LANs) will count as more Hops.
    Ports.
    Most devices have the first 1024 port open (there are 65355 in total).
    These lower numbered port handle things like Web Browsing on port 80.
    FTP on port 21 and 22
    Some Outgoing Mail servers on port 25
    Secure web connection on port 443
    and so on.
    Messages and FaceTime Video chats use ports above this.
    These are the one you tend to have to allow.
    Video uses 5678 to send invites then moves to port 16402  (or one from a group of 10 ports below this)
    10:02 PM      Saturday; November 22, 2014
    ​  iMac 2.5Ghz i5 2011 (Mavericks 10.9)
     G4/1GhzDual MDD (Leopard 10.5.8)
     MacBookPro 2Gb (Snow Leopard 10.6.8)
     Mac OS X (10.6.8),
     Couple of iPhones and an iPad

  • Screen Sharing Insecure

    When I ran a screen sharing session with a friend, he had control of my screen. I couldn't find an option to limit access to my system while screen sharing. Anyone know where it is? Or does apple still have to implement some form of option for that?

    Soundman5 wrote:
    When I ran a screen sharing session with a friend, he had control of my screen.
    I couldn't find an option to limit access to my system while screen sharing.
    that's just what screen sharing is for. if you don't want it, disable screen sharing in system preferences->sharing or keep it enabled but don't give out your password to friends.
    Anyone know where it is? Or does apple still have to implement some form of option for that?
    I'm not sure what you mean. when someone is sharing your screen you get a scrrensharing menu icon and you can stop a screen sharing session from there. is this what you are asking?
    Message was edited by: V.K.

  • Chicken of the VNC connects to my PC running RealVNC, Screen Sharing can't?

    Hi,
    One of the big features I was looking forward in to Leopard was being able to connect to VNC servers using the OS instead of a dedicated app, but when I try to use Screen Sharing to connect to my PC which is running a VNC server, I get the error:
    "Connection Failed .... Please make sure that Screen Sharing (in the Sharing section of System Preferences) is enabled on the computer you're attempting to connect to. Also make sure your network connection is working properly."
    This also happens if I try to make the connection via directly launching Screen Sharing or from the side panel of a Finder window or by doing command-K.
    The weird thing is that Chicken of the VNC connects to the server without a hitch. Anyone know what might be wrong here? The PC is running RealVNC Personal Edition and has Bonjour for Windows installed. The Mac and the PC are on the same subnet.
    Thanks in advance for any assistance!

    Halle Winkler wrote:
    ....I still have to use command-k in order to connect because the finder doesn't auto-detect the VNC server....
    The weird thing is that Chicken of the VNC connects to the server without a hitch. Anyone know what might be wrong here? The PC is running RealVNC Personal Edition and has Bonjour for Windows installed. The Mac and the PC are on the same subnet.
    Finder probably isn't auto-detecting the VNC server because it likely isn't being advertised via Bonjour. I don't think Bonjour for Windows does much aside from give a Windows box the ability to listen for Bonjour printers and see Bonjour HTTP bookmarks. I'm unaware of it performing any sort of advertising of the services on a Windows box.
    For Finder to do the auto biz, you will likely need some other sort of Bonjour advertiser, like Rendezvous Proxy or a mdns DNS server sending out an appropriate rfb.tcp service advertisement.

  • Screen Sharing freezing and high CPU usage

    Hello all,
    I use screen sharing to remote my mac mini as a media server connected to ma HD TV to play movies, music and surf.
    Since I upgrade to mavericks on my macs (Macbook Pro Retina and my Mac Mini) I have some troubles with the screen sharing feature.
    No problems with the login step, the connexion is fast, all permissions are OK (I saw there were a bug with some RDP release) but sometimes, when I use fullscreen software as VLC, Firefox, etc (not the native apple full screen feature, I just clic on the + at the top of the window), my sreen sharing freeze and I can't do or move anything on the remoted mac mini. I'm unable to close (or reduce) the screen sharing app too, it's totaly busy (But I can see the movie or the website on the 2 computer, there is no deconnection)... I have to kill the process through the monitoring activity.
    During the freezing time, I try to use vnc light from my Iphone and I have no problem, I can move the mouse, reduce le VLC windows... As soon I reduce the VLC windows, the screen sharing works again. I also use the logitech TouchMouse to remote the mouse, everything work fine.
    Here are a screen shot of the monitoring activity of the Mac running the screen sharing app, we can see that there is a very high CPU usage when I use VLC in fullscreen on my mac mini. The first is in normal mode. The second is in freeze mode. Screen Sharing is named "Partage d'écran".
    Can someone help me to fix that, everything works fine with Mountain Lion.

    I have a Macbook Pro 13.5" 2.8 GHz 4 core (2 real, 2 hyperthreaded) i7 machine running with 1920X1200 display, 3 virtual screens and VMWare adding a few virtual screens (full sized).  I have another Macbook Pro 15" with 2.6 GHz Haswell 8 core (4 real, 4 hyperthreaded).  I see the problem using Screen Sharing on the 15 inch (Retina screen) mode simulating 1920 X 1200 pixels using Screen Sharing to the 13.5" Macbook Pro.
    When I get the ScreenSharing problem, I have identified it as related to the VMWare screen on the 13.5" Macbook Pro being shown through Screen Sharing on the Retina Screen.  Before you conclude it is a VMWare problem, the computations are only on the Screen Sharing client side, not on the server side running VMWare.  The mouse gets unusable through Screen Sharing.  If I physically move the mouse on the 13.5" Macbook, no problem.  If I switch virtual screens, the Screen Sharing goes to normal processing.
    I see an appearance of a compute-bound thread on the Screen Sharing client.  It takes 100% CPU on one thread, the machine as a whole is 12.5% busy (the performance monitor considers all 8 threads as equal when in fact, they are not).
    A few more pieces of information.  The VMWare client ends up having a lot of overlapping windows with a lot of changing graphics.  My mouse runs into problems especially when it is overlaying a changing plot (Perfmon running in Windows 7, or updating email client).  It does turn out that VMWare has a "native" VNC server built-in and I tried to connect to the virtual screen using the Screen Sharing Client on the machine with computing problem and voila!, no problem.  I end up having a Screen Sharing Client running native running screen (supposed to be VNC, but I have not verified that) sharing protocol on a virtual screen that is NOT the VMWare virtual screen and a separate session using actual VNC protocol using the VMWare VNC server.  It works perfectly fine.
    If I may hazard a guess, I think I know what the bug is, or at least, what is the nature of the problem that I have.  The rest of you may have a different bug.  When I have difficulty, it is because I am on a window that suppresses the dock, both in remote virtual screen and on the local machine showing the screen.  Two docks are suppressed, one remote, one local.  Throw in overlapping windows with changing graphics in the overlapped windows and toss in a mouse on top of that.  I think that the Screen Sharing is trying to refresh overlapping windows with mouse and going through the suppressed dock calculations and never converging on what the picture should be.  The mouse ends up being the visible cue that shows the time frame for iterating the windows - flickers with a timeframe of greater than a second.  That is far greater than the screen update time.  It is totally compute bound with all the overlapping stuff that it is deconflicting.  At least, that is what I think is going on.
    Meanwhile, the VMWare VNC server appears to send out a single graphics context and causes the Screen Sharing client to converge to a picture.  Note, the mouse appearance is very different when attaching to the VMWare VNC Server rather than the ScreenSharing native server.  I see two mouse renderings, the virtual machine remote and a mouse rendering from my Screen Sharing client side.  They are mostly in sync in position unless I move the mouse very quickly.  If I use Screen Sharing client and server instead, I usually see only one mouse, the client side's mouse rendering.
    I have a solution for my problem.  It is similar to using a different VNC server/client pairing.  I will use a VNC server for the systems giving me trouble that is not Screen Sharing Server exercising a probable bug in the Client (though, it could be a problem in the design of Screen Sharing itself).

  • Screen Sharing (Messages)

    I am trying to take over control of my fathers MBP using Messages (Screen Sharing feature). I am so glad that in Yosemite they brought the screen sharing functionality back ( I think in Mavericks it was gone??). Well, when he would have problems I would simply take over and move his mouse and do what I needed to do. Now with Yosemite I can  only view his screen and I cannot take full control of his MBP.
    Is there a setting I am missing? Our computers (Mine is a MBP and so is his) are on different networks. I found today that if I hold my mouse down it will create a small circle that is highlighted and shows my dad where I want him to navigate to but it was much easier if I could do it. If there is a thread on this please direct me to it since I have not found it.
    Thank you,
    Jeremy

    The default mode is view only. He has to allow remote control as illustrated on the page linked below:
    http://9to5mac.com/2014/08/19/apple-activates-screen-sharing-over-imessage-accou nts-in-latest-yosemite-beta/

Maybe you are looking for