Screen Sharing Fails After 5 Seconds

Heres the deal.
1) Both running Snow Leopard.
2) New Macbook Pro and New iMac top of the line.
3) Fast Bandwidth speeds.
4) Florida <--> Utah.
5) Screen Sharing not working! Steve Jobs ***!
Can anyone help with this issue? And Ralph Johns, if you have any advice please share. I just dont want to hear how it works on your G4/1Ghz Dual Processor! That just wouldn't really help.
Sean

Hi,
So iChat 5
Which increment versions ? (if Updated)
Snow Leopard.
Update to ?
Exactly what is "Fast Bandwidth" where you are ?
In iChat, in the Video menu, have you turned On Screen Sharing ?
In your routing device have you used UPnP to open the ports iChat uses ?
Do you get any error message ?
Does the Connection Doctor say anything in the Errors tab ?
Do you get the Pop up to Send to Apple (Or not) ?
My ageing MacBook Pro of only 3 years of age can also Screen Share
Sometimes I even let it do it to the 8 and 1/2 year old G4/Dual 1Ghz
Your reason for telling me your 2) is to Say "I have the Latest and Greatest, so it should work".
My Reason for telling people my G4 can do it is to say "It can be run on anything above a G4/1Ghz Dual processor, so it's not the Mac or the App"
Notes.
iChat 4 and 5 use 20 ports to do various bits.
One of these, that is used during Screen Sharing is Random. Only UPnP will get around this. (Or Port Mapping Protocol on a Apple Base Station).
My Internet Connection is 8Mbps down (I get about 7.25) and 780 up (I get about 700) and this is average here.
24Mbps both up and down is about top of the Range. 8Mbps down and 500 up is more common.
In Australia anything faster than 128kbps outside of a major town is considered fast.
What is the internet speed like in Utah ?
Are we talking a town or somewhere a bit more remote ?
Re 5)
It's nice that you rate Steve jobs with 3 stars (I presume there are only three stars in your rating system). I don't see what that has to do with Screen Sharing though.
11:07 PM Sunday; June 13, 2010
Please, if posting Logs, do not post any Log info after the line "Binary Images for iChat"

Similar Messages

  • 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 stops after few seconds

    I am screen sharing between two 10.5.8 computers and have successfully shared a number of times between these 2 computers with no network changes. Now, over the past few days, whenever we start a connection, I see computer 2 and I can move the mouse for a few seconds. Then it stops and we get an iChat communication error.
    Settings: Both iChats have bandwidth limit set to none, both have sufficient bandwidth (connector doctor says screen share ok). The error log says no data received in the past 10 secs, but it has not even been 10 sec.
    Any ideas?

    Hi,
    The symptoms of those that do Block this sort of connection is that it seems to connect but gets shut down immediately.
    The 10 Sec Error message means it was connected but the connection was dropped or broken or ended but not by iChat.
    I would also look at Router and Modem settings.
    See if your or the other end has DoS (Denial of Service) or SPI (Stateful Packet Inspection) which can impact on some Chats (Mostly Video normally).
    5:32 PM Friday; October 23, 2009
    Please, if posting Logs, do not post any Log info after the line "Binary Images for iChat"

  • Screen sharing stops after a few seconds of sound

    I am struggling to resolve this. And I thought I was good at this.
    I can do a video chat without incident.
    Quicktime streaming is set to 1.5M
    Bandwidth is set to none
    Screen sharing is allowed in sharing prefs
    I have tried all configurations in the prefs security firewall
    We are both using ADSL routers
    I can connect to others, this is their first attempt.
    I don't believe there is anything other than the default router settings on their router.
    (The remote client has an applescript to automatically accept screen sharing invites)
    Anyone with any more ideas?
    Ralph?!
    JKB

    Hi,
    Is this failing with Error 20 ?
    Sometimes in a the router or modem if you use Port Forwarding then you are your Buddy may be missing the Screen Sharing Port.
    The Screen Sharing part uses a different port to the Audio port.
    As the port for Audio (And therefore Video) are known and can be port Forwarded it is the random Screen Sharing port that can be the problem.
    iChat 3 info http://support.apple.com/kb/HT1507 that includes Bonjour and Jabber info
    iChat 4 info http://support.apple.com/kb/HT2282
    If you are not using (or your Buddy) UPnP then I would change the method of opening the port to that.
    6:14 PM Saturday; June 20, 2009

  • 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 shows a second display

    I have installed a graphics card in my Xserve G5, an ATI Radeon 9200, with a monitor attached with the DVI-cable. When I use Screen Sharing or ARD, then it shows two monitors, the second (without the monitor) being of a lower resolution. I have tried to mirror these, but then I only get the lower resolution. How do I get rid of the fake second display? Once a window gets over there, then I have to use Screen Sharing to relocate it and place it back on the real monitor. Frustrating.

    Hi,
    Change the resolution on the Older OS.
    It is the only workaround we have found at the moment.
    9:05 PM      Wednesday; October 17, 2012
    Please, if posting Logs, do not post any Log info after the line "Binary Images for iChat"
      iMac 2.5Ghz 5i 2011 (Mountain Lion 10.8.2)
     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

  • Screen sharing slow after recent update (june 2012)

    I have installed the latest update that Apple posted a few days ago on multipl computers.  It seems that after the update, screen sharing still works, but instead of bringing up the shared screen in about 5 seconds as it used to, it now takes almost 30 seconds.  This has happened for me on two seperate networks so I believe it is not network related.  Something in the Lion update seems to be culpret.  My 10.6 server machines still can be shared fine.

    I just upgraded all my MACs to Mavericks and have now found this issue.  It isn't unusable but is real close.  I use screenshare every day and all day so this is a real pain.
    Is anyone else seeing this?  Is it worth my while to try VNC?  Is it reasonable to think it may perform better?
    Thanks!

  • 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 Problem after Lion Install

    Greetings,
    After installing Lion on my MacBookPro 17", I am now unable to use screen sharing to access my Mac Mini Server running 10.6.8 server.  When I attempt to make the connection, the Screen Sharing application starts, but I never see a desktop of the Mac Mini.  In the system.log, I see entries that include:
    Screen Sharing[2062]: MVS Codec - bad rectangle size - closing connection
    I've tried rebooting both machines and it doesn't make any difference.
    I've only been able to find one mention of a similar message from someone trying to use desktop sharing in iChat, but it didn't include a fix.
    Anyone have any ideas?
    Thanks,
    Dave

    Apple appears to have solved the problem for me.  :-)
    My scenario was a MacBook Pro running Lion attempting to screen share the screen of a Mac Mini Server (My HTPC) running 10.6.8.  Apple pushed some updates to the Mac Mini on 10.6.8, including:
    Remote Desktop Client Update 3.5.1
    Safari 5.1
    Mac OS X 10.6.8 Supplemental Update 1.0
    iTunes 10.4
    After these updates, I can once again screen share with the Mac Mini.  So, my guess would be something in more likely the Remote Desktop Update or less likely in the Mac OS X 10.6.8 Supplemental Update solved the problem. 
    Check your Software Update on the machines that you're trying to connect to and see if that solves your problems too.
    Thank you Apple!
    Dave

  • Screen Sharing hangs after a few minutes idle

    I've enabled Screen Sharing on my Mac and am connecting from a Windows machine. I've tried connecting with TigerVNC, TightVNC, and TurboVNC clients but after about 10 minutes of no activity on the screen hangs. I'm able to move the mouse pointer, but no screen updates are sent over to the client. Reconnecting works, but it's a nuisance to have to connect every ten minutes
    Any help on how to debug this would be appreciated. I bought my machine a month ago and I have the latest updates installed. Both the Mac and the VNC client are on the same LAN switch.
    Thanks.
    - Amir

    You could try the Vine Server (a different VNC server).
    Vine Server (aka OSXvnc)
    <http://www.versiontracker.com/dyn/moreinfo/macosx/16699>
    Just make sure you either give the Vine Server a different port number (for example port 5901), or you turn off the Mac OS X Screen Sharing VNC server.

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

    Hey,
    I'm failing to get access to a distant computer's screen.
    I'm running OSX 10.6.8 (snow leopard) on a 27" iMac
    The distant computer is an ibook running OSX 10.7.5 (Lion), behind a router I have admin access to.
    I set the NAT/PAT options on the distant router to be redirected to the ibook.
    I set a separate user account on the ibook in the screen sharing prefs.
    When I connect to the router's IP, i get the dialog box asking me to login. When password wrong, it does say so, and when password right, it just starts "connecting", and not much happens, until Screen Share finally opens, but displays nothing. The ibook is checked in the Window menu, letting me think that the connexion worked, but there's no window to be displayed.
    I did try to run Sreen share in 32 bits mode, I then got a pretty small black window for the ibook, but nothing more. Now it runs the same way as usual : just no window at all.
    To check the connection itself, I tried to setup a file sharing access under the same settings (using the proper afp ports redirections in the router of course), and it works fine. So it's obviously no network issue, something goes wrong when initiating Screen Share.
    I think I've already managed to initiate a screen share connection with the same computers when on the same network (i.e. ibook back home), but I'll try again tonight, just to make sure it works fine when running local.
    Any idea why my distant connection doesn't work?
    Bat

    Yes, I have this issue as well. Yosemite has killed my ability to screen share from my MBPr to my desktop mini when I am away from home. Screen sharing works fine over the LAN when I'm at home.
    This function used to work well for me in Mavericks. At my office, I would see my home machine in the Shared section of Finder window sidebar. I'd click on it, and I'd see two buttons, one to connect one to share screen. Both worked, at home and from my office.
    Upgraded to Yosemite on both machines, made no changes at all to Sharing on either machine. Now my home machine doesn't appear at all in the Shared portion of Finder window sidebar when I'm away from home. When I'm at home, the target machine appears and I can connect to, share screen, etc.
    I'm logged into iCloud on both machines. At home, I can connect from my MBPr to my Mini as a guest, as a registered account, and through iCloud. I've confirmed sharing settings on both machines, made sure that the correct user is listed as having access, firewalls are off on both machines, my router supports uPnP, ???. I don't know what else to do. Bummer, my workflow depended on access to my home machine.

  • VNC / Screen Sharing SLOOOW after Chicken of the VNC connection

    We have a vacation home with a Mac Mini installed behind a standard cable modem / router.  I occasionally VNC using the Lion Screen Sharing function (Connect to Server aka Command-K, vnc://ipaddressofvacationhome).  I have the ports open on my router, everything worked well up until today.
    I was having some redraw issues with Screen Sharing over the internet, so I thought I'd try another VNC client to see if that worked any faster / better.  In Sharing/ Screen Sharing I enabled "VNC viewers may control my screen with password" (usually i just login with the user account of the machine with the built in client.
    Anyway, I connected this way with COTVNC once and didn't like it, so uninstalled it and went back to use my built in Lion VNC app.  Now the VNC session is crawling slow (10-20 seconds to register a click) and I've tried everything to get it back from restarting to turning screen sharing off and on, unchecking VNC viewers may control my screen with password... everything.  It seems that COTVNC has crippled my VNC connection and I have no idea why.  A google search came up with nothing, so I thought I'd come here.  The weird thing is... it's not physically taxing the cpu or anything, becuase if I connect via teamviewer that is also installed that is snappy.  It's only when I use VNC.  Sure I could continue to use teamviewer, but I liked the response time using the native client.
    Any ideas?  Is there a way to reset the VNC service or something to clear the cobwebs of COTVNC away?

    I should also add that this mac mini in the vacation home is headless (no monitor).  I'm not sure if COTVNC could have messed up some video setting when it connected which the machine couldn't repaid upon disconnection because of the lack of montior attached.

  • Web Sharing fails after 10.5.3 update

    Hi there, folks. Most of the time I lurk around here and find great answers, but this time I need some help. I just upgraded to 10.5.3 and now the webserver is failing to load. I checked the console and found the following:
    5/29/08 1:58:06 AM org.apache.httpd[295] httpd: aprsockaddr_infoget() failed for (insert addy here)
    5/29/08 1:58:06 AM org.apache.httpd[295] httpd: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1 for ServerName
    5/29/08 1:58:06 AM com.apple.launchd[1] (org.apache.httpd[295]) Exited with exit code: 1
    5/29/08 1:58:06 AM com.apple.launchd[1] (org.apache.httpd) Throttling respawn: Will start in 10 seconds
    Repeat ad nauseam. I tried adjusting the servername (it was commented in the configuration) to localhost in etc/apache2/httpd.comf, restarted and was presented with this error:
    5/29/08 2:08:55 AM com.apple.launchd[1] (org.apache.httpd) Unknown key: SHAuthorizationRight
    5/29/08 2:08:55 AM com.apple.launchd[1] (org.apache.httpd[330]) Exited with exit code: 1
    I'm just a PHP scripter, I don't know the details of apache configuration so kindly forgive my ignorance if I'm overlooking something obvious. It worked perfectly before the 10.5.3 update, so I'm pretty sure that it was the cause... this especially bites since I'm on a deadline.
    Thanks in advance for any enlightenment you can offer!

    Thanks for the defense, Carlene. Again he's chosen to insult both me and my work instead of provide any kind of useful reference. I guess someone as smart as he has nothing better to do than to play vulgar games with those of us who are less mentally matured.
    At any rate, no, you don't need the tilde. Be sure you have the spelling and capitalization in the files/terminal written correctly, that the .conf file you saved was in plain-text, and that the chown command was actually successful. In theory once you restart web sharing, it will work. There are a couple of other things that I did which may or may not have had any effect:
    1. A permissions check with Disk Utility.
    2. Being sure "Listen 80" (or whatever port you want to use) appears in /etc/apache/httpd.conf
    3. That the proper servername is listed in httpd.conf (I use "ServerName 127.0.0.1:80")
    4. That you clicked reload in your browser and cleared out the cached page.
    After you mess with all of this be sure to check Activity Monitor and Console to see that things are running. If httpd doesn't appear in AM after starting web sharing, you still have a problem. It doesn't hurt to try a reboot once in a while either.
    Good luck!

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

Maybe you are looking for

  • Old Ipod Software won't run iTunes 7

    So I am getting ready to fly home and I had gotten a brand new ipod ( I had an old 80 gig video and got a new one!) so I install the new Itunes 7.1 ( after uninstalling the old iTunes of course) and it tells me that it cannot update iTunes because of

  • KM Search API for "Date" Property

    Hi, I've a problem with the following code. SearchQueryBuilder searchQueryBuilder = new SearchQueryBuilder(); Calendar c = new GregorianCalendar(); c.set(2005, 05, 30); searchProperty = new SearchPropertyFormat(); searchProperty.setName("myProp"); se

  • Corrupted iTunes Library

    My iTunes library seems to have become corrupted, and I want to replace it with a backup copy on my external hard drive. I emailed Apple, and they told me it can't be done. Instead, the library has to be recreated. Does anyone know if this is really

  • Premiere Pro CC Eternally Crashing

    I have used the program on my computer for months without issue.. Suddenly today, I can't manage to keep the program open for more than 20 seconds without it crashing. Severely irritating. Everything is up to date. My PC is not by any means slow, and

  • Hotspot vs Classic

    What is the advantage of Hotspot VM over Classic VM? Does the hotspot vm use method inlining?