Screen Sharing: Authentication Failed

Since updating to OS 10.7 on my Mac Mini, I have been unable to log in via Screen Sharing (using my 10.7-installed Macbook). I continually receive the error "Authenticaion failed to 'MacMini'. Please verify you have entered the correct name and password." The name and password are correct, and I can log into the computer as an administrator via the Finder to access its files without issue. Only the Screen Sharing application fails to authenticate. I had no troubles literally an hour ago using Snow Leopard.
Thoughts?

After restarting both computers a few times, I can now no longer connect via normal File Sharing -- it will connect as a guest just fine, but when I try to connect as a user, it stalls out. It sounds like the problem in this thread:
https://discussions.apple.com/message/15676665

Similar Messages

Screen Sharing authentication fails or shows only a small black box

Hi everybody!
I've been working on a issue and as I found a solution only by collecting bits of help from all over the web, I thought I could help somebody else by posting it here, where I found lots of help on other issues myself.
Here's the topic: I couldn't connect to my 10.5.7 OS X Server via Screen Sharing anymore. Everything else worked fine, i.e. I could login to all other services (AFP, LoginWindow, VPN, etc.).
I saw some strange errors in my Kerberos-Server log. As I thought of an OD or Kerberos problem, I tried different things concerning these services. Running "kinit <yourusername>" got me to the point where the authentication didn't fail anymore, but all I could see was a little (i.e. ~ 100x200px) black box instead of my server's screen.
The problem finally turned out to be NOT connected to my strange log entries but with somehow having turned on "Remote Management" in Server Admin. Here's my solution to it:
1. Turn off "Remote Management".
Server Admin -> Settings -> General, tick off "Remote Management"
2. Turn on Screen Sharing.
2.1 ssh to your server.
2.2. cd /Library/Preferences
2.3. echo -n enabled > com.apple.ScreenSharing.launchd
That's it after that I was able to log in again. Thanks goes to a lot of folks out there in the web, not to me.

Hi everybody!
I've been working on a issue and as I found a solution only by collecting bits of help from all over the web, I thought I could help somebody else by posting it here, where I found lots of help on other issues myself.
Here's the topic: I couldn't connect to my 10.5.7 OS X Server via Screen Sharing anymore. Everything else worked fine, i.e. I could login to all other services (AFP, LoginWindow, VPN, etc.).
I saw some strange errors in my Kerberos-Server log. As I thought of an OD or Kerberos problem, I tried different things concerning these services. Running "kinit <yourusername>" got me to the point where the authentication didn't fail anymore, but all I could see was a little (i.e. ~ 100x200px) black box instead of my server's screen.
The problem finally turned out to be NOT connected to my strange log entries but with somehow having turned on "Remote Management" in Server Admin. Here's my solution to it:
1. Turn off "Remote Management".
Server Admin -> Settings -> General, tick off "Remote Management"
2. Turn on Screen Sharing.
2.1 ssh to your server.
2.2. cd /Library/Preferences
2.3. echo -n enabled > com.apple.ScreenSharing.launchd
That's it after that I was able to log in again. Thanks goes to a lot of folks out there in the web, not to me.

Unsolvable Screen Sharing Authentication Error

Here's my scenario...
I have three Core2Duo iMacs (Let's call them "A" "B" and "C") on a local appletalk network all communicating fine in all directions via an Airport Extreme base station.
When it comes to logging into each machine via file sharing, I have no trouble accessing any machine from any other machine.
HOWEVER,
When I attempt screen sharing over the network, this is my result.
Computer "A" can access the screens of "B" and "C",
Computer "B" can access the screens of "A" and "C",
Computer "C" can access the screen of "B" but not "A"
When I attempt to log into Screen sharing from "C" to "A", I get the following error message:
*+Authentication failed to "NameofComputer"+*
*+Please verify you have entered the correct name and password.+*
I have turned screen sharing on/off, restarted, etc, but it doesn't fix that one issue.
Now, to add to the strangeness, when I access computer "A" via computer "B" through file sharing, I can see all of my drives, including an externally connected hard drive that I use for storage.
BUT, when I connect from "C" to "A" via file sharing, all of my user areas and native partitions show up, but the External drive does NOT.
Does anyone have any suggestions other than archiving and reinstalling Leopard? AND, any idea which system even has the problem? The authentication error responds so quickly that I somewhat think that authentication is not even being attempted from "C" to "A".
Any help is REALLY appreciated!
Thanks,
Chris

Here's just a bit more info. I created a new user on the computer that I noted as "C" and under the new user area I was able to connect to computer "A"; however, when I switch back to the original user, it still will not connect, so now I know that the problem lies somewhere in "C".
I deleted my screen sharing prefs, but that made no change.
I have verified that the sharing and network settings are consistent across all three machines.
Could there be another preference file I should attempt to delete to see if I have a corrupted preference?
Thanks again,
Chris

Screen sharing authentication

Somehow authentication for screen sharing on one machine (say machine A) from another machine (say machine B) got set to use kerberos (kdc) and not to require a password.
Both machines are running OS X 10.10.1.
After successful connection, the console on machine A contains an entry of the form:
kdc: TGS-REQ username@LKDC:SHA1.xxxxxxx from (ip address) for vnc/LKDC://SHA1.yyyyyyyy
where xxxxxx and yyyyyyyyy stand for long codes.
I didn't set this up and I don't want this. I would like to authenticate each time using a password.
How did this happen, where is the authentication information stored on the two machines, and how can I undo it?

Well, I figured it out! Turns out that I was playing with open directory recently (not successfully) because I wanted to have a networked home drive between my mbp and my mini. So during that process os x uses LDAP for looking up users. After I decided to give up on open directory, i just turned the service off. I guess the machines were still trying to authenticate against a LDAP service. So what I had to do:
open directory utility (/System/Library/CoreServices/Directory Utility.app)
look at the list of sources there. If you aren't using open directory, uncheck LDAP.
*I disabled LDAP on both the client and the server, its possible you only need to do it on the server.
restart ARDAgent (ps aux | grep ARD find the procid, then kill <procid>).
viola! working screen sharing again.

Screen Sharing Connection failed when using dock shortcut

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

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

Screen Sharing suddenly fails with "Communication Error" in console log. File sharing works fine. Thoughts?

I have been using Lion provided Screen Sharing for months without incident. Suddenly (I do not believe there was an intervening o/s update), it will not connect. I get a "Connection Error" dialog after a minute or two. The console log shows the same thing w/o any useful info. I can share files with the target mac fine and run time machine without error. Any ideas on what's up?
Thanks

Check the host property configured in KM URL generator service.
Navigate to
System Administration -> System Configuration -> Knowledge Management -> Content Management -> Global Services -> (switch to advanced mode) ->URL generator Service -> Host
You should use the fully qualified host name and port.
Regards,
Prasanna Krishnamurthy

Screen Sharing.app fails through ssh tunnel with "You cannot control your own screen"

I need to control a remote Mac mini running 10.7 through an ssh tunnel. I've set up ssh with -L for the appropriate ports, and bound my local ports 5900 and 5800 through this.
When I connect to 127.0.0.1 with Screen Sharing.app on my macbook pro which runs 10.8.4, it says "You cannot control your own screen" however, screen sharing is not enabled locally on my machine, I'm trying to access a remote machine.
I tried something else. I created an alias IP of 127.0.0.2 on lo0, and tried again, and got the same thing, so it's doing an ifconfig and looking through all the IPs to see if the IP address of what I'm trying to connect to is bound locally, which defeats the purpose of tunneling through SSH. I don't wish to setup a VPN.
How do I let the Screen Sharing.app know that I'm not trying to connect to my own machine and it should skip this check.
I've also tried with another app, Chicken of the VNC, and that almost works. It connects and shows a login screen desktop to the target machine, but I'm unable to click on any of the account icons displayed in order to login, and all key presses such as tab, space, and enter are ignored.
When at the location (on the same vlan as the target machine) I'm able to remote into it just fine with screen sharing.app, but Chicken of the VNC has the same issue of showing a login screen, but not allowing logins to it.

Your ssh command should look something like:
ssh -L 22590:localhost:5900 remove.mac.system.address
Then you connect using
Finder -> Go -> Connect to server -> vnc://localhost:22590
Have you been doing anything close to that?

IChat screen sharing does not work on my Mac Pro

I have a weird iChat screen sharing problem that i can't seem to resolve on my Mac Pro. Ever since i got my Mac Pro in early 2008, using the screen sharing feature in iChat has always been flaky. I have never gotten to the point of getting it consistently working. Lately, i have not been able to get it to work at all.
Most of the time, when i choose to share my chat target's screen (or when i share my screen), i would be able to see my chat target's screen and use the mouse for several seconds before the shared screen session is ended. The errors that i am getting are:
+"Disconnected from Screen Sharing because:+
+No data has been received for the last 10 s..."+
+"There was a communication error during your chat.+
+No data has been received for the last 10 seconds. You can send+
+details about this problem to Apple to help improve future versions of+
iChat."
On other occasions (mostly when i am trying to troubleshoot this issue by testing in the same network with my Powerbook, which is on 10.5.6 as well), i get this error:
+"Disconnected from Screen Sharing because:+
+Screen sharing could not be established."+
I have tried to do screen sharing via iChat with other Macs in the same network and also on the internet but with the same problems.
Initially, i thought this may be router related. But the fact that iChat screen sharing on my Powerbook works perfectly both in intranet and internet eliminates my router as the culprit.
I have also tried disabling the OSX Firewall but the outcome was the same.
I read some posts that there may be issue with using the external iSight web cam. I unplugged it, cleaning up all the iChat-related caches and preferences and tried again but with the same result.
I have also tried connecting to iChat using several different account types (mobileme, .mac and AIM) but the end result is the same.
I run a Ubuntu VMWare fusion VM on my Mac Pro as my webserver. I thought that may be the problem. Shutting down the Ubuntu VM also does not help.
Applecare support personnel also instructed me to re-install iChat but that did not help as well.
One interesting error i noticed in the system.log (seen via the Console app) that is generated everytime iChat screen sharing fails on my Mac Pro:
+12/23/08 12:32:00 AM /Applications/iChat.app/Contents/MacOS/iChat[507] error getting server version+
I am really running out of ideas on what else i can do to get this resolved.
Thanks in advance for any suggestion.
Message was edited by: Changren Yong
The audio and video chat portions of iChat work fine.

I managed to make some headway in my attempts to troubleshoot this problem. I did a fresh Leopard install on one of the drives in my Mac Pro. I then proceeded to update it to 10.5.6. After that, i launched iChat and attempted screen sharing with my Powerbook. The first few attempts failed, with the following symptoms:
- i would be able to see and control the Powerbook's screen
- after 5 seconds, my screen sharing session is disconnected
I then unplugged my external iSight. After i relaunched iChat, i managed do screen sharing in iChat without being disconnected!!! When i connected the iSight back into the ACD, with iSight off, i attempted to screen share again. This time, it failed after about 5 seconds, just like earlier. I then turned iSight on. This time round, the screen sharing session was not disconnected!!
So in addition to the iSight issue, something in my original Leopard startup disk is causing iChat screen sharing to fail because even when screen sharing was failing on my fresh Leopard install, i do not see this error:
/Applications/iChat.app/Contents/MacOS/iChat(507) error getting server version
So if i can figure out what is causing this error to show up in system.log, then i can manage the iSight issue.

After Lion install screen sharing won't accept my password

I just updated my *headless* mac-mini to 10.7. As soon as it rebooted
Since updating to OS 10.7 on my Mac Mini, I have been unable to log in via Screen Sharing (using my 10.7 installed Mac Pro). I continually receive the error "Authenticaion failed to 'MacMini'. Please verify you have entered the correct name and password." The name and password are correct, and the mac-mini lets me "Connect As ..." with the username and password. Only the Screen Sharing application fails to authenticate. I had no troubles an hour ago when it had Snow Leopard installed.
Any solution before I have to travel to this mini?
Thanks,
Jim

My family has multiple Macs at home and I also help a friend at a remote location. What is weird, is I was able to do screen sharing with the Mac at the remote location and a couple at home, but was not able to get screen sharing to work on the majority of our Macs at home. Rebooting did not help. Deleting my user login and corresponding home folder (then rebooting) and recreating a new user under the same login name that was deleted did not help. Repairing permissions in Disk Utility did not help. I did not try creating a user under a totally different login name and setting up screen sharing to share with that user name. I was going to try that this morning. However, on another thread, someone offered another thing to try. I tried it and it worked.
This is what eventually worked for me... This work around seems to expose that there is definitely a bug:
https://discussions.apple.com/message/15812668#15812668
Quote from andifor:
"Full name and account name on my computers are also the same.
But I did some deviation last time I tried. I changed my name on the connection dialog. I changed the name from "user" to "uSer" (changed one letter to capital) and it did work!
So if you login name is "peter", change it to "pEter" or "peTer", just on the login screen.
Looks more and more like a bug and only Apple can help. Does anybody know, if they are monitoring these discussions or is there a possibility to log some bug report?"

Any Better Screen Sharing VNC alternative ?

just stat to use Screen Sharing to control my other PCs at home ,
not sure is it some setting problem or what.
Every time Screen Sharing first start it will run fine, but after a while screen sharing will fail to refresh the remote computer screen at the mean time still having control the remote PC it just don't refresh the screen or don't refresh completely.
so is there any thing i can do to improve SS ? or is there any other VNC viewer for OSX , the only free viewer i find is Chicken of the VNC it had very limited function.
any suggestion is welcome
thx

Apple's screen sharing is the most compatible solution, though any VNC viewer should work. Most are rather buggy and Chicken of the VNC was the best that I came across. The best is "Apple Remote Desktop", but you have to purchase it. From my experiences the screen sharing is the best alternative to ARD.

Screen Sharing not working from Yosemite 10.10.2 = Mavericks

Seemingly after the upgrade from 10.10.1 to 10.10.2 my workstation can no longer connect to the workstations that I had successfully before been connecting to before the upgrade. I have already tried formatting my hard drive and transferring files from a previous Time Machine backup.
From the terminal if I issue this command:
open vnc://192.168.1.201
Below you can find the relevant logging to /var/log/system.log (including leading and trailing logs for potentialy relevance)
http://tny.cz/69b303b6
I can succesfully connect to that URL from a machine running mavericks version 10.9.4 on the same wireless network.
Clearly something is crashing on the newer Yosemite machine – potentially relevant lines are:
"Screen Sharing[309]: No valid display name"
"acquire_kerberos failed com.apple.idms.appleid.prd"
"-[SSAddress url]: unrecognized selector sent to instance 0x7fad60e77510"
Another thing to note is that I can only perform that operation one time and achieve that stacktrace. Every other time I issue that command Screen Sharing.app fails silently.
Thanks!
James

Hi Bill,
You could try removing all the installed components manually and then try again (install, don't open but update right away).
According to the installer the files are located in:
/Applications/Remote Desktop.app (that one was hard to find )
/Library/Application Support/Apple/Remote Desktop/
/Library/Preferences/com.Apple.ARDAgent.plist
/Library/Preferences/com.Apple.RemoteDesktop.plist
/Library/Receipts/
/Library/Widgets/RemoteDesktop.wdgt
(not sure if the following files tie into other parts of the OS so removing them may cause issues)
/System/Library/CoreServices/RemoteManagement
/usr/bin/share/man/man1
perhaps a permission repair after all parts have been deleted and a restart before trying again.

Authentication failed on screen sharing

Since moving from MobileMe to iCloud, screen sharing via Back to my Mac has completely failed.
I see my computer in SHARED - this is either from home to my work machine, or from work to my home machine. I then select my remote computer and click "Share Screen..." Then choosing the "Connect As a registered user," I enter my Name (the account name on the remote machine) and Password, and am told "Authentication failed to 'XXXX's iMac'. Please verify you have entered the correct name and password."
If I "Connect Using an Apple ID," (which is is set up appropriately on both machines), I get the same response "Authentication failed to 'XXXX's iMac'. Please verify you have entered the correct name and password."
Thoughts?
Curiously, if I choose to "Connect As" (just accessing the remore machine's drives) instead of "Share Screen...", I am able to connect with the same credentials.

What helped for me was the following:
Until iCloud, my Apple ID used to be my Hotmail address. Since I am on the iCloud I have created an @me under this Apple ID. I had the same problem as you described above. I signed into everything using my Apple ID (@hotmail.com) but i couldn't share screens using this Apple ID.
So I changed everything:
In Users & Groups I signed in with my @me apple ID. Technically they both belong to the same Apple Account. I deactivated and changed the login for the iCloud in System Preferences from my Hotmail to the @me.com email address. same for the time capsule. I did that on all the computers i wanted to share screens and bang. It works perfect.
Maybe it also helps, if the user you define as yourself in your address book has the @me.com as an email address in your address book.
Its a shame that apple doesnt let you change the primary email address yet.

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 fails for one user

Hi
I have an iMac and MacBook Pro, both running Snow Leopard 10.6.5. I have enabled screen sharing on the iMac, and can log in with one of my other user accounts (Greg). This works fine.
When i am on my MBP, logged in as Joe, and logged in as Joe on the iMac, i always get an "Authentication failed", but i can connect as Greg ok... I thought it was to do with the currently logged in user having the same short name, so i tried logging in as Greg on the iMac, and connecting as Joe from the MBP, but still no success.
Is there anything i can check?
Thanks
Joe.

Identical short user names on the different computers shouldn't be a problem - I have multiple Macs with identical short user names and have no problem.
As an aside, you don't need to already be logged in on the other computer; the VNC connection, if VNC login is permitted for that iMac user, would simply present the remote VNC client with its login screen, at which point you could login to the iMac as any user that you wanted, even though you made the VNC connection as someone else. Similarly, regardless of who is at the console on the iMac, the authorized VNC client user on the MBP can connect and view(/control) the screen(/keyboard/mouse).
In the iMac's Sys Prefs Sharing, when Screen Sharing is highlighted, what does it say for "Allow Access for:"?
In the iMac's Sys Prefs Security under the Firewall tab, is the Firewall on? If so, in "Advanced..." is the "Block All Incoming Connections" checkbox unchecked? In the application list there, what does it say about incoming connections for Screen Sharing?
Finally, the iMac and the MBP are on the same home LAN, i.e., the MBP is not having to traverse through your home router's firewall, correct?

Screen Sharing and Authentication

During deployment, I used this command to bind my clients to the directory server:
yes | dsconfigldap [-fvxsgemSN] -a myservername -n “myservername” -c $computerid -u diradmin -p mydiradminpass -l localadmin -q localadmin's pass
after doing this, I can no longer use screen sharing to access the bound clients. Unable to authenticate.
Is this becuase of the
-s
enforce not using cleartext authentication via policy
flag?
Is there still a way for me to screen share into my clients w/o having to use logmein?
Will ARD do it?

From the menu bar on the Screen Sharing server, select
 ▹ System Preferences... ▹ Users & Groups ▹ Login Options
and check the box marked
Allow network users to log in at the login window
If there's a closed padlock icon in the lower left corner of the preference pane, you may need to click it to unlock the settings. Enter your login password when prompted.
Note that this option is only available when the server is bound to a network directory server.
See also:
Screen Sharing with Open Directory Authentication

Screen Sharing: Authentication Failed

Similar Messages

Maybe you are looking for