Screen sharing on startup ?

Hi all,
Is it possible to start a screen sharing connection to another Mac upon booting up ? Like, a script that is added to the startup items ?
Thanks !

#1 Can you use the Terminal? #2 Here goes
On my Desktop I made a file with Pico:
#!/bin/bash
open vnc://USERnamegoshere:password@ip of the othermac
Save as whatever name you want file and then chmod u+x whatever name you want file
Ok here is the plist that I used to open screen sharing from Leo to Tiger:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>Label</key>
<string>com.dougp.userstartup</string>
<key>ProgramArguments</key>
<array>
<string>/Users/dougp/Desktop/testsc</string>
<string>open</string>
</array>
<key>RunAtLoad</key>
<true/>
</dict>
</plist>
The Tiger machine has to have, at minimum AppRemDTop going. And if you are going Leo to Leo, then ScrSharing going on the other mac. I don't know how to turn that stuff all on in a script.The plist goes in /Users/yourname/Library/LaunchAgents
Run launchctl load com.dougp.userstartup.plist You should be able to restart your machine and you'll get a screen from the connect to server from toolbar asking usual. If you want to avoid the password item then, well that's another story with sudoers.
Obviously you have to change some names. Now what have I forgot to enter here?
This I forgot. testsc is the Desktop executable(the Pico file)
Message was edited by: doug pennington

Similar Messages

  • Why do I need to start up Screen Sharing twice to get it to work ?

    I have an Intel Mac Mini connected to my TV, so I started using Screen Sharing from my MacBook Pro to be able to work on it when others were watching TV.
    Both Macs used to have OSX 10.5 Leopard, and everything worked fine.
    Now they both have OSX 10.6 Snow Leopard, and whenever I startup Screen Sharing, the connection-windows asking for my Name & Password comes up properly, but then it hangs... it stays in "Connecting..." for ever (litteraly).
    I'm not able to quit or force-quit the connection-window by then, so it stays in view...
    (Screen Sharing isn't even listed in the force-quit list as a running app)
    but...
    when I just try Screen Sharing again, I get connection immediately and it seems to work flawlessly...
    ...it's just that the connection-window is impossible to quit...
    it stays in view an is really annoying...
    this looks really crappy...
    can anyone tell me why I do need to startup Screen Sharing twice to get it to work ?
    Is this a bug ?
    (If so : please apple fix this a.s.a.p.)
    ...or am I doing something wrong ?
    (if so : what am I doing wrong ? and how can I get rid of this annoying screen ?)
    Thank you for your kind reply.
    Toon.B

    it's October and this really annoying problem still exists !
    the unnamed screensharing-loginwindow keeps "Connecting...", and I'm unable to shut it down...
    ...even after my screen sharing session is over
    ...even force-quitting is impossible (this 'app' just isn't showing up in the force-quit-window...)
    please Apple - fix this ; under 10.5 it was working great !
    Does anyone have any idea how to fix this ?
    (besides restarting my Mac)
    Thanks !
    Toon.B

  • IChat screen sharing does not work on my Mac Pro

    I have a weird iChat screen sharing problem that i can't seem to resolve on my Mac Pro. Ever since i got my Mac Pro in early 2008, using the screen sharing feature in iChat has always been flaky. I have never gotten to the point of getting it consistently working. Lately, i have not been able to get it to work at all.
    Most of the time, when i choose to share my chat target's screen (or when i share my screen), i would be able to see my chat target's screen and use the mouse for several seconds before the shared screen session is ended. The errors that i am getting are:
    +"Disconnected from Screen Sharing because:+
    +No data has been received for the last 10 s..."+
    +"There was a communication error during your chat.+
    +No data has been received for the last 10 seconds. You can send+
    +details about this problem to Apple to help improve future versions of+
    iChat."
    On other occasions (mostly when i am trying to troubleshoot this issue by testing in the same network with my Powerbook, which is on 10.5.6 as well), i get this error:
    +"Disconnected from Screen Sharing because:+
    +Screen sharing could not be established."+
    I have tried to do screen sharing via iChat with other Macs in the same network and also on the internet but with the same problems.
    Initially, i thought this may be router related. But the fact that iChat screen sharing on my Powerbook works perfectly both in intranet and internet eliminates my router as the culprit.
    I have also tried disabling the OSX Firewall but the outcome was the same.
    I read some posts that there may be issue with using the external iSight web cam. I unplugged it, cleaning up all the iChat-related caches and preferences and tried again but with the same result.
    I have also tried connecting to iChat using several different account types (mobileme, .mac and AIM) but the end result is the same.
    I run a Ubuntu VMWare fusion VM on my Mac Pro as my webserver. I thought that may be the problem. Shutting down the Ubuntu VM also does not help.
    Applecare support personnel also instructed me to re-install iChat but that did not help as well.
    One interesting error i noticed in the system.log (seen via the Console app) that is generated everytime iChat screen sharing fails on my Mac Pro:
    +12/23/08 12:32:00 AM /Applications/iChat.app/Contents/MacOS/iChat[507] error getting server version+
    I am really running out of ideas on what else i can do to get this resolved.
    Thanks in advance for any suggestion.
    Message was edited by: Changren Yong
    The audio and video chat portions of iChat work fine.

    I managed to make some headway in my attempts to troubleshoot this problem. I did a fresh Leopard install on one of the drives in my Mac Pro. I then proceeded to update it to 10.5.6. After that, i launched iChat and attempted screen sharing with my Powerbook. The first few attempts failed, with the following symptoms:
    - i would be able to see and control the Powerbook's screen
    - after 5 seconds, my screen sharing session is disconnected
    I then unplugged my external iSight. After i relaunched iChat, i managed do screen sharing in iChat without being disconnected!!! When i connected the iSight back into the ACD, with iSight off, i attempted to screen share again. This time, it failed after about 5 seconds, just like earlier. I then turned iSight on. This time round, the screen sharing session was not disconnected!!
    So in addition to the iSight issue, something in my original Leopard startup disk is causing iChat screen sharing to fail because even when screen sharing was failing on my fresh Leopard install, i do not see this error:
    /Applications/iChat.app/Contents/MacOS/iChat(507) error getting server version
    So if i can figure out what is causing this error to show up in system.log, then i can manage the iSight issue.

  • Script to start and stop screen sharing

    I've had no luck finding an applescript that will launch system preferences and select screen sharing in the sharing tab. I want to use this as a rule in Mail so I can open screen sharing and subsequently close after use with Jaadu on my iphone for only the time while I want to access my home computer.
    Is there anyone skilled at writing that for me?
    Thanks,
    Michelle

    You can do it on the command line but you have to have admin privileges
    sudo /System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/Resources/kickstart -help
    kickstart -- Quickly uninstall, install, activate, configure, and/or restart
    components of Apple Remote Desktop without a reboot.
    kickstart -uninstall -files -settings -prefs
    -install -package <path>
    -deactivate
    -activate
    -configure -users <user1,user2...>
    -access -on -off
    -privs -all -none
    -DeleteFiles
    -ControlObserve
    -TextMessages
    -ShowObserve
    -OpenQuitApps
    -GenerateReports
    -RestartShutDown
    -SendFiles
    -ChangeSettings
    -ObserveOnly
    -mask <mask>
    -allowAccessFor
    -allUsers [-privs <priv options>]
    -specifiedUsers
    -computerinfo -set1 -1 <text>
    -set2 -2 <text>
    -set3 -3 <text>
    -set4 -4 <text>
    -clientopts
    -setmenuextra -menuextra yes
    -setdirlogins -dirlogins yes
    -setdirgroups -dirgroups ardadmin,ardinfo
    -setreqperm -reqperm no
    -setvnclegacy -vnclegacy yes
    -setvncpw -vncpw mynewpw
    -setwbem -wbem no
    -stop
    -restart -agent -console -menu
    -targetdisk <mountpoint>
    -verbose
    -quiet
    -help ## Show verbose documentation
    Examples:
    - Uninstall program files (but not preferences and settings), install the given package, and then restart the service.
    kickstart -uninstall -files -install -package RDAdminInstall.pkg -restart -console
    - Install the given package and then restart the ARD agent.
    kickstart -install -package RDClientInstall.pkg -restart -agent
    - On 10.4 and earlier, stop the Remote Management service but, if activated, it will start after the next computer restart.
    - On 10.5 and later, use kickstart -deactivate instead.
    kickstart -stop
    - Stop the Remote Management service and deactivate it so it will not start after the next computer restart.
    kickstart -deactivate -stop
    - Restart the agent.
    kickstart -restart -agent -console
    - Activate the Remote Management service and then restart the agent.
    kickstart -activate -restart -agent -console
    - Activate the Remote Management service, enable access, and restart the agent.
    kickstart -activate -configure -access -on -restart -agent
    - Disable user access.
    kickstart -configure -access -off
    - Give admin and bob all access.
    kickstart -configure -access -on -privs -all -users admin,bob
    - Use Directory Server accounts for authentication. Users must be a member of one of the directory
    - groups to authenticate.
    kickstart -configure -clientopts -setdirlogins -dirlogins yes -setdirgroups -dirgroups ardadmin,ardcontrol
    - Disable the Remote Management menu extra.
    kickstart -configure -clientopts -setmenuextra -menuextra no
    The following examples are only for Mac OS X 10.5 and later.
    - Allow access for only these users (the users must be specified in a separate command).
    kickstart -configure -allowAccessFor -specifiedUsers
    - Allow access for all users and give all users full access.
    kickstart -configure -allowAccessFor -allUsers -privs -all
    - Start the Remote Management service.
    kickstart -activate
    Version 0.9
    RUNNING FROM THE COMMAND LINE
    This script can be run like any UNIX tool from the command line or
    called from another script.
    Before starting:
    - Use this script at your own risk. Read it first and understand it.
    - Log in as an administrator (you must have sudo privileges)
    - Copy this script to any location you like (such as /usr/bin/local/)
    - Ensure this file has Unix line endings, or it won't run.
    Running:
    - Run the script using "sudo" (enter your password if prompted)
    sudo ./kickstart -restart -agent
    Command-line switches:
    The optional "parent" switches activate the top level kickstart features:
    -uninstall
    -install
    -deactivate
    -activate
    -configure
    -stop
    -restart
    These features can be selected independently, but will always be done
    in the order shown above.
    For anything interesting to happen, you must specify one or more of
    the parent options, plus one or more child options for those that
    require them. Child options will be ignored unless their parent
    option is also supplied.
    All options are switches (they take no arguments), except for -package
    <path> -users <userlist> and -mask <number>, as noted below.
    -uninstall ## Enable the "uninstall" options:
    -files ## Uninstall all ARD-related files
    -settings ## Remove access privileges in System Preferences
    -prefs ## Remove Remote Desktop administrator preferences
    -install ## Enable the "install" options:
    -package path ## Specify the path to an installer package to run
    -configure ## Enable the "configure" options:
    -users john,admin ## Specify users to set privs or access (default is all users)
    -activate ## Activate ARD agent in Sys Prefs to run at startup
    -deactivate ## Deactivate ARD agent in Sys Prefs to run at startup
    -access ## Set access for users:
    -on ## Grant access
    -off ## Deny access
    -privs ## Set the user's access privileges:
    -none ## Disable all privileges for specified user
    -all ## Grant all privileges (default)...
    ## ... or grant any these privileges...
    -DeleteFiles ##
    -ControlObserve ## Control AND observe (unless ObserveOnly is also specified)
    -TextMessages ## Send a text message
    -ShowObserve ## Show client when being observed or controlled
    -OpenQuitApps ## Open and quit aplicationns
    -GenerateReports ## Generate reports (and search hard drive)
    -RestartShutDown ##
    -SendFiles ## Send and/or retrieve files
    -ChangeSettings ## Change system settings
    -ObserveOnly ## Modify ControlObserve option to allow Observe mode only
    -mask number ## Specify "naprivs" mask numerically instead (advanced)
    -allowAccessFor ## Specify the Remote Management access mode
    -allUsers ## Grant access to all local users
    -specifiedUsers ## Only grant access to users with privileges
    -computerinfo ## Specify all four computer info fields (default for each is empty)
    -set1 -1 <text>
    -set2 -2 <text>
    -set3 -3 <text>
    -set4 -4 <text>
    -clientopts ## Allow specification of several opts.
    -setmenuextra -menuextra yes|no ## Set whether menu extra appears in menu bar
    -setdirlogins -dirlogins yes|no ## Set whether directory logins are allowed
    -setdirgroups -dirgroups grp1,grp2 ## Set directory groups allowed
    -setreqperm -reqperm yes|no ## Allow VNC guests to request permission
    -setvnclegacy -vnclegacy yes|no ## Allow VNC Legacy password mode
    -setvncpw -vncpw mynewpw ## Set VNC Legacy PW
    -setwbem -wbem yes|no ## Allow incoming WBEM requests over IP
    -stop ## Stop the agent and/or console program (N/A if targetdisk is not /)
    -restart ## Enable the "restart" options: (N/A if targetdisk is not /)
    -agent ## Restart the ARD Agent and helper
    -console ## Restart the console application
    -menu ## Restart the menu extra
    -targetdisk ## Disk on which to operate, specified as a mountpoint in
    ## the current filesystem. Defaults to the current boot volume: "/".
    ## NOTE: Disables the -restart options (does not affect currently
    ## running processes).
    -verbose ## Print (non-localizable) output from installer tool (if used)
    -quiet ## No feedback; just run.
    -help ## Print this extended help message
    ARD has four main components:
    1) ARD Helper
    2) ARD Agent & associated daemons
    3) ARD Menu Extra (controlled by the SystemUIServer)
    4) ARD Admin Console (if you have an Administrator license)
    What this script does:
    1) Any running ARD components will be stopped as needed. For example,
    they'll be stopped before an uninstall, reinstall, or restart
    request. They will not be restarted unless you specify the
    -restart options.
    2) Components will be restarted as required. For example, restarting
    the administrator console forces a restart of the agent.
    Restarting the agent, in turn, forces a restart of the helper.
    3) If you -uninstall but don't specify a new installer to run, then
    the -restart family of switches will be ignored.
    4) Options can be specified in any order, but remember that the
    options are ignored unless their parent options are specified. For
    example, -package is ignored unless -install is specified.
    RUNNING THIS SCRIPT FROM A GUI
    You can make yourself a GUI-based kickstarter program to run this
    script if you like. The options, set in the console, can be conveyed
    via environment variables to this script, per a spec shown in the
    source code for this script (or the traditional way using command-line
    switches). Be sure the console application runs this script with sudo
    privileges. The console should also specify its own location in the
    APP environment variable, and may specify the location of a
    STRINGS_FILE to use to load string definitions for any localizable
    messages produced by this script.
    A GUI console could stay up & running between runs of the script but
    should avoid running multiple instances of this script at the same
    time.
    WARNING
    This script can be used to grant very permissive incoming access
    permissions. Do not use the -activate and -configure features unless
    you know exactly what you're doing.

  • Crash after screen sharing

    Hi there, it´s a bit long story.
    I had an MB138xx/A mid 2007 mac mini with Snow Leopard installed, connected to my TV for watching movies. everything worked great.
    I had a Macbook Pro 17" with Snow leopard too from which I used to control my mini via screen share.
    Recently I purchased a new MB pro 15" retina with mavericks.
    I tried to do some screen sharing again with my mini, and it seemed to work, until after 30 min aprox. of use, the mini got frozen.
    I shut down my mini with the power button and it got stacked at the apple logo screen. After a couple tries more, I managed to get to the login screen but mouse and keyboard did not connect bluetooth and I was not able to do anything. After some more tries there was no way to start it, safe reboot, verbose, clean NVram.. nothing.
    Fortunately, I was able to start it as FW disk and was able to get all the data back using my laptop, but something looked wrong into disk utility and was not able to format it. The I got a software that enabled me to format it again, and finally I installed marevicks to the mini.
    The mini worked perfectly even with 2 GB or ram, 1080p movies played perfectly.
    I was able to control it with my new MPB with no problem.
    PS: It was totally full of home dust and I had to vacuum it in order to remove it.
    BUT.
    Yesterday, my wife connected to the mini using my old 17" MBP and guess what.. The mini freezed again!!!!
    Nos I am in the same point, no way to go beyond the apple logo.
    Do you guys know why is this happening? Is there any kind of malfunction related to screen share between Snow leopard and Mavericks that makes the host computer to die?
    The any other reason I can imagine is that screen sharing takes a lot of processing effort and my old mini suffers some kind of overheating?
    But then, why can´t I start it again after it becomes cooler? Why was my HD kinda damaged in the first problem?
    May be all the problems are because my HD is unstable? I was watching some MKV movies with no problem..
    Might the home dust have caused some hardware problem because of unproper cooling?
    Thank you so much for your time.

    I can only guess right now, but I'd say there's a fair chance that dust on the RAM may have corrupted the drive in unseen ways.
    Bootup holding CMD+r, or the Option/alt key to boot from the Restore partition & use Disk Utility from there to Repair the Disk, then Repair Permissions.
    Open console in Applications>Utilities, check the system log for the date/time of the last problem  & the Startup right after that for clues.
    click on the top line we want, Shift plus click on the bottom line we want, CMD+c to copy, then paste the text in a reply with CMD+v
    A couple dozen lines should be about right, hundreds or thousands won't likely be readable.

  • Screen sharing: can't access after update to SL

    I have a set-up with a new mini server running SL Server 10.6.2. A Macbook Pro and iMac are on the network, they were both running 10.5.8. I manage my mini server with one of these computers through screen sharing.
    I updated my Macbook Pro last week to SL 10.6.2.
    I updated my iMac this week to SL 10.6.2.
    I can't log in to my mini server from these 2 machines since the update. I get a message "Authentication failed, please verify user name and password".
    I have restarted my imac under 10.5.8, and I can use screen sharing again to manage my server.
    I am at a loss to figure why the update to SL on my clients has killed may screen sharing access to the server.
    Any hints would be appreciated.
    Thansk

    1. Startup in Safe Mode
        http://support.apple.com/kb/PH14204
    2. Repair Disk
        Steps 1 through 7
        http://support.apple.com/kb/PH5836
    Best.

  • Screen sharing and multiple users

    I have an iMac at home that is used by multiple family members. I have multiple logins enable so it is common to have 2-3 accounts logged in at once. I would like to use screen sharing to connect to my account even when one of the kids is logged into their account.
    I started by looking at the vnc processes. There is one process that run as root:
    root 21792 0.0 0.0 2437128 1736 ?? Ss 12:25PM 0:00.02 /System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/RFBRegisterMDNS
    Then there is another process for each person logged in:
    username 22006 0.0 0.3 2734876 13964 ?? S 12:33PM 0:00.29 /System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Ma cOS/AppleVNCServer
    So I have two questions. One is how can there be three processes running that listen on the same 5900 port at the same time and how does it decide which one to connect a vnc client to? My second question is how can I prevent the AppleVNCServer process from starting for each user. I've tried killing those processes but they respawn immediately.

    Hi
    Thank you for your answer. Sorry to have been unclear - I'll give it another go :o)
    Here is what I am trying to do:
    I have 2 users (Plex and Ursus) that I want to have logged on at the same time. Plex will be "in the front" i.e. that is the screen that is seen if you are at the mini. Ursus is a user that is logged on but you cannot currently see (i.e. in the back as it where). I would like to work using the user Ursus (to, for example, rip a movie from a DVD (that I own of course :o).
    Using file sharing would mean that I have 2 machines running and that I need to copy all the files from the one machine to the other, not exactly what I want but manageable.
    I have managed to get this "partly" working - I am using Vine Server for Mac (http://www.testplant.com/products/vineserver/OSX) which allows me to start a VNC server on e.g. port 5901 and then screen share to that session. If I setup the second user (Ursus in this case) to use this server then I can connect to the "back" user. The only problem being that Vine Server seems to crash with Plex - as soon as I start it Plex just hangs and randomly crashes!
    Was that clearer?
    Thanks again
    Ursus

  • Airport Extreme is allowing access to screen sharing, file sharing from external IP addresses (some from China, Canada etc)

    How to get control over the ports/port forwarding etc in Airport Extreme?
    How to make AE drop packets to certain ports from external ports.  Or create whitelist/blacklists?
    I figured out where the MAC filtering is!  (It is inside the Timed Access Control).  I wish it had a list of connected device and allowed me to select, name and add them.
    I am getting requests from Chinese IP to the screen sharing ports forwarded to my iMac.  Had requests to other ports as well.  There was one IP address from CANADA too.
    I want to open file sharing for local use only.

    Why is Airport Extreme forwarding requests for screen sharing from external ip addresses to my imac?  I don't have a public address, nor use dynamic dns service, and I have removed the server app (at least I think I have, but Apple Store doesn't think so).

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

  • Screen-Sharing and Internet-Sharing via same network connection

    Hello out there,
    I'm using a TiBook (G4 867MHz) and a MacBook Pro 17". They are connected via a WLAN-router. Additionally the MBP is connected to the internet via an UMTS-connection established with a Merlin 870XU type PC-card.
    Network is working fine, including screen-sharing. Also the internet connection on MBP works without error. But if I activate Internet-Sharing via WLAN to get my TiBook connected to the internet, the MBP connection to the WLAN is cut off.
    Can somebody tell me what's going wrong and how to solve it?
    Greetings from good old Germany
    Ansgar

    Hello out there,
    I'm using a TiBook (G4 867MHz) and a MacBook Pro 17". They are connected via a WLAN-router. Additionally the MBP is connected to the internet via an UMTS-connection established with a Merlin 870XU type PC-card.
    Network is working fine, including screen-sharing. Also the internet connection on MBP works without error. But if I activate Internet-Sharing via WLAN to get my TiBook connected to the internet, the MBP connection to the WLAN is cut off.
    Can somebody tell me what's going wrong and how to solve it?
    Greetings from good old Germany
    Ansgar

  • How do I speed up my Screen Sharing experience?

    Hi. Apologies if this has already been answered, but I couldn't find post that matched. Anyway, I have set up Screen Sharing on my iMac so I can run it with my eMac (running Tiger 10.4.11). It all works fine except the response is a bit slow - that is to say the refresh rate doesn't make it workable if I'm working in image editing or whatever, in fact even just moving open windows around there's a noticeable lag in response time.
    I think I should mention that both computers are networked via ethernet cables - not wirelessly - so the response is as good as I can get it at the moment.
    I did hear somewhere that if I had an 'N' speed Router (as opposed to the standard 'G' speed) then this would improve the speed noticeably. Is that right? Also, my iMac is equipped with a 10/100/1000 Base T ethernet port, whereas my eMac is only the 10/100 variety. Will this make an 'N' speed router pointless. I just want to know before I waste money on something that'll make no difference really.
    Thanks
    Simon
    Message was edited by: Simon Bramley

    If you are using ethernet to ethernet connection, then 802.11g vs 802.11n WiFi does not matter.
    The slowest ethernet connection will be the limiting factor, so the eMac's ethernet port is the controlling factor for transfer speeds.
    If you want to experiment with a different VNC client and server, you might try installing Vine Server (aka OSXvnc) on the Mac to be controlled, and then use Chicken of the VNC as the client on the Mac you are sitting at. This pair of VNC client and server are very good at compressing the screen data to maximize network bandwidth.
    The next trick you could try is to tell Chicken of the VNC to use less colors. CofVNC -> Connection -> Connection Profiles -> Default Profile -> Color. Try "Thousands of Colors" first, then maybe "256 Colors" although 256 is going to look very Andy Wohl'ish

  • Screen Sharing/network problem seems confined to 1 volume. What's the fix?

    I am having a networking problem on one of the volumes of my multi-volumed, three-Mac local area network, and I need a networking guru to identify the specific software file(s), application(s), or system configuration that is the cause of the problem. I have already spent several hours checking and re-checking the various hardware and system preference settings involved, and I have narrowed the problem down to a software corruption issue and/or system configuration issue on one volume.
    I now need someone to identify specifically what the nature of the problem is, and how to eliminate it. I am not looking for a sledgehammer solution that says I should re-install all of the Mac OS X software on the problem volume. That may be held in reserve as a last resort. I'm looking for a more elegant approach, one that points out the specific corrupt files to remove without disturbing everything else.
    Here's some background to set the context. I have a MacBook Pro laptop; a PowerMac iMac G5; and a PowerMac G4 hooked up in a network. All are running Leopard 10.5.8. All have file sharing and screen sharing enabled. Besides being able to connect to each other using registered users, my goal here is for each of the Macs to be able to share the screen of the others upon my demand. Since each of the 3 Macs can theoretically share the screens of the other 2, that makes a total of six possible connections. Five succeed; one does not. That's the problem. I am trying to determine why the iMac G5 cannot share the screen of the MacBook Pro.
    The iMac G5 has no problem sharing the screen of the PowerMac G4. That connection is fast and immediate. But, every time that I hit the Share Screen button on the iMac G5 to try to connect to the MacBook Pro, I get a window with the blue barber pole spinning for two or three minutes as it is allegedly "Connecting to Mac Book Pro," followed by a window with a headline telling me that "Connection Failed to MacBook Pro." The text within that window goes on to say: "Please make sure that Screen Sharing (in the Sharing section of System Preferences) is enabled on the computer to which you are attempting to connect. Also make sure that your network connection is working properly."
    Well, as I indicated, the PowerMac G4 has no problem sharing the screen of the MacBook Pro, so the Screen Sharing settings on the laptop are correct; and the iMac G5 can share the screen of the PowerMac G4, so its network connection is working properly in that regard. It is only in regards to sharing the screen of the MacBook Pro that the iMac G5 is not working properly.
    The reason why I say that the issue must be unique to the one volume in question, let's call it "iMacG5 Music," is that another Leopard volume on the same computer has no problem whatsoever in sharing the screen of the MacBook Pro. Whenever I boot up in that volume, let's call it "iMacG5 JMB," it makes a network connection with a registered user name immediately, and it is able to share the screen of the MacBook Pro within a second of my issuing the command. In sharp contrast to the success of the iMacG5 JMB volume, the iMacG5 Music is unacceptably slow (several minutes slow!) in making a network connection with the MacBook Pro, and it always fails to share the screen of the MacBook Pro, preferring instead to take about three minutes to attempt the connection, before announcing its failure.
    Since the iMacG5 Music volume makes an immediate network connection to the PowerMac G4, as well as sharing the screen of the PowerMac G4 the moment I ask it to, I have concluded that the hardware of the iMac G5 is just fine. The problem seems confined to the system software and/or associated networking files that are unique to the iMacG5 Music volume. I just don't know what those files could be, or where the problem lies, so I've issued this call for help.
    Let me add one more little twist to this puzzle which baffles me even more. I use external LaCie Firewire drives as clone backups of my Macs. As part of my trouble-shooting process, I booted up from the cloned versions of the iMacG5 JMB volume and the iMacG5 Music volume. What I learned surprised me!
    The iMacG5 JMB clone worked just fine in making a fast network connection to the MacBook Pro, as well as sharing the screen of the MacBook Pro. I expected that. What I did not expect was that the iMacG5 Music clone was also able to make a fast network to the MacBook Pro, as well as share its screen!
    Yes, that's right. It's weird! Screen sharing works OK when I start-up from the clone of the iMacG5 Music volume, but it does not succeed when I boot up on the source itself! I was surprised to find that out, but I'm glad I did.
    (Over the past few days since I executed the last clone, I did use Drive Genius to de-frag the source volume, and maybe that has contributed to the problem I am now encountering. But it's hard to say, since nothing else seems to be amiss.)
    One solution, I suppose, would be to sync the clone back to the source. But, before I do that, I'm just wondering if anyone has a clue as to the nature of this problem on the source volume and what I might do to remedy it—short of re-installing the system software or restoring from the clone. Anyone have any insight to this problem?

    CORRECTION #2:
    Ignore the previous "CORRECTION" post.
    Oops, excuse me, I wrote that sentence correctly the first time.
    I was trying to point out that the ability of the iMac G5 computer to connect quickly and effectively to the PowerMac G4 when booted up into the iMacG5 Music volume was an indication (to me, anyway) that there is nothing wrong with the computer's hardware, nor its network connection ability, but that the problem lay somewhere in the files/settings used to connect to the MacBook Pro, which it cannot accomplish.
    This is what happens when I get engrossed in one of these technical morasses and it ***** me into its vortex all through the night... time for bed.

  • Can you use screen sharing outside of your local network?

    I've been poking around with the "screen sharing" in osx Lion. I have a few questions about it.
    Firstly, is the built-in screen sharing only accessible through the finder?
    Also, is it only available on local networks? I've gotten it to work on two computers on the same network. But, can I use in the built-in screen sharing to look at my work iMac while I'm at home on my Macbook? Or would I need a full VPN client to do this? (Although isn't there built-in VPN compatibility in Lion?)
    Thanks!

    Go here..
    https://discussions.apple.com/message/16439571#16439571
    ... and read my post explaining the different ways to share your screen.  Things should be a little clearer for you, I hope.
    Bob

  • Is it possible for multiple users to use a "generic" account simultaneously without screen sharing?

    Hey and thanks for checking out the thread.
    I am wondering if it is possible to have users use a generic account at the same time without any sort of screen sharing.
    I have set up a generic user account (for example useraccount, password 1234) for users to use in the time before I can set up a custom user name for them. However, I have run into some issues with this.
    When multiple users log on using this generic account, their applications seem to be shared on each screen. In the room with multiple Mac workstations, if someone starts working on Photoshop, Photoshop will open on every one elses screen who is logged on under that generic account.
    Is it possible for users to log on using a generic network account and have their own isolated work environment or is this sort of sharing a feature? I am new to Mac servers and am not sure.
    Thanks for reading the thread.

    That shared-account approach seems impractical for the various reasons you've identified, as well as the inevitable issue of cleaning up the detritus that'll inevitably build up in a shared account, and for the lack of accountability for activities occuring under the shared account for both auditing and security, and sharing directories would tend to introduce obscure conflicts around which-file-version-wins file updates when the same file is used in several places, and would probably be contrary to any per-user application software licensing agreements that might be involved.
    Put another way, get unique accounts created for folks, and work toward the ability to create accounts for arriving folks, and — if it's applicable here — talk to management about getting any per-user software licensing issues sorted out, whether that's having spare copies purchased and ahead or some advanced notice on accounts, or establishing group software licensing where that's available.
    AFAIK, there are tools around which can automate account creation, too.  Either generic, a tool such as Passenger, or it's certainly feasible to script the account creation sequence.
    Trying this shared-access generic-account approach just looks like it can create more work and more hassles and more effort to me...

  • How can I set up a screen screen sharing VNC at a resolution higher than display?

    I have a mid 2010 MacBook Pro 13in, and i have set up screen sharing to access over VNC. I want to view my mac on my 1920x1080 display hooked up to my PC. But when i do it is not full screen, it is the same resolution as my MBP. how can i run it at a higher resolution only over VNC?

    As Cvid suggests, I create my "frames" in Photoshop. Not sure about all versions, but my PS has several Actions, just for frames, and I have made a few more, with a different "look."
    I Save_As PSD, and just Import those as Footage (I do not need the capability to work with the individual Layers).
    Good luck,
    Hunt

Maybe you are looking for

  • Numbering squares in a grid

    I wish to be able to sequentially number squares in a grid created by Illustrator 11.0.0  I would like to place the first number in, and the rest will follow. James

  • What will happen when I remove controllers from mobility groups?

    Hi, I'm wondering what exactly will happen when I remove a controller from a mobility group? 1) Will it require a reboot? (I don't think so, nothing I've found says so) 2) Will it deauth/reauth the AP's connected (I don't think so, nothing I've found

  • Vim umlaut

    Hi, i just upgraded to Yosemite (10.10.1) and i noticed, that 'vim' does not handle umlauts correctly. I'm using the the default German locale settings and the value of the $LANG environment variable is 'de_DE.UTF-8' however vim is not able to displa

  • Overriding equals and hashCode

    Everywhere I look it talks about overriding equals and hashCode together, and it also warns that doing it wrong could complicate things severly. However I haven't been able to find good documentation on how to do it properly. Any suggestions on where

  • Universe based on SAP BW in Crystal Reports

    Hello everybody. Yesterday I've visited the CeBIT. Here I've talked to other colleges working on BO issues. We're using the Version BO Enterprise XI 3.0. In this version it is not possible to use Universes in Crystal Reports 2008 that base on SAP BW