File Sharing, Screen Sharing keeps disappearing

I have one machine out of five in my studio, all running 10.10 that keeps having problems staying visible for File Sharing, Screen Sharing, Printer Sharing, and I suppose any other Bonjour service. It's unpredictable, but every couple days I need to go into the Sharing Preference Pane and uncheck/recheck each service. Just this one machine.
Anybody else seeing this?

how are you connecting to the machine? is it a specific pice of software? have you tried a different method?
Are you connecting via bonjour? try IP instead.

Similar Messages

Screen sharing: screen refresh keeps pausing but cursor always moves

Hi,
I am screen sharing between two iMacs running the latest Leopard.
Ports have been opened according to the Apple KB. Quicktime bandwidth is set to LAN (both ends have high-speed internet connections), and iChat bandwidth limit is set to "none".
When I screen share the other person's screen everything works fine apart from this:
Every five seconds or so the screen refresh stops completely (the iMac is still working at the other end as I can hear the other person and he tells me what is on the screen). After about 10 seconds the screen refreshes and everything starts working again. Performance during these times is very good.
The odd thing is that when the screen refresh freezes I can still see the mouse pointer moving, and the person at the other end confirms that the mouse pointer is moving and that if I click a mouse button it performs an action at the other end!
I'm assuming that the screen refresh and the mouse handling are actually two seperate functions, and that the problem is with the screen refresh.
Everything used to work fine. Since the last time it worked fine we have:
- Upgraded to the 10.5.5 Leopard
- Upgraded QuickTime through Software Update
- Replaced one of the cable modems. This modem does not have a firewall, and locally everything works fine.
Can anyone suggest what might be going wrong on the screen refresh side please?
Thanks
Darren.

Set the Quicktime streaming setting, goto sys prefs/quicktime/streaming/streaming speed, set to 1.5mbps
Restart iChat.
Tony

Why do my home screen messages keep disappearing (SMS, missed calls, etc.)?

My messages, all others beside e-mail, because I haven't even set it up, just keep disappearing. I have the home screen theme that shows messages, calendar, call log and applications. The messages section shows me when I have a missed call or a text or anything like that....but for some reason, I go back to my phone and I can't see who has called or texted. The home screen messages section is empty, and if I select it and go to my messages app., there are only 3 listed and 2 are from Blackberry on Apr. 25 and Jul. 30, and only one shows up from my boss on Aug. 5. The only reason I can even imagine that still shows up is because she too has a blackberry. I don't know, but, it's really starting to aggravate the crap out of me. Anyone know how to help?
I've gone to messages General Options and made sure that all calls are sent to messages and the call log.
Oh, yeah! The Call Log doesn't hold anything either. It's ridiculous!
Please help because I like this phone, but, it's not doing its job to the fullest, and that's disappointing.
Solved!
Go to Solution.

this has been asked before and solved.. you have a memory issue.. you need to have at least 12 mb of free space for the phone to operate smothly.. if you havent got one yet get a memory card and move your pics and videos to memory card. along with any downloaded ringtones.. to find out what your file free status is click on options --> status and see what your file free is..another thing that might help is do a battery pull then do above step.. also make sure you dont have any internet programs running in background IE: weatherbug.. cause it continuously downloads data.. clear your browser history by going to an open browser clicking menu then options then cache and clear your history.. there are other steps to help but i cant think of any at the moment..

Screen Sharing, Screen Sharing, Screen Sharing

I've lost the ability to share the screen from my laptop 10.6.8 to my desktop which is running Lion. I had to run the Lion machine off a clone when I ran into an update that I needed to back out of. Since then I have not been able to share into the Lion screen. I've done permissions repair on both machines, checked that sharing was on, rebooted both machines, rebooted the router. I can share the Lion machines disks though, and log in to that machine, manipulate folders, copy documents etc. it's just that I can no longer share the screen.
Any advice?

Hey there Sweejak,
It sounds like the screen sharing funciton is no longer working from the computer with Snow Leopard to one with Lion. I found this article for you to help troubleshoot what is going on here named:
OS X Mountain Lion: If you can’t share computer screens
http://support.apple.com/kb/PH11152
If you’re having problems sharing your screen with another computer, or viewing another computer’s shared screen on your Mac, there are several things to check.
Make sure you turned on screen sharing and set up sharing permissions on the Mac whose screen you want to share.Share your screen
If you’re trying to share the screen of another Mac, open Sharing preferences on that Mac and make sure you’re in the list of users who have been given permission to share its screen.
Make sure neither Mac is in sleep mode. Adjust sleep settings using Energy Saver preferences.
If you’re using Back to My Mac to share screens, make sure it’s turned on on both computers.Share your screen using Back to My Mac
Make sure both computers are connected to the same network, or if you’re sharing screens using Back to My Mac, make sure they’re both connected to the Internet.To check your connection, open the Network pane of System Preferences. Your type of network connection is listed on the left. The indicator next to it should be green.
If there’s a problem with your network connection, use Network Diagnostics to troubleshoot.
Thank you for using Apple Support Communities.
All the very best,
Sterling

File sharing and screen sharing stop working suddenly

I have been using file sharing and screen sharing without any issues between my mac mini (10.7 Lion) and MBA (10.8 ML). However, both suddenly stopped working the other day - that is, I saw the mac mini on my MBA's list of Devices, but when I clicked on a drive or on screen sharing, it just said could not connect. I rebooted the computer and they started working again...but a few hours later suddenly stopped. I toggled those options on/off in the Sharing section of Sys Prefs, and they started working fine again...but then stopped again. It seems no matter what I do, file and screen sharing just stop working after a short period of time after being enabled.
Ideas?

Turns out the problem was that I had a daisey-chained ethernet switch. My mac mini was on an ethernet switch that was not visible to my wireless network. Make sure that your ethernet switch is somehow directly connected to whatever is serving as your DHCP server, then your wireless devices should see it.

Screen sharing across internet

I had set up my Mac for screen sharing with Lion and was able to share the screen to another Mac on the local network, or VNC across the internet. Upgraded to Mountain Lion and screen sharing continued to work both locally and remote.
Moved to Mavericks and now the screen sharing works locally, but will only work for about 30 minutes across the internet. If I reboot the Mac, then I can access the screen across the internet for about 30 minutes, then the connection drops and I would have to reboot the Mac again.
I have screen sharing turned on by:
System Preferences -> Sharing -> Screen Sharing. Clicked on 'Computer Settings...' and checked 'VNC viewers can connect...' and gave it a password.
I can access this remote Mac across the internet using either JollysFastVNC, or the screen sharing app via Finder. Turns out that remote command line and Finder also can access this machine for about 30 minutes, then connection drops.
Has anybody else seen this problem, or have any suggestions on what I can try to keep remote access working for more than 30 minutes?

I don't have a solution (yet). I have the same problem with a Mac Mini remotely. After some short length of time, my ability to control remotely vaporizes. The Mini is running 10.9.1. It seemed to work ok earlier - although the previous version of Mavericks kept screen sharing from working if the firewall was enabled at all. The last system update from Apple fixed that.
But this isn't universal. I can connect with LogMeIn to the Mini after a fresh reboot, but eventually (30 min?) all I get is a black screen. I can connect with LogMeIn to a MacBook Pro on the same remote network as the Mini and it works just fine. I can even connect with LogMeIn to the MacBook Pro and then do screen sharing to the Mini on the same remote network - until that 30 minute? window has elapsed, and then screen sharing fails to connect without even telling me it failed (no black screen, no alert, nothing). Then that doesn't work either. File sharing from that MacBook Pro to the Mini on the same remote network continues to work, and server applications continue running fine on the Mini. For some reason the only problem is that I can't *see* the remote Mini on 10.9.1 for more than a short period after a reboot. All 3 computers involved are running 10.9.1, but only one (the Mini) is failing like this.
It sounds like the problem you are having. If I figure anything else out I'll let you know.

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.

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 / vnc with OS X 10.5.6 fails

I can not get the Screen Sharing that comes with OS X 10.5.6 to work with any vnc client. The server is my laptop, an MBP 2.4 GHz Intel running OS X 10.5.6.
*I enable Screen Sharing by doing the following:*
1) +System Preferences > Sharing > Screen Sharing+ is checked
2) +System Preferences > Sharing > Screen Sharing > Computer Settings > Anyone may request permission to control screen+ is checked
3) +System Preferences > Sharing > Screen Sharing > Computer Settings > VNC viewers may control screen with password+ is checked and I've entered a password
4) I also have Remote Login enabled for SSH access, but no other services are enabled.
*I see two different behaviors depending on one of two clients that I try using:*
1) +Chicken of the VNC v2.0b4+ running on same machine- Always says "Connection Terminated / Authentication Failed" without ever asking for a password. Logs the following in system.log (dates, hostnames and pids removed):
Chicken of the VNC: Server reports Version RFB 003.889
Chicken of the VNC: Bogus RFB Protocol Version Number from AppleRemoteDesktop, switching to protocol 003.007
I believe that the information in system.log is OK, and is just warning me that Chicken of the VNC is working around Apple's strange protocol version.
2) +TightVNC 1.3.9 on Windows XP sp2+- Says "Security type requested", then asks for a password. I enter it, click OK and tightvnc simply waits endlessly.
*Other Notes:*
1) I have tried configuring and starting the server using kickstart from the command line as suggested at http://support.apple.com/kb/HT2370 (+sudo /System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/Resources/k ickstart -activate -configure -access -on -restart -agent -privs -all+)
2) I have tried unchecking +VNC viewers may control screen with password+, but in this case Chicken of the VNC says "Please configure Apple Remote Desktop to allow VNC Viewers to control the screen. Unknown authType 30,31,32" and TightVNC says "Server did not offer supported security type!"
3) If I disable the Screen Sharing feature that comes out of the box with OS X, I CAN install and successfully run the OSXVnc server available at http://sourceforge.net/projects/osxvnc/. In this case, both Chicken of the VNC and TightVNC are able to connect.
*So Apple's Screen Sharing does not work. Does anyone know what the problem is? Are there any log files I can look at, or is there another way I can debug this? I'm not impressed. :)*

Thanks for the suggestion. It was possible that one of these files had become corrupted, so I tried moving each of these files to another directory but unfortunately I'm still seeing the same behavior.
Here's what happens with each of these files individually after they're moved:
1) When I set the VNC password in the system prefs, com.apple.VNCSettings.txt gets re-created (with the same contents as the original unless I change the password, so that just looks like a hash of the password).
2) com.apple.RemoteManagement.plist also gets recreated when I change the system prefs. If I use "sudo plutil -convert xml1 com.apple.RemoteManagement.plist" I get the following:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>ARD_AllLocalUsers</key>
<true/>
<key>ARD_AllLocalUsersPrivs</key>
<integer>2</integer>
<key>ScreenSharingReqPermEnabled</key>
<true/>
<key>VNCLegacyConnectionsEnabled</key>
<true/>
</dict>
</plist>
3) For me, com.apple.RemoteDesktop.plist does not exist.
4) Interestingly, com.apple.ARDAgent.plist does not get created until I run "sudo /System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/Resources/k ickstart -activate -configure -access -on -restart -agent -privs -all". Its XML contents are as follows:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>AdminConnectInfoList</key>
<dict/>
<key>AgentLogLevel</key>
<integer>3</integer>
<key>ServerConnectInfoList</key>
<dict/>
<key>Version</key>
<real>3</real>
</dict>
</plist>
Looking at this, I tried setting ScreenSharingReqPermEnabled to false, but that didn't help. Then I increased AgentLogLevel to 100 and got a lot of output in system.log (12:28:45 is when I restart the server and 12:29:34 is when I try to connect):
Feb 24 12:28:45 ARDAgent [749]: ******ARDAgent Launched******
Feb 24 12:28:45 ARDAgent [749]: got a sessionDict, onConsoleRef is 0xa04cd400
Feb 24 12:28:45 ARDAgent [749]: grUserOnConsole is 1
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 122
Feb 24 12:28:45 ARDAgent [749]: LoadMenuExtra: Attempting to unload menu extra
Feb 24 12:28:45 ARDAgent [749]: PostNotificationForced: Going to send notifation value 9
Feb 24 12:28:45 ARDAgent [749]: UpdatePrefs: versionFlt : 0.000000 kCurrentPrefsVersion : 3.000000
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 44
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 22
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 100
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 94
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 96
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 18
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 106
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 74
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 130
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 60
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 45
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 65
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 66
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 105
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 115
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 38
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 12
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 61
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 20
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 62
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 39
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 30
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 101
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 53
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 103
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 107
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 109
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 135
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 41
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 110
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 111
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 28
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 36
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 48
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 59
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 57
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 116
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 58
Feb 24 12:28:45 ARDAgent [749]: InitAppUsageHandlers: Called gTrackingDays is set to 0
Feb 24 12:28:45 ARDAgent [749]: CheckRFBServerPIDFile: return 679
Feb 24 12:28:45 ARDAgent [749]: RemoteCommandListenerThread init communications
Feb 24 12:28:45 ARDAgent [749]: RFBServerStart - did not kill 679
Feb 24 12:28:45 ARDAgent [749]: DOCStartDOC: No serial number. Task Server not started.
Feb 24 12:28:45 ARDAgent [749]: DT_InitLocalProcessing: Loading existing tasks from disk.
Feb 24 12:28:45 ARDAgent [749]: DT_InitLocalProcessing: Found 0 tasks
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 158
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 117
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 118
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 162
Feb 24 12:28:45 ARDAgent [749]: ARD Agent: RFB Server exited quickly after starting - probable failure.
Feb 24 12:28:45 ARDAgent [749]: PostNotificationForced: Going to send notifation value 6
Feb 24 12:28:45 ARDAgent [749]: PostNotificationForced: Setting lastNotification to value 6
Feb 24 12:28:45 ARDAgent [749]: ******ARDAgent Ready******
Feb 24 12:29:34 Chicken of the VNC[693]: Server reports Version RFB 003.889
Feb 24 12:29:34 Chicken of the VNC[693]: Bogus RFB Protocol Version Number from AppleRemoteDesktop, switching to protocol 003.007
Feb 24 12:29:36 ARDAgent [749]: PostNotificationForced: Going to send notifation value 1
Feb 24 12:29:36 ARDAgent [749]: PostNotificationForced: Got request for kCurrentStateNotification. Sending value 6
Interesting that it says "ARD Agent: RFB Server exited quickly after starting - probable failure." That doesn't sound too good.
I will try to watch fs_usage more closely to see what else gets modified and accessed, but I'm increasingly suspicious that there's simply a bug which is showing up under whatever specific conditions I have on my machine. Perhaps the included log info will trigger an idea for someone.

Screen Sharing debug

I was wondering if there is a log file for screen sharing, or how I can enable debugging?
I am trying to connect using a VNC client, this works on my internal netowrk but I cannot get access from outside despite adding the correct port forwarding rules. I have tested this with a Windows based VNC server on my network so can confirm it is not an issue with the router.
When I connect from outside I get the password prompt, enter tha password, the connection starts to negotiate (momentary blue VNC display) and then the connection drops. Being able to enable logging would probable help me resolve this in a matter of minutes.
I could just install a clean VNC server on the Mac but don't really want to do that seeing as there is already one built-in.
Thanks,

I too am having this problem recently... I switched from Static IPs to DHCP at the house... I noticed it starting then, but we also had a bunch of machines move, and added machines to the network, AND upgraded some machines to newer operating systems... so... I'm having trouble isolating the issue.
I get the EXACT same bug as you! But I also got this:
4/16/10 11:09:48 AM [0x0-0x2f02f].com.apple.ScreenSharing[383] Screen Sharing: OpenScripting.framework - scripting addition "/Library/ScriptingAdditions/Adobe Unit Types.osax" declares no loadable handlers.
So I moved both of those files mentioned above... and it still didn't work...
I am also at a loss.

Screen sharing stopped working after last update

Hello all,
I have run software update yesterday, and there were about 10 downloads (I run this weekely, so these must have been new ones). The thing is that after installing all the updates, one of the features that I use more frequently, screen sharing, stopped working properly. I have a Mac Book Pro and an I Mac, both running on Snow Leopard, and screen sharing has always worked just fine, but not after the latest update.
I checked passwords and they are all right, and also checked sharing properties and all seems to be fine. I can share files all right, but for screen sharing now is only possible by setting the option "anyone may request permission to control screen" (under sharing>screen sharing>computer settings) to on, and ask for authorization each time I need to share screens, not good, mainly if you have the computers in different rooms.
Finally, I own an Me account, so I tried sharing screen via Back to my Mac, but it didn't work either.
Can anyone help?
Thanks a lot,
Luis

Problem solved!
After working with Apple, I have an answer. It looks like the 10.10.2 update changed your firewall settings. Try this:
System Preferences>Security and Privacy>Firewall Options
Scroll down the list till you find "screensharingd". If it's marked as block in coming connections, change it to allow incoming connections.
Be sure to reboot your computer and you should be good to go!

Screen sharing from Mtn Lion to Lion?

Currently I'm on a Mountain Lion system and I have a system that is remote which uses Lion, I am able to use Back to My Mac to connect and browse files but Screen Sharing (Lion system on the Mtn Lion system) will never connect.
Should this be expected to work?

Jim, I may have solved the problem. Don't know if it is a permanent fix yet though.
On the Lion computer, on the Sharing Control Panel, I turned on "Remote Management" rather than screen sharing.
When I did this, Screen Sharing was disabled. I then turned off Remote Management and re-activated Screen Sharing.
From this point Share Screen seems to work and I am now able to see the screen from the Lion computer on the Mountain Lion computer.
Throughout the day I have been able to share screen the other way (displaying the Mountain Lion computer's screen on the Lion computer) without any problems.
No idea why this would work, but seems to have done the trick for me!

Asking for permission when screen sharing between MBP and Mini?

Hi Guys,
Like many others I have a mini connected to the TV, and use that as my media center, all music, movie, pictures, etc. is shown thrue the mini.
After upgrading to Lion I cannot use screen sharing as before, where I just connected to the mini, and voila I had the full control. Now it seems I have to accept the screen sharing request!?!? Is there a way around this, I surely hope so, because otherwise it will defeat the purpose of my mini! I mean, I have no mouse or keyboard attached to it obviously!
I hope there is an answer to this
Best regards
Viktor

Viktorrrrr,
It appears that Screen Sharing is a bit "buggy" in this first release of Lion.
Having said that, I have managed to get mine working and it is possible to have screen sharing without the approval prompt - the key is that you need to connect using the same account that is already logged on at the machine you're connecting to. So, in your case, after you click "Share Screen..." on your MBP, you should enter the account name and password that matches the account currently logged on your Mac Mini.
This should be fine if the account currently logged on your Mac Mini is allowed to do Screen Sharing (see the list of users in the "Allow access for:" section of the "Sharing--->Screen Sharing" system prefs).
If this works for you, stop reading here!
However, if (like me) you log on locally to your Mac Mini with a Standard account, but only allow Administrators to connect to the Mac Mini via Screen Sharing, then you have some extra work to do because, as you know, when you connect via Screen Sharing with one account in order to view the screen of another logged-on account on the Mac Mini, you get the prompt asking for permission. There does not appear to be an option to switch off this behaviour and, I suspect, this behaviour will remain due to privacy/security issues. So, if you want to avoid this prompt, you are going to have to log in using the same account. And to do this, you will need to allow this account to Screen Share.
The quick way to enable this would be to choose the option to "Allow access for: All users" on your Mac Mini - this would then allow your account (and ALL others!) to connect via Screen Sharing. But you really don't want to enable this if you can help it. Much better, would be to create a new local group on your Mac Mini called something like "Screen Share" and populate this group with all the accounts you want to be allowed to connect via Screen Sharing.
To create and populate a new group:-
Go to the "Users & Groups" system pref and click the + below the list of users to bring up the "New Account" window. Where you see the pull-down menu that says "Standard", click on this and select "Group". Enter your new group name and click "Create Group". The new group will be created and you can then select the accounts you want to include in this group (ie. the accounts you want to allow to connect via Screen Sharing) in the "Membership" section - just tick the boxes of the ones you want.
Now go back to the "Sharing-->Screen Sharing" system pref. Where it says "Allow access for:", click the "Only these users:". Now click the + below the list to bring up a window of all users. Make sure "Users & Groups" is selected in the left pane, then click on your newly-created group in the right pane and click "Select".
Sadly, this is where the real bugs seem to be!! When I try to permission my group for access, more often than not, my selected group is not added to the list of allowed access. I have played with this for hours, clicking various options in various sequences, but have not found a pattern. Even when my selected group does get added successfully, I sometimes find access is still not granted to that group and its members!!
I'm afraid it seems to be trial and error at the moment - I guess a fix will come eventually, but for now you just need to keep adding the group, removing it, turning Screen Sharing on then off then on again, try adding again...etc! I CAN tell you that I did eventually get my group to stick and work as intended, so it is possible...but it will take time!
Sorry for the lengthy response. Good luck!
C.

Screen sharing mobile account (open directory) not working

Can anybody else verify that screen sharing, through Remote Management, does not work when trying to connect to mobile accounts on 10.7 Lion?
Please note, when I say through Remote Management, I mean that under System Prefs->Sharing->Screen Sharing is disabled but Remote Management is enabled. (Remote Management being able to provide it's own screen sharing)
Also I dont mean VNC... please make sure the "VNC viewers may control my screen with password" option is turned off under System Prefs->Sharing->Remote Management->Computer Settings

I can confirm this. Same experience here on a 10.7.2 Mac.
I get a "Please verify you have entered the correct name and password".
Does this work on 10.6? I'm unable to check at the moment.

I cant get screen sharing to work on my home network

I am trying to connect my macbook pro to screen sharing so i can access it at my school computers, which are all iMacs running 10.6.6. When i was at school, and connected to the wireless network at my school i could screen sharing through the finder>go>connect to server. Once screen sharing was enabled i just entered the vnc address and it connected flawlessly. When i got home, and i set my netgear router( wireless-n 150 model: wnr100v2) for port forwarding start port: 5900 end port:5900 server name vnc, and set the ip address to my computer, and when i tried to screen share from another macbook within my network through the finder>go>connect to server, i could not connect. Oddly when i connected my mobile me, i cold screen share over the network. I want to do a WAN screen sharing and i cannot figure out how do do it. I would appreciate any help because it is very important that i enable this feature.

I'm a little confused by your explanation (it's late), so I am going to say what I think I read:
You want to set up your home computer so you can access it via screen sharing from school.
The home computer needs sys prefs sharing screen sharing enabled, and sys prefs security firewall must allow it, too. You port forward port 5900 through your home router to that home computer, which may or may not require that you use a static "192.168.x.x" (or "10.x.x.x" -- whatever the router's LAN subnet is) LAN IP address on that computer -- some routers require that computers acting as servers have static IPAs -- some routers don't.
You need to find out what is the public (internet-facing) WAN IP address that your ISP has assigned to your router; it is not the 192.168.x.x (or 10.x.x.x) address given to your home computer by your home router. You can find that by going to http://checkip.dyndns.com on your home computer. Unless you pay extra for a static public IP address from your ISP, ISPs may (and do) change it periodically on you without warning. So vnc://123.45.67.89 may work one day but not the next.
Some routers have a built-in feature to work around this by allowing the router to advise dynamic DNS servers of any changes in the public-facing IP address of the router. Of course, you need to have established an account with a dynamic DNS provider so you have a host name (like lomberg.noip.com or lomberg.dyndns.com). These are generally free accounts unless you want a special name that doesn't have the dynamic DNS provider as part of your host name.
If your router does not have this capability, these dynamic DNS providers have a piece of software that you will need to install on your home computer (the "VNC server") that reports changes in your public-facing IP address to their DNS servers.
Once this is done, then from afar, you can ⌘k to vnc://lomberg.dyndns.com (or whatever you set up your host name to be with dyndns or equivalent outfit) and you don't need to worry about what your ISP has done to you with regards to your public-facing WAN IP address du jour.
Note that with some (most?) routers, when you are on your home network, you will not be able to vnc to the host name or numeric WAN IPA in this manner. I don't know why it doesn't work, it just doesn't. I've had modems both ways -- my current ISP rental modem doesn't while the previous one (which broke so I had to replace it with my current POS modem) did. So in such case, you have to vnc://192.168.x.x of the "vnc server" computer when you are on the same LAN.
You are aware that on the client (school) machine, screen sharing preferences can be set to encrypt all data on the connection, not just the username/password negotiation piece, right? I don't know whether that setting persists across sessions or only persists for the duration of the current session. I wouldn't want my client mouse/keyboard and "server" screen video to be transmitted in the clear; that's why I bring this up.
Does that answer your question? Or did I totally misunderstand what you were asking?

File Sharing, Screen Sharing keeps disappearing

Similar Messages

Maybe you are looking for