Apple Support Communities > Servers and Enterprise Software > Mac OS X Server v10.6 Snow Leopard > Discussions
11795 Views 23 Replies Latest reply: Aug 29, 2011 3:29 AM by kburden000
Currently Being ModeratedNov 6, 2010 3:48 PM (in response to mightyjlr)are you using the Screen Sharing client on the local machine, another machine on the same network, or from outside your network?
If on the server itself, did you use localhost (127.0.0.1) or some other address ?... If you used a name, it is possible the name cannot be resolved on the local machine, or resolves to an outside address. Try using an IP rather than a name.
It should work, the screen sharing client is plain old VNC, hacked up a bit to work well with the Mac.MBP 17, MBP 15 i7, Powerbook G4, iMac 20, Mini OS X Server, 32gig iPhone4, Mac OS X (10.6)
Currently Being ModeratedNov 6, 2010 3:52 PM (in response to DCGOO)I'm using Screen Sharing from different computers connected to the same wireless network as the Mac Mini Server is on. I have tried connecting by clicking on the Screen Sharing button in the Finder, as well as Ctrl-K and using vnc:// and the ip address. All the computers I try just hang at Contacting "Mac Mini Server", but they all work using other VNC clients.Mac, Mac OS X (10.5.6)
Currently Being ModeratedNov 6, 2010 4:56 PM (in response to mightyjlr)Did you use the name of the machine, or its IP address on the wireless network?MBP 17, MBP 15 i7, Powerbook G4, iMac 20, Mini OS X Server, 32gig iPhone4, Mac OS X (10.6)
Currently Being ModeratedNov 7, 2010 8:09 AM (in response to DCGOO)I'm using the ip address.Mac, Mac OS X (10.5.6)
Currently Being ModeratedNov 7, 2010 9:14 AM (in response to mightyjlr)To restate your issues and your question and your concern, you're frustrated, you're using a WiFi connection, you're not attempting remote access, it's not working for some protocols, and you're receiving unspecified error message(s).
Start by posting the diagnostics and messages received when this "doesn't work".
Then reconfigure the network, and (for testing) specifically move the screen sharing client box onto (and add one if needed) the same network switch as the server. Remove the WiFi device (a router) from the network connection. (Unmanaged gigabit network switches are cheap, too.)
In addition to and in parallel with reconfiguring the network (for testing), also confirm that all of the network port connections on the WiFi are established on the correct physical ports, if you're using that device as a network gateway and NAT device in addition to using it as a router.
Also ensure the firmware on the WiFi device is current.
Drop the firewall on the client.
Given you're probably on a NAT-based network and (guessing) using the WiFi device is configured as a gateway, post up some DNS or mDNS information, and a forward and reverse dig of the IP address. (I haven't seen issues such as this with local screen sharing via the Apple tools, but other Apple tools are known to be sensitive to incorrect DNS configurations.) From the same client you're attempting the screen-sharing:
dig -x your.target.ip.address.
Currently Being ModeratedNov 7, 2010 10:24 AM (in response to MrHoffman)There arent really any messages received when it doesn't work, it just doesn't proceed past the "Contacting Mac Mini Server" or "Contacting 192.168.0.190" dialog that pops up. As for the rest of your post, every VNC client works fine other than OSX's built in Screen Sharing, so I don't think there are any communication problems with the server.Mac, Mac OS X (10.5.6)
Currently Being ModeratedNov 24, 2010 12:41 AM (in response to mightyjlr)Check for any antivirus software that may be blocking access to your Mini. I was running VirusBarrier and for some reason it detected a 'Connection Flood/Port Scan' from the computer I was trying to screen share with and blocked the IP address within my own network. I made it a trusted IP within VirusBarrier and all is good.iMac, Mac OS X (10.6.5)
Currently Being ModeratedJan 2, 2011 8:02 AM (in response to mightyjlr)I'm having this same issue. . .it worked fine yesterday afternoon but now it doesn't. I can access the Mac Mini using VNC Lite from my iPad, but can't get screen sharing to work from my Mac Pro.Mac Mini, Mac OS X (10.5.8)
Currently Being ModeratedJan 2, 2011 8:29 AM (in response to Catastrofe)Might there be anything relevant visible within the logs available from Console.app when the connection fails?
Any recent changes to network settings, or differences in where you're connecting from or to?
What is your network configuration between your client and your server?
Is there one or two NAT gateways involved?
Are the ever-problematic 192.168.0.0/24 or 192.168.1.0/24 subnets involved in the network connections anywhere, either local to the client or at the target for screen sharing?
Currently Being ModeratedJan 3, 2011 11:40 PM (in response to MrHoffman)I hope you won't see this as a hijack, but I think I'm seeing the exact same issue.
I have the built-in vncserver from ubuntu running on machine 192.168.1.103 on my network.
My mac is 192.168.1.109. I see the vnc share available in the finder window. When I select it and click on "share screen", then I get a window that pops up and says "contacting jeffw's remote desktop on 192.168.1.103". That window will just sit there forever.
If I go look at the screen for the ubuntu server 192.168.1.103, and check the status that shows what clients are connected to the screen, it thinks there is a connection from ::ffff:192.168.1.109. I don't know where the ::ffff: is coming from or what it means, but my ubuntu box thinks there is a client connected.
I don't get any relevant messages in the console window while the client is "contacting". With the exact same config, I can connect with "chicken of the vnc" with no problems, so it does not appear to be a network connectivity issue.Mac Pro, Mac OS X (10.6.5)
Currently Being ModeratedJan 8, 2011 5:22 PM (in response to jeffwight)Jeff (and others)
::ffff:192.168.1.109 is an IPv6 address. I have seen this kind of issue before , while not DIRECTLY an issue with Screen Sharing, but a generic, cannot do 'that' even though EVERYTHING else looks fine. Most notably my issue was iTunes across an Airport WDS to any of my aTV's or even administering the Airport devices themselves.
The issue I found is within IPv6. It seems to be just not that well implemented, or some other issues are causing it to behave non-optimally and for all intents it is acting like it is the only protocol and is not configured or not configured well. So that is what I did, I turned off IPv6 on EVERY device I have (more then a few, I can tell you this) and I have had ZERO issue with administration of any device; screen sharing, FTP, ssh, VPN, it all 'just works' now.
Give that a try. It could be enough to turn it off on your 'local' client as the remote machine should then only respond with a same-kind (IPv4) packet.
BTW: this post is not an attack on the OS. The industry as a whole (and even Apple) are starting to realize that IPv6 is VERY powerful and is making it harder to get IPv6 in wide-spread use. Look at the IPv6 changes made to 10.6.6 for a perfect example.MacMini Server, Mac OS X (10.6.6), Server - 8Gb RAM - 6.6TB HD - _EVERY_ port in use '-)
Currently Being ModeratedFeb 5, 2011 6:46 PM (in response to mightyjlr)I'm having the same problem. I can connect with Chicken of the VNC but not with the built in VNC. All i get is contacting xxx.xxx.xxx.xxx
Currently Being ModeratedFeb 6, 2011 3:40 AM (in response to mightyjlr)If having the ALF on:
A broken "signed application signature" for ARD can prevent remote access to another machine from the machine running the ALF and ARD.
Don't know if Screen Sharing is affected.
"A hint on another forum told me to check the validity of ARDAgent.app by running the following.
codesign -vvv /System/Library/CoreServices/RemoteManagement/ARDAgent.app
it returned "code or signature modified""
Currently Being ModeratedFeb 24, 2011 3:31 AM (in response to mightyjlr)Same problem. I can connect to one of our networked Macs with Chicken of the VNC, and I can even use Screen Sharing on that Mac to connect back to my Mac ... but none of our Macs can connect to it using Screen Sharing. Console shows this message on the Mac that is trying to connect:
24/02/2011 11:25:23 Screen Sharing * -[NSLock unlock]: lock (<NSLock: 0x10b01a930> '(null)') unlocked from thread which did not lock it
The 'Connecting to ...' dialog just sits there with its progress bar. I can click Cancel, but no connection. I've tried setting up a User account on the Mac (to match mine). I've tried every option in the Sharing prefs pane – on both Macs - but have drawn a complete blank. I can't even find a route to troubleshoot the issue: is there anybody out there who can help?!All of 'em, Mac OS X (10.6.6)