Screen sharing redraw problem

I am seeing graphical redraw problems when I try screen sharing with another Mac 10.8 computer, Mac Mini mid 2011. For example, when switching menus, the old ones remain. This always worked just fine in Lion. I tried turning adaptive and scaling off and on, but no difference.

Don't know whether I found the problem, but I did manage to get Screen Sharing working reasonably again.
Things had gotten so bad that even mouse moves and keystrokes were getting mangled and delayed, so I decided to try a VNC client (Chicken of the VNC) to see whether things were better. I had to set the host machine to accept VNC connections, so you could say I "touched" the screen sharing panel in System Preferences. I also shut down the Screen Sharing app on the client side so I could use the VNC. The VNC worked OK but would not display the entre screen, so I quit. Then I restarted the Screen Sharing client, and--hey presto--it worked! Response to mouse & keyboard were back, and video was good enough to watch a video.
So, I guess folks could try (1) jiggling something in the Screen Sharing prefs on the host machine, and (2) restarting the Screen Sharing client.
-- rick

Similar Messages

  • 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 viewing problem

    I am using Skype Version 4.3.0.37 on a desktop using Ubuntu 12.04. Using Screen Sharing in full screen mode there are huge blocks of filler surrounding the screen sharing image making the screen sharing image much smaller and much harder to read. Is there a solution? Is anyone working on the problem? It seems as if linux problems are ignored.

    Here's a couple things you can try:
    Cntl-Shift-Eject will put the displays into sleep mode. Then space bar will bring them back out of sleep. See if that results in a screen on the Sony. If not, then try this one:
    Hit the power button on the MB. This will pop a screen up (which you can't see because the Sony is black) but if you hit the S key, the MB will go into sleep mode. After it goes to sleep, hit space bar to awaken the MB and see if the screen comes back on the Sony.

  • Screen sharing preferences problem

    When I upgraded to Yosemite, it seems to have changed my sharing preferences. I want to restrict sharing to certain users. I have 2 sharing only users set up. They work as they always have for file sharing. But they no longer appear in my users list for screen sharing, and if I click the + to add a user, they don't appear in the list of users I can select.  Apple's instructions for setting this up say:
    If you selected “Only these users,” click Add  at the bottom of the users list, then do one of the following:
    Select a user from Users & Groups, which includes all the users of your Mac. - but it doesn't display my sharing only users
    Select a user from Network Users or Network Groups, which includes everyone on your network. - this option doesn't even appear
    Does screen sharing not work with sharing only users? Is there some other setting I need to change?

    My dad has always used his full username, including domain, so there's nothing to change in terms of that.
    According to AT&T's support website, his FastAccess DSL username/password should be unchanged and still work. That said, I believe I need to try changing the settings of his DSL modem to use bridge mode and then try the PPPoE configuration on the AEBSn again.
    I think I remember my dad saying an AT&T service tech came out and tested his DSL line and may have done something to the modem which my dad claims he didn't. Reading about the specs of the DSL modem and the accounts of a few AT&T techs, the modem is supposed to be in bridge mode in order to work with a router that uses a PPPoE configuration for single NAT.
    Thanks for your input!

  • IChat Screen Sharing mouse problems

    I just bought a new iMac 20" for my mom for xmas with the thought that the iChat screen sharing will help me to remotely configure her system.
    I am finding that once I have initiated the screen share I am have erratic mouse behavior. When I am sharing her screen and moving the mouse the cursor will jump around the screen. this happens even worse if I am click-dragging a window around.
    Is there any way to improve this performance? At work I use Windows remote desktop with no issues such as this, and I would expect the same performance from OSX.
    Thanks

    My first thought is that your mother is also trying to control the mouse.
    I presume though you have exclude this.
    iChat Screen Sharing does include an Audio component so the computer is doing an Audio chat at the same time effectively. This will have a impact on the processor usage particularly over the way iChat A/V chats use the processor. (they tend to dip in and out to spread the load and not hog the processor).
    10:11 PM Friday; January 9, 2009

  • Screen Sharing Capital Problems

    I have a PowerBook G4 (OS 10.5.8) that activates screen sharing on my MacBook Pro (OS 10.6.7)  The Powerbook cannot successfully type capital letters on the MacBook Pro's screen.  Any help would be appreciated.

    My first thought is that your mother is also trying to control the mouse.
    I presume though you have exclude this.
    iChat Screen Sharing does include an Audio component so the computer is doing an Audio chat at the same time effectively. This will have a impact on the processor usage particularly over the way iChat A/V chats use the processor. (they tend to dip in and out to spread the load and not hog the processor).
    10:11 PM Friday; January 9, 2009

  • Screen Sharing, recent problem seeing two monitors, anyone else?

    I have a G5 running dual 20"monitors on the G5 dual DVI video card. I used to be able to screen share back to the G5 with my macbook pro and I would get to view the two screens. I could see them both or select on or the other.
    Recently, I can only view the one monitor (the one set as the main monitor on the right) and I cannot see them both or switch between them.
    Not sure if this is a bug in of the recent OS updates or what?
    Thoughts
    Tom

    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.

  • Problems connecting video and screen sharing

    see the leopard iChat forum, I moved it to there. thanks, its called Another Video and screen sharing connection problem
    Message was edited by: wishiwasmtbin

    Hi,
    Welcome to the  Discussions
    IS this Linksys doing UPnP ?
    This is set in the Administration page of the set up pages.
    Also in the Security Page disable the Anonymous Ping Blocking.
    If you set UPnP then make sure any Port Forwarding, Port Triggering and DMZ is disabled.
    These last three use NAT more strongly than UPnP and NAT can be an Issue.
    The Appleu3test accounts are effectively on Public IP address so Lees/no NAT
    1:52 PM Sunday; December 9, 2007

  • Problem using file sharing and screen sharing in Leopard

    I have Mac OS 10.5 Leopard installed on 4 computers in a Home Network and have a problem with sharing files and using screen sharing. Here is my setup.
    MacBook Pro with my logon ID
    MacBook Pro with my fiancee's logon ID
    Mac Mini with both of our logon ID's
    Mac Pro with both of our logon ID's
    The problem I have is I am able to access the Mac Mini computer where we have an external Hard Drive connected for data. She is also able to access it. The only problem is we have it set up to only share this external USB drive. Yet for both of us it shares the external drive along with the internal Macintosh HD. Fortunately this is not a very big deal but since I'm not sharing all those drives why is it doing this?
    Also, I am able to connect from the Mac Mini for example to my MBP and vice versa for screen sharing along with file sharing. Yet if she tries to connect to the Mac Pro from her MBP and vice versa it won't. It simply times out and will never connect for screen sharing or file sharing but yet the Finder shows the Mac Pro. We have a 2nd hard drive in the Mac Pro which is the one set up for file sharing. I am also unable to connect to the Mac Pro's HD. Everything appears to be set up correctly. For my MBP on the Finder it shows the Mac Pro but once again I am unable to connect to it for screen sharing or file sharing.
    Also, not sure if it's related but even for her MBP she is unable to connect to it from any other computer in our network although it's set up for file sharing and screen sharing so I'm not sure if it's related to her logon ID. Then again as mentioned above neither of us can connect to the Mac Pro.
    I tried to make the above sound as simple as possible. I am relatively new to networking and of course Leopard but even on the Mac Pro all settings sound the same as on the Mac Mini where we can both connect to. The only big difference is on the Mini we are connect to a USB external drive, on the Mac Pro an internal drive. Is there something I could have overlooked or are there known issues with Leopard's sharing features?
    We both have .mac but since we are using this on an internal network (some wi-fi, some wired, all through an Airport Base Station Extreme) I would think this has nothing to do with Back to my Mac.
    I appreciate any help with the above.

    FaceTime doesn't do any of that, so I'll assume you mean Messages.
    From the Messages menu bar, select
    Video ▹ Connection Doctor
    In the window that opens, select
    Show: Capabilities
    There should be a checkmark on the line with the words "1-on-1 video chat." Select
    Show: Network Status
    You should have two green dots.
    Make sure that you and the other party meet the applicable requirements shown in these support articles:
    Share your screen
    Requirements for audio chats, video chats, and screen sharing
    See also:
    Fix video chat issues

  • Mac Pro 2007 with Nvidia 8800GT screen redraw problems on Mac OS 10.5.2

    I seem to be having a slight screen redraw problem. Such as when grabbing the browser window and moving up and down it seems the redraw can't keep up,also seems problematic when watching flash or other video online. It does it in the finder too for windows listings or in icon view there is a fluttering or flashing back and forth, kind of like a white super split second flash when dragging the window box smaller or larger not as bad as when making smaller. Hard to describe but my original Ge-force that I pulled was not having these characteristics. I figure that the drivers need tweaking. In windows I am not getting these results. I have newer boot camp installed as well as the leopard graphics update done so I am trying to see if others are having a slight problem or maybe it is me.
    Also I make certain it is not heat related as I monitor that and it does not matter at what temp it is.

    Here's another similar experience -- and my solution.
    I bought a Quad-core 2.8GHz (8GB RAM) Mac Pro in May and got the "better" Nvidia 8800GT. I thought I was happy, but there were redraw issues after sleeping and a display "roughness" I found annoying. Upgrading to OSX 10.5.4 didn't help.
    I found it to be mostly absent on startup, but sleeping the Mac would bring it on. I.e., after sleep, the relatiionship between the 8800GT would be different than before. when I logged out and in again, the problem woud vanish. No what I expect from a "superior" graphics card. I ascribed it to funky drivers from Apple.
    The store I bought the Mac from offered to swap for my suggestion of an ATI HD 3870, so I went for it about a week ago.
    This card is far smoother than the 8800GT and just as fast in rendering benchmerks for graphics. (I'm not a gamer.) I am a happy camper! There is no stuttering, oddball redraw, or jerkiness as there had been with the 8800. It's perfect! Never mind that it may be 5% slower for gamers, it feels faster for my use.
    BUT NOTE: As I now see from reading several forums, I wasn't alone is getting a screaming-Mimi at first! The first 3870 ran at nearly full fan speed at power-up. The speed changed a little with resolution changes on my big Mitsubishi CRT monitor, and actually stopped when I switched to 1080x1920 @ 72Hz! Then the fan would start and quit, start and quit randomly -- convincing me it was defective.
    I returned this RED-shrouded unit and the store replaced it, this time with (randomly) a BLUE-shrouded unit. (Slightly lower serial.)
    Bottom Line: This replacement 3870 is quiet as a mouse! Fan runs near-silently at startup and after hours of regular use in a 75ºF room. I get the distinct feeling that a bunch of cards with wonky fan controllers were built, and some of us got 'em.
    Bad News: The ATI HD 3870 does NOT support multiple refresh rates under Windows XP-SP2 booting the Mac Pro, with or without Boot Camp drivers installed. No version of the ATI drivers fixes this, and ATI does not officially support Boot Camp yet. You can choose a resolution okay, but you're stuck at 60Hz refresh -- a pain for those of us who hate 60Hz flicker. (I like 100Hz refresh.)

  • HELP: Problem accessing host Mac MSL Mini using "Screen Sharing"

    I have screen sharing enabled on my mother-in-law's Mac Mini so I can access it with Chicken of the VNC.
    There are 2 user accounts, one Admin and the other regular. The problem is that when Chicken Of the VNC connects and I choose one of the accounts and log-in the connection terminates and I have to close Chicken of the VNC and re-connect.
    Is there something in Sharing/screen sharing that needs to be set so the connection will not terminate when switching account .

    From Finder help on screen sharing...
    -=-=-=-
    If you can’t share computer screens
    If you’re having problems sharing your screen with another computer, or sharing the screen of another computer, there are several things to check.
    Here are things to try if you can’t share screens:
    Make sure screen sharing is turned on and you have set up sharing permissions on the computer whose screen you want to share.
    Sharing your screen with other computer users
    If you’re trying to share the screen of another computer, open Sharing preferences on that computer and make sure you’re in the list of users who have been given permission to share that computer’s screen.
    Make sure neither computer is in sleep mode. A computer can’t share its own screen or share the screen of another computer if it’s in sleep. Adjust the computer’s settings using Energy Saver preferences.
    If you’re using Back to My Mac to share screens, make sure it’s turned on on both computers.
    Sharing your computer’s screen using Back to My Mac
    Make sure both computers are connected to the same network, or if you’re sharing screens using Back to my Mac, make sure they’re both connected to the Internet.

  • Problems using iPhoto via Screen Sharing

    To deal with our family's ever-growing photo library, I bought a new Mac Mini with a jumbo hard drive. For now, I want to run this as a headless server so that whoever wants to can work with the photo library from whichever of our other Macs is handy, so I've set it up with Screen Sharing.
    So far so good, I've copied the iPhoto library there and things seem to work well except for one important detail: When I try to see/edit the detail of any photo, I just get a black screen! Or rather, the iPhoto window contains a big black rectangle where the photo should be. If I touch the zoom control, the navigation mini-view shows up correctly, but I still can't see the picture itself. Oddly enough, if I look at the detail of a video, I can see the first frame (but no more than that, the "play" button doesn't do anything).
    I'm running Mac OS X 10.6.7 on both machines, iPhoto '11 (9.1.3) on the server.
    I realize that I can access the photo library directly from iPhoto on the "client" using iPhoto's built-in sharing mechanism, but that won't give me full control of the remote photo library.
    Has anyone else experienced this?

    Do you see the same if you're working directly on the Mini?  Do you see anything in the middle of the black screen?  Maybe something like this:
    Click to view full size
    If so then that's an indication that the file path to the original file has been broken.
    So make a temporary, duplicate copy of the library and apply the two fixes below in order as needed:
    Fix #1
    Launch iPhoto with the Command+Option keys held down and rebuild the library.
    Select the options identified in the screenshot. 
    Fix #2
    Using iPhoto Library Manager  to Rebuild Your iPhoto Library
    Download iPhoto Library Manager and launch.
    Click on the Add Library button, navigate to your Home/Pictures folder and select your iPhoto Library folder.
    Now that the library is listed in the left hand pane of iPLM, click on your library and go to the File ➙ Rebuild Library menu option
    In the next  window name the new library and select the location you want it to be placed.
    Click on the Create button.
    Note: This creates a new library based on the LIbraryData.xml file in the library and will recover Events, Albums, keywords, titles and comments but not books, calendars or slideshows. The original library will be left untouched for further attempts at fixing the problem or in case the rebuilt library is not satisfactory.
    NOTE: You do know that you can connect an external HD to the Mini and let the other computer log into it and access the library on the EHD for full access to the photos, right? However, doing so wirelessly is dangerous due to dropouts that can occur and if they do while the library's database file is being written to the database can be damaged.  So if you're wirelessly connected between the two Macs screen sharing would be the safest way to go. If you're wired then the other method would be optimal.
    OT

  • Problems with screen sharing

    Upgraded three systems to Mountain Lion yesterday (Early 2011 MBP, Mid 2010 Mini and Mid 2011 Mini). 
    I rely on Screen Sharing to maintain the two Minis using the MBP.  Now, while the Mid 2010 Mini can be accessed just fine, the same is not true for the Mid 2011 Mini.  After a long delay, a window will pop up but is black.  If I toggle between scaled and full screen a couple of times, the screen will be displayed but will accept no input.  Odd.

    I was able to resolve the problem with screen sharing from my MBP to my problematic Mini.
    My home network uses a Belkin N600 dual band router with both the MBP and Mini using the faster N band.  After switching the Mini to the slower band, screen sharing began working again.  My other Mini that worked all along was hardwired to the router so was not an issue.
    Oddly, with Lion, screen sharing worked having the MPB and Mini on the same N band.

  • Screen sharing drive access problem

    I have a Mac Mini I'm using as a media server. This mini has 2 hard drives and Mavericks installed in it.   When I access the mini via screen sharing from my MacBook Air, if an no longer access the 2nd hard drive.  It appears, and I can open the hard drive, but I can't access the folders on the hard drive. I can't access anything on that drive using applications, either.
    This wasn't a problem using Mountain Lion.  Any tips on how to fix this?  All of my permissions are still set up correctly as they were before.
    Thanks,
    Bryan

    Hey Guys,
    I'm having this EXACT same problem, using this exact model of Belkin Wireless G Router: F5D7234-4 v4
    We're both running the most current version of OS X, and when the user who is on the Belkin router plugs her MBP directly into her Comcast cable modem, everything works perfectly.
    So given that the issue lies within the Belkin, I have remotely logged into the router and tried every possible combination of enabling and disabling:
    - UPnP
    - WMM
    - Firewall
    - QoS Monitoring
    After doing this, we're still only getting audio whenever we try to screen share. As with the original post, we will start the screen sharing process, the window will say "starting screen sharing with....", but then we will only have audio.
    Is my only other option to go through, set a static IP for this user, and setup all of the port forwarding per this article?
    http://portforward.com/english/routers/port_forwarding/Belkin/F5D7234-4/iChat.ht m
    Thanks in advance for anyone's help!!

  • 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

Maybe you are looking for