Remove an entry in Screen Sharing

Hello,
I added many entries into "My Computers" in Screen Sharing.
I would like to remove some of them
How to remove them ?
Rgs

Hey there,
One way you could do this is to trash this file located at Users/yourusername/Library/Preferences/com.apple.ScreenSharing.plist, which will remove all of them entirely. Or you could open it up in Property List Editor, which is available as a part of Apple Developer Tools or you could find one of your own Editors off the Internet. Once you have that, you can open up and edit the parts you believe you no longer need. Hope this helps.
B-rock

Similar Messages

  • Remove little window "my computer" screen when screen sharing with iChat?

    Anyone know if it is possible to remove or minimize the little window when screen sharing with iChat? if you try to drag it off the screen, it just pops back. It does not seem possible to close it without getting booted out of the screen sharing.

    As the "little Screen" is either your Desktop or the other Desktop depending which you have as the current one you are working in it seems silly to have no access to changing back and forth.
    But as you say or rather imply it does sometimes occupy the space you want someone at the other end to see and you can not access that part of the screen or if the other end is trying to show you something it can be hidden my your own desktop.
    AT present Not Even Chax does what you want.
    7:31 PM Monday; March 10, 2008

  • No audio/video/screen-sharing problem in iChat 4.0

    I've been using iChat for years (since its original release) and since upgrading to 10.5 I can no longer audio or video chat; and the new screen-sharing option doesn't work either.
    I connect to the net through an AirPort wireless network, which is connected to an ADSL Nation X-Modem/Router. I have a 2Mbps connection. As far as I know all the required ports are open on the router. My friend has the same ISP as me (Force9) and has made sure he has the same ports open on his router too.
    I've adjusted my iChat settings to port 443 with no SSL and a Bandwidth limit of 500 Kbps in iChat; and QuickTime settings to 1.5 Mbps in System Preferences. I've read other discussions on this forum suggesting these options.
    However, nothing seems to work. I can't even get audio and video to work across Bonjour on my home network any more. I'd be grateful for any help anyone can offer.
    Below is my error report:
    Date/Time: 2007-12-27 23:38:05.737 +0000
    OS Version: 10.5.1 (Build 9B18)
    Report Version: 4
    iChat Connection Log:
    2007-12-27 23:37:16 +0000: AVChat started with ID 1971558074.
    2007-12-27 23:37:16 +0000: [email protected]: State change from AVChatNoState to AVChatStateWaiting.
    2007-12-27 23:37:16 +0000: 0x1c023ad0: State change from AVChatNoState to AVChatStateInvited.
    2007-12-27 23:37:27 +0000: 0x1c023ad0: State change from AVChatStateInvited to AVChatStateConnecting.
    2007-12-27 23:37:27 +0000: [email protected]: State change from AVChatStateWaiting to AVChatStateConnecting.
    2007-12-27 23:38:03 +0000: 0x1c023ad0: State change from AVChatStateConnecting to AVChatStateEnded.
    2007-12-27 23:38:03 +0000: 0x1c023ad0: Error -8 (Did not receive a response from 0x1c023ad0.)
    2007-12-27 23:38:03 +0000: [email protected]: State change from AVChatStateConnecting to AVChatStateEnded.
    2007-12-27 23:38:03 +0000: [email protected]: Error -8 (Did not receive a response from 0x1c023ad0.)
    Video Conference Error Report:
    56.475488 @SIP/SIP.c:2719 type=4 (900A0015/0)
    [SIPConnectIPPort failed]
    63.478531 @SIP/SIP.c:2719 type=4 (900A0015/0)
    [SIPConnectIPPort failed]
    239.541694 @SIP/SIP.c:2719 type=4 (900A0015/0)
    [SIPConnectIPPort failed]
    246.544032 @SIP/SIP.c:2719 type=4 (900A0015/0)
    [SIPConnectIPPort failed]
    Video Conference Support Report:
    6.263009 @Video Conference/VCInitiateConference.m:1582 type=2 (00000000/0)
    [Connection Data for call id: 1 returns 1
    10.836896 @Video Conference/VCInitiateConference.m:1582 type=2 (00000000/0)
    [Connection Data for call id: 2 returns 1
    39.051949 @Video Conference/VCInitiateConference.m:1582 type=2 (00000000/0)
    [Connection Data for call id: 3 returns 1
    43.450824 @VCChannel/VCChannel.m:252 type=2 (00000000/0)
    [VCChannel prepareConnectionWithRemoteConnectionData - remote VCConnectionData: 1]
    43.453466 @Video Conference/VCInitiateConference.m:1597 type=2 (00000000/0)
    [Prepare Connection With Remote Data - remote VCConnectionData: 1, local VCConnectionData: 1
    43.455651 @Video Conference/VCInitiateConference.m:1701 type=2 (00000000/0)
    [Initiate Conference To User: u0 with Remote VCConnectionData: 1 with Local Connection Data: 1 conferenceSettings: 1]
    54.474920 @SIP/Transport.c:2353 type=1 (00000000/0)
    [INVITE sip:user@rip:16402 SIP/2.0
    Via: SIP/2.0/UDP lip:16402;branch=z9hG4bK1c92401a6e250ccf
    Max-Forwards: 70
    To: "u0" <sip:user@rip:16402>
    From: "0" <sip:user@lip:16402>;tag=1537014430
    Call-ID: 4860ab94-b4d4-11dc-92ee-be9358c74012@lip
    CSeq: 1 INVITE
    Contact: <sip:user@lip:16402>;isfocus
    User-Agent: Viceroy 1.3
    Content-Type: application/sdp
    Content-Length: 399
    v=0
    o=howardberry 0 0 IN IP4 lip
    s=0
    c=IN IP4 lip
    b=AS:2147483647
    t=0 0
    a=hwi:17412:2:2330
    a=iChatEncryption:NO
    a=bandwidthDetection:YES
    m=audio 16402 RTP/AVP 110 121 12 3 0
    a=rtcp:16402
    a=rtpmap:121 speex/16000
    a=rtpmap:122 speex/8000
    a=rtpmap:113 X-AAC_LD/44100
    a=rtpmap:110 X-AAC_LD/22050
    a=rtpmap:3 GSM/8000
    a=rtpmap:0 PCMU/8000
    a=rtpID:3253226420
    54.975547 @SIP/Transport.c:2353 type=1 (00000000/0)
    [INVITE sip:user@rip:16402 SIP/2.0
    Via: SIP/2.0/UDP lip:16402;branch=z9hG4bK1c92401a6e250ccf
    Max-Forwards: 70
    To: "u0" <sip:user@rip:16402>
    From: "0" <sip:user@lip:16402>;tag=1537014430
    Call-ID: 4860ab94-b4d4-11dc-92ee-be9358c74012@lip
    CSeq: 1 INVITE
    Contact: <sip:user@lip:16402>;isfocus
    User-Agent: Viceroy 1.3
    Content-Type: application/sdp
    Content-Length: 399
    v=0
    o=howardberry 0 0 IN IP4 lip
    s=0
    c=IN IP4 lip
    b=AS:2147483647
    t=0 0
    a=hwi:17412:2:2330
    a=iChatEncryption:NO
    a=bandwidthDetection:YES
    m=audio 16402 RTP/AVP 110 121 12 3 0
    a=rtcp:16402
    a=rtpmap:121 speex/16000
    a=rtpmap:122 speex/8000
    a=rtpmap:113 X-AAC_LD/44100
    a=rtpmap:110 X-AAC_LD/22050
    a=rtpmap:3 GSM/8000
    a=rtpmap:0 PCMU/8000
    a=rtpID:3253226420
    55.976046 @SIP/Transport.c:2353 type=1 (00000000/0)
    [INVITE sip:user@rip:16402 SIP/2.0
    Via: SIP/2.0/UDP lip:16402;branch=z9hG4bK1c92401a6e250ccf
    Max-Forwards: 70
    To: "u0" <sip:user@rip:16402>
    From: "0" <sip:user@lip:16402>;tag=1537014430
    Call-ID: 4860ab94-b4d4-11dc-92ee-be9358c74012@lip
    CSeq: 1 INVITE
    Contact: <sip:user@lip:16402>;isfocus
    User-Agent: Viceroy 1.3
    Content-Type: application/sdp
    Content-Length: 399
    v=0
    o=howardberry 0 0 IN IP4 lip
    s=0
    c=IN IP4 lip
    b=AS:2147483647
    t=0 0
    a=hwi:17412:2:2330
    a=iChatEncryption:NO
    a=bandwidthDetection:YES
    m=audio 16402 RTP/AVP 110 121 12 3 0
    a=rtcp:16402
    a=rtpmap:121 speex/16000
    a=rtpmap:122 speex/8000
    a=rtpmap:113 X-AAC_LD/44100
    a=rtpmap:110 X-AAC_LD/22050
    a=rtpmap:3 GSM/8000
    a=rtpmap:0 PCMU/8000
    a=rtpID:3253226420
    61.478080 @SIP/Transport.c:2353 type=1 (00000000/0)
    [INVITE sip:user@rip:50431 SIP/2.0
    Via: SIP/2.0/UDP lip:16402;branch=z9hG4bK1cc0b6ce6e567e1e
    Max-Forwards: 70
    To: "u0" <sip:user@rip:50431>
    From: "0" <sip:user@lip:16402>;tag=1593623839
    Call-ID: 4c8d2436-b4d4-11dc-92ee-eb3fab0f4012@lip
    CSeq: 1 INVITE
    Contact: <sip:user@lip:16402>;isfocus
    User-Agent: Viceroy 1.3
    Content-Type: application/sdp
    Content-Length: 399
    v=0
    o=howardberry 0 0 IN IP4 lip
    s=0
    c=IN IP4 lip
    b=AS:2147483647
    t=0 0
    a=hwi:17412:2:2330
    a=iChatEncryption:NO
    a=bandwidthDetection:YES
    m=audio 16402 RTP/AVP 110 121 12 3 0
    a=rtcp:16402
    a=rtpmap:121 speex/16000
    a=rtpmap:122 speex/8000
    a=rtpmap:113 X-AAC_LD/44100
    a=rtpmap:110 X-AAC_LD/22050
    a=rtpmap:3 GSM/8000
    a=rtpmap:0 PCMU/8000
    a=rtpID:3253226420
    61.978667 @SIP/Transport.c:2353 type=1 (00000000/0)
    [INVITE sip:user@rip:50431 SIP/2.0
    Via: SIP/2.0/UDP lip:16402;branch=z9hG4bK1cc0b6ce6e567e1e
    Max-Forwards: 70
    To: "u0" <sip:user@rip:50431>
    From: "0" <sip:user@lip:16402>;tag=1593623839
    Call-ID: 4c8d2436-b4d4-11dc-92ee-eb3fab0f4012@lip
    CSeq: 1 INVITE
    Contact: <sip:user@lip:16402>;isfocus
    User-Agent: Viceroy 1.3
    Content-Type: application/sdp
    Content-Length: 399
    v=0
    o=howardberry 0 0 IN IP4 lip
    s=0
    c=IN IP4 lip
    b=AS:2147483647
    t=0 0
    a=hwi:17412:2:2330
    a=iChatEncryption:NO
    a=bandwidthDetection:YES
    m=audio 16402 RTP/AVP 110 121 12 3 0
    a=rtcp:16402
    a=rtpmap:121 speex/16000
    a=rtpmap:122 speex/8000
    a=rtpmap:113 X-AAC_LD/44100
    a=rtpmap:110 X-AAC_LD/22050
    a=rtpmap:3 GSM/8000
    a=rtpmap:0 PCMU/8000
    a=rtpID:3253226420
    62.979288 @SIP/Transport.c:2353 type=1 (00000000/0)
    [INVITE sip:user@rip:50431 SIP/2.0
    Via: SIP/2.0/UDP lip:16402;branch=z9hG4bK1cc0b6ce6e567e1e
    Max-Forwards: 70
    To: "u0" <sip:user@rip:50431>
    From: "0" <sip:user@lip:16402>;tag=1593623839
    Call-ID: 4c8d2436-b4d4-11dc-92ee-eb3fab0f4012@lip
    CSeq: 1 INVITE
    Contact: <sip:user@lip:16402>;isfocus
    User-Agent: Viceroy 1.3
    Content-Type: application/sdp
    Content-Length: 399
    v=0
    o=howardberry 0 0 IN IP4 lip
    s=0
    c=IN IP4 lip
    b=AS:2147483647
    t=0 0
    a=hwi:17412:2:2330
    a=iChatEncryption:NO
    a=bandwidthDetection:YES
    m=audio 16402 RTP/AVP 110 121 12 3 0
    a=rtcp:16402
    a=rtpmap:121 speex/16000
    a=rtpmap:122 speex/8000
    a=rtpmap:113 X-AAC_LD/44100
    a=rtpmap:110 X-AAC_LD/22050
    a=rtpmap:3 GSM/8000
    a=rtpmap:0 PCMU/8000
    a=rtpID:3253226420
    221.875355 @Video Conference/VCInitiateConference.m:1582 type=2 (00000000/0)
    [Connection Data for call id: 5 returns 1
    226.522875 @Video Conference/VCInitiateConference.m:1597 type=2 (00000000/0)
    [Prepare Connection With Remote Data - remote VCConnectionData: 1, local VCConnectionData: 1
    226.527478 @Video Conference/VCInitiateConference.m:1701 type=2 (00000000/0)
    [Initiate Conference To User: u0 with Remote VCConnectionData: 1 with Local Connection Data: 1 conferenceSettings: 1]
    237.541363 @SIP/Transport.c:2353 type=1 (00000000/0)
    [INVITE sip:user@rip:16402 SIP/2.0
    Via: SIP/2.0/UDP lip:16402;branch=z9hG4bK7c8b8e053141eae8
    Max-Forwards: 70
    To: "u0" <sip:user@rip:16402>
    From: "0" <sip:user@lip:16402>;tag=538595231
    Call-ID: b57cadae-b4d4-11dc-92ee-d6e5d2954012@lip
    CSeq: 1 INVITE
    Contact: <sip:user@lip:16402>;isfocus
    User-Agent: Viceroy 1.3
    Content-Type: application/sdp
    Content-Length: 734
    v=0
    o=howardberry 0 0 IN IP4 lip
    s=0
    c=IN IP4 lip
    b=AS:2147483647
    t=0 0
    a=hwi:17412:2:2330
    a=iChatEncryption:NO
    a=bandwidthDetection:YES
    m=audio 16402 RTP/AVP 110 121 12 3 0
    a=rtcp:16402
    a=rtpmap:121 speex/16000
    a=rtpmap:122 speex/8000
    a=rtpmap:113 X-AAC_LD/44100
    a=rtpmap:110 X-AAC_LD/22050
    a=rtpmap:3 GSM/8000
    a=rtpmap:0 PCMU/8000
    a=rtpID:3830094153
    m=video 16402 RTP/AVP 123 126 34
    a=rtcp:16402
    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 16402 VIDEO 16402
    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:196956011
    238.041987 @SIP/Transport.c:2353 type=1 (00000000/0)
    [INVITE sip:user@rip:16402 SIP/2.0
    Via: SIP/2.0/UDP lip:16402;branch=z9hG4bK7c8b8e053141eae8
    Max-Forwards: 70
    To: "u0" <sip:user@rip:16402>
    From: "0" <sip:user@lip:16402>;tag=538595231
    Call-ID: b57cadae-b4d4-11dc-92ee-d6e5d2954012@lip
    CSeq: 1 INVITE
    Contact: <sip:user@lip:16402>;isfocus
    User-Agent: Viceroy 1.3
    Content-Type: application/sdp
    Content-Length: 734
    v=0
    o=howardberry 0 0 IN IP4 lip
    s=0
    c=IN IP4 lip
    b=AS:2147483647
    t=0 0
    a=hwi:17412:2:2330
    a=iChatEncryption:NO
    a=bandwidthDetection:YES
    m=audio 16402 RTP/AVP 110 121 12 3 0
    a=rtcp:16402
    a=rtpmap:121 speex/16000
    a=rtpmap:122 speex/8000
    a=rtpmap:113 X-AAC_LD/44100
    a=rtpmap:110 X-AAC_LD/22050
    a=rtpmap:3 GSM/8000
    a=rtpmap:0 PCMU/8000
    a=rtpID:3830094153
    m=video 16402 RTP/AVP 123 126 34
    a=rtcp:16402
    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 16402 VIDEO 16402
    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:196956011
    239.042442 @SIP/Transport.c:2353 type=1 (00000000/0)
    [INVITE sip:user@rip:16402 SIP/2.0
    Via: SIP/2.0/UDP lip:16402;branch=z9hG4bK7c8b8e053141eae8
    Max-Forwards: 70
    To: "u0" <sip:user@rip:16402>
    From: "0" <sip:user@lip:16402>;tag=538595231
    Call-ID: b57cadae-b4d4-11dc-92ee-d6e5d2954012@lip
    CSeq: 1 INVITE
    Contact: <sip:user@lip:16402>;isfocus
    User-Agent: Viceroy 1.3
    Content-Type: application/sdp
    Content-Length: 734
    v=0
    o=howardberry 0 0 IN IP4 lip
    s=0
    c=IN IP4 lip
    b=AS:2147483647
    t=0 0
    a=hwi:17412:2:2330
    a=iChatEncryption:NO
    a=bandwidthDetection:YES
    m=audio 16402 RTP/AVP 110 121 12 3 0
    a=rtcp:16402
    a=rtpmap:121 speex/16000
    a=rtpmap:122 speex/8000
    a=rtpmap:113 X-AAC_LD/44100
    a=rtpmap:110 X-AAC_LD/22050
    a=rtpmap:3 GSM/8000
    a=rtpmap:0 PCMU/8000
    a=rtpID:3830094153
    m=video 16402 RTP/AVP 123 126 34
    a=rtcp:16402
    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 16402 VIDEO 16402
    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:196956011
    244.543484 @SIP/Transport.c:2353 type=1 (00000000/0)
    [INVITE sip:user@rip:50468 SIP/2.0
    Via: SIP/2.0/UDP lip:16402;branch=z9hG4bK47f51d1236ccf090
    Max-Forwards: 70
    To: "u0" <sip:user@rip:50468>
    From: "0" <sip:user@lip:16402>;tag=289044260
    Call-ID: b9a91160-b4d4-11dc-92ee-a8a976dd4012@lip
    CSeq: 1 INVITE
    Contact: <sip:user@lip:16402>;isfocus
    User-Agent: Viceroy 1.3
    Content-Type: application/sdp
    Content-Length: 734
    v=0
    o=howardberry 0 0 IN IP4 lip
    s=0
    c=IN IP4 lip
    b=AS:2147483647
    t=0 0
    a=hwi:17412:2:2330
    a=iChatEncryption:NO
    a=bandwidthDetection:YES
    m=audio 16402 RTP/AVP 110 121 12 3 0
    a=rtcp:16402
    a=rtpmap:121 speex/16000
    a=rtpmap:122 speex/8000
    a=rtpmap:113 X-AAC_LD/44100
    a=rtpmap:110 X-AAC_LD/22050
    a=rtpmap:3 GSM/8000
    a=rtpmap:0 PCMU/8000
    a=rtpID:3830094153
    m=video 16402 RTP/AVP 123 126 34
    a=rtcp:16402
    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 16402 VIDEO 16402
    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:196956011
    245.044025 @SIP/Transport.c:2353 type=1 (00000000/0)
    [INVITE sip:user@rip:50468 SIP/2.0
    Via: SIP/2.0/UDP lip:16402;branch=z9hG4bK47f51d1236ccf090
    Max-Forwards: 70
    To: "u0" <sip:user@rip:50468>
    From: "0" <sip:user@lip:16402>;tag=289044260
    Call-ID: b9a91160-b4d4-11dc-92ee-a8a976dd4012@lip
    CSeq: 1 INVITE
    Contact: <sip:user@lip:16402>;isfocus
    User-Agent: Viceroy 1.3
    Content-Type: application/sdp
    Content-Length: 734
    v=0
    o=howardberry 0 0 IN IP4 lip
    s=0
    c=IN IP4 lip
    b=AS:2147483647
    t=0 0
    a=hwi:17412:2:2330
    a=iChatEncryption:NO
    a=bandwidthDetection:YES
    m=audio 16402 RTP/AVP 110 121 12 3 0
    a=rtcp:16402
    a=rtpmap:121 speex/16000
    a=rtpmap:122 speex/8000
    a=rtpmap:113 X-AAC_LD/44100
    a=rtpmap:110 X-AAC_LD/22050
    a=rtpmap:3 GSM/8000
    a=rtpmap:0 PCMU/8000
    a=rtpID:3830094153
    m=video 16402 RTP/AVP 123 126 34
    a=rtcp:16402
    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 16402 VIDEO 16402
    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:196956011
    246.044704 @SIP/Transport.c:2353 type=1 (00000000/0)
    [INVITE sip:user@rip:50468 SIP/2.0
    Via: SIP/2.0/UDP lip:16402;branch=z9hG4bK47f51d1236ccf090
    Max-Forwards: 70
    To: "u0" <sip:user@rip:50468>
    From: "0" <sip:user@lip:16402>;tag=289044260
    Call-ID: b9a91160-b4d4-11dc-92ee-a8a976dd4012@lip
    CSeq: 1 INVITE
    Contact: <sip:user@lip:16402>;isfocus
    User-Agent: Viceroy 1.3
    Content-Type: application/sdp
    Content-Length: 734
    v=0
    o=howardberry 0 0 IN IP4 lip
    s=0
    c=IN IP4 lip
    b=AS:2147483647
    t=0 0
    a=hwi:17412:2:2330
    a=iChatEncryption:NO
    a=bandwidthDetection:YES
    m=audio 16402 RTP/AVP 110 121 12 3 0
    a=rtcp:16402
    a=rtpmap:121 speex/16000
    a=rtpmap:122 speex/8000
    a=rtpmap:113 X-AAC_LD/44100
    a=rtpmap:110 X-AAC_LD/22050
    a=rtpmap:3 GSM/8000
    a=rtpmap:0 PCMU/8000
    a=rtpID:3830094153
    m=video 16402 RTP/AVP 123 126 34
    a=rtcp:16402
    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 16402 VIDEO 16402
    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:196956011
    Video Conference User Report:
    0.000000 @:0 type=5 (00000000/16402)
    [Local SIP port]
    0.000017 @:0 type=5 (00000000/16402)
    [Local SIP port]
    0.000032 @:0 type=5 (00000000/16402)
    [Local SIP port]
    0.000064 @:0 type=5 (00000000/16402)
    [Local SIP port]
    0.000080 @:0 type=5 (00000000/16402)
    [Local SIP port]
    252.557643 @Video Conference/VideoConferenceMultiController.m:1476 type=5 (00000000/0)
    [IP And Port Data With Caller IP And Port Data: Obtained 400 bytes of local IP and port data (10 entries). Remote data was 0 bytes (0 entries).
    []

    Hi,
    Technically it should not matter if you are using AIM or @Mac names.
    However you have solved that bit.
    The Screen Sharing part uses three ports.
    Two randomly picked ports for the Screen Sharing and the same A/V port for the Audio component. As the Airport is normally set to Share An IP and does NAT on the fly so to speak this also should not be a problem
    The ADSLNAtion site is a bit behind on it's Airport page
    http://www.adslnation.com/support/knowledgebase/ht007.php as it shows the older Firmware pics.
    I found the new page
    http://www.adslnation.com/knowledgebase/xmodem+airport-11n.php
    This says that the DNS server info in the Airport needs to be removed.
    It is not clear if this is a variation for the X-Modem M3
    Very few of the posts here http://forum.adslnation.com/viewforum.php?f=3 are after Leopard came out and nothing appears to be about iChat.
    So it would somewhat depend if the Airport is Sharing and IP or is Static to the computer and Port Mapping used.
    1:56 PM Saturday; December 29, 2007

  • Lion Screen Sharing Asks?

    I'm trying to share the screen of my Lion MacMini located in the other room. Both machines are Lion 10.7.1.
    Regardless of which account I use to connect to the macMini, I'm presented with a dialog that says "Ask to share the display. 'mini User' is using the display". This is a hassle, because no one is sitting at that machine.
    When I attempt to share the screen with other machines, I can start screen sharing without intervention on the far end.
    What determines whether someone needs to be sitting at the machine to initiate Screen Sharing on it?

    Scratch that: there is still something wrong. Now, when "Connected as" mini User, I still must obtain permission from someone sitting there to start screen sharing, even though now, no windows are open.
    So, as an alternative, I click "Virtual Display" and... and I get logged into _another_ user's account, the one which the machine defaults to because that password is saved in the keychain.
    Furthermore, when I click "Ask" and walk over to the remote machine, it says the _other_ user is requesting access, even though I am "Connected As" the correct user.
    So to summarize: I cannot start screen sharing in the account that I need to share without intervention -- even with no applications open, and virtual sharing automatically logs into some _other_ user's account.
    Next, I opened Keychain Access and removed all entries for the server I'm trying to contact. Then, I "Connect As" and enter the appropriate user name "mini user" and _no_ password, since that account does not have a password. The file sharing connection proceeds. I click "Share Screen" and attempt to use the same user name and _no_password, and the system refuses to accept it.
    So, perhaps for Lion Screen Sharing to work without intervention, accounts _must_ have passwords?
    No, that's not it either. I went and set a password for mini User, and can log out and log in successfully there. I can "Connect As" with the new password, successfully. But when I try Screen Sharing, even with the correct user name and password, I get an authorization failure. I simply cannot start Screen Sharing without intervention, regardless of what I try.
    But wait: maybe the problem was that I was not _authorized_ to screen share? So I started up the "Sharing" control panel and sure enough, only "administrators" are allowed to share the screen, and mini User is a Standard User. I unlock the settings using an admin log-in and click the "+" button... and nothing happens. Darn. So I switch _to_ that Admin account and in Sharing, click "+", and I'm able to add mini User. OK. Now, when I try to screen share, my credentials are _still_ rejected
    Finally, I started Screen Sharing by logging in as a "Sharing Only" user, to the Virtual Display. I'm presented with a User selection screen. I click mini User, no password, and I can see the screen.
    Gee, this all used to work flawlessly in Snow Leopard.

  • Screen sharing security question

    I recently set up my imac to allow screen sharing from my MBP. On my iMac I randomly see the screen sharing icon appear in the menu bar despite not being connected. Is this normal?
    Also i setup security so that it should only be me that is able to connect via password to my iMac, yet there is aslo an option to connect as a guest which connects & shows the imac screen & allows me to do things.
    I thought the whole point of setting access only to me was that no-one else ( eg guest) could connect.
    i am a bit baffled here, can anyone help me out?
    TIA,
    john

    I would not consider the presence of the screen sharing icon normal. I encourage you to open terminal and run the command
    netstat | grep vnc
    the next time you see it. This will return either nothing (bringing you back to the prompt ending in $, or return a line such as this:
    tcp4 0 39 10.0.42.116.vnc-server 10.0.42.243.54233 ESTABLISHED
    In this case, my Macintosh is 10.0.42.116, and the computer connected to it is 10.0.42.243.
    By this method you can determine if there is a glitch causing the icon to appear or if there is actually a connection being made to your Macintosh.
    What you are probably experiencing with the guest account is a bit of confusion related to how Finder thinks of computers.
    The Guest/User Account is not for Screen Sharing, but for File Sharing.
    When you clicked "Share Screen..." the first time, regardless of if you connected to file sharing as Guest or Registered User, you got a box requesting "the username and password to share the screen of (computer name)." There, you probably selected remember password in keychain, and that is why you are not being prompted again, and why you are connecting to screen sharing as a guest. (You're actually connecting to screen sharing as your registered user, but you are connected to file sharing as a guest).
    To change this behavior, (on the client Mac) navigate to Applications, Utilities, Keychain Access. There, you will find an entry with a blue @ sign as an icon, and your destination PC's name. The Kind will be Network Address and when you select the line the "Where" in the info viewer panel will begin with vnc://. When you find this line, press the delete key to remove the saved password, and don't tick the "remember" checkbox again.

  • Screen Sharing Problems/Questions

    Greetings!
    I really like the screen sharing feature of Leopard, however, it has a serious problem, but probably only for me, as I can't find anywhere on the internet where my problem is mentioned.
    Whenever I attempt to drag ANYTHING on the other person's computer, the mouse pointer freaks out and jumps to a random place on the screen, or even offscreen entirely. After it has completed its jump, it drops the drag leaving the window I was dragging in the wrong place, or moving a list of files to the wrong place.
    This renders screen sharing basically unusable for me.
    I've confirmed this bug, both ways, with two seperate systems. I can't drag on their machine and they can't drag on mine. All three of us turned off spaces and removed any external monitors to make sure that wasn't the problem. None of us are on an internal network... this was all done with iChat over Google talk on an internet connection.
    Can anyone confirm this bug?
    Has anyone found a fix for this bug?
    Thanks!
    -Sastira

    Umm.
    I am not sure you are doing it right.
    Go to the File Menu.
    iChat Theatre item.
    Navigate to File (Can be Movie or Pic or PowerPoint etc)
    Click the share button.
    The iPhoto Share works solely with iPhoto but the principles are the same.
    There should not be any Dragging involved.
    TO Send an Item as a file or include a pic in a text chat is different.
    In that case it is a quetion of dragging the item the the Text entry field during a Text chat or dropping it on a Buddy in the Buddy list.
    Sometimes with a New buddy (freshly added) the second option of Dropping it on their name can be more successful.
    10:36 PM Thursday; November 22, 2007

  • Screen sharing hangs and requires restart of target macintosh

    Discovered a recurring problem with screen sharing in Mountain Lion.  Note I have Apple Remote Desktop installed on many of my machines, as well as the build in VNC Screen Sharing application.  I am able to remotely control a target Mac using ARD, however, issues come up when using Screen Sharing.  The first connection from client Mac to target Mac (both on 10.8) works fine.  However, if I quit the screen share and then try again 15 mins later, screen sharing seems to hang.   The connection attempts to be made, but no dialog box comes up.  At this point, ARD will not connect to the target mac either.  If I use ARD to restart the target mac, a hidden dialog box flashes on my screen (not long enough for me to fully see, but looks like the user/password screen or a varient thereof), followed by a "connection failed" dialgoue on the client.  It seems that on the second connection, the client is flashing a dialog and waiting for a response, but the user does not see the dialogue and cannot respond.
    Not sure what processes to look for on the client.  I have scanned the console and do not see anthing on the client side.  On the target side, it appears the connection is being made, even though the client does not realize it.  This is from the console of the target machine.   By the way, I have replicated this behavior on iMacs and Mac Minis.
    7/31/12 3:42:37.170 PM kdc[52]: Got a canonicalize request for a LKDC realm from 192.168.0.101:54288
    7/31/12 3:42:37.170 PM kdc[52]: LKDC referral to the real LKDC realm name
    7/31/12 3:42:37.170 PM kdc[52]: Got a canonicalize request for a LKDC realm from fe80::ca2a:14ff:fe24:5a23%en0:54289
    7/31/12 3:42:37.170 PM kdc[52]: LKDC referral to the real LKDC realm name
    7/31/12 3:42:37.195 PM kdc[52]: AS-REQ com.apple.idms.appleid.prd.48754677515363427155546442422b5a642b325872413d3d@LKD C:SHA1.3A3F14EB43CCE771F87D6E1E53C5F49DD2E6636A from 192.168.0.101:54290 for krbtgt/LKDC:SHA1.3A3F14EB43CCE771F87D6E1E53C5F49DD2E6636A@LKDC:SHA1.3A3F14EB43C CE771F87D6E1E53C5F49DD2E6636A
    7/31/12 3:42:37.196 PM kdc[52]: UNKNOWN -- com.apple.idms.appleid.prd.48754677515363427155546442422b5a642b325872413d3d@LKD C:SHA1.3A3F14EB43CCE771F87D6E1E53C5F49DD2E6636A: no such entry found in hdb
    7/31/12 3:42:37.196 PM kdc[52]: AS-REQ com.apple.idms.appleid.prd.48754677515363427155546442422b5a642b325872413d3d@LKD C:SHA1.3A3F14EB43CCE771F87D6E1E53C5F49DD2E6636A from fe80::ca2a:14ff:fe24:5a23%en0:54291 for krbtgt/LKDC:SHA1.3A3F14EB43CCE771F87D6E1E53C5F49DD2E6636A@LKDC:SHA1.3A3F14EB43C CE771F87D6E1E53C5F49DD2E6636A
    7/31/12 3:42:37.198 PM kdc[52]: UNKNOWN -- com.apple.idms.appleid.prd.48754677515363427155546442422b5a642b325872413d3d@LKD C:SHA1.3A3F14EB43CCE771F87D6E1E53C5F49DD2E6636A: no such entry found in hdb
    7/31/12 3:42:37.344 PM kdc[52]: AS-REQ 563A9892EA210311A5167D3D71B50ECC2A6170DB@LKDC:SHA1.3A3F14EB43CCE771F87D6E1E53C5 F49DD2E6636A from 192.168.0.101:54292 for krbtgt/LKDC:SHA1.3A3F14EB43CCE771F87D6E1E53C5F49DD2E6636A@LKDC:SHA1.3A3F14EB43C CE771F87D6E1E53C5F49DD2E6636A
    7/31/12 3:42:37.345 PM kdc[52]: UNKNOWN -- 563A9892EA210311A5167D3D71B50ECC2A6170DB@LKDC:SHA1.3A3F14EB43CCE771F87D6E1E53C5 F49DD2E6636A: no such entry found in hdb
    7/31/12 3:42:37.345 PM kdc[52]: AS-REQ 563A9892EA210311A5167D3D71B50ECC2A6170DB@LKDC:SHA1.3A3F14EB43CCE771F87D6E1E53C5 F49DD2E6636A from fe80::ca2a:14ff:fe24:5a23%en0:54293 for krbtgt/LKDC:SHA1.3A3F14EB43CCE771F87D6E1E53C5F49DD2E6636A@LKDC:SHA1.3A3F14EB43C CE771F87D6E1E53C5F49DD2E6636A
    7/31/12 3:42:37.346 PM kdc[52]: UNKNOWN -- 563A9892EA210311A5167D3D71B50ECC2A6170DB@LKDC:SHA1.3A3F14EB43CCE771F87D6E1E53C5 F49DD2E6636A: no such entry found in hdb
    7/31/12 3:42:37.492 PM screensharingd[390]: Authentication: SUCCEEDED :: User Name: logan gershon :: Viewer Address: 192.168.0.101 :: Type: DH
    7/31/12 3:47:43.173 PM WindowServer[81]: Created shield window 0x68 for display 0x04273740
    7/31/12 3:47:43.173 PM WindowServer[81]: device_generate_desktop_screenshot: authw 0x0(0), shield 0x0(0)
    7/31/12 3:47:43.181 PM WindowServer[81]: device_generate_lock_screen_screenshot: authw 0x0(0), shield 0x0(0)
    ANYBODY HAVE ANY THOUGHTS ON HOW TO GET PAST THIS.  SEEMS LIKE A BUG ON APPLE'S PART.

    I repaired permissions on target mac and removed a corrupted file from preferences (com.apple.VNCpref.txt).  Now working.

  • Airport Extreme is allowing access to screen sharing, file sharing from external IP addresses (some from China, Canada etc)

    How to get control over the ports/port forwarding etc in Airport Extreme?
    How to make AE drop packets to certain ports from external ports.  Or create whitelist/blacklists?
    I figured out where the MAC filtering is!  (It is inside the Timed Access Control).  I wish it had a list of connected device and allowed me to select, name and add them.
    I am getting requests from Chinese IP to the screen sharing ports forwarded to my iMac.  Had requests to other ports as well.  There was one IP address from CANADA too.
    I want to open file sharing for local use only.

    Why is Airport Extreme forwarding requests for screen sharing from external ip addresses to my imac?  I don't have a public address, nor use dynamic dns service, and I have removed the server app (at least I think I have, but Apple Store doesn't think so).

  • Screen Sharing/network problem seems confined to 1 volume. What's the fix?

    I am having a networking problem on one of the volumes of my multi-volumed, three-Mac local area network, and I need a networking guru to identify the specific software file(s), application(s), or system configuration that is the cause of the problem. I have already spent several hours checking and re-checking the various hardware and system preference settings involved, and I have narrowed the problem down to a software corruption issue and/or system configuration issue on one volume.
    I now need someone to identify specifically what the nature of the problem is, and how to eliminate it. I am not looking for a sledgehammer solution that says I should re-install all of the Mac OS X software on the problem volume. That may be held in reserve as a last resort. I'm looking for a more elegant approach, one that points out the specific corrupt files to remove without disturbing everything else.
    Here's some background to set the context. I have a MacBook Pro laptop; a PowerMac iMac G5; and a PowerMac G4 hooked up in a network. All are running Leopard 10.5.8. All have file sharing and screen sharing enabled. Besides being able to connect to each other using registered users, my goal here is for each of the Macs to be able to share the screen of the others upon my demand. Since each of the 3 Macs can theoretically share the screens of the other 2, that makes a total of six possible connections. Five succeed; one does not. That's the problem. I am trying to determine why the iMac G5 cannot share the screen of the MacBook Pro.
    The iMac G5 has no problem sharing the screen of the PowerMac G4. That connection is fast and immediate. But, every time that I hit the Share Screen button on the iMac G5 to try to connect to the MacBook Pro, I get a window with the blue barber pole spinning for two or three minutes as it is allegedly "Connecting to Mac Book Pro," followed by a window with a headline telling me that "Connection Failed to MacBook Pro." The text within that window goes on to say: "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 that your network connection is working properly."
    Well, as I indicated, the PowerMac G4 has no problem sharing the screen of the MacBook Pro, so the Screen Sharing settings on the laptop are correct; and the iMac G5 can share the screen of the PowerMac G4, so its network connection is working properly in that regard. It is only in regards to sharing the screen of the MacBook Pro that the iMac G5 is not working properly.
    The reason why I say that the issue must be unique to the one volume in question, let's call it "iMacG5 Music," is that another Leopard volume on the same computer has no problem whatsoever in sharing the screen of the MacBook Pro. Whenever I boot up in that volume, let's call it "iMacG5 JMB," it makes a network connection with a registered user name immediately, and it is able to share the screen of the MacBook Pro within a second of my issuing the command. In sharp contrast to the success of the iMacG5 JMB volume, the iMacG5 Music is unacceptably slow (several minutes slow!) in making a network connection with the MacBook Pro, and it always fails to share the screen of the MacBook Pro, preferring instead to take about three minutes to attempt the connection, before announcing its failure.
    Since the iMacG5 Music volume makes an immediate network connection to the PowerMac G4, as well as sharing the screen of the PowerMac G4 the moment I ask it to, I have concluded that the hardware of the iMac G5 is just fine. The problem seems confined to the system software and/or associated networking files that are unique to the iMacG5 Music volume. I just don't know what those files could be, or where the problem lies, so I've issued this call for help.
    Let me add one more little twist to this puzzle which baffles me even more. I use external LaCie Firewire drives as clone backups of my Macs. As part of my trouble-shooting process, I booted up from the cloned versions of the iMacG5 JMB volume and the iMacG5 Music volume. What I learned surprised me!
    The iMacG5 JMB clone worked just fine in making a fast network connection to the MacBook Pro, as well as sharing the screen of the MacBook Pro. I expected that. What I did not expect was that the iMacG5 Music clone was also able to make a fast network to the MacBook Pro, as well as share its screen!
    Yes, that's right. It's weird! Screen sharing works OK when I start-up from the clone of the iMacG5 Music volume, but it does not succeed when I boot up on the source itself! I was surprised to find that out, but I'm glad I did.
    (Over the past few days since I executed the last clone, I did use Drive Genius to de-frag the source volume, and maybe that has contributed to the problem I am now encountering. But it's hard to say, since nothing else seems to be amiss.)
    One solution, I suppose, would be to sync the clone back to the source. But, before I do that, I'm just wondering if anyone has a clue as to the nature of this problem on the source volume and what I might do to remedy it—short of re-installing the system software or restoring from the clone. Anyone have any insight to this problem?

    CORRECTION #2:
    Ignore the previous "CORRECTION" post.
    Oops, excuse me, I wrote that sentence correctly the first time.
    I was trying to point out that the ability of the iMac G5 computer to connect quickly and effectively to the PowerMac G4 when booted up into the iMacG5 Music volume was an indication (to me, anyway) that there is nothing wrong with the computer's hardware, nor its network connection ability, but that the problem lay somewhere in the files/settings used to connect to the MacBook Pro, which it cannot accomplish.
    This is what happens when I get engrossed in one of these technical morasses and it ***** me into its vortex all through the night... time for bed.

  • Screen Sharing and Keyboard Commands

    Wow! I just discovered screen sharing on Leopard! I knew I could share across Ichat but didn't realise you could share on your own home network. It works brilliantly but i have a question.
    How do you use keyboard commands whilst sharing?
    For example I want to use quicksilver on the computer I'm controlling from my laptop of course quicksilver becomes active on laptop not the machine I'm controlling.
    In other words how do i direct all keyboard entry to the other machine?

    Sorry,
    but taking a more accurate look to the posts I find the response: in the "Account", at the login option, is avaiable "Show keyboard menu at login" (something similar, my OS is in Italian).
    Thanks anyway!!

  • Screen Sharing and ARD broken

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

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

  • Screen Sharing does not accept my password anymore

    Hi
    I have a headless Mac Mini Server running Snow Leopard Server 10.6.8 and a MacBook Pro  running Snow Leopard 10.6.8. I detected this morning, that I'm not able to connect from the MacBook Pro to my Mac Mini over Screen Sharing. All other services, mail server, iCal server, Address Book server, file sharing over SMB or AFP even connecting over VNC do work.
    - I select the Mac Mini symbol in Finder
    - in column view, I select Share Screen...
    - in the connection dialog, I add the password (username is already predefined)
    - on connect, I get: Authentication failed to "servername". Please verify you have entered the correct name and password.
    I use the same username and password with Server Admin, or logging in locally over VNC so I know this is correct.I'm sure I did not change any settings concerning screen sharing (I did some experiments with WebDAV recently)
    I'm not sure, when I used Screen Sharing the last time, is there a log on the server for this? Could be, the problem was introduced with 10.6.8, but I'm not sure. From the logs I see, Screen Sharing did work on July, 16th. This would narrow it down to: iTunes 10.4 (not likely), Migration Assistant Update for Mac OS X SL 1.0, and Remote Desktop Client Update 3.5.1.
    On the server, I found the following log entries: Jul 21 20:24:33 servername AppleVNCServer[1362]: no such user: user@LKDC:SHA1.xxxxxx: 2
    Any help on this problem?

    Sorry if that didn't come out right. I should have taken the time to get the correct labels off of the user preferences dialogue and it would have made more sense.
    When you create a new user, there are two fields: one for "Full Name" (typically the user's actual name) and another for "Account name" (this usually a more Unix-like user-id). On my system, typing "John Doe" into the Full Name box automatically populates "johndoe" into the Account Name box. I would guess the majority of Mac users will leave that default in there, type in a password and hint and complete creating the account.
    Interestingly, you cannot view the Account name in the user preferences dialogue once the account is created. However, the Account name is used as the name of your Home folder.
    In the past, I've used that Account name when connecting to shares in finder. I just verified that when you open finder and click "Connect As" and choose "Registered User," the authentication prompt in SL automatically has the Account name in the user field. Once connected in finder, all I had to do is click Screen Sharing and it would just open up. Presumably since I had already authenticated via finder. After the last updates, I started getting a password prompt only when attempting to start screen sharing. Finder still worked the same as before, and I was able to view all my folders. Using the Full Name instead of the Account name got me through the second password prompt and opened the screen sharing session.
    I tried authenticating the finder with the Full Name instead, and still got the second authentication prompt when launching screen sharing. Clearly Apple has made a change to screen sharing that no longer passes through your finder authentication.
    If you've somehow already been using the Full Name, and not the Account name, to authenticate in finder, this fix doesn't help you.
    What I meant by "feeling stupid" is going to great lengths to step through a lot of troublesome reboots and whatnot, only to discover that the problem is an arcane, and apparently pointless change with which user name on the account authenticates for two apparently related features (you do go through finder to get to screen sharing!). I certainly didn't mean you were stupid. I wouldn't blame you for having to figure out something Apple changed up after years for no apparent reason. I wasn't real happy about it either after wasting an hour or so figuring it out. My poor choice of words was really meant in the spirit of that "d'oh!" moment when you find the trivial 5 second fix after spending that hour (or days) doing lots of potentially risky stuff to no avail.

  • Upgraded to Yosemite and can no longer remote into my work iMac through screen sharing- it is turned on in settings?

    My screen sharing functionality did not show up in the dock with an updated icon.  It had a question mark- shows my connections but nothing works, I did make sure screen sharing is on and also connected to VPN.  Once I tried to launch screen sharing nothing happens.  Such an elegant solution in Mavericks not does not work. Ugh. Help!

    This is the post that got me set up- I too am running an older version at work vs. Yosemite. As soon as I followed is advice everything worked.
    Upgraded to Yosemite and can no longer remote into my work iMac through screen sharing- it is turned on in settings?
    I believe the location of the "Screen Sharing" app has changed, which explains why if you had it in the dock it has been replaced by a ?
    Don't forget you can launch screen sharing (once your VPN connection is up) by typing in the Safari destination slot vnc://remotemachinename:portnumber  (omit the :port number if you are using the default VNC port, 5900).  This should launch Screen Sharing and put its icon in the dock.  You can drag the Screen Sharing icon to the left of your dock and it will hopefully remain there after you exit Screen Sharing, or you can right-click on the icon when it's running and select Options->Show in Finder to find out its new location and drag its icon to the permanent entries in your dock.
    Hope this helps; worked for me.

  • 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.

  • Having security issue with SL Screen Sharing

    Hello,
    Maybe I am missing some new setting in Snow Leopard that increases screen sharing security, but as it is, screen sharing is now insecure on my network.
    Prior to Snow Leopard I would log into my Mac from another without selecting the "remember this password in my keychain"... after finishing the session, I would again be asked for my password before ropening a new screen sharing session. All machines on the network were Leopard.
    Now, with all macs on the network Snow leopard, on one of the machines I can log on in the morning, work for a while, quit screen sharing, and go back in an hour and start sharing that mac's screen with no password required. Anoyone else can can do this also! I have checked the keychain on the Mac I am viewing from and there does not seem to be an entry there for screen sharing.
    On another of the Snow machines it always asks for the password, but on 2 of them, once I have started viewing another Mac's screen a password is no longer required regardless of the fact that I haven't checked that "remember password" .
    This means that after I leave a Mac from screen sharing it, someone else has full access to that machine just by clicking on the Share Screen button... unless I can close the hole somehow.
    Any ideas or a way to fix this would be appreciated.
    Thanks
    Jamy

    Hi all,
    I just upgraded to Snow 10.6.2 so through 2 separate updates, this security hole on all 3 Macs on my network exists.
    To test it I went to an office and opened a screen on another (Snow Leopard) Mac that was set up to allow users only to connect. I then quit Screen sharing, and returned 3 hours later, only to be able to open the Hard Disk window and return to that Mac's screen without any passwords required. I was very careful not to allow the Keychain to remember me.
    Since I originally posted I see another thread has begun up expressing essentially the same issue.
    I would strongly advise anyone who uses Snow Leopard in a secure environment , at least through 10.6.2, to disable screen sharing or risk unauthorized access, or monitoring, of their Macs from within their networks. Screen Sharing's security settings (if they work at all) do not work on Snow Leopard the same as they worked on Leopard.
    I have not found a fix for this in the 3 weeks since I first noticed it other than to disable it, or restart the Mac I started the session from, then it will ask for a password, but that is hardly an acceptable fix in some secure or corporate environments (akin to having to restart in order to empty the browser cache when accessing webMail lol)
    Regards,
    Jamy

Maybe you are looking for

  • Can a 2012 Mac Pro use a 2012 27in iMac as a primary display?

    Greetings all, I am trying to spec out a trade show configuration. It will have a Mac Pro, A couple iMacs, a few Macbook Pros and a couple iPads. What I need to know is if one of the iMacs can serve as the display for the Mac pPro. The money is not a

  • Inter Company STO without delivery

    Hello All, I have a scenario related to STO for both inter and intra company. Please guide me. a) For intra company , we will be using UB type b) For inter company without delivery, do wehave to use NB type ( correct me if am wrong and can anyone ple

  • How to run import from Unix Oracle 8.0.5 database with Windows Oracle client?

    How to run import from Unix Oracle 8.0.5 database via network with Windows Oracle client? Is it possible? When I try to do it Oracle client just hangs... If not which ones are compatible Aix or Solaris to Unix or it must be a Unix client to connect t

  • Number 2 key on numeric keypad does not work. All other keys work properly.

    The number 2 on the numeric keypad does not work.  Is there some way to clean it?  If not how do I go about ordering another keyboard?

  • CRM 2015 + IFD Error when i add new User

    Hi all member, I have a CRM 2015 Server on-premise after installing and configuring IFD + ADFS, when i want to add a new user i have this error :  InnerException: System.DirectoryServices.DirectoryServicesCOMException (0x80072032): An invalid DN synt