Screen sharing connect dialog hung

last nite i tried 2 connect 2 a m.b.pro (running 10.6.8) over wifi from my 10.7.4 m.b.pro. it was still spinning when i closed up 4 the nite, and now this morning the dialog is still spinning, and even when selected, the dialog's cancel button is disabled...see attached screengrab:
also note that even tho the dialog is selected, the menubar still shows the previous f/g app (ffx as i type this msg;-) so i don't even kow what process 2 kill;-\
perhaps i should file a bug report, but i'll have 2 figure out again where apple hides that;-\
also note that i am able 2 screen share no problem w/ my 10.6.8 minimac (ethernetted to the wifi router) so the only difference is wifi2wifi...nope: i just tried s.s'ing from the minimac to the problem m.b. (via s.s from my m.b.) and got the same hung dialog:
bouncing screen sharing doesn't help, but bouncing finder allowed s.s. to finally go thru, but the dialog is still there:-( now i got 2 machines w/zombie dialogs:-P

No, not looking to disable Screen Sharing, just to clear the dialog box (it floats above all other windows) without restarting.
Found this post that resolves the issue:
"This happens to me often if I have a problem connecting a remote computer -- those connecting windows just never go away if they hang. The issue is that NetAuthAgent is hanging. To get rid of these without rebooting:
From GUI:
1. Launch the Activity Monitor program.
2. In the Process Name list, look for "NetAuthAgent". It may show as "Not Responding".
3. Select NetAuthAgent, and then click Quit Process (the red stop sign button at the top of the Activity Monitor window). Then, click Force Quit.
From Terminial:
1. ps ax | grep NetAuthAgent
2. kill <pid-of-the-process-found-above>
This should get rid of the dialog boxes and the hung process, and VNC/Screen Sharing should continue to work, as it will launch NetAuthAgent again when it needs it."
This did just what I was looking to do!

Similar Messages

Saving Screen Sharing Connections

Ok, this is driving me crazy. How do you save a Screen Sharing connection so that you do not have to enter the IP address every time. I am referring to accessing a computer remotely over the Internet done through port 5900. I have the screen sharing set up and working fine, and I even have one of these shortcuts made a year ago, but for the life of me I can't remember how I did it again.
I think may be it was a trick using TextEdit? I know you can do this for ssh connections, but I can't remember the syntax for doing it for screen sharing. If I remember correctly you can type the right syntax followed by the IP address in TextEdit. Then you highlight the text and drag it to the desktop which results in a .inetloc file. After that you can simply doubleclick on the file and it will automatically launch the Screen Share.app and go to the right IP.

Open Safari
Type in "vnc://your.ip.address" in the address bar (I use Bonjour so it's "vnc://computername.local")
Drag the blue globe in the address bar onto your desktop
Source: http://www.mail-archive.com/[email protected]/msg46630.html

Start Screen Sharing Connection in Observe Mode?

Hi,
I've been able to add the toolbar button to switch screen sharing between the control and observe modes using tips I've found around the web.
I need to be able to check on what's going on with one of the computers on my home network without taking control of the mouse and keyboard.
Screen sharing defaults to control mode on connection, does anyone know if there's a way to make it default to observe or if not then to start a specific connection in observe?
TIA,
Rob.

You need Leopard and iChat 4 to work with Shinywhitebox's[Chatter|http://www.shinywhitebox.com/chatter/chatter.html]

Screen sharing connecting then immediately disconnecting

I've recently bought an Intel Mac Mini for my Mother to use, and installed it at her place with Leopard. I'm running Leopard on my Macbook pro, and was hoping to use iChat screen sharing to solve problems for her. Now my problem here is that when I try to initiate screen sharing, the connection goes through, and sometimes (but not always) we see the large writing across the screen, but then it immediately disconnects citing the inititiator as disconnecting the screen sharing session. This happens whether I initiate screen sharing or my mother does.
I am on a 10+ meg broadband connection with 700kb upload, and she's currently on a 2 meg connection with 256 + kb connection. Is this part of the problem? I've opened port 5900 on her router to pass through to her computer. Also internally on my network ichat sharing works as it should.

After an hour if pulling out my hair, I finally had an idea of what might be causing the crash... I noticed I had my old iSight plugged in (the external firewire iSight) into my Apple Cinema Display. I unplugged it and iChat screen sharing worked PERFECTLY. You should also know that I don't have problems with my iSight, it works well on Video Chat and Audio Chat and even presentation mode but, it screwed up screen sharing.
In conclusion, if you're experiencing sudden connection losses with iChat screen sharing, check to see if you have an iSight plugged into your Mac and unplug it.

Screen Sharing Connection failed when using dock shortcut

I have 10.10.2 installed on this computer - just updated - and 10.10.1 installed on a couple others (in the process of upgrading) as well as older versions installed on some older computers.
I have Screen Sharing in the Dock and when I right click on it I get a list of recently connected computers. Until recently this generally worked for making the connection to that remote computer. Sometimes there were minor issues such as systems showing up which are no longer on my network - or showing up with an obsolete name. The big issue is that lately systems are showing up with a .vncloc extension and even when they don't it is hit or miss as to wether or not using the shortcut will make the connection.
I get an error message that says: Connection failed to "ComputerName".
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 your network connection is working properly.
In every case - after I see that message if I open a Finder folder - and navigate to the other system and click on Screen Sharing in the Finder window it will connect - and I can do this repeatedly. Every so often the shortcut will work but mostly it does not.
I have looked for ways to clear that recent items list without success.
I have cleared the keychain access to the remote computers and reset without success.
I don't recall seeing this behavior prior to the first 10.10.x system being on my network.
I have not (yet) tried - turning off screen sharing on ALL systems throughout the network then turing them all back on.
Not sure if this is a I am using a single iTunes/iCloud account for many of the systems - but also have one permanent and several guest machines that have their own iCloud account.

Hi Matt Wolanski,
Thanks for using Apple Support Communities. Based on what you stated, it sounds like you are having intermittant trouble with screen sharing. It looks like you have already done some troubleshooting. I would recommend that you read this article, there are several things you can check that may be able to help the issue.
OS X Yosemite: If you can’t share computer screens
Cheers,
Mario

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

Problems connecting video and screen sharing

see the leopard iChat forum, I moved it to there. thanks, its called Another Video and screen sharing connection problem
Message was edited by: wishiwasmtbin

Hi,
Welcome to the  Discussions
IS this Linksys doing UPnP ?
This is set in the Administration page of the set up pages.
Also in the Security Page disable the Anonymous Ping Blocking.
If you set UPnP then make sure any Port Forwarding, Port Triggering and DMZ is disabled.
These last three use NAT more strongly than UPnP and NAT can be an Issue.
The Appleu3test accounts are effectively on Public IP address so Lees/no NAT
1:52 PM Sunday; December 9, 2007

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 and Drive Sharing

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

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

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

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

Best Way To Set Up Screen Sharing Over The Internet

What is the best/simplest way to set up screen sharing over the internet so I can remotely control my Mac at home from my Mac at work? My Mac at work is running 10.5.6, my Mac at home is running 10.4.11.

simplest
Get both Macs up to Mac OS X (Leopard). Then use Apple's MobileMe Back-to-my-Mac service.
Or, use iChat screen sharing along with the iChat free 3rd party Chax add-on which allows selected iChat Buddies to auto-accept an iChat screen sharing request. Free AOL Instant Messaging accounts can be used as the iChat accounts.
If you do not want to upgrade all systems to Leopard...
Next would be using the free LogMeIn.com account, or similar service. This will work
The above avoid needing to figure out how you get through the home routers, and provide encrypted screen sharing sessions.
After that you need to arrange for router port forwarding. If you want secure connections, then you should arrange to port forward the SSH port 22, then use ssh tunnels for VNC based screen sharing connections. There are GUI based utilities that will help setting up SSH tunnels. Do some searches over at VersionTracker.com or MacUpdates.com

Screen Sharing to Device with iCloud

Prior to Yosemite, every machine associated with my iCloud ID would show up in the Finder under "Sharing". If I selected that machine's name, I'd see the shared folders, and be able to activate Screen Sharing directly to that machine with a button click.
Since upgrading to Yosemite, I no longer see these machines available to connect-to. I've tried disabling and re-enabling "Back to my Mac". I've also upgraded the Server service running on the host machine I'd planned to connect-to in case that was a factor, but it hasn't resolved the problem.
Anybody know how to get iCloud-linked machines to show up under Sharing in the Finder so I can easily establish Screen Sharing connections?
Thanks

If you changed nothing other than to update your client Mac to Yosemite, what you describe strongly resembles an earlier bug making an encore appearance.
What follows is what I had to say about it roughly a year ago, updated for today. Some of it will be obvious to experienced Mac users so overlook that.
This can be a challenging problem to diagnose. It appears that Mavericks Yosemite has changed something about BTMM resulting in it being less reliable than it was with Mountain Lion Mavericks. It works, but not always, and I have yet to correlate its cause to anything specific.
Here are some possible hints.
Make sure you are using a compatible router. BTMM requires a router that supports NAT Port Mapping Protocol (NAT-PMP) or Universal Plug and Play (UPnP). Most routers will work without any trouble at all, but an Apple AirPort will eliminate any uncertainty.
Review all the steps in OS X: Using and troubleshooting Back to My Mac with your iCloud account
The most useful suggestion may be the simplest:
Toggle Back To My Mac off and back on by deselecting and then reselecting Back To My Mac in iCloud System Preferences.
Sometimes that's all it takes.
You can also try some simple steps with Terminal to verify that your BTMM settings are correct:
dns-sd -B _rfb | grep icloud
That will show the Macs using your iCloud ID advertising screen sharing services. If you get no response, ensure the Sharing services on the Macs you wish to use remotely are configured correctly. Perhaps Mavericks simply reverted their settings during installation, as a "security" measure.
dns-sd -B _afpovertcp will show Macs advertising file sharing services.
To ping your Mac use:
ping6 <macname>.<nnnnnnn>.members.btmm.icloud.com
where <macname> is the name of your Mac and <nnnnnnn> is your Back to My Mac account number. See below. You should get a response from ping6; if there is none then screen or file sharing will not work. If the response times are excessively long then the connection may time out and fail.
The name of your Mac is in System Preferences > Sharing > Computer Name:
Your Back to My Mac account number can be determined with the following
dns-sd -E
It will respond with something like this
Timestamp    Recommended Registration domain
0:43:20.322 Added    (More)              local
0:43:20.322 Added    (More)              icloud.com
                                            - > btmm
                                            - - > members
                                            - - - > 0123123
0:43:20.322 Added                          icloud.com
                                            - > btmm
                                            - - > members
                                            - - - > 987654321
The numbers at the end (0123123 etc) are your BTMM account numbers. Most users will have only one.
^C to terminate each of the above.
Good luck.
An example of the above is as follows. Assuming your iCloud ID is 123456 and the Mac you're trying to connect to is named MyMac the above ping6 command is
ping6 MyMac.123456.members.btmm.icloud.com
You should get a response.
You can also try to login to the remote Mac using ssh. Assuming your login name is telstar that would be
ssh -l telstar MyMac.123456.members.btmm.icloud.com
Both should work regardless of your location, whether both Macs are on the same LAN or separated by thousands of miles makes no difference because they are using iCloud services and not local Bonjour to access the remote machine.
Given that your Mac is not appearing in a Finder Sidebar under "shared" I doubt either of the above will work for you.
Report it to Apple. The problem may be related to the particular model Mac you are using, or not.
That's all I have to offer.

Snow Leopard and Screen sharing question

I followed the information in this article to use screen sharing between 2 SL computers and I can make the basic SS work. However, two items from this article don't function as described. It is an older article and I'm asking to see how it still applies to Snow Leopard users.
http://www.macworld.com/article/131094/2007/12/screensharepower.html
One item that doesn't seem to work is Bonjour Browser window. Launching screen share doesn't automatically launch Bonjour Browser. This is a small incovenience but it means I launch BB manually then cut and paste a device address from BB to SS.
The second item is the terminal command to add additional items to the basic SS toolbar such as the button to capture the remote screen to a local file. I've tried it but the additional buttons don't appear. Are their other commans I could use to locally capture a screenshot from the remote machine to my computer?
Are either of these features compatible in Snow Leopard? If yes, how could I trouble shoot my setup to find out why an item isn't functining as described.
Thanks!

What did you do to make it work?
In my setup, I am facing pretty much all the issues I saw on the forum around screen sharing. So from a Snow Leopard iMAC:
1. I can't even get the black remote screen when trying to get access to another iMAC 10.6.1 system. In most of the case the connecting window stays on for about 1 min and than closes; the screen sharing application shows nothing connected. Once or twice I got a black remote screen and once I think it did work well. Tens of times it just did not connect. Console messages show errors with NetAuthAgent (even that file sharing and screen sharing are enabled on the remote Snow Leopard system and the file sharing was fine but connection is slower than with leopard).
2. I can connect to a Leopard system but takes almost a minute to connect. I can access Leopard regardless of the screen sharing options and I never get a black remote screen.
All systems are in a LAN. Before Snow Leopard upgrade the screen sharing connection was instant on all systems.

IChat screen sharing security/encryption

I'm going to be using iChat for the first time and want to use the screen sharing feature between two computers running 10.6. iChat's documentation says:
"While every screen sharing connection uses encryption, the highest level of security requires both participants to have MobileMe subscriptions with encryption enabled. If this is the case, you will see a lock icon in the screen sharing window."
Neither I nor the person I'm going to do screen sharing with has a MobileMe account. I'm wondering:
1. What is the difference between the encryption that "every screen sharing connection uses" and the enhanced security allowed with MobileMe accounts? How does this compare with, say, doing VNC over an SSH connection? Is it adequate for the usual "family help desk" tasks, which may involve typing passwords?
2. I understand that one can get a free MobileMe account which only has iChat capabilities. Does this free MobileMe account enable iChat encryption, or do I have to pay to get that?
Thanks!

re 1)
I am not aware that Screen Sharing is claiming to be Encrypted in each and every connection.
As far as I am aware it uses a modified Apple Remote Desktop engine and is a VNC connection tied together with a Audio Chat (two separate Ports/Data streams in tandem) and that a problem connecting either part will result in failure of the whole connection.
It is claiming to be encrypted in each and every connection -- as I quoted in the original post, "While every screen sharing connection uses encryption..." This is from http://docs.info.apple.com/article.html?path=iChat/5.0/en/17157.html

Screen sharing connect dialog hung

Similar Messages

Maybe you are looking for