Screen sharing mac to mac external

Hello, i am writing from Norway.
I wanna to give support to en external mac machine over internett, but when i search youtube i can only find video that demonstration screen sharing localy in the same local nettwork.
I have tried everyting in my MAC sharing folder but i dont get it work, maybe i am not understanding everything i guess in this sharing folder in MAC-option.
I am not a beginner when it comes to MAC, realy not, but this case its hard for me to solve.
I hope someone can help me or give som feedback.
I have the Macbook Pro from 2011 with Mountain Lion installed.
Best regaards
Kristian Magnussen.

Actually, the 'dns-sd -R' command only registers a service running on the machine on which you are running the command. Notice how there is no parameter for the remote host's IP.
To register a service running on another machine, you have to use the proxy command, 'dns-sd -P'.
The syntax, per the command help, is:
dns-sd -P <Name> <Type> <Domain> <Port> <Host> <IP> \[<TXT>...\]
Playing around with it, I've only been able to get it to work as such:
dns-sd -P label rfb.tcp local. 5900 name.example.com 192.168.1.10
Strangely enough, I had to pass it both a fully-qualified host name that resolves properly in DNS (or maybe .hosts -- I didn't test that) AND the IP address (even though I'd think if it had one, it wouldn't need the other.) Also, just the host name without the fully-qualified domain didn't work either, even though it resolves fine for ping, etc.
Alternatively, one could use a program like Rendezvous Proxy.

Similar Messages

  • Mouse not working on screen shared Mac

    Screen sharing from Messages works as expected, except the mouse doesn't appear. I see the mouse on my local mouse but when I mouse over to the remove screen/window, the mouse dissapears. The keyboard works– command-tab, for example works on the remote mac from my mac- but the mouse just isn't visible.
    Any ideas?

    Hi,
    I just did this using Bonjour between a Snow Leopard Computer (iChat 5) and Messages in Mountain Lion (version 7)
    I started from the Snow Leopard Computer and Offered to "Share My Screen" from there.
    The MacBook Pro (Snow Leopard) Screen cam up on the iMac (Mountion Lion).
    I could see the cursor on both Screens as I moved around the pic/screen on my iMac the cursor moved on the MacBook Pro.
    I tried bringing my own Screen to the front (no Problems) and then mousing over the reduced MacBook Pro screen. It seems it is isolated from the Cursor (As it should be) at this point and did not appear on the MacBook Pro.
    How many physical Screens/Displays does the Buddy have ?
    Any chance your cursor is so far off to one side that it is not on the view you can see ?
    This might also depend on how the Buddy has any external Screens set up.
    Most run them left and right but some have them one above the over.
    It may also depend if the display is actually On.  I once used a second Display/Monitor/Screen and had it turned Off but System Preferences identified it as being "there" and in an iChat Screen Sharing it distorted the view.  Very wide letter boxed pic.
    10:40 PM      Tuesday; July 31, 2012
    Please, if posting Logs, do not post any Log info after the line "Binary Images for iChat"
      iMac 2.5Ghz 5i 2011 (Lion 10.7.2)
     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

  • Screen sharing Mac and PC?

    I am on a LAN and i want to know if you could share the Mac's screen with another PC. If the macbookpro is ON and opened up could i control or see its screen from another PC o the network? If yes, how?

    OSX's Screen Sharing is based on the VNC protocol.  So on paper, any VNC client should work.  In reality, some VNC clients work better than others.  And the way Apple implemented Screen Sharing in Lion "broke" some of the PC VNC clients.  So try a several different VNC client on your PC to see which works best for you.
    Me personally, I still use the original AT&T VNC client, which is really old, hasn't been updated in years (but still works on Windows 7,) and doesn't have many features that have been added on by other vendors.  But that lack of add-ons I belive are why I seem to have very few problems with connecting from my Windows PC.  YMMV, of course.

  • Back to My Mac - Screen Sharing Mac OS X 10.10 problem

    Sense Mac OS X 10.9 great feature Screen Sharing & Back to My Mac does not works any more.
    Mac OS X 10.10.1
    Russian interface:
    We can see remote computers, but can not connect. We get a error.
    English interface:
    We can not even see remote macs.
    If I start up main computer from Mac OS X 10.8 Screen Sharing works fine. Remote macs has Mac OS X 10.8 and 10.9

    I have the same problem, just today (although I'm still running 10.6.8). Every morning I turn on my main Logic mac then fire up my 2 slave macs, connect to them, activate Screen Sharing, and get going.
    This morning I tried it, connected to the other macs as usual (I can see/access/alter their hard drives from my main mac) but when I click "Share Screen" I just get the "connecting" dialog box & it just keeps going.
    The weird thing is, when I put my laptop into the network via wifi, I can screenshare my main mac's screen (all 3 of them, actually!)  but not my 2 slave macs that are ethernet'd to the main mac.
    I've tried every solution I could find via google, and nothing is working.
    Kirby

  • Screen sharing -- Mac to Windows

    I have two Windows XP computers and one Ubuntu computer that I want to share screens with my MacPro (OSX 10.5.5).
    I have TightVNC one one of the Windows XP computers and RealVNC on the other. Both computers have Bonjour installed -- for what it's worth.
    My goal is to have all three of my networked computers show up for screen sharing in the Finder's SHARING section.
    I enabled Remote Desktop on the Ubuntu computer and "ta-da" it showed up in the Finder's "Sharing" section to screen share with no other intervention whatsoever.
    I can't figure out how to make the Windows XP computer show up in the Finder's sidebar.
    Note I can use Chicken of the VNC to connect to ALL machines on my network via their static IP addresses. It works fine -- it's just that I think it's very slick and convenient to do it the OSX "way" instead of using the CotVNC client.
    What does it take for the Windows XP computers to advertise their screen sharing capability so they'll show up in the Finder's "Shared" sidebar??

    Actually, the 'dns-sd -R' command only registers a service running on the machine on which you are running the command. Notice how there is no parameter for the remote host's IP.
    To register a service running on another machine, you have to use the proxy command, 'dns-sd -P'.
    The syntax, per the command help, is:
    dns-sd -P <Name> <Type> <Domain> <Port> <Host> <IP> \[<TXT>...\]
    Playing around with it, I've only been able to get it to work as such:
    dns-sd -P label rfb.tcp local. 5900 name.example.com 192.168.1.10
    Strangely enough, I had to pass it both a fully-qualified host name that resolves properly in DNS (or maybe .hosts -- I didn't test that) AND the IP address (even though I'd think if it had one, it wouldn't need the other.) Also, just the host name without the fully-qualified domain didn't work either, even though it resolves fine for ping, etc.
    Alternatively, one could use a program like Rendezvous Proxy.

  • Screen sharing Mac apps (that are not iChat)

    I only have luck with iChat when I use my AirPort Extreme router. Using my neighboars lynksys router, it never works. Are they are Mac apps out there that will do what iChat does, but without the headaches? I'm looking for some good paid software.
    Bryan

    You may want to use a web browser based option
    Use this link and scroll down to Item 9 through 12
    http://www.ralphjohns.co.uk/page5.html#_other
    7:59 PM Friday; February 6, 2009
    I may receive some form of compensation, financial or otherwise, from my recommendation or link.

  • Why can't I connect to my Mac Mini via Finder (but I CAN via screen sharing)?

    My problem concerns a quad-core 2.0 GHz Mac Mini Server (mid 2011, I think) with SSD and 3 external hard drives. It's (a) my desktop workstation (b) our Time Machine backup repository (c) iTunes server and (d) Printopia server for our iDevices. That's it. The only thing I use the server app for, really, is Time Machine.
    So recently we lost power a couple of times. As always, I ran Disk Utility, repaired permissions and verified the main disk. All appeared well.
    But all is assuredly not well. Now, none of my other Macs can (a) find the Time Machine backup volume or (b) connect to the server at all. Whenever I try either thing, I receive the message below:
    The network is in flawless shape otherwise. My router is the latest generation Airport Extreme Base Station. The server has a static IP, and I CAN connect to it from my other Macs by clicking Finder, then Go, then entering the IP address -- but ONLY if I use an smb:// prefix!
    Moreover, even when I'm connected in this way, I STILL get the message whenever I try to connect by merely clicking the name on the finder sidebar -- or whenever I try to access the machine using Time Machine preferences. Weirder still, I CANNOT connect to the ip address via afp.
    Final piece of weirdness: I can also connect to this machine from any other Mac via screen sharing. So please....
    WHAT'S MY PROBLEM AND HOW CAN I FIX IT? I've wracked my brains, combed through forums and can find nobody else with this problem, let alone a solution.The problem persists when I shut down the server app.
    I'm assuming that either something is corrupted or some setting is afoul, but can't figure out what it might me,
    I'm just about at the point of reformatting my main drive and reinstalling Mountain Lion, but am hoping someone can spare me that pain.
    THANK YOU so much!
    Arthur P. Johnson
    P.S. I have no problem at all with outbound connections from this bewitched Mini. Just inbound.
    P.P.S I will, of course, be happy to provide shots of any other settings you may desire,

    For some reason, the error box photo didn't appear in my post. Here it is:

  • IChat screen sharing and video not working on MacBook but works on Mac pro

    I have a MacBook and MacBook pro. Both have the lion os 10.7.2. I can use iChat on the MacBook pro for screen sharing, video chat, and text chatting, with others remote to me. However, I can only do texting with the MacBook.  I can do screen sharing via Finder between my MacBook and MacBook pro. I can do FaceTime between both systems. I can also do FaceTime between the MacBook and anyone remotely.
    I also tried installing teamviewer on the MacBook, and on a remote MacBook..... And I get the same results where I cannot share the screen, from the one that has not been working.
    I have checked the settings under system preference and made sure screen sharing was enabled. I have checked under iChat under video to make sure screen sharing was checked.
    The macbook that is having this problem is configured for AIM for iChat
    I have run out of ideas. Any suggestions on what I might try?
    Thanks

    Ok,
    I will list the ports in greater detail and point out when iChat uses them.
    AIM Login and 1-1 Text Chatting
    iChat version 1  through 5 will Log in to the AIM server on port 5190 (TCP Protocol) by default.
    Since iChat 2 we have been posting here that the AIM servers allow a Login on almost any port and have been suggesting port 443.
    This is used by both Web Browsers for secure Login to some sites and by the Mail app with some mail servers.
    It is also below port 1024  (most domestic routers have the ports above this figure closed)  In some campus situations using port 443 will normally allow at least Login and Text chatting.
    iChat 6 uses port 443 by default.
    File Transfers (AIM)
    When doing File Transfers with AIM Buddies iChat will move to using Port 5190 on the UDP Protocol.
    This cannot be changed.  (This invokes the little Message about Starting Direct IM in an open Chat)
    It also uses this port for Pics-in-chats, dropping Files on a Buddy's name with out a Chat or sending other files that are not pics.
    In the case of Port Forwarding some devices don't like port 5190 being forwarded "twice" which is another reason for moving the login and Text chat port.
    Jabber Logins
    No matter what Jabber server you use ichat will use one of two ports (5222 and 5223)
    Which one it uses is dependent on whether it needs and is using an SSL Login or not.
    SSL Logins use port 5223 and NON SSL one use 5222 (ticking or Unticking the SSL box on a Jabber account will automatically change the port).
    Google Talk is the exception in that it allow a Login on port 443 as well.
    The First Apple Doc I linked you to says iChat uses port 5220 in Jabber.
    I run Little Snitch and have never seen any version of iChat use this port at any time.
    Bonjour
    Any Mac to Mac Connection or Mac to any Bonjour able peripheral will be on port 5353.
    This is normally opened (Preset) in the Mac Firewall for the Finder/System side of Sharing.
    iChat needs and uses two other ports  (5297 UDP and 5298 on both TCP and UDP)
    As they an LAN Side connections the router would normally pass them.
    At iChat 3 there were issues with the Mac Firewall (it included UDP set up and the preset in the firewall only listed them and TCP so we had people add all the iChat ports  (you had to manually enter them in Tiger)
    A/V Chats
    No matter which Buddy List you start from iChat will do A/V chats the same way.
    The Visible Invite you or your Buddy sends is on port 5678 (UDP)
    In iChat 3 and earlier iChat then moves to port 5060 to send the SIP Connection Process invite behind the scenes  (SIP = Session Initiation Protocol)
    Port 5060 is one of 4 ports internationally agreed for SIP (How VoIP phones connect) (5060-5063).
    Although ISPs were not supposed to block Through traffic many started blocking End users  and then Charging them to open these ports (Many ISP were telecom companies that were losing long distant Telephone calls monies).
    The SIP process then in iChat 3 contacts a server run by Apple for this purpose (Snatmap.mac.com to give it it's full name).
    This acts like a old fashioned telephone operator connecting the call.
    SIP is a text based process.
    Your end "Calls" the operator.
    The Operator "Calls" Buddy.
    Buddy Accepts
    iChat then negotiates the ports to be used.
    In iChat 2 and 3 it uses 4 ports (vid in Vid out, Audio In and Audio Out) from "the group of 20" starting at the bottom (16384 to 16387 normally)
    Three and 4 way chats uses more ports (which is why 20 are set aside)
    In iChat 4 Apple realised the issue with the 5060 port and changed the way iChat worked
    Since then it has Sent the invite on Port 5678 but then moved to port 16402 (it starts at the top of a smaller group of 20)
    All Video and Audio traffic is also now on one port  (so no need for 20 ports and iChat now lists 10).
    NOTES so Far.
    File Sharing during a Chat converts the Chat to Direct IM for AIM Logins
    This is Peer-to-Peer in AIM
    A/V Chats are Peer-To-Peer and you can actually log out of the Buddy list and continue the chat. (The exception is using iChat 6's  AIM Video relay option)
    Screen Sharing
    Screen Sharing is an Audio Chat with a VNC connection along side.
    Both bits have to wok to avoid the Pop-up to send to Apple and the Log that contains.
    The Audio part is on port 16402 and the VNC part is random. (So random it is different every time you do it)
    The reason it is classed as an Audio Chat+ is so the AppleScript for Auto Accept can  filter out Screen Sharing connection and Not Auto Accept them.
    This does have a knock on effect as far as your Router is concerned as already mentioned earlier.
    You cannot Forward or Trigger the random Port so you have to use UPnP in your router to open the ports.
    NOTES
    Jabber File sharing may possibly be on port 1080 as listed in the Server Article I linked you to (I have also seen it written about in other stuff I have come across)
    However Little Snitch does not seem to confirm this either.
    Most time it will be peer-to-peer like the AIM connections for this.
    However some Jabber servers do not seem to allow this and have this Jabber65 Proxy set up which passes things Server to Server in between it leaving your end and arriving at a Buddy.
    This on  Port 7777 but you do not need to open this port (unless you are running a Jabber server)
    I have yet to test File Transfers using a Yahoo Buddy List in iChat 6.
    AppleCare and Geniuses.
    Previously I have been contacted by Geniuses in Stores asking to test customer's iChat.
    They and the Applecare people have details about Apple wants an designed the App to work.
    What they don't have is the knowledge about what it takes to set it up in the "real world".
    There are literally thousands of Makes and Models of routers.
    Some like the Thomson-Alcatel brand state they are SIP/VoIP ready but this means the router strips out all SIP Data trying to send it to a Phone.
    Early models of Alcatels can get around this with a tweak. Later models can't.
    Motorola devices tend not to have UPnP.
    Apple Base Stations have Port Mapping Protocol instead of UPnP and this needs setting up.
    The Zyxel range definitely does not like the dual use of port 5190 and does much better using UPnP (You almost certainly have to do your AIM login on port 443 with these).
    1. I have two computers (MacPro and MacBook Pro) that are both running Lion 10.7.2 and both running iChat 6.0.1.  <<-- Fine
    2. The Netgear router model is: WNDR3700.    <<<<---  With any Brand there are exceptions and I do wonder about this one
    3. The firewall for both Macs is turned on and in the advanced area iChat is listed as being "allowed."  <<<<---- Fine
    4. In iChat, under the video options, "Screen Sharing Allowed" is checked.                                        <<<<<---- Fine
    5. In System Preferences, "Screen Sharing" is checked and this is for "All Users" at present.               <<<<<---- Not Required
    6. There are two separate AIM accounts being used for iChat purposes.                                            <<<<<----  OK
    7. In iChat preferences, each AIM account is "Enabled" under "Account Information" and the "Server Settings" show the Server as "api.oscar.aol.com" and the Port is "443" and "Use SSL" is checked.                                <<<<---- As it should be
    From this and the other info in the first port it was only the router set up that seem to throw some light on a possible cause (Port Forwarding and UPnP conflict)
    If just doing Port Forwarding the ports listed would have covered things (Except the Screen Sharing's random port)
    Regarding your latest post.
    I have  table similar to that on my Sagem 2504Fast Modem/router combined device and it too seems to list a different port on the external side on occasions.
    I would try the router with the Disable SIP ALG unticked (so it is not disabled). If the Help info on the right gives any info about what this Netgear version does it would be helpful.
    Some are like the Thomson-Alcatels I was talking about in that it points the SIP data to a specific place (Possibly a Phone socket on the device)
    Others seem to provide an "boost"  to enable SIP to work and don't seem to get in the way of iChat.
    Try adding the Names in Table 1 from this page and see if you can Video to those.
    There are 6 names in total (I am actually only seeing one on Line as I type)
    9:19 PM      Wednesday; January 25, 2012
    Please, if posting Logs, do not post any Log info after the line "Binary Images for iChat"
      iMac 2.5Ghz 5i 2011 (Lion 10.7.2)
     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

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

  • Screen sharing on Mac's through Messages (remotely) ?

    Hi,
    I'm visiting my in-laws and have just helped them set up their new iMac. I expect they will from time to time need me to assist them remotely (we live app. 1200 km apart), so now I am trying to get screen sharing in Messages to work (all Macs are running latest Mountain Lion).
    Using my MBPro on their local WiFi network, I noticed that the screen sharing commands remain grayed out in Messages when chatting between the two iCloud accounts. By playing around a bit I noticed that when activating Bonjour on both Macs it appears to work. On my own Mac I noticed an AIM account which should also do the trick according to what I can find on the web ... but I don't recall ever creating an AIM account and wouldn't know how to do so for my in-laws.
    So here are a couple of questions I am struggling with (and given my departure date later this week would like to resolve quickly) :
    - Does screensharing work in Messages between iCloud accounts ?
    - What is Bonjour ? Why do I need it ? (seems a bit of blurry on the web as far as I can find)
    - What do I need an AIM account for ? Was this created automatically on my own Mac at SnowLeopard time ? Should I create one for my in-laws and if so how ?
    - Is chatting over bonjour / AIM possible on iPad / iPhone ? or will the conversations re

    Hi
    - Does screensharing work in Messages between iCloud accounts ?
    Yes and No
    The No is as an iMessage account.
    If the Apple ID is an Apple Issued one (@Mac.com and @me.com) then it can be added as an AIM account and will Screen Share
    - What is Bonjour ? Why do I need it ? (seems a bit of blurry on the web as far as I can find)
    Bonjour is Apple's Zero configuration method of finding other Macs, Bonjour enabled items like Printers and some PCs running Bonjour enabled apps.
    These show up in the Share in the Finders Side bar.
    This shows up as the Computer name (See System Preference > Sharing)
    Within iChat/Messages (if Enabled) then you can see other people with Bonjour Enabled on their iChat or Messages.
    In iChat or Message the Buddy Name is taken from the Address Book (Contacts in Mountain Lion) My Card.
    You will see what other people call themselves in their Card, they will see what you call yourself.
    It will do all that a AIM or Jabber accounts can do except Group Text chats.
    - What do I need an AIM account for ? Was this created automatically on my own Mac at SnowLeopard time ? Should I create one for my in-laws and if so how ?
    Messages added iMessages to iChat to create an iChat+ type app
    Before in iChat AIM and Jabber were the main services that you could use to send messages to other people.
    Some Apple IDs ending with @mac.com or @me.com are valid AIM names
    (You do have to keep the password to 16 characters or less (AIM Server limit)
    iCLoud issues @me.com names will not work in iChat 5 or earlier
    iChat 6 and Messages have a Dual login to AIM and Me.com that allows AIM to "see" the password.
    It might be the case that you had or have an email valid Apple ID from earlier that now appears in System Preferences > Mail, Contacts and Calendars and has been marked as valid for Messages when you only previously used it for Mail.
    You could create your relatives an Apple ID (keep the password to 16 characters or less) from iCloud and both use "AIM" to then do the Screen Sharing.
    You can also register a Name with AIM themselves.
    Creating the Apple ID tends to Hard Code an external to Apple Email address to that Account but the name is then a valid Email.
    AIM can use an email as the name.  You can create a name with AIM without listing an email as the name and you then enter this as a plain Username in the Add section of Messages.
    You realistically still need to list a separate email for Verification and Password Recovery but you can use the same email over and over and create as many names as you like.
    - Is chatting over Bonjour / AIM possible on iPad / iPhone ? or will the conversations re
    Bonjour is only used on a LAN (Local chats in the same premisses)
    iPad and  iPhones are not Bonjour Enabled.
    AIM text chat are possible on an iPad/iPhone to a Computer.
    The simplest is the iPad logs in with  an AIM name via a web Browser and use AIM Express.
    The Name used would have to be either @mac.com or an AIM one as an @me.com from iCloud could not get the password checked this way.
    The Mac uses Messages/iChat depending on OS and iChat version.
    However between iPhones/iPads and a computer the iMessages account is easier.
    9:36 PM      Monday; September 17, 2012
    Please, if posting Logs, do not post any Log info after the line "Binary Images for iChat"
      iMac 2.5Ghz 5i 2011 (Lion 10.7.2)
     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

  • 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 Sleeping Mac Mini

    Hi,
    After months of nagging from my IT colleagues I have just bought a Mac mini, just upgraded to Leopard and am just getting to grips with how it functions. (very impressed to date now I have a "proper operting system" :o) )I am using it in my lounge connected to my Plasma TV. I have enabled Screeen sharing and can access it succesfully from my windows machines using VNC viewer free edition. The colour and picture quality is excellent however it won't allow me to connect when the machine is asleep. I also have Vine VNC server which I am sure would go to sleep and let me connect using VNC however it doens't seem to sleep with Vine anymore and I also get two icons appear in the dock. The screen quality appear to be much better with Screen sharing so I'd rather use that than Vine. I could switch sleeping off howevere I don't use the Mac and would like to let it sleep. I was a bit nervous about posting here for the first time incase I get "abuse" but my other Mac users assure somebody will know the answer. I have some other questions so I'll post these on the site in the relevent areas now I'm registered.
    Cheers in advance.
    Clarkerz

    Clarkerz...Wondering the same thing. No "abuse" from my direction. This is a great question I am also trying to find a solution for.
    I often work remotely between my home office work horse (g4 tower) and my 17" MacBook Pro. Files are often duplicated between the systems...and having one access point (screen sharing) is great. However, I am wondering the same thing. I hate to leave the slave computer (in most cases this is my G4 tower) on permanently in the event I happen to need to share in.
    Before Leopard, I was using Astro View / Share. I am sure some will wonder...why that program. Well, long story short, pain in the arse, but it worked...althoughbeit not as well as Leopards built in screen share. Though Screen Share is a much better solution...I still wonder about the "sleep" issue. Hate to leave it on permanently.

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

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

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

  • Can't access iTunes and Screen Sharing sharing services on my mac Mini

    Since several weeks now I face a networking issue of the stranger kind.
    Currently I've got my Mac mini acting as the central server for music, photos and files in my home. Central Network Mgmt device is a Wireless Lan router.
    In the past I was accessing the Mac Mini from my MacBook via Screen Sharing this doesn't work anymore. When requesting the service the connection effort just runs idle. In iTunes on my MacBook I can see the Libary of my Mac Mini iTunes but clicking on it brings the rotateing ball and after a certain while the message that the iTunes Libary is not responding and that I should check my Firewall settings. Which I did on both computers and they are wide open. 'Ipfw show' in Terminal brings back the message 'Open for any to any communication' also on both computers.
    Makeing use of the File sharing service from the MacBook to the MacMini works but it takes a extreme long while until the shared folder appears on the MacBook.
    Trying to access from the Mac Mini my MacBook for all these services is no problem.
    One more thing is that my Mac Mini cannot access the Wireless Lan router anymore thru the Web Browser or thru a Ping. Here I get the message 'Ping Send to: permission denied'. I changed the Router still the same message. Internet traffic is only possible after I manually applied a DNS Server with its IP number.
    Anyone out there who could help? I'm close to completely reinstall my Mac Mini but would naturally love to avoid this.

    wireduck,
    Highlight the music folder and on the keyboard type (Command) + i: on the window that opens scroll down if need and click on the lock on the bottom right. Type in an Admin User name and password. Then under the (Sharing & Permissions:) make sure the users you want to open the folder are listed and that there (Privilege) is set to @ least Read. If not hit the ( + ) sign and add them. After you have that all set up click on the little gear next to the ( - )s sign and (Apply to a enclosed items). that way each user can read the files. After that the little ( - ) sign should be gone on the folders.
    Hope that helps.

  • Back to my mac screen sharing no longer works since Mountain Lion release, even on Lion

    I've used screen sharing via iCloud and back to my mac between a 2007 macbook and a 2010 imac.  Both computers are still on Lion but screen sharing stopped working when Mountain Lion was released.  I've read a number of comments on this forum that people were having trouble since upgrading to Mountain Lion, but I don't think that's the problem b/c I haven't upgraded either machine.  I think the problem is something Apple did in preparation for the Mountain Lion release date and it seems to have damaged screen sharing functionality.  Anybody else experiencing this or have a fix for it. 
    As for the specifics, I can still see my "other" machine under shared and can click "share screen," it usually searches for a couple minutes, then pops up the password dialogue box, but then searches for a while and eventually the password box closes, "screen sharing" stays open, but there are no windows associated with it.

    I have the same problem, just today (although I'm still running 10.6.8). Every morning I turn on my main Logic mac then fire up my 2 slave macs, connect to them, activate Screen Sharing, and get going.
    This morning I tried it, connected to the other macs as usual (I can see/access/alter their hard drives from my main mac) but when I click "Share Screen" I just get the "connecting" dialog box & it just keeps going.
    The weird thing is, when I put my laptop into the network via wifi, I can screenshare my main mac's screen (all 3 of them, actually!)  but not my 2 slave macs that are ethernet'd to the main mac.
    I've tried every solution I could find via google, and nothing is working.
    Kirby

Maybe you are looking for