Screen Sharing: Viewing extended desktop on extended desktop

My buddy and I both have the same current versions of iChat and Leopard and both have dual displays (extended desktops). When we do ScreenSharing, his dual screens (the entire extended desktop) come through into just one screen of mine (into the larger primary screen but I don't know how iChat determines it) and vice versa when I share my screen with him. We can still see everything, but everything is just smaller to fit two widths into one. The second screen remains dark and blank.
Is there a way to enlarge the shared screen?
Or is this a limitation at the current version?

But of course I want more, not less. The second screen contains all the important tool palettes, which is half the experience! I will nonetheless try (looking for) your suggestion next time, if just to know it. Thanks.

Similar Messages

  • Screen Sharing and Virtual Desktop

    Is there a way to force a new remote screen sharing connect to a "Virtual Desktop"?
    In my experience, if another user is logged into the computer the new remote screen connection will be forced or given the option to connect to a virtual desktop. This will allow the new connection to run in the "background" without the first connection being influenced.
    The issue is when a new remote connection is initiatied and no other connections are active the new connection will be shown on the computer's hardware monitor. i.e. No option is given to connect via a virtual desktop.
    This is a security issue because a user can connect remotely and if he is the only connection on the computer he will have all his work shown on the hardware display.
    I am hoping to find a way to force all remote connections to be on virtual desktops.

    I guess its worth mentioning that although you can indeed screen share from Leopard to Tiger, it only works when you are on the same network. But Remote Desktop works across the internet...
    Of course the trick to using Remote Desktop from a truly "remote" location elsewhere on the internet is that you have to be able to reach the IP of the computer you want to control, which can be tricky if its behind a NAT and the person your trying to reach is my Mom who has no idea how to configure her NAT, or firewall, or even find her IP address without my help.
    Screen sharing Leopard to Leopard via iChat should be much more straight forward... translation: this will make my life much easier the next time my mom needs help.

  • Screen Sharing viewing problem

    I am using Skype Version 4.3.0.37 on a desktop using Ubuntu 12.04. Using Screen Sharing in full screen mode there are huge blocks of filler surrounding the screen sharing image making the screen sharing image much smaller and much harder to read. Is there a solution? Is anyone working on the problem? It seems as if linux problems are ignored.

    Here's a couple things you can try:
    Cntl-Shift-Eject will put the displays into sleep mode. Then space bar will bring them back out of sleep. See if that results in a screen on the Sony. If not, then try this one:
    Hit the power button on the MB. This will pop a screen up (which you can't see because the Sony is black) but if you hit the S key, the MB will go into sleep mode. After it goes to sleep, hit space bar to awaken the MB and see if the screen comes back on the Sony.

  • Remote desktop and screen sharing with RMI

    Iam developing an application for screen sharing and remote desktop
    the problem is a performance problem
    in the screen sharing application server screen is captured and the image is sent to all connected clients through rmi connection
    I used JPEGImageEncoder to compress the image and convert it to array of bytes
    then zipped the resulted array using deflater.
    the result is sent through rmi connection
    the performance is so poor
    i tried JMF but the performance is worse
    i am thinking of a way to send the server screen only if it is changed but i don't know how
    anyone could help me to enhance it with acceptable quality for the image
    thanks

    As you said, you need to only send the changes over the line.
    Java can not tell you what has changed, so you need to either write some JNI, or do a check on the current image, with the last image. (this would eat quite a bit of CPU time on the server).
    It might be worth looking at the source for VNC, and other simler products.
    The simpliest solution would be to split the image into blocks of x by y pixels, then do a pixel-by-pixel check on that block, and only send the block if it has changed.
    Next thing to think about is scrapping RMI, and using raw sockets. RMI has a fair sized overhead.
    Zipping a JPEG is unlikely to have any effect. A JPEG is already compressed.
    You might want to look at a lossless compression format, like PNG, as the JPEG will have articles. This might be acceptable. If so, changing the compression ratio of the JPEG might be an option.
    Finally, the bottle neck might be the call to Robot.createScreenCapture. This is not the fastest method.

  • Back To My Mac multiple display screen sharing issue

    Since upgrading to Yosemite, I've been unable to access one of my screens remotely via Screen Sharing and BTMM. It only shows the screen attached to the HDMI interface, it's as if the other display doesn't exist. There is no option to select the other display in the Screen Sharing View menu. In Mavericks it would by default show both screens and I could select one. I've tried disabling and re-enabling the Sharing function on the host Mac. The screen that it does share works perfectly, so it seems to just be a problem of recognizing the other display.
    Host is a 2012 Mac Mini, client machine a MBP, both running 10.10.1.

    Spoke with Apple who spoke with Apple and so on. Tech support for Apple Desktop Remote acknowledges (as best they could) that there is a bug/ problem. Yes, reverting to an older (3.5 - 3.4 ARDagent) solves the problem (short term ?). They captured my OS info and will get back to me in 3-5 days - how do you like them apples! So, revert to ARDagent 3.4 and you can remote connect - may try this later... will post if it works. Here's what's been posted on this: https://discussions.apple.com/thread/3192451?start=0&tstart=0

  • Enabling screen sharing through .mac or VNC

    I want to enable screen sharing on my desktop computer from another network (so I can connect to my home machine from the office, or on the road). I have successfully enabled my router to allow VNC traffic, and have been able to connect from my laptop on another network. Everything seems to be working fine besides the fact that I am concerned about having port 5900 open on my home router. Is connecting using a .mac account more secure? I suppose I would be able to turn off port 5900 on my router, but I'd also have to pay $100 a year, and worry about someone hacking my .mac account also (I really wish that apple would come out with [FREE] remote desktop software like windows!).

    My last effort
    turn on process accounting:
    "mkdir /var/account"
    "touch /var/account/acct"
    "accton /var/account/acct" or reboot
    "chmod o-rx /usr/bin/lastcomm"
    "chmod -R o-rx /var/account"
    Everything has to be run in sudo. If you do the above, then run sudo lastcomm and check what that says.

  • Screen sharing stuck on 'Connect...' - but only on one client account. Please help!

    I've got a bizarre problem that cropped up sponaneously, and which I can't for the life of me seem to reslove.
    I have 2 home machines:
    MacBook running 10.6.8  (Server / Media machine)
    MacBook Pro running 10.7.4 (Client machine).  Apple Remote Desktop software is installed on this machine, and connections through it work fine.
    A few days ago, the sidebar "Share Screen..." link on the client machine stopped working.  All I get is the 'Connecting...' dialog box, endlessly.  The bugger of it is that this is only happening with my main account on the client machine. Switching into another (unused) admin account on the client results in the 'Share Screen...' button working as expected.
    I've tried the following cures, found on these forums, to no avail:
    Reset PRAM and NVRAM on both systems
    updated all software
    repaired permissions on both systems
    changed bonjour names of both machines
    rebooter & power-cycled router
    killed the NetAuthAgent process a billion times
    trashed all of the preferences, caches, etc. for screen sharing and remote desktop in the afflicted user account on client machine
    etc. etc.
    As far as screen sharing connection options go, these are my results:
    using connect to server (via finder > go > connect to server), and plugging in the address (vnc://192.168.0.103): works
    launching /System/Library/CoreServices/Screen Sharing.app, and plugging in the above address: works
    connecting via the Apple Remote Desktop software: works
    using the "Share Screen..." link from the Lion Sidebar: DOES NOT WORK and results in the stall mentioned above, constrained to my primary user account on the client machine.
    As mentioned, this was working properly until a few days ago, and stopped spontaneously, with no changes to either system.
    Any help finding a resolution to this would be greatly appreciated; this is driving me utterly bananas .
    -Tim
    Message was edited by: Timoluka

    My wife ran into the very same problem today, while trying to connect Screen Sharing to her media center Mac Mini (server) from a Mac Book Pro (client). I was also unable to connect from my machine as well when logged into my usual account but noticed I had no problem with a Guest User account (as you've described), but had also tried most of the unsuccessful attempts at solutions that you've enumerated.
    Then, I read this very similar thread: https://discussions.apple.com/thread/4131788?start=0&tstart=0
    ...and logged out of our now defunct MobileMe accounts on the affected machines. Upon hitting the "Share Screen..." button again, I was now prompted for a local login and password to the Mini, and once that was input, Screen Sharing connected and started up without any problems! Yes!
    Given the similarity of our problems, I hope this works for you as well. My best guess is that Screen Sharing might be prioritizing the use of MobileMe authentication over local logins and passwords, and some of Apple's recent work in decommissioning MobileMe had unexpected results for folks like us.
    Jim

  • Screen sharing performance

    I have been screen sharing to my desktop for quite a while, with no performance problems. Recently my MacBook will "freeze". For example, while entering a transaction into Quicken, the screen will freeze and will take several seconds for Quicken to show the data I've entered. I've placed the MAcBook next to my destop and entered data through the desktop and it will take several seconds for the MacBook to update.
    There are some time where the cursor will freeze in any application when running in a screen share mode.
    This just started happening within the past 30 days.

    OK, earlier client here:
    http://support.apple.com/kb/DL1491
    Can someone kindly instruct me how to uninstall the latest version so that I can revert.
    AC

  • Can I display EyeTV's live TV over HDMI-out and be able to see my desktop using screen-sharing on a headless mac-mini used as a media-box?

    Hi,
    I'm thinking of buying a new mac-mini to replace my current one which acts as an iTunes server and records TV programs using eyeTV. I connect using screen-sharing/VNC to be able to do stuff on it (like handbrake etc.)
    I have eyeTV with a satelite receiver and I want to change the setup so that:
    - the new mac-mini continues to work as an iTunes server (and handbrake workhorse)
    - I can use the HDMI output (inc. audio) to show eyeTV's live TV full-screen app
    - I can connect using screen-sharing/VNC to the mac-mini and see my normal desktop to be able to maintain it etc. but this is a headless display (no screen is connected to the display-port).
    - recorded media I'd play through the appleTV2 still + rentals etc. unless anyone knows if eyeTV software can offer up iTunes content? I don't like the eyeTV recordings in general as it seems very slow to me for access when there are lots of recordings and wouldn't be available in other apleTVs in the house AFAIK.
    The main benefit that this gives me is that I'd no longer need a seperate satelite box to watch live TV and can add more eyeTV hardware to get additional TV channels all through the same HUD on the TV for ease of access.
    Does this seem possible in theory & practice (ie are there any gotcha's to consider?)
    - can I force the HDMI output resolution to 1080i as I go via an amp to the TV and the appleTV2 drops to low-res in this configuration so I have had to find a workaround for that.
    - does the mac-mini have IR input that can be programmed?
    - Does eyeTV software remain stable for long periods?
    - Does the HDMI out have any handshake issues that would need a reset of the display (somehow)?
    thanks in advance for any thoughts/contributions
    Lee

    I think the easiest way to do this is to have the EyeTV app running in one user account and sent via HDMI to the TV, and use a separate user account for Screen Sharing. Both logins can be active at the same time and with Lion you can connect via screen sharing to which ever login you need.
    With regards to the Mac video resolution changing, when it is not the current input on your AV receiver. This is 'normal', if the Mac sees no signal it drops down the a lower level. What you need is to buy a HDMI Detective Plus which tricks the Mac in to always seeing a signal and hence it will not drop down the resolution. See http://www.gefen.com/kvm/dproduct.jsp?prod_id=8005
    The Mac mini does have an IR receiver. This can be used with the EyeTV app, iTunes, and similar. Yes I believe EyeTV would run for prolonged periods quite happily, it is has been around for a long time and had most of the rough edges polished off. However one issue you will have to deal with is that it does not automatically update its program guide data. For this you might have to write or modify an AppleScript. Elgato support or their user forums will be a lot of help.
    You can set EyeTV to convert recordings to an iTunes (Apple TV) compatible format and then delete them from EyeTV.
    The HDMI Detective should solve your handshaking problems.

  • Can i set up multiple desktop screens to view at once?

    I am trying to set up a view different desktop views that I can alternate between.  Is this possible?

    1) will this work across platforms, using SSH on the Windows machine?
    You can ssh on any unix/linux/mac/windoze computer
    have a look at putty which is an ssh client for windows.
    2) Once a connection is established, can I use the GUI to handle file transfers, or would I have to do all of that from the terminal?
    Yes, once you enable SSH on your mac (ie Turn on remote login in the sharing prefs) it also enables an SFTP server as well. So you dont need to use the command line to initiate the connection.
    So you can use any PC SFTP client.I am not sure of the best PC SFTP client so you will have to google. Most SFTP clients allow drag and drop file transfers. From a mac to a mac the best SFTP client is transmit.

  • Messages Screen Sharing Ends with a "Hanging" Desktop Screen

    Since the OS X 10.8.1 update, Messages screen sharing – that used to work well in my environment – everytime ends up with a hanging desktop screen. That means: The screen of the desktop, where Messages screen sharing took place, freezes. I have to swipe to another desktop in order to successfully quit Messages via the dock context menu. After that, its desktop screen is responsive again.
    This happens independant of who ends the screen sharing session.
    It used to work seemlessly before OS X 10.8.1. So I think there is an issue with this update, Messages and the screens (desktops) management.
    Message was edited by: Kurt J. Meyer

    Hi,
    As Screen Sharing does tend to involve a change from the Shared Screen at one resolution changing to your screen at possibly another (which for some produces the White Screen In Sharing) I thought it might pay to look at the method when wanting to go back to your own screen during a Screen Sharing Chat
    I would still report it here
    http://www.apple.com/feedback/ichat.html
    Obviously you have to use some of the free text area to state your OS version and Messages version at it will not appears in any of the drop downs.
    7:55 PM      Wednesday; September 19, 2012
    Please, if posting Logs, do not post any Log info after the line "Binary Images for iChat"
      iMac 2.5Ghz 5i 2011 (Mountain Lion 10.8.1)
     G4/1GhzDual MDD (Leopard 10.5.8)
     MacBookPro 2Gb (Snow Leopard 10.6.8)
     Mac OS X (10.6.8),
    "Limit the Logs to the Bits above Binary Images."  No, Seriously

  • How do I switch remote desktops with lion server screen sharing?

    When I sometimes use the Lion Server screen sharing feature to take over my iMac using my Macbook, I find that I'm not able to switch desktops on the remote computer, i.e. using the three finger swipe.
    Both are running the latest versions of Lion Server.
    Now there MUST be some way to do that right?
    Who knows?

    Hi John, perhaps I did not express myself clearly.
    My desktop iMac is set up with multiple desktops (desktop 1 for system stuff, desktop 2 for mail, messages, skype etc, desktop 3 for Safari and desktop 4 for text proessing, VM-Ware and other work).
    When I work on that machine I'm logged in as one user and use the three finger swipe left and right or the Cmd-1 thru Cmd-4 keys to switch between those desktops.
    I haven't founf how to do that from my a remotely connected MacBook Pro.
    Both of which are running Mountain Lion in the mean time. The iMac runs Mountain Lion Server and the MBP has ML Server installed as well, but nut implemented. Just to be able to use the remote screen...
    Hope this makes my question a bit mre clear...
    Gerard

  • Apple Remote Desktop 3 screen sharing performance

    Apple Remote Desktop 3 screen sharing performance
    Apple should licence citrix terminal technology to improve screen sharing experience and performance over low bandwidth connections like the internet.
    ARD works very nice on LANs. But the screen sharing performance for remote offices really has to be improved. Look at Citrix and MS Terminal Server - these products work very snappy over low bandwidth connections like 3G UMTS or Cable, DSL.
    Also adding the terminal server technology (multi user over network) to the OS would be great. Not only redirect the hole client screen - map a GUI user session over the network for an admin while the user on the client has his own usual local session.
    The curtain mode is good beginning.
    Kind regards,
    Bjoern

    Hi,
    I mean that MS Terminal Server is a completely different beast, because you don't transfer the whole bitmap here as VNC or ARD does.

  • Screen sharing not working after Remote Desktop 3.2 install

    OK, I think I screwed it up.
    I'm moving to a new iMac running Mountain Lion, and I need to use Remote Desktop.  I own Remote Desktop 3.2 on DVD, so I installed from disk and launched the app.  My plan was to download the latest update to 3.6.x, but I figured I would launch it to enter my license key and then quit and download the update.
    I was given an error that newer components were already installed and clicked the Quit button.  Ugh.  Next I went to Apple's download site and downloaded the newest update but when I ran that installer it told me it could not install on my drive.
    My grand plan has now left me with no Remote Desktop, and the built-in Screen Sharing core service beach balls when I try to connect to a remote client.
    Is there a way to save me from myself?
    Thanks in advance,
    Bill

    Hi Bill,
    You could try removing all the installed components manually and then try again (install, don't open but update right away).
    According to the installer the files are located in:
    /Applications/Remote Desktop.app (that one was hard to find )
    /Library/Application Support/Apple/Remote Desktop/
    /Library/Preferences/com.Apple.ARDAgent.plist
    /Library/Preferences/com.Apple.RemoteDesktop.plist
    /Library/Receipts/
    /Library/Widgets/RemoteDesktop.wdgt
    (not sure if the following files tie into other parts of the OS so removing them may cause issues)
    /System/Library/CoreServices/RemoteManagement
    /usr/bin/share/man/man1
    perhaps a permission repair after all parts have been deleted and a restart before trying again.

  • Screen Sharing doesn't work after updating to Remote Desktop 3.6.1

    Hi everyone!
    I hope others can help.  We just noticed this at two different schools today after upgrading to 3.6.1.  We upgraded Admin and Client Apple Remote Desktop to ARD 3.6.1 today and now we cannot share our screens with the clients.  It turns black, hangs, then returns the client to its original desktop. 
    We tried from a 3.5.1 admin machine, and it still works fine as it used to.
    We feel like the issue is 3.6.1, but cannot find any support for the issue online. 
    Other troubleshooting steps:
    1) emptied user and system Caches
    2) restarted all units
    3) tried 3.6.1 admin to 3.5.1 clients, no luck
    4) tried 3.6.1 admin to 3.6.1 clients, no luck
    5) checked for loops in the network, nothing.
    We can perform most other tasks like controlling the clients and copying files, but not screen sharing.
    Thank you for your help!

    All right!  Total workaround here, and no fix, but at least we're able to Screen Share in ARD now.  This is how we downgraded to 3.5.1 Admin in Apple Remote Desktop.  The only hiccup that may not work for most is that you must have an older Remote Desktop file on hand. (hopefully from a computer that was not upgraded which was our case).
    Here is what we did...
    1) Login as an admin.
    2) Throw out the Remote Desktop app (in Applications)
    3) From another computer, drag in an old Remote Desktop app into your Applications folder
    4) Throw out the "RemoteManagement" folder inside System/Library/CoreServices
    5) From support.apple.com/downloads, download Remote Desktop 3.5.1 (both the Client and Admin installers).
    6) Run the Admin install first, then the Client Install.
    I did the above steps in two schools in a different order, but I wrote it this way to make it more streamlined.  I never had to re-enter the Serial # or anything.  Once I did the steps above, it just worked again.
    Hope this helps you! 

Maybe you are looking for