10.6.8 MBPro Screen Sharing suddenly can not connect to our other Macs.

We've used Screen Sharing from our MBPros for the past few years to manage our Mac file & media servers. Last year we replaced our G5 file server with a Mac Mini with Lion server. No problems - we could still use Screen Sharing to manage both this Lion file server and the Snow Leopard MacPro that's hooked up to our TV (among other things).
Friday morning my MBP could not see or connect to the Lion file server - the MBPs have the Lion server's data drives in Login Items so they mount when we log in. I also cound not Screen Share to either the Lion server or the SL MacPro. I checked the MBP's ethernet connection and could get to our router and the internet. When I tried to connect via Screen Sharing (by using the Share Screen... button in a Finder window, by using the Connect to Server command with vnc:// protocol, or by using the ScreenSharing menulet) I would get the "Connecting to Lion server" alert but nothing further. I left it for 10 minutes or so and it eventually disappeared but the connection never opened.
I checked the two servers and both were up and running. From the SL MacPro I could use Screen Sharing to get to the Lion server - and my MBPro too. From the Lion server I could Screen Share to the MacPro and my MBPro also.
The problem appeared to be with my MBPro. I switched to an unprivledged user account on it and found I could then get to both servers using Screen Sharing. So it was just my account on the MBPro. Rebooting did not help. Turning on AirPort, connecting to our home AirPort Extreme and unplugging the ethernet cable did not change anything with my account connecting to the servers.
I figured something somehow got pranged in my account's credentials. I used Keychain Access to delete all keychains containing the servers' names, IP addresses or sharing. I was asked for my credentials when I mounted the server's shared drives, but not when I tried Screen Sharing - got the same "Connecting to Lion server" or "Connecting to media server" dialogues and was never asked for username or password, but never connected either.
I cleared all caches using the utility Maintenance in case my MBPro was using invalid cached info. No improvement.
Saturday morning I shut down everything on our entire network - FiOS "modem"/router, Netgear gigabit switch, AirPort Snow, AirPort Extreme, MacPro, MacMini, both MacBookPros... even the FiOS cable box. Still no improvement.
IPv6 is disabled on the Lion server. All the Macs have all curent updates applied.
I've spent most of today Googling for solutions and trying them out. None have worked - though I see several very recent reports in these Apple Communities about Screen Sharing suddenly not working.
I really do not want to have to move to a new account on my MBP - and what's to say it won't happen again? Anyone have other suggestions?

sunnovagun!
Hitting the Log Out button in the MobileMe panel worked. I can now connect to both the SnowLeopard and Lion servers just like I used to.
My condition appears to have been slightly different from yours, gmia - the MobileMe on my MBP had the correct info, but hose are not the credentials i use to remote to the two servers. I'm guessing that for some reason ScreenSharing began using my MobileMe credentials instead of what I had saved in the keychains.
Wonder if it had anything to do with the shutdown of the MM servers. That would be odd as using ones apple ID to log into a Mac remotely was new with Lion, and I had the same problem with our SnowLeopard server - which I remote into much more frequently.
Probably didn't hurt though to reboot the entire network...

Similar Messages

Can not connect to one other mac in in-house Ethernet network 10.9.2

I have a small inhouse ethernet network with 3 Macs
All mac´s are running under 10.9.2
On my main mac I see both other macs as approved. When I select the first mac, put in my user ID and password I can connect.
The other mac will not connect; "connection failed" and I see on the console:
27.02.14 15:13:38,186 NetAuthSysAgent[243]: RPC to srvsrvc gave error 0x16c9a042
27.02.14 15:13:38,187 sharingd[212]: SDSharePointBrowser::handleEnumerateCallBack returned -6600
Up to today both connection were working fine; but today I updated to 10.9.2 - but I am not sure if that coused the problem.
Has one any suggestion?
Thanks
Hans

In the meantime I have reinstalled OSX 10.9.2; repaired permisions - no effect.
The settings on both other macs are the same.
No suggestions????

Suddenly can not connect to our Acitive Directory server.

ColdFusion code that was running fine this last Friday, for nearly two
years before then, is suddenly throwing this error today "Connection to
LDAP server failed". The Active Directory is up and responding to pings
and all normal windows logons are being preformed properly. But neither
ColdFusion nor my Softerra LDAP Browser can make a connection with
multiple user names.
Can anybody provide a short list of what could have been changed that
would of started this problem?

The server was not responding to anything, accept pings, as best as we could tell.
Since this was affecting production applications, preventing empoyees from duing their work, the box was booted. The sys admin had to physically walk up to the server room as he could not even remote into the system.
I am now told that there are three active directory servers sharing the load in our organization. I'm guessing it is possible that the windows login operations where failing over to another of the trio. But that the CFML code, that is hard coded to a specific one of the AD servers, could not do this.
If this is a common set up, I have to research the details more, is there some way to tell ColdFusion to make to a connection to any of the three AD servers, whichever one is availaible. Or do I need to create my own fail over code using try-catch blocks, or some other exception handling choice. Basically code it to try server A, if that does not work, try server B, if still a problem try server C.
That later is not hard code to visualize, but it seems to be very dependant on the exact network configuration. Whereas, if there was some way to query all the available AD servers as a clustor, then I presume the network folks could swap servers into and out of the clustor without really affecting our code. That would by my hope anyway.

HT4628 some times my internet connection will say it has timed out and I can not connect. but my friends mac never has a problem. How can I fix this?

some times my internet connection will say it has timed out and I can not connect. but my friends mac never has a problem. How can I fix this?

Just confirming, when you have the trouble, the wifi icon is grayed-out or has all bars showing? I believe you are saying that is is grayed-out - not connected to your wireless router.
I have a Mini that started to lose connection to the Internet after the 10.7.3 update but still showed the wireless as connected. If I pinged the wireless router, I would get a quarter of the packets failing to return. The router was a Netgear that supported 802.11N connections. As a test, I set it to 802.11G (54MBps) maximum and the Mini worked fine for a week - no dropouts. And for the other devices that did support 802.11N, while there was a noticeable delay with downloads and pages loading, they still worked.
As another test, I changed the Netgear router to a Billion 802.11N model and the Mini has not had a problems since. (It is still using 802.11g). So it could be your router that is causing trouble for your Mac.
Have a look at some of the More Like This postings in the right column. There has been a number of Mac owners experiencing wifi connection issues and some very good suggestions as to how to resolve their issue.

My airport network will not connect to to the internet via my modem. My host computer is a hp running windows xp. I have had great connection for 3 years. Then suddenly can not connect. Please can you assist

My airport will not connect to the internet via my modem. Worked for 3 years. Suddenly stopped. Main host computer is hp running windows xp.
When trying to connect windows states connection was cancelled. I have had hp checked by compputer repair and still have same problem?

The router is much, much newer than the computer, perhaps some characteristic of the WiFi network as it's currently setup is preventing the computer from connecting.
Try to go back to the basics: set your WiFi network to "b" mode only (i.e., turn off "g") and termporarily remove the password from it. See if the computer will at least establish a connection at that point. Then start turning on one thing at a time ("g" mode, then security, etc).
Not sure what format your WEP key is, but if it's not 10 characters (the minimum for the standard, which constitutes a 64-bit key), you can try making it that long. If it's 13 or 26 characters, it might be a higher encryption than the computer can support.
If all else fails, you could try looking on ebay/craigslist for a copy of Tiger to install on the iMac, which would have software support for more WiFi encryption schemes. Also, it would provide software support for USB WiFi adapters that would also be able to connect to more modern networks.

Can not connect to google on Mac mini or iPad, says Ido not have a certificate. This problem started after installing latest operating system

Cannot Connect to google on iPad or Mac. Mini says I do not have a certificate. What is the problem and how can I fix it.

I have Maverick on my iMac and haven't noticed any connection or any other issues. Also, that won't have any affect on your mobile devices.
Most likely an issue with your router or isp.
Try rebooting your modem and router (if applicable) by unplugging it for 5-10min.
At the same time, reboot mac and both/all mobile devices by pressing and holding both the home and sleep/wake buttons at the same time until the apple logo appears on the screen.

Airport can not be activated. Other mac computers in home all function properly using my apple router.

How can I get airport activated?
Software Versions:
Menu Extra:          6.2.2 (622.2)
configd plug-in:          6.2.5 (625.6)
System Profiler:          6.0.1 (601.1)
Network Preference:          6.2.2 (622.2)
AirPort Utility:          5.5.3 (553.20)
IO80211 Family:          3.2 (320.1)
Interfaces:
en1:
Card Type:          AirPort Extreme (0x14E4, 0x8C)
Firmware Version:          Broadcom BCM43xx 1.0 (5.10.131.42.4)
Locale:          FCC
Country Code:          X0
Supported PHY Modes:          802.11 a/b/g/n
Supported Channels:          1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 36, 40, 44, 48, 52, 56, 60, 64, 100, 104, 108, 112, 116, 120, 124, 128, 132, 136, 140, 149, 153, 157, 161, 165
Wake On Wireless:          Supported
Status:          Off     I check it ON in airport utility and Nothing happens, airport stays OFF
My other mac computers in home still have wireless contact with my network.

You do realize you don't turn on Airport on your MacBook Pro with Airport Utility??? You actually turn it on on the menu bar. There should be an icon that looks like a V with a semicircle on top. Click on that, and turn WiFi on. Or you can go into System Preferences>Network, click on Wi-Fi on the left hand side, then turn on Wi-Fi.

Drive 2.1 can not connect to our cs3 versioncue server what do I need to use our projects in CS5?

Mac XServe is our CS3 server. Trying to upgrade to CS5 and found out Version Cue is no longer. Read and found the Drive 2.0. It can't seem to connect to my current server. We still have access with one of our CS3 machines. Is there a program I need to get to continue on with our versioning and the ability to use our projects we have? Or do I need to go into every project and export or something to be able to start using CS5? Thank you in advance for any help!!!

sunnovagun!
Hitting the Log Out button in the MobileMe panel worked. I can now connect to both the SnowLeopard and Lion servers just like I used to.
My condition appears to have been slightly different from yours, gmia - the MobileMe on my MBP had the correct info, but hose are not the credentials i use to remote to the two servers. I'm guessing that for some reason ScreenSharing began using my MobileMe credentials instead of what I had saved in the keychains.
Wonder if it had anything to do with the shutdown of the MM servers. That would be odd as using ones apple ID to log into a Mac remotely was new with Lion, and I had the same problem with our SnowLeopard server - which I remote into much more frequently.
Probably didn't hurt though to reboot the entire network...

Computer Suddenly can not connect to server

I have a problem specific only to my Macbook that no one can seem to figure out and I really need help!
I have my own site that I'm working on and my Mac is just completely blocking it for some reason. Here's the situation:
I can access my site on any browser on any computer (in this house on the same wifi network) except from my computer. I can access my site through any FTP client on any computer in this house or anywhere, except through my computer. So on my computer, every browser says "cannot connect to server" (or some version to that effect). Every FTP client does the same exact thing on my computer alone.
So I guess I've narrowed down the problem that somehow locally on my computer, my mac is completely rejecting that server and/or that address for some reason! I have no issue with any other site on my computer or anything!
I've emptied cache(s) repeatedly, I've tried to ping other sites and I get good feedback, but when I ping my site, I get nothing. I've looked through other forums for help and found nothing! Nobody from Godaddy, charter, or apple support seems to have an answer for this! But I'm certain that this is a Mac issue, not an internet issue!
about 4 days ago, I had my site forwarding to another site and up to that point, I had no issue with any ftp client, or any browsers accessing it! In the midst of changing everything, somehow something changed on my computer to reject access to that server!
If anyone can help me, that would be GREATLY appreciated! I'm about to pull my hair out! thanks for any help!
Blake Weber

Perhaps your problem is with DNS. Try setting your DNS to OpenDNS by going to 'System Preferences'>'Network'>'Advanced'
Click on the DNS tab and remove your existing DNS servers.
Replace them with 208.67.222.222 and 208.67.220.220.
While you are at it, verify that your mac isn't connecting through a proxy.
Once you do that go to 'Finder' and click on 'Go'>'Connect to Server'
type in the server address in the following format "ftp://foo.com"
Click on Connect.

IMac 10.7 can not connect to an old Mac with Os 9 classic

Hi, hope somebody can help me with this issue
My company bought a brand new IMac 10.7 Osx an I need to make a conection from this machine to an old G3 with Mac Os 9 classic system where all my files are stored and even my Rip software resides.
When I try to make the conection a message appears telling me ¨the system is not supported¨ or something like that, so what can I do? Any way to make the conection?
No, no way to take my old Mac to the trash, my rip software only works on Classic 9 system...
Thanks in advance for any help

Connecting via IP versus system name will not solve the problem, nor will me "finding a newer solution" - I already have a Mac OS 10.7 system and as of today, there is NOTHING newer (that will change possibly in the up-coming week). I may look at the "work--round" again though. I checked the link but did not understand it on my first pass. It appeared to be a modification process executed on the 10.7 system to enable some "old and insecure behavior".
The 10.5 based tower I have does not provide built-in hardware support for the IDE disks either, so I cannot just move them to it. Booting the old system in target mode means physically relocating it into the immediate proximitiy of the 10.7 system, or vice versa AND it does not provide access to all of the hard disks installed. It only provides access to the boot disk in many cases. Not to mention, such relocation is not always convienient for the period of time necessary to move the files and then check the integrity to the relocated versions. I may however attempt to install an NFS server if I can still find one and connect that way.
There is something wrong with the system hardware too. It will not boot into 10.x from an external drive or from the DVD. When all memory modules are installed, the system indicates a memory test errorr, and it does NOT move when the order of modules is changed. Therefore I cannot install a more recent version of the OS and attempt to get the disks seen over the network that way.
Message was edited by: Daniel O\'Leary to add additional information on things I have tried but yielded unsuccessful results.

HT4623 How come I can not use WIFI to update the new IOS in my iPhone 5 ? the screen pop up " you no longer connection to Internet " . And I won't be able to download any Apps using Wifi, the screen popup " can not connect to iTunes stores " ..

I can not use Wifi at home to download Apps . The screen pop up " can not connect to iTunes Store " ?? I am using iPhone 5 . I used to be able to download any Apps before .
I can not even download the new IOS which Apples sent to my phone to update . ???? Please help !!!
My husband is using IPhone 5 and his phone is fine , he can use WIFI to download any apps or update any software from apple . Does that mean my phone have problem , not my WIFI right ???
Now, I have to use my data plan to download any Apps which waste my money :( Thanks a lot !!

Hello phonphon,
We've got an article that can help restore your phone's connection to the iTunes Store while on your WiFi network.
Can't connect to the iTunes Store
http://support.apple.com/kb/TS1368
Cheers,
Allen

I can not connect to iCloud from safari

I suddenly can not connect to iCloud.com from safari. I have no issues with chrome, firefox etc. Is there a setting that is blocking this site?

Hi ..
Might be a cookies, cache, or extensions issue.
From your Safari menu bar click Safari > Preferences then select the Privacy tab.
Click: Remove All Website Data
Then delete the cache.
Open a Finder window. From the Finder menu bar click Go > Go to Folder
Type or copy paste the following
~/Library/Caches/com.apple.Safari/Cache.db
Click Go then move the Cache.db file to the Trash.
Quit and relaunch Safari to test.
If that doesn't help, troubleshoot Safari extensions.
From the Safari menu bar click Safari > Preferences then select the Extensions tab. Turn that OFF, quit and relaunch Safari to test.
If that helped, turn one extension on then quit and relaunch Safari to test until you find the incompatible extension then click uninstall.

Display is not working But Through Screen Sharing I can Access my computer

Ok. After turning my computer off and then turning it back on a couple hours later the screen would not turn on. Im still able to log in. With screen Sharing I can acces my computer and system profiler shows that my RAM cards are OK. However when I click on Graphics/Display it unexpectedly quits.
What could the problem be? Any help is greatly appreciated : )
Ps. I wrote this through screen sharing out of my account on the display-less computer.

Welcome to Apple Discussions!
I wonder if you could have the NVIDIA chip problem?
http://support.apple.com/kb/TS2377
Is the display totally dead, or can you see your desktop if you shine a strong light through the apple on the back of the display? If so, you may have a different issue with just the internal display. A good test would be to see what happens with an external display connected directly to the MBP.
Good luck!

"Disconnected from Screen Sharing because: Can't get video from the Camera"

Whenever I try to do Screen Sharing with another Mac (with Leopard), I get this warning:
"Disconnected from Screen Sharing because: Can't get video from the Camera"
It doesn't seem to affect video chats, which I can do just fine.

It's an AirPort Express, but the problem doesn't seem to be unique to the router. I tried it in another location with another router and it still didn't work.

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

10.6.8 MBPro Screen Sharing suddenly can not connect to our other Macs.

Similar Messages

Maybe you are looking for