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.

Similar Messages

Mouse pointer/cursor clicking fails while screen sharing in Messages & iChat

Has anyone else had this problem?
My work partner is sharing her screen using iChat on OS 10.6.8 and I'm controlling it with Messages on OS 10.8.3 - usually working on Adobe Lightroom and Photoshop.
Every few minutes or so, I lose the ability to click anything on her screen. Audio/video works fine, and my keyboard commands run fine on her computer, I can usually even move the pointer fine but, clicking my mouse or trackpad has no affect on her computer. This is sometimes accompanied by a flashing stalled pointer.
We can usually fix it by having her click her mouse/trackpad a couple times and then I can continue with clicking again from mine.
But, sometimes she's not at the computer so there's no way for me to recover screen share clicking when her computer is unattended.
We both have high speed internet with 10+mb down and 5+mb up speeds.
I've also tried it with bluetooth off and still have the same problem.
Does anyone know how to recover from failed mouse clicking during screen sharing?
Thanks.

HI,
I have not see this but at the same time I do not Screen Share as extensively as you seem to describe.
One interpretation I could out on this from what you have written is that not only is your girlfriend getting bored and wondering Off ( ) but her computer may also be going to sleep.
I have never waited long enough for one of my other computers to go to Sleep during a Screen Share to find out what happens.
1) does the Share Screen go dark ?
2) do you lose the connection as it closes the network ?
3) Is a Screen Saver starting that you can see ?
4) what does your girlfriend see when this happens ?
I would guess there is something about the VNC part of the iChat Screen Sharing that stops the Shared computer going to sleep.
However I am not sure if a Screen Saver can be active or if you are bumping into the time set for one to start.
I would also be interested in what the other computer is doing in a "behind the scenes" way.
Is something using up the Processor cycles and holding up the Share view as it were ?
I would guess her computer is doing something on it's own such as fetching Mail or similar or even the Time Machine Back up which can be known to cause the computer to be held up for a moment or two.
8:36 PM Tuesday; April 16, 2013
 iMac 2.5Ghz 5i 2011 (Mountain Lion 10.8.3)
 G4/1GhzDual MDD (Leopard 10.5.8)
 MacBookPro 2Gb (Snow Leopard 10.6.8)
 Mac OS X (10.6.8),
 Couple of iPhones and an iPad
"Limit the Logs to the Bits above Binary Images."  No, Seriously

IChat screen sharing fails (only screen sharing though)

I was trying to assist my in-laws the other day and have never used Screen Sharing in iChat before. We started an A/V session (which works fine), but when we started the Screen Sharing session, it dies after about 5 seconds of use. Both sides get the error "no activity after 10 seconds...". Thinking it was an internet thing (perhaps firewall settings), i tried internally on my LAN with a MacBook Pro and a new Mac Mini, same thing. Either way the session is initiated, failure.
Did some research through these discussions and found the common thread was the UPnP and internal preference settings. Have checked both, they all seem ok.
Some statistics of my example: (Remote machine) Mac#1 is an iMac G5 20" 2GHz running Snow Leopard fully updated, with Comcast as the IP and an Airport Express as the router. Port Mapping is turned on in NAT, and Screen Sharing is turned on in preferences -> Sharing.
(Local machine) Mac#2 is a Mac Mini 2.4 GHz Core 2 Duo running Snow Leopard, with Comcast as the IP and a Time Machine as the router. Both settings above turned on.
(Local machine) Mac#3 is a MacBook Pro 15" 2.53 GHz Core 2 Duo running Snow Leopard (same IP as #2) on the same LAN as #2.
All 3 accounts are on MobileMe, A/V chats work fine without problems for limitless amounts of time. Have tried screen sharing both ways, same result.
Here's a log between #2 and #3 fail (sorry for long post):
Date/Time: 2010-07-08 19:13:41 -0500
OS Version: 10.6.4 (Build 10F569)
Report Version: 4
iChat Connection Log:
2010-07-08 19:13:31 -0500: 0x11ae38640: State change from AVChatStateConnected to AVChatStateEnded.
2010-07-08 19:13:31 -0500: 0x11ae38640: Error -20 (No data has been received for the last 10 seconds.)
2010-07-08 19:13:31 -0500: **[email protected]: State change from AVChatStateConnected to AVChatStateEnded.
2010-07-08 19:13:31 -0500: **[email protected]: Error -20 (No data has been received for the last 10 seconds.)
Video Conference Error Report:
Video Conference Support Report:
8.275079 @/SourceCache/VideoConference/VideoConference-415.22/Video Conference/VCInitiateConference.m:2059 type=2 (00000000/0)
[Connection Data for call id: 1 returns 1
9.155420 @/SourceCache/VideoConference/VideoConference-415.22/Video Conference/VCInitiateConference.m:2074 type=2 (00000000/0)
[Prepare Connection With Remote Data - remote VCConnectionData: 1, local VCConnectionData: 1
9.165268 @/SourceCache/VideoConference/VideoConference-415.22/SIP/Transport.c:338 type=2 (00000000/0)
[INVITE sip:user@lip:16402 SIP/2.0
Via: SIP/2.0/UDP rip:55667;branch=z9hG4bK7cc8269d38bfe756
Max-Forwards: 70
To: 0 <sip:user@lip:16402>
From: u0 <sip:user@rip:16402>;tag=457027611
Call-ID: 1df8aee9acfb7f6-8aee-11df-8b6c-fd20244f4012@rip
CSeq: 1 INVITE
Contact: <sip:user@rip:55667>;isfocus
User-Agent: Viceroy 1.4
Content-Type: application/sdp
Content-Length: 702
[v=0
o=Merricks 0 0 IN IP4 rip
[email protected]
c=IN IP4 rip
b=AS:2147483647
t=0 0
a=hwi:1056:2:2400
a=iChatEncryption:NO
a=bandwidthDetection:YES
m=audio 55667 RTP/AVP 110 12 124 3 0
a=rtcp:55667
a=rtpmap:110 X-AAC_LD/22050
a=rtpmap:3 GSM/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:124 iLBC/8000
a=fmtp:124 mode=30
a=rtpID:1740916373
m=video 55667 RTP/AVP 123 126 34
a=rtcp:55667
a=rtpmap:123 H264/90000
a=rtpmap:126 X-H264/90000
a=rtpmap:34 H263/90000
a=fmtp:34 imagesize 1 rules 30:352:288
a=framerate:30
a=RTCP:AUDIO 55667 VIDEO 55667
a=fmtp:126 imagesize 0 rules 20:640:480:640:480:20
a=fmtp:123 imagesize 0 rules 20:640:480:640:480:20
a=rtpID:3396090499
9.165844 @/SourceCache/VideoConference/VideoConference-415.22/SIP/Transport.c:2138 type=1 (00000000/0)
[SIP/2.0 100 Trying
Via: SIP/2.0/UDP rip:55667;branch=z9hG4bK7cc8269d38bfe756
To: 0 <sip:user@lip:16402>
From: u0 <sip:user@rip:16402>;tag=457027611
Call-ID: 1df8aee9acfb7f6-8aee-11df-8b6c-fd20244f4012@rip
CSeq: 1 INVITE
User-Agent: Viceroy 1.4
Content-Length: 0
9.165935 @/SourceCache/VideoConference/VideoConference-415.22/SIP/Transport.c:2138 type=1 (00000000/0)
[SIP/2.0 180 Ringing
Via: SIP/2.0/UDP rip:55667;branch=z9hG4bK7cc8269d38bfe756
To: 0 <sip:user@lip:16402>;tag=116363815
From: u0 <sip:user@rip:16402>;tag=457027611
Call-ID: 1df8aee9acfb7f6-8aee-11df-8b6c-fd20244f4012@rip
CSeq: 1 INVITE
Contact: <sip:user@rip:55051>
User-Agent: Viceroy 1.4
Content-Length: 0
9.176133 @/SourceCache/VideoConference/VideoConference-415.22/SIP/Transport.c:2138 type=1 (00000000/0)
[SIP/2.0 200 OK
Via: SIP/2.0/UDP rip:55667;branch=z9hG4bK7cc8269d38bfe756
To: 0 <sip:user@lip:16402>;tag=116363815
From: u0 <sip:user@rip:16402>;tag=457027611
Call-ID: 1df8aee9acfb7f6-8aee-11df-8b6c-fd20244f4012@rip
CSeq: 1 INVITE
Contact: <sip:user@rip:55051>
User-Agent: Viceroy 1.4
Content-Type: application/sdp
Content-Length: 436
v=0
o=jmerrick 0 0 IN IP4 rip
[email protected]
c=IN IP4 rip
b=AS:2147483647
t=0 0
a=hwi:17412:2:2530
a=bandwidthDetection:YES
a=iChatEncryption:NO
m=audio 55051 RTP/AVP 110
a=rtcp:55051
a=rtpmap:110 X-AAC_LD/22050
a=rtpID:1191125273
m=video 55051 RTP/AVP 123
a=rtcp:55051
a=rtpmap:123 H264/90000
a=RTCP:AUDIO 55051 VIDEO 55051
a=fmtp:123 imagesize 0 rules 20:640:480:640:480
a=rtpID:4102577296
9.178372 @/SourceCache/VideoConference/VideoConference-415.22/SIP/Transport.c:338 type=2 (00000000/0)
[ACK sip:user@lip:16402 SIP/2.0
Via: SIP/2.0/UDP rip:55667;branch=z9hG4bK323287a4467da958
Max-Forwards: 70
To: 0 <sip:user@lip:16402>;tag=116363815
From: u0 <sip:user@rip:16402>;tag=457027611
Call-ID: 1df8aee9acfb7f6-8aee-11df-8b6c-fd20244f4012@rip
CSeq: 1 ACK
User-Agent: Viceroy 1.4
Content-Length: 0
9.181889 @:0 type=1 (00000000/0)
[Bandwidth Detection]
[Received the first BWD packet from rip:55667]
9.495818 @:0 type=1 (00000000/0)
[Bandwidth Detection]
[Avg=100964.70, NSDev=1.29%]
9.600142 @:0 type=1 (00000000/1)
[Bandwidth Detection]
[Avg=883694.30, NSDev=10.60%]
9.689564 @:0 type=1 (00000000/2)
[Bandwidth Detection]
[Avg=10202609.90, NSDev=206.74%]
23.854766 @/SourceCache/VideoConference/VideoConference-415.22/SIP/Transport.c:2138 type=1 (00000000/0)
[MESSAGE sip:user@rip:16402 SIP/2.0
Via: SIP/2.0/UDP rip:55051;branch=z9hG4bK2fe1d4391a735632
Max-Forwards: 70
To: u0 <sip:user@rip:16402>;tag=457027611
From: 0 <sip:user@lip:16402>;tag=116363815
Call-ID: 1df8aee9acfb7f6-8aee-11df-8b6c-fd20244f4012@rip
CSeq: 1 MESSAGE
User-Agent: Viceroy 1.4
Content-Type: text/plain
Content-Length: 16
VCRemoteMuted:ON]
23.861278 @/SourceCache/VideoConference/VideoConference-415.22/SIP/Transport.c:338 type=2 (00000000/0)
[SIP/2.0 200 OK
Via: SIP/2.0/UDP rip:55051;branch=z9hG4bK2fe1d4391a735632
To: u0 <sip:user@rip:16402>;tag=457027611
From: 0 <sip:user@lip:16402>;tag=116363815
Call-ID: 1df8aee9acfb7f6-8aee-11df-8b6c-fd20244f4012@rip
CSeq: 1 MESSAGE
User-Agent: Viceroy 1.4
Content-Length: 0
27.969942 @/SourceCache/VideoConference/VideoConference-415.22/SIP/Transport.c:338 type=2 (00000000/0)
[MESSAGE sip:user@lip:16402 SIP/2.0
Via: SIP/2.0/UDP rip:55667;branch=z9hG4bK38c4bd117f30ee85
Max-Forwards: 70
To: 0 <sip:user@lip:16402>;tag=116363815
From: u0 <sip:user@rip:16402>;tag=457027611
Call-ID: 1df8aee9acfb7f6-8aee-11df-8b6c-fd20244f4012@rip
CSeq: 2 MESSAGE
User-Agent: Viceroy 1.4
Content-Type: text/plain
Content-Length: 4
[PING]
27.972367 @/SourceCache/VideoConference/VideoConference-415.22/SIP/Transport.c:2138 type=1 (00000000/0)
[SIP/2.0 200 OK
Via: SIP/2.0/UDP rip:55667;branch=z9hG4bK38c4bd117f30ee85
To: 0 <sip:user@lip:16402>;tag=116363815
From: u0 <sip:user@rip:16402>;tag=457027611
Call-ID: 1df8aee9acfb7f6-8aee-11df-8b6c-fd20244f4012@rip
CSeq: 2 MESSAGE
User-Agent: Viceroy 1.4
Content-Length: 0
30.000459 @/SourceCache/VideoConference/VideoConference-415.22/SIP/Transport.c:2138 type=1 (00000000/0)
[MESSAGE sip:user@rip:16402 SIP/2.0
Via: SIP/2.0/UDP rip:55051;branch=z9hG4bK4210350f26913012
Max-Forwards: 70
To: u0 <sip:user@rip:16402>;tag=457027611
From: 0 <sip:user@lip:16402>;tag=116363815
Call-ID: 1df8aee9acfb7f6-8aee-11df-8b6c-fd20244f4012@rip
CSeq: 2 MESSAGE
User-Agent: Viceroy 1.4
Content-Type: text/plain
Content-Length: 4
PING]
30.004047 @/SourceCache/VideoConference/VideoConference-415.22/SIP/Transport.c:338 type=2 (00000000/0)
[SIP/2.0 200 OK
Via: SIP/2.0/UDP rip:55051;branch=z9hG4bK4210350f26913012
To: u0 <sip:user@rip:16402>;tag=457027611
From: 0 <sip:user@lip:16402>;tag=116363815
Call-ID: 1df8aee9acfb7f6-8aee-11df-8b6c-fd20244f4012@rip
CSeq: 2 MESSAGE
User-Agent: Viceroy 1.4
Content-Length: 0
31.622031 @/SourceCache/VideoConference/VideoConference-415.22/VCChannel/VCChannel.m:302 type=2 (00000000/0)
[VCChannel prepareConnectionWithRemoteConnectionData - remote VCConnectionData: 1]
31.886122 @/SourceCache/VideoConference/VideoConference-415.22/SIP/Transport.c:2138 type=1 (00000000/0)
[MESSAGE sip:user@rip:16402 SIP/2.0
Via: SIP/2.0/UDP rip:55051;branch=z9hG4bK6525ce694ef2153c
Max-Forwards: 70
To: u0 <sip:user@rip:16402>;tag=457027611
From: 0 <sip:user@lip:16402>;tag=116363815
Call-ID: 1df8aee9acfb7f6-8aee-11df-8b6c-fd20244f4012@rip
CSeq: 3 MESSAGE
User-Agent: Viceroy 1.4
Content-Type: text/plain
Content-Length: 17
VCRemotePaused:ON]
31.898618 @/SourceCache/VideoConference/VideoConference-415.22/SIP/Transport.c:338 type=2 (00000000/0)
[SIP/2.0 200 OK
Via: SIP/2.0/UDP rip:55051;branch=z9hG4bK6525ce694ef2153c
To: u0 <sip:user@rip:16402>;tag=457027611
From: 0 <sip:user@lip:16402>;tag=116363815
Call-ID: 1df8aee9acfb7f6-8aee-11df-8b6c-fd20244f4012@rip
CSeq: 3 MESSAGE
User-Agent: Viceroy 1.4
Content-Length: 0
32.026459 @/SourceCache/VideoConference/VideoConference-415.22/SIP/Transport.c:338 type=2 (00000000/0)
[MESSAGE sip:user@lip:16402 SIP/2.0
Via: SIP/2.0/UDP rip:55667;branch=z9hG4bK7caf68b0330b846f
Max-Forwards: 70
To: 0 <sip:user@lip:16402>;tag=116363815
From: u0 <sip:user@rip:16402>;tag=457027611
Call-ID: 1df8aee9acfb7f6-8aee-11df-8b6c-fd20244f4012@rip
CSeq: 3 MESSAGE
User-Agent: Viceroy 1.4
Content-Type: text/plain
Content-Length: 17
[VCRemotePaused:ON]
32.026863 @/SourceCache/VideoConference/VideoConference-415.22/SIP/Transport.c:2138 type=1 (00000000/0)
[SIP/2.0 200 OK
Via: SIP/2.0/UDP rip:55667;branch=z9hG4bK7caf68b0330b846f
To: 0 <sip:user@lip:16402>;tag=116363815
From: u0 <sip:user@rip:16402>;tag=457027611
Call-ID: 1df8aee9acfb7f6-8aee-11df-8b6c-fd20244f4012@rip
CSeq: 3 MESSAGE
User-Agent: Viceroy 1.4
Content-Length: 0
57.667457 @/SourceCache/VideoConference/VideoConference-415.22/Video Conference/VCInitiateConference.m:2059 type=2 (00000000/0)
[Connection Data for call id: 2 returns 1
69.057730 @/SourceCache/VideoConference/VideoConference-415.22/Video Conference/VCInitiateConference.m:2074 type=2 (00000000/0)
[Prepare Connection With Remote Data - remote VCConnectionData: 1, local VCConnectionData: 1
69.059710 @/SourceCache/VideoConference/VideoConference-415.22/Video Conference/VCInitiateConference.m:2266 type=2 (00000000/0)
[Initiate Conference To User: u0 with Remote VCConnectionData: 1 with Local Connection Data: 1 conferenceSettings: 1]
69.629813 @/SourceCache/VideoConference/VideoConference-415.22/SIP/Transport.c:2138 type=1 (00000000/0)
[INVITE sip:user@rip:16402 SIP/2.0
Via: SIP/2.0/UDP rip:55051;branch=z9hG4bK6d0a0202172485ce
Max-Forwards: 70
To: "u0" <sip:user@rip:16402>
From: "0" <sip:user@lip:16402>;tag=1160108830
Call-ID: 1df8aeebedd19cc-8aee-11df-af20-86f3848f4012@lip
CSeq: 1 INVITE
Contact: <sip:user@rip:55051>;isfocus
User-Agent: Viceroy 1.4
Content-Type: application/sdp
Content-Length: 703
v=0
o=jmerrick 0 0 IN IP4 rip
s=0
c=IN IP4 rip
b=AS:2147483647
t=0 0
a=hwi:17412:2:2530
a=iChatEncryption:NO
a=bandwidthDetection:YES
m=audio 55051 RTP/AVP 110 12 124 3 0
a=rtcp:55051
a=rtpmap:110 X-AAC_LD/22050
a=rtpmap:3 GSM/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:124 iLBC/8000
a=fmtp:124 mode=30
a=rtpID:2054428442
m=video 55051 RTP/AVP 123 126 34
a=rtcp:55051
a=rtpmap:123 H264/90000
a=rtpmap:126 X-H264/90000
a=rtpmap:34 H263/90000
a=fmtp:34 imagesize 1 rules 30:352:288
a=framerate:30
a=RTCP:AUDIO 55051 VIDEO 55051
a=fmtp:126 imagesize 0 rules 20:640:480:640:480:20
a=fmtp:123 imagesize 0 rules 20:640:480:640:480:20
a=rtpID:2001158912
69.646627 @/SourceCache/VideoConference/VideoConference-415.22/SIP/Transport.c:338 type=2 (00000000/0)
[SIP/2.0 100 Trying
Via: SIP/2.0/UDP rip:55051;branch=z9hG4bK6d0a0202172485ce
To: "u0" <sip:user@rip:16402>
From: "0" <sip:user@lip:16402>;tag=1160108830
Call-ID: 1df8aeebedd19cc-8aee-11df-af20-86f3848f4012@lip
CSeq: 1 INVITE
User-Agent: Viceroy 1.4
Content-Length: 0
69.646674 @/SourceCache/VideoConference/VideoConference-415.22/SIP/Transport.c:338 type=2 (00000000/0)
[SIP/2.0 180 Ringing
Via: SIP/2.0/UDP rip:55051;branch=z9hG4bK6d0a0202172485ce
To: "u0" <sip:user@rip:16402>;tag=74774650
From: "0" <sip:user@lip:16402>;tag=1160108830
Call-ID: 1df8aeebedd19cc-8aee-11df-af20-86f3848f4012@lip
CSeq: 1 INVITE
Contact: <sip:user@rip:55667>
User-Agent: Viceroy 1.4
Content-Length: 0
69.656640 @/SourceCache/VideoConference/VideoConference-415.22/SIP/Transport.c:338 type=2 (00000000/0)
[SIP/2.0 200 OK
Via: SIP/2.0/UDP rip:55051;branch=z9hG4bK6d0a0202172485ce
To: "u0" <sip:user@rip:16402>;tag=74774650
From: "0" <sip:user@lip:16402>;tag=1160108830
Call-ID: 1df8aeebedd19cc-8aee-11df-af20-86f3848f4012@lip
CSeq: 1 INVITE
Contact: <sip:user@rip:55667>
User-Agent: Viceroy 1.4
Content-Type: application/sdp
Content-Length: 434
[v=0
o=Merricks 0 0 IN IP4 rip
s=0
c=IN IP4 rip
b=AS:2147483647
t=0 0
a=hwi:1056:2:2400
a=bandwidthDetection:YES
a=iChatEncryption:NO
m=audio 55667 RTP/AVP 110
a=rtcp:55667
a=rtpmap:110 X-AAC_LD/22050
a=rtpID:794658613
m=video 55667 RTP/AVP 123
a=rtcp:55667
a=rtpmap:123 H264/90000
a=RTCP:AUDIO 55667 VIDEO 55667
a=fmtp:123 imagesize 0 rules 20:640:480:640:480
a=rtpID:3616868992
69.656733 @/SourceCache/VideoConference/VideoConference-415.22/SIP/Transport.c:2138 type=1 (00000000/0)
[ACK sip:user@rip:16402 SIP/2.0
Via: SIP/2.0/UDP rip:55051;branch=z9hG4bK19b439ee7b1a3a93
Max-Forwards: 70
To: "u0" <sip:user@rip:16402>;tag=74774650
From: "0" <sip:user@lip:16402>;tag=1160108830
Call-ID: 1df8aeebedd19cc-8aee-11df-af20-86f3848f4012@lip
CSeq: 1 ACK
User-Agent: Viceroy 1.4
Content-Length: 0
69.660304 @:0 type=1 (00000000/0)
[Bandwidth Detection]
[Received the first BWD packet from rip:55667]
69.975012 @:0 type=1 (00000000/0)
[Bandwidth Detection]
[Avg=100985.80, NSDev=2.06%]
70.079592 @:0 type=1 (00000000/1)
[Bandwidth Detection]
[Avg=889226.20, NSDev=6.32%]
70.150256 @:0 type=1 (00000000/2)
[Bandwidth Detection]
[Avg=3506655.00, NSDev=39.71%]
76.718688 @/SourceCache/VideoConference/VideoConference-415.22/SIP/Transport.c:2138 type=1 (00000000/0)
[MESSAGE sip:user@rip:16402 SIP/2.0
Via: SIP/2.0/UDP rip:55051;branch=z9hG4bK680d8ec50284d4dd
Max-Forwards: 70
To: "u0" <sip:user@rip:16402>;tag=74774650
From: "0" <sip:user@lip:16402>;tag=1160108830
Call-ID: 1df8aeebedd19cc-8aee-11df-af20-86f3848f4012@lip
CSeq: 2 MESSAGE
User-Agent: Viceroy 1.4
Content-Type: text/plain
Content-Length: 16
VCRemoteMuted:ON]
76.721457 @/SourceCache/VideoConference/VideoConference-415.22/SIP/Transport.c:338 type=2 (00000000/0)
[SIP/2.0 200 OK
Via: SIP/2.0/UDP rip:55051;branch=z9hG4bK680d8ec50284d4dd
To: "u0" <sip:user@rip:16402>;tag=74774650
From: "0" <sip:user@lip:16402>;tag=1160108830
Call-ID: 1df8aeebedd19cc-8aee-11df-af20-86f3848f4012@lip
CSeq: 2 MESSAGE
User-Agent: Viceroy 1.4
Content-Length: 0
85.580688 @/SourceCache/VideoConference/VideoConference-415.22/VCChannel/VCChannel.m:302 type=2 (00000000/0)
[VCChannel prepareConnectionWithRemoteConnectionData - remote VCConnectionData: 1]
85.824030 @/SourceCache/VideoConference/VideoConference-415.22/SIP/Transport.c:338 type=2 (00000000/0)
[MESSAGE sip:user@lip:16402 SIP/2.0
Via: SIP/2.0/UDP rip:55667;branch=z9hG4bK13543b054db63f4b
Max-Forwards: 70
To: "0" <sip:user@lip:16402>;tag=1160108830
From: "u0" <sip:user@rip:16402>;tag=74774650
Call-ID: 1df8aeebedd19cc-8aee-11df-af20-86f3848f4012@lip
CSeq: 1 MESSAGE
User-Agent: Viceroy 1.4
Content-Type: text/plain
Content-Length: 17
[VCRemotePaused:ON]
85.824453 @/SourceCache/VideoConference/VideoConference-415.22/SIP/Transport.c:2138 type=1 (00000000/0)
[SIP/2.0 200 OK
Via: SIP/2.0/UDP rip:55667;branch=z9hG4bK13543b054db63f4b
To: "0" <sip:user@lip:16402>;tag=1160108830
From: "u0" <sip:user@rip:16402>;tag=74774650
Call-ID: 1df8aeebedd19cc-8aee-11df-af20-86f3848f4012@lip
CSeq: 1 MESSAGE
User-Agent: Viceroy 1.4
Content-Length: 0
86.016699 @/SourceCache/VideoConference/VideoConference-415.22/SIP/Transport.c:2138 type=1 (00000000/0)
[MESSAGE sip:user@rip:16402 SIP/2.0
Via: SIP/2.0/UDP rip:55051;branch=z9hG4bK54989b9f3ab846c0
Max-Forwards: 70
To: "u0" <sip:user@rip:16402>;tag=74774650
From: "0" <sip:user@lip:16402>;tag=1160108830
Call-ID: 1df8aeebedd19cc-8aee-11df-af20-86f3848f4012@lip
CSeq: 3 MESSAGE
User-Agent: Viceroy 1.4
Content-Type: text/plain
Content-Length: 17
VCRemotePaused:ON]
86.021704 @/SourceCache/VideoConference/VideoConference-415.22/SIP/Transport.c:338 type=2 (00000000/0)
[SIP/2.0 200 OK
Via: SIP/2.0/UDP rip:55051;branch=z9hG4bK54989b9f3ab846c0
To: "u0" <sip:user@rip:16402>;tag=74774650
From: "0" <sip:user@lip:16402>;tag=1160108830
Call-ID: 1df8aeebedd19cc-8aee-11df-af20-86f3848f4012@lip
CSeq: 3 MESSAGE
User-Agent: Viceroy 1.4
Content-Length: 0
87.965096 @/SourceCache/VideoConference/VideoConference-415.22/SIP/Transport.c:338 type=2 (00000000/0)
[MESSAGE sip:user@lip:16402 SIP/2.0
Via: SIP/2.0/UDP rip:55667;branch=z9hG4bK4189780d0f2ba815
Max-Forwards: 70
To: "0" <sip:user@lip:16402>;tag=1160108830
From: "u0" <sip:user@rip:16402>;tag=74774650
Call-ID: 1df8aeebedd19cc-8aee-11df-af20-86f3848f4012@lip
CSeq: 2 MESSAGE
User-Agent: Viceroy 1.4
Content-Type: text/plain
Content-Length: 4
[PING]
87.965318 @/SourceCache/VideoConference/VideoConference-415.22/SIP/Transport.c:2138 type=1 (00000000/0)
[SIP/2.0 200 OK
Via: SIP/2.0/UDP rip:55667;branch=z9hG4bK4189780d0f2ba815
To: "0" <sip:user@lip:16402>;tag=1160108830
From: "u0" <sip:user@rip:16402>;tag=74774650
Call-ID: 1df8aeebedd19cc-8aee-11df-af20-86f3848f4012@lip
CSeq: 2 MESSAGE
User-Agent: Viceroy 1.4
Content-Length: 0
90.000670 @/SourceCache/VideoConference/VideoConference-415.22/SIP/Transport.c:2138 type=1 (00000000/0)
[MESSAGE sip:user@rip:16402 SIP/2.0
Via: SIP/2.0/UDP rip:55051;branch=z9hG4bK2ad74c4851d9447d
Max-Forwards: 70
To: "u0" <sip:user@rip:16402>;tag=74774650
From: "0" <sip:user@lip:16402>;tag=1160108830
Call-ID: 1df8aeebedd19cc-8aee-11df-af20-86f3848f4012@lip
CSeq: 4 MESSAGE
User-Agent: Viceroy 1.4
Content-Type: text/plain
Content-Length: 4
PING]
90.004582 @/SourceCache/VideoConference/VideoConference-415.22/SIP/Transport.c:338 type=2 (00000000/0)
[SIP/2.0 200 OK
Via: SIP/2.0/UDP rip:55051;branch=z9hG4bK2ad74c4851d9447d
To: "u0" <sip:user@rip:16402>;tag=74774650
From: "0" <sip:user@lip:16402>;tag=1160108830
Call-ID: 1df8aeebedd19cc-8aee-11df-af20-86f3848f4012@lip
CSeq: 4 MESSAGE
User-Agent: Viceroy 1.4
Content-Length: 0
Video Conference User Report:
0.000000 @:0 type=5 (00000000/16402)
[Local SIP port]
0.000041 @:0 type=5 (00000000/16402)
[Local SIP port]
0.000079 @:0 type=5 (00000000/16402)
[Local SIP port]
9.155545 @/SourceCache/VideoConference/VideoConference-415.22/Video Conference/VCInitiateConference.m:2171 type=5 (00000000/0)
[Remote Router]
[FULLCONE]
9.155553 @/SourceCache/VideoConference/VideoConference-415.22/Video Conference/VCInitiateConference.m:2173 type=5 (00000000/0)
[Remote CommNAT Result: 0x00000102
9.166348 @/SourceCache/VideoConference/VideoConference-415.22/Video Conference/VideoConferenceMultiController.m:2547 type=5 (FFFFFFFF/0)
[Caller User Agent: Viceroy 1.4]
9.166350 @/SourceCache/VideoConference/VideoConference-415.22/Video Conference/VideoConferenceGlobalObjects.m:1670 type=5 (00000000/0)
[Router]
[FULLCONE]
9.166355 @/SourceCache/VideoConference/VideoConference-415.22/Video Conference/VideoConferenceGlobalObjects.m:1672 type=5 (00000000/0)
[CommNAT Result: 0x00000102
9.166754 @:0 type=5 (00000000/1)
[Accept conference from user]
[[email protected]]
9.693286 @:0 type=5 (00000000/60)
[Detected bandwidth (kbits/s): 929 up, 929 down. (00000000)
9.698468 @/SourceCache/VideoConference/VideoConference-415.22/Video Conference/VideoConferenceMultiController.m:2423 type=5 (00000000/0)
[Start Conference With UserID: [email protected]]
69.057850 @/SourceCache/VideoConference/VideoConference-415.22/Video Conference/VCInitiateConference.m:2171 type=5 (00000000/0)
[Remote Router]
[FULLCONE]
69.057857 @/SourceCache/VideoConference/VideoConference-415.22/Video Conference/VCInitiateConference.m:2173 type=5 (00000000/0)
[Remote CommNAT Result: 0x00000102
69.059714 @/SourceCache/VideoConference/VideoConference-415.22/Video Conference/VideoConferenceGlobalObjects.m:1670 type=5 (00000000/0)
[Router]
[FULLCONE]
69.059720 @/SourceCache/VideoConference/VideoConference-415.22/Video Conference/VideoConferenceGlobalObjects.m:1672 type=5 (00000000/0)
[CommNAT Result: 0x00000102
70.160706 @:0 type=5 (00000000/60)
[Detected bandwidth (kbits/s): 2317 up, 2317 down. (00000000)
70.164156 @/SourceCache/VideoConference/VideoConference-415.22/Video Conference/VideoConferenceMultiController.m:2423 type=5 (00000000/0)
[Start Conference With UserID: u0]
Thanks in advance for any suggestions.
<Edited by Host>

Hi,
The "Share a Public IP" can be a bit misleading if your Modem routes (does DHCP itself)
If you turn this Off (Bridge Mode) the IP address come from the previous device that issues IPs
From a Cable Modem this is likely to be from the ISP and not likely that you have two Public IPs
Also the range you describe seems to be from a LAN Device (one that issues IPs in one of three ranges of which 10.xxx.xxx.xxx is one)
However although I have not seen it done I presume the Apple Airport devices can be set to Manually (Static routing). They can be set to use the 10.xxx.xxx.xxx range as well (with the early ones it was the default range).
With the Share A Public IP Off I don't think you get a NAT tab on that same screen.
However in the NAT tab is the Port Mapping Protocol which is Apple's version of UPnP (very basic comparison).
This should be on for two devices to use the same ports.
See pic
If the modem is the device that is issuing IPs then this should have UPnP Enabled.
You need this rather than Port Forwarding (Or Triggering) as the Screen Share uses a Random port which cannot be forwarded or Triggered).
A Video that drops out with the 10 secs error points to features in routing devices that "protect" you from getting overloaded with a data stream.
Look for DOS or SPI (Denial of Service or Stateful Packet Inspection) which may be separate items and standalone or be included in any firewall the device may have.
At this point I am confused.
You say Comcast which I believe is cable Only meaning their Modem does not do DHCP and passes the Public IP to the Time Capsule.
Yet you say the Time Capsule is not doing DHCP (Share a Public IP).
What do you have at the top of the Screen ?
This pics shows Ethernet to a Cable Router which gives a Public IP starting 70.xxx.xxx.xxx
And you also confirm that the Share a Public IP box in the Pic is set to Static Routing and from there you are using the 10.xxx.xxx.xxx range ?
9:39 PM Wednesday; July 14, 2010
Please, if posting Logs, do not post any Log info after the line "Binary Images for iChat"

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.

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

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.

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 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 to one machine fails for short account name

I have an iMac, MacBook and a Mac mini. Screen sharing works between any and all of them except that in the case of the mac mini, the 'short' account name fails. Only when I use the "full name" (and the same password) does it work.
File sharing with the short names works just fine. It is only screen sharing, and only when connecting to that one machine.
***?

You have to forgive me
Fix is hoping for a lot
I'm just offering up something you can do to make you feel better
In all seriousness
It continues to be a pain
We have about five machines and do a lot of screensharing
With every OS update I pray that this gets sorted out

Failed to establish Screen Sharing

Hi,
I'm in India on my home wifi network. Following is the setting of my macbook.
OS 10.5.8
iChat 4.0.8(619)
Firewall: Allow all incoming connections
Screen Sharing: On for all users (Any one can request screen sharing is checked)
My bro is is VA, USA. He is behind a wifi network..
OS 10.6
iChat 5.0(741)
Firewall: Allow all incoming connections
Screen Sharing: On for all users (Any one can request screen sharing is checked)
When signed in to google account we can voice and video chat but screen sharing fails.
When signed in to .mac account screen sharing just starts with a message on the screen but immediately stops again.
Any help?

Hi,
There are many Buffalo devices listed here http://portforward.com/routers.htm
Click on yours.
Click the Dismiss item on the next page.
Choose iChat in the next.
The page you arrive at is for Pics and Default access info only.
Near the top it will tell what IP is the default to use in a Web Browser.
Many also require User IDs ad Passwords and these are listed.
For Screen Sharing to work you will need UPnP
The page will tell you how to do Port Forwarding but don't do that.
Check all the Menu items, tabs and links that appear on the pages to see if you have UPnP.
Enable it if it is Not Enabled and Save Settings.
The hostel end may have problems.
iChat in Video is somewhat Bandwidth hungry. With lots of others doing things on the internet they may not get enough Bandwidth to Video.
7:26 PM Sunday; September 13, 2009
Please, if posting Logs, do not post any Log info after the line "Binary Images for iChat"

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.

TS4196 screen sharing fails to start when i am using messages beta and other party is using ichat

anyone having issues screen sharing fails to start when i am using Messages beta and other party is using iChat?

Sorry for the short answer, but was your problem similar at all to this?

Screen Sharing Failed to Connect Please Try Again with different credentials

Very strange behavior from Screen Sharing - which I have been using across multiple Mac system and OS versions for years. I have one system that is 10.8, several that are 10.7 and a 10.6. Most of the time it works as expected - the weird thing is that every so often I get a failure and please try different credientials but that do not get any way to enter other credientials.
Even stranger - sometimes - after failing to connect mulitple times - if I connect with LogMeIn - then Screen Sharing works.
In some cases I am able to connect no issue - then disconnect - and opps need to check something else and unable to reconnect.
I have looked in KeyChain access - and preferances - and other places - cannot find where Screen Sharing is storing info bits that might need deleting to clean things up.

Perhaps stranger still - one of the systems - a Mac OS X Server 10.7 - which is headless - had not been rebooted for nearly 100 days - so I rebooted it - and no can connect to all remote systems on the first try - repeatedly - even though I have not changed anything on or rebooted any of the others. And the OS X Server is NOT my domain, or DNS server.
except now Time Machine is not finding the backup disk on the server - which has been workign for the past year - and I did not delete the time machine stored keychains. ugh.

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

Authentication failed on screen sharing

Similar Messages

Maybe you are looking for