Screen Sharing and finder

Just bought an Apple Time Capsule a fortnight ago.
Previously I was able to see local computers and conduct screen sharing through finder with no problems with my old wireless setup.
Having problems do so now. I have reinstalled 10.5.6 on my main mac but all the details and shares are standard and setup on the other.
I am able to screen sharing if I do it by ip but it is a mess around and not as easy as before.
Am I missing a setup item/process in Time Capsule?
Cheers.

Hi amthflea
I have a very similar setup.
I VNC to my other computers using JollyFast VNC (free and open software) - very very very fast and a lot better than the built in one. Very easy to use. You need to input the ip once, that's it, then it saves an easy list of your computers.
http://www.jinx.de/JollysFastVNC.html
I don't know about the sharing though. The devices i VNC to Are PPC-models and it pops up fine in finder.
In sharing
Personal File Sharing
Apple Remote Desktop and Printer Sharing are enabled.

Similar Messages

Screen sharing and login

I've got a mini running Leopard and a MBP running Snow Leopard. I'm trying to use screen sharing in finder to connect to the mini from the MBP. There seems to be something preventing screen sharing whenever a user is logged in to the mini, even if the login occurs in screen sharing.
Here are some examples of the behavior:
If I'm logged in as "macuser1" on the mini, I can connect to the mini as "macuser1" or "macuser2" and see folders, etc in Finder, but, when I click the share screen button, I get a connection failed message.
If I go to the mini and logout, then go to the MBP and connect to the mini as "macuser1" I can see folders just fine. When I click share screen it connects just fine and I see the login screen on the mini. If I enter a username and password it logs in just fine (I can see it logged in on the mini), but screen sharing from the MBP says "reconnecting" and can't connect anymore.
Something about being logged in on the mini prevents me from sharing its screen.
I tried creating a new user account without success. I could log into the new account, but as I was logging it, I got the "reconnecting" screen on the MBP (but could see that the login worked on the mini).
I've got all the right users in the screen sharing part of sharing settings.
Any ideas?

have you tried the obvious - restarting the computers involved and the router?

Screen sharing and yosemite

I have 2 iMacs running 10.10.1 not on the same LAN. Under Mavericks both screen sharing and file sharing worked fine on both computers
Since the upgrade to yosemite, i can access file and screen sharing on one computer but only file sharing on the other.
Both computers have back to my mac activated. Since screen sharing works fine on one computer, I must assume a setting somewhere is incorrect
Thanks
Jeff

Screensharing doesn't require a 'bonjour advertisement'. The advertisement causes other Macs to add it to the sidebar - but that is just to help cut out manual config.
You could try working out the IP address of the Mac see if Screensharing works that way. Find that in Network Prefernces for the interface that is on the same local network.
Insert the following into Safari…
vnc://YOUR-IP-OF-REMOTE-MAC
That will open the Screensharing app (which is buried in the System folder) and attempt to open the IP of the machine in question. If that works you know sharing is OK but mDNS a.k.a bonjour is failing somewhere. If that fails double check the local IP & retest. It indicates screensharing itself is failing etc.
You can also try the computer names like 'Macbook.local' instead of the IP address.

Screen sharing and file sharing not working on LAN

This is not a Mavericks specific problem since it existed before I upgraded to Mavericks. I have a LAN that consists of 3 MBPs and 1 MacPro.
Local screen sharing and file sharing works fine on all of these computers except for one MBP. From this MBP I am able to connect to all of the other computers for screen sharing and file sharing. But I can't connect to this particular MBP for screen sharing or file sharing from any of the other Macs.
This MBP shows up in the left hand side column under "Shared" on all the other computers. But I am unable to make a connection from any computer to the problematic MBP. I get the message, "There was a problem connecting to the server "xxxxxxxx". The server may not exist or is unavailable at this time".
I have tried toggling off and on screen sharing and file sharing with no effect. One probably pertinent strange thing that I notice is that under the Screen Sharing set up the green button next to "Screen Sharing:On" is green. But the message under it states:
"Other users can access your computer's screen
at vnc://johnmacbookproretina/ or by looking for “John MacBook Pro” in the Finder sidebar."
The problem is that my computer name is "John MacBook Pro" and the LocalHostName is "JohnMBPr.local". I believe that at some point in the past the computer name and/or LocalHostName was "johnmacbookproretina".
Similiarly, under File Sharing I am informed:
"Other users can access shared folders on this computer, and administrators all volumes, at “afp://johnmacbookproretina” or “smb://johnmacbookproretina”."
I would appreciate any help I could get to resolve this perplexing issue. Thanks.
John

I've finally been able to solve my own problem.
File sharing and screen sharing on the problematic MBP was being blocked by firewall rules that had been set up several weeks ago when I had installed a trial version of DoorStop X firewall software. I had previously trashed the app when the 30 day trial ended. I did not realize that the software had left a set of firewall rules in the Library/StartupItems folder. Among other things, the rules were set to deny access to the computer on the ports used for file sharing and screen sharing. Once I trashed the DoorStopStartup folder in the StartUpItems folder all the connection problems resolved with a computer restart.

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 and ARD broken

Hi,
I have 10.9.4. I had remote management switched on and it was working fine.
I installed ARD 3.7 and started it up fine and it was running fine allowing me to do all what I needed.
I also need to remote to this Mac and so set the preference in ARD to allow control whilst the app was running. Thats when it went pear shaped.
It suddenly stopped allowing remote access to the machine.
I now have to be physically at the unit. I have removed ARD and all the files it has added and switched off all screen sharing and Remote Management in Sys Pref. Restarted and switched on Remote Management again.
I can still not access the machine remotely (i.e. screen sharing).
When trying to use screen sharing on the Mac itself to remote onto another machine I get the following in Console.
20/08/2014 15:08:23.459 Screen Sharing[1422]: unable to get server port
20/08/2014 15:08:23.459 Screen Sharing[1422]: *** -[__NSSetM addObject:]: object cannot be nil
20/08/2014 15:08:23.537 Screen Sharing[1422]: (
0   CoreFoundation                      0x00007fff93cd525c __exceptionPreprocess + 172
1   libobjc.A.dylib                     0x00007fff94276e75 objc_exception_throw + 43
2   CoreFoundation                      0x00007fff93bf4966 -[__NSSetM addObject:] + 790
3   ScreenSharing                       0x00007fff91f3a0e2 -[SSInputEventSourceCoordinator addSource:] + 69
4   CoreFoundation                      0x00007fff93ca3e0c __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 12
5   CoreFoundation                      0x00007fff93b9782d _CFXNotificationPost + 2893
6   Foundation                          0x00007fff905277ba -[NSNotificationCenter postNotificationName:object:userInfo:] + 68
7   AppKit                              0x00007fff96fb1cde -[NSApplication finishLaunching] + 440
8   AppKit                              0x00007fff96fb17f3 -[NSApplication run] + 128
9   AppKit                              0x00007fff96f9c783 NSApplicationMain + 940
10 libdyld.dylib                       0x00007fff8f5b55fd start + 1
20/08/2014 15:08:23.622 Screen Sharing[1422]: *** -[NSLock lock]: deadlock (<NSLock: 0x6000000ca330> '(null)')
20/08/2014 15:08:23.622 Screen Sharing[1422]: *** Break on _NSLockError() to debug.
I can ssh to the machine fine, just not screen share (VNC).
Any help to fix allowing VNC to the machine would be greatly appreciated.
Regards
Keith

Further,
I have run a port scan and confirmed that port 5900 is open.
When using COTVNC it sort of sits there trying to connect but doesn't show the screen. If whilst it is trying I switch off Remote Management then COTVNC instantly throws up the error that screen sharing is not enabled.
Thus I am deducing that the actual VNC server of the os is goosed.

Screen Sharing and WindowServer processes using 35-45% of CPU!!

I have recently relocated and reconfigured my Apple network and computers in the house :1) MacBook Air dual display MBA with 20" cinema screen in the office, and 2) and Mac Mini connected to a large LCD TV in the living room.
The plan now is to use the MBA as a primary computer and connect via wireless screen sharing to the MM so that I can monitor that system, run more intensive apps, watch EyeTV, file server tasks, etc.
But now this has increased CPU and fan activity on the MBA beyond what I would expect. The activity monitor indicates that the Screen Sharing and WindowServer processes are using combined between 35-45% of the CPU (screen share process is a constant 25%!!).
This is not good, and I wonder if it will be fixed in a future release. Any ideas or suggestions on how to limit the impact of screen sharing on CPU?

It seems to be running better with system update, and use of a faster computer (now using the higher end mac book air)

Screen Sharing and VPN functionality with ARD

Can somebody with ARD tell me if the following setup is going to work? There's no demo version so I can't tell if it's going to be worth 300 dollars.
I have a number of local machines in a network and a couple external machines in other parts of the state that VPN in to the network. I want to be able to have a local machine that can screen share w/ voice reliably with these guys.
"Reliably" being the key. iChat screen sharing and VNC alternatives do not work reliably at all. They crash, they are slow, they sometimes disconnect video and keep the audio. Or some days they work perfectly, but that's few and far between. Zero-conf services like MacHelpMate work just fine, but I'm reluctant to pay 600 a year for something like this.
Is ARD going to be able to be able to fix this problem for me, or am I really just going to end up with more of the same issues?

ARD uses VNC for observation and control, so if you're having problems with iChat screen sharing and with VNC clients, I would not expect that ARD would be any better. My suspicion is that your network and/or VPN are cutting things off, since most people have found iChat sharing and VNC to be pretty reliable, but without being able to perform reliability tests on your network to VPN clients, I can't say for sure.

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?

Screen Sharing and video chats don't work

I've been searching this forum for awhile and I haven't found a concrete answer to my problem, so if this question has been answered please excuse me. Ok, So here's my situation am running iChat on Mac OS 10.5.1. Whenever I am using my laptop at my school on the network their, I am able to use both screen sharing and video chat. But when I am at home, I am unable to use either one. It begins to try to start the session, but then i receive a message that tells me that a connection could not be established. I know that I have internet access, but I don't know what could be wrong with it.

After investing far to long in looking at this exact issue on my end, reading the seemingly endless threads on the exact same error, trying all the various tweeks and QT settings, bandwidth limit settings, etc etc. proposed here, I have now solved this problem, and the none of the above were part of the solution.
I have perhaps one of the the most common routers on the market, Linksys WRT54GL.
In a totally unrelated network problem (a printing issue), Linksys tech support advised me to reset my router. There is a small button on the bottom. I depressed it for 30 seconds. Rebooted everything and my printer miraculously worked. Yea, I had to reenter my WAP passkey, router admin password etc., but that took 2 secs. So, what does this have to do with iChat?.... The very next time I tried iChat video and turned on and enabled my camera, the recipient immedialty saw me. No connection error.
Problem solved, for me art least. Not sure if anyone has tried this, but makes sooooo much more sense than the other unApple like suggestions I previous tried. Hope this helps.

Screen sharing and remote management no longer working after some uptime

Server is withoiut monitor.
Users need to login via screen sharing from time to time.
"Enable screen sharing and remote management" is ticked in Server.app everything is working fine (for days, weeks).
ARD reports "Screen Sharing Available", so remote management is not running how it should.
Screen Sharing.app is "Connecting…" forever.
Kickstarting ARD (http://support.apple.com/kb/HT2370) does not help.
Restart fixes it.
Is there a workaround (over ssh) or a fix?

seduc wrote:
Do you know if
fdesetup authrestart
works then too?
Off-hand, no. I don't. See this posting, or as would be typical in any case, try it?

Screen sharing and ARD windows to other computers are invisible!

Hi
I have been using screen sharing and or ARD with no problem, for some odd reason today when i went to control a iMac in my network, the window opens but is not there, like i hit command W and i noticed it closed windows on the iMac i can not see the screen at all.
Please advise

ahhh, thanks you did it!
forgot to restart after system update!
cheers

Screen Sharing and Remote Login suddenly stopped working

I have had Screen Sharing and Remote Login turned on on my iMac for several weeks and they have been working fine up until now. I have been accessing the computer via VNC programs and command-line ssh logins from other computers on the same local network. When I tried to connect today, i was given the following error message.
ssh: connect to host xxx.xxx.xxx.xxx port 22: No route to host
I have all of the required settings turned on in System preferences and there are no firewalls or router settings blocking it. I connected the two computers together via ethernet cable and the error message still occurred.
I can ssh from the machine to 127.0.0.1, so the ssh server is running. I can ssh to other locations from the laptop i am attempting to connect with, so that's not the problem either. I just spent an hour on the phone with the apple tech support line and they couldn't figure anything out either. Can anybody figure something out?

have you tried the obvious - restarting the computers involved and the router?

Screen Sharing and Remote Management

Is there a way in 10.6 to make both Screen Sharing and Remote Management run at the same time?
In the past (10.5), you could convince Mac OS to run both Screen Sharing and Remote Management to run simultaneously. I say "convince" because you could not enable them both through System Preferences. You could turn one on, then use Terminal to enable the other. This worked great for me, because I needed remote management for the machines I managed, and the users need screen sharing to work from home.
However, the work-around for 10.5 no longer seems to work for 10.6. Has any one gotten this to work yet for 10.6? Thanks!

I figured this out. First enable Remote Management via System Preferences. Then create /private/etc/ScreenSharing.launchd with 'enabled' as it's contents.

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.

Screen Sharing and finder

Similar Messages

Maybe you are looking for