Start Screen Sharing Connection in Observe Mode?

Hi,
I've been able to add the toolbar button to switch screen sharing between the control and observe modes using tips I've found around the web.
I need to be able to check on what's going on with one of the computers on my home network without taking control of the mouse and keyboard.
Screen sharing defaults to control mode on connection, does anyone know if there's a way to make it default to observe or if not then to start a specific connection in observe?
TIA,
Rob.

You need Leopard and iChat 4 to work with Shinywhitebox's[Chatter|http://www.shinywhitebox.com/chatter/chatter.html]

Similar Messages

Saving Screen Sharing Connections

Ok, this is driving me crazy. How do you save a Screen Sharing connection so that you do not have to enter the IP address every time. I am referring to accessing a computer remotely over the Internet done through port 5900. I have the screen sharing set up and working fine, and I even have one of these shortcuts made a year ago, but for the life of me I can't remember how I did it again.
I think may be it was a trick using TextEdit? I know you can do this for ssh connections, but I can't remember the syntax for doing it for screen sharing. If I remember correctly you can type the right syntax followed by the IP address in TextEdit. Then you highlight the text and drag it to the desktop which results in a .inetloc file. After that you can simply doubleclick on the file and it will automatically launch the Screen Share.app and go to the right IP.

Open Safari
Type in "vnc://your.ip.address" in the address bar (I use Bonjour so it's "vnc://computername.local")
Drag the blue globe in the address bar onto your desktop
Source: http://www.mail-archive.com/[email protected]/msg46630.html

Screen sharing connecting then immediately disconnecting

I've recently bought an Intel Mac Mini for my Mother to use, and installed it at her place with Leopard. I'm running Leopard on my Macbook pro, and was hoping to use iChat screen sharing to solve problems for her. Now my problem here is that when I try to initiate screen sharing, the connection goes through, and sometimes (but not always) we see the large writing across the screen, but then it immediately disconnects citing the inititiator as disconnecting the screen sharing session. This happens whether I initiate screen sharing or my mother does.
I am on a 10+ meg broadband connection with 700kb upload, and she's currently on a 2 meg connection with 256 + kb connection. Is this part of the problem? I've opened port 5900 on her router to pass through to her computer. Also internally on my network ichat sharing works as it should.

After an hour if pulling out my hair, I finally had an idea of what might be causing the crash... I noticed I had my old iSight plugged in (the external firewire iSight) into my Apple Cinema Display. I unplugged it and iChat screen sharing worked PERFECTLY. You should also know that I don't have problems with my iSight, it works well on Video Chat and Audio Chat and even presentation mode but, it screwed up screen sharing.
In conclusion, if you're experiencing sudden connection losses with iChat screen sharing, check to see if you have an iSight plugged into your Mac and unplug it.

Screen sharing connect dialog hung

last nite i tried 2 connect 2 a m.b.pro (running 10.6.8) over wifi from my 10.7.4 m.b.pro. it was still spinning when i closed up 4 the nite, and now this morning the dialog is still spinning, and even when selected, the dialog's cancel button is disabled...see attached screengrab:
also note that even tho the dialog is selected, the menubar still shows the previous f/g app (ffx as i type this msg;-) so i don't even kow what process 2 kill;-\
perhaps i should file a bug report, but i'll have 2 figure out again where apple hides that;-\
also note that i am able 2 screen share no problem w/ my 10.6.8 minimac (ethernetted to the wifi router) so the only difference is wifi2wifi...nope: i just tried s.s'ing from the minimac to the problem m.b. (via s.s from my m.b.) and got the same hung dialog:
bouncing screen sharing doesn't help, but bouncing finder allowed s.s. to finally go thru, but the dialog is still there:-( now i got 2 machines w/zombie dialogs:-P

No, not looking to disable Screen Sharing, just to clear the dialog box (it floats above all other windows) without restarting.
Found this post that resolves the issue:
"This happens to me often if I have a problem connecting a remote computer -- those connecting windows just never go away if they hang. The issue is that NetAuthAgent is hanging. To get rid of these without rebooting:
From GUI:
1. Launch the Activity Monitor program.
2. In the Process Name list, look for "NetAuthAgent". It may show as "Not Responding".
3. Select NetAuthAgent, and then click Quit Process (the red stop sign button at the top of the Activity Monitor window). Then, click Force Quit.
From Terminial:
1. ps ax | grep NetAuthAgent
2. kill <pid-of-the-process-found-above>
This should get rid of the dialog boxes and the hung process, and VNC/Screen Sharing should continue to work, as it will launch NetAuthAgent again when it needs it."
This did just what I was looking to do!

Can't start Screen Sharing, Video Chat, or Audio Chat

Hi there,
I've been through countless Apple Discussion and other website threads, but I can't figure this out.
I just got my dad a brand-new iMac with Mountain Lion 10.8.3 on it. I'm using a MacBook Pro, also with 10.8.3 on it. We're both using the Messages app, signed into our respective Google Talk accounts (not Apple IDs with Google email addresses).
But for the both of us, "Invite to Video Chat," "Invite to Audio Chat," and "Share Screen With..." are grayed out in the Buddies menu, even though both of us have "Video Chat Enabled," "Audio Chat Enabled," and "Screen Sharing Enabled" checked off. I unchecked the option to consolidate the various Buddy Lists in the Messages > Preferences > General pane, and when I go to my Gmail account's Buddy List, I see the four buttons underneath the list (with my dad's name highlighted), but only the "A" button is clickable--not the other buttons for Audio (the phone icon), Video (the camera icon), or Screen Sharing (the two rectangles layered over one another icon).
Does anyone have any ideas on how to remedy this (short of using a completely different method of screen sharing)?

HI,
On your GoogleMail Page pull down your own Name/ID
Click Account
Choose "Products" from Menu.
Enable "Talk" (Sign in to Dashboard far right)
This is separate from the settings to actions on the Web Mail Page accessed in the Settings icon.
However I am not sure if the setting absent there if TALK has not been enabled as it was done some time ago for for me as well.
Jabber apps can have Priority Setting to allow people to be logged in via several devices and be sure a messages goes to the right device at the time.
iChat version 3 through 5 had the same Priority as the Web Browser login and would stop text Messages getting through.
iChat would show the Buddy still on line if they were logged in via the web page at a later stage
but the Video and Audio green icons would disappear from the Buddy List and the icons at the bottom would be greyed out.
Messages has a default priority of 0 compared to iChat's 23.
However I have never managed to work out which end of the scale outranks the other.
Essentially logging in to Google Mail web page to Check things is likely to stop the ability to Video chat.
This is because Jabber app use a Protocol called Jingle to connect and this is not compatible with the SIP iChat and Messages uses.
It is included in the Web Browser Plug-in you can get from Google.
The default setting for the Bandwidth setting is the NONE one.
However it can pay to set it to 500kbps.
This helps when internet speeds that are faster vary too much for the Buffering in iChat and Messages to work.
In broad terms a 5% variance in a 10Mbps download speed can be 500kbps.
Forcing Message to only use 500kbps is fast enough for 4 way video chats but is well below any variance interference.
It can also help where the ISP slows the connection as it thinks it is a Peer-to-Peer file sharing event.
Video and Audio chats (including Screen Sharing) are peer-to-Peer connections.
7:33 PM Saturday; May 18, 2013
 iMac 2.5Ghz 5i 2011 (Mountain Lion 10.8.3)
 G4/1GhzDual MDD (Leopard 10.5.8)
 MacBookPro 2Gb (Snow Leopard 10.6.8)
 Mac OS X (10.6.8),
 Couple of iPhones and an iPad
"Limit the Logs to the Bits above Binary Images."  No, Seriously

Screen Sharing Connection failed when using dock shortcut

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

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

Screen sharing stuck on 'Connect...' - but only on one client account. Please help!

I've got a bizarre problem that cropped up sponaneously, and which I can't for the life of me seem to reslove.
I have 2 home machines:
MacBook running 10.6.8 (Server / Media machine)
MacBook Pro running 10.7.4 (Client machine). Apple Remote Desktop software is installed on this machine, and connections through it work fine.
A few days ago, the sidebar "Share Screen..." link on the client machine stopped working. All I get is the 'Connecting...' dialog box, endlessly. The bugger of it is that this is only happening with my main account on the client machine. Switching into another (unused) admin account on the client results in the 'Share Screen...' button working as expected.
I've tried the following cures, found on these forums, to no avail:
Reset PRAM and NVRAM on both systems
updated all software
repaired permissions on both systems
changed bonjour names of both machines
rebooter & power-cycled router
killed the NetAuthAgent process a billion times
trashed all of the preferences, caches, etc. for screen sharing and remote desktop in the afflicted user account on client machine
etc. etc.
As far as screen sharing connection options go, these are my results:
using connect to server (via finder > go > connect to server), and plugging in the address (vnc://192.168.0.103): works
launching /System/Library/CoreServices/Screen Sharing.app, and plugging in the above address: works
connecting via the Apple Remote Desktop software: works
using the "Share Screen..." link from the Lion Sidebar: DOES NOT WORK and results in the stall mentioned above, constrained to my primary user account on the client machine.
As mentioned, this was working properly until a few days ago, and stopped spontaneously, with no changes to either system.
Any help finding a resolution to this would be greatly appreciated; this is driving me utterly bananas .
-Tim
Message was edited by: Timoluka

My wife ran into the very same problem today, while trying to connect Screen Sharing to her media center Mac Mini (server) from a Mac Book Pro (client). I was also unable to connect from my machine as well when logged into my usual account but noticed I had no problem with a Guest User account (as you've described), but had also tried most of the unsuccessful attempts at solutions that you've enumerated.
Then, I read this very similar thread: https://discussions.apple.com/thread/4131788?start=0&tstart=0
...and logged out of our now defunct MobileMe accounts on the affected machines. Upon hitting the "Share Screen..." button again, I was now prompted for a local login and password to the Mini, and once that was input, Screen Sharing connected and started up without any problems! Yes!
Given the similarity of our problems, I hope this works for you as well. My best guess is that Screen Sharing might be prioritizing the use of MobileMe authentication over local logins and passwords, and some of Apple's recent work in decommissioning MobileMe had unexpected results for folks like us.
Jim

Screen sharing only connects as audio chat...

When i try to start screen sharing with one of my clients, I can hear the noise that ichat makes on a successful connection, and the 2 way audio chat starts. but the invitation window just spins it's wheels and perpetually says "starting screen sharing..." and i never see the remote screen.
Screen sharing works with everyone else but this one person. btw, he is using a brand new airport extreme for a router...
any ideas?

Answering my own question: turns out I had an old vnc server still hanging around, called OSXvnc. When any used was logged in, it was waiting for vnc connections and failing. Once I thought to look in /var/log/system.log it was pretty obvious.

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

IChat AV screen sharing display size limit?

My machine OSX 10.5.1, iChat 4.0 on 17in Powerbook; other machine OSX 10.5.1, iChat 4.0 on Macbook Pro WITH 20in Cinema Display connected as 2nd desktop. Connection is Jabber via an OSX 10.4.11 Server and is 'long-range' in the sense of being via the internet, not down the hall.
Sharing my Powerbook's screen works fine. Sharing the other way around hangs at 'Starting Screen Sharing'. However, if I reduce the resolution of the Cinema display by a few notches it works.
Screen sharing (i.e. the vnc://...) works both ways without messing with the resolution.
I'm trying to make this work as a support service for my clients, many of whom have this dual-display setup. I can't use Screen Sharing because the users are behind NAT.
Is there a known limit in the size of desktop iChat can share? And why would it be different from Screen Sharing? Any ideas gratefully received.

I have seen the screen shared display at different sizes on my Apple Cinema 17". (will be 5 years old on 22nd Jan)
As far as I could tell the differences were/are based on the Screen resolution at the far end.
As both methods are based on Apple Remote Desktop it would seem strange that there would be a difference.
I would say by casual observation that iChat's version does seem somehow to be more screen intensive.
My G4 connected to the 17" screen shows the MacBook Pro 15" display at full height and width (Less menu bar and DOCK) with VNC.
Some strange quirk is preventing me from doing it with iChat right now.
Does seem odd.
I have tried playing with the resolutions on both to see if it will work over Bonjour but no luck.
10:18 PM Monday; January 14, 2008

Double-NAT when iChat "Screen Sharing"

I have a weird situation, wondering if all you super-network geniuses could offer an opinion...
My current setup:
-DSL Modem hooked up to a Time Capsule.
-Time Capsule in Ethernet Mode & "Share Public IP Address: NAT & DHCP Enabled."
-Time Capsule has a wireless 5Gz "N-Only" network.
-2PC's, and an Airport Express connected to N Network wirelessly.
-Airport Express "Extends network" via ethernet cable to Slingbox & TiVo (via switch.)
-Airport Extreme wired to Time Capsule.
-Airport Extreme in Bridge Mode.
-Airport Extreme has a wireless "G" network & USB Printer.
-Airport Extreme network for "iPhones & G computer."
-Only Port Mapping is for slingbox, ports 5001,5001.
O.k. Everything works PERFECTLY! Except when I start a "Screen Sharing" session in iChat AV.
When I click "Ask to share xxx's screen" It says "Waiting on xxx" and then Airport Utility pops up, saying that the Time Capsule has an error - "Double NAT" and I'm off the internet. All I have to do is select "Restart Time Capsule" and after a reboot, I'm back in business, and all is well again. I can screen share, chat, etc. However, if I try and start "Screen Sharing" again, same thing - Double NAT.
Do I need to enable a Port Mapping for iChat?
Any suggestions or help would be greatly appreciated. I thought I finally had the network thing down, but this one little thing keeps making me reset my router. (Doesn't seem like the Apple way.)
Thanks.

I have the Time Capsule set up as the DHCP server, distributing a shared IP address.
The Express is set up to "Join and existing network."
I only have 1 Extreme and it is set to "Bridge Mode."
The Time Capsule is the router hooked directly to the DSL modem. It is in "Ethernet" mode, and I'm not quite sure how to check the little DSL modem's settings.
It's so strange, that only this one little request, "Ask to share xxx's screen" does this error occur.
Looking at more settings on the Time Capsule, under NAT settings, I do NOT have the "Enable default host at:" option checked, and the "Enable NAT Port Mapping Protocol" IS checked. Under Port Mappings, 5001,5001 is the only item for Slingbox.

IChat Screen Sharing causes Time Capsule to have "Double NAT"

I have a weird situation, wondering if all you super-network geniuses could offer an opinion...
My current setup:
-DSL Modem hooked up to a Time Capsule.
-Time Capsule in Ethernet Mode & "Share Public IP Address: NAT & DHCP Enabled."
-Time Capsule has a wireless 5Gz "N-Only" network.
-MacBook Pro, PC and an Airport Express connected to N Network wirelessly.
-Airport Express "Extends network" via ethernet cable to Slingbox & TiVo (via switch.)
-Airport Extreme hard-wired to Time Capsule.
-Airport Extreme in Bridge Mode.
-Airport Extreme has a wireless "G" network & USB Printer.
-Airport Extreme network for "iPhones & G computer."
-Only Port Mapping is for slingbox, ports 5001,5001.
O.k. Everything works PERFECTLY! Except when I start a "Screen Sharing" session in iChat AV.
When I click "Ask to share xxx's screen" It says "Waiting on xxx" and then Airport Utility pops up, saying that the Time Capsule has an error - "Double NAT" and I'm off the internet. All I have to do is select "Restart Time Capsule" and after a reboot, I'm back in business, and all is well again. I can screen share, chat, etc. However, if I try and start "Screen Sharing" again, same thing - Double NAT.
Do I need to enable a Port Mapping for iChat?
Any suggestions or help would be greatly appreciated. I thought I finally had the network thing down, but this one little thing keeps making me reset my router. (Doesn't seem like the Apple way.)
Thanks.

I have the Time Capsule set up as the DHCP server, distributing a shared IP address.
The Express is set up to "Join and existing network."
I only have 1 Extreme and it is set to "Bridge Mode."
The Time Capsule is the router hooked directly to the DSL modem. It is in "Ethernet" mode, and I'm not quite sure how to check the little DSL modem's settings.
It's so strange, that only this one little request, "Ask to share xxx's screen" does this error occur.
Looking at more settings on the Time Capsule, under NAT settings, I do NOT have the "Enable default host at:" option checked, and the "Enable NAT Port Mapping Protocol" IS checked. Under Port Mappings, 5001,5001 is the only item for Slingbox.

Screen Sharing does not accept my password anymore

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

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

IChat screen sharing and video not working on MacBook but works on Mac pro

I have a MacBook and MacBook pro. Both have the lion os 10.7.2. I can use iChat on the MacBook pro for screen sharing, video chat, and text chatting, with others remote to me. However, I can only do texting with the MacBook. I can do screen sharing via Finder between my MacBook and MacBook pro. I can do FaceTime between both systems. I can also do FaceTime between the MacBook and anyone remotely.
I also tried installing teamviewer on the MacBook, and on a remote MacBook..... And I get the same results where I cannot share the screen, from the one that has not been working.
I have checked the settings under system preference and made sure screen sharing was enabled. I have checked under iChat under video to make sure screen sharing was checked.
The macbook that is having this problem is configured for AIM for iChat
I have run out of ideas. Any suggestions on what I might try?
Thanks

Ok,
I will list the ports in greater detail and point out when iChat uses them.
AIM Login and 1-1 Text Chatting
iChat version 1 through 5 will Log in to the AIM server on port 5190 (TCP Protocol) by default.
Since iChat 2 we have been posting here that the AIM servers allow a Login on almost any port and have been suggesting port 443.
This is used by both Web Browsers for secure Login to some sites and by the Mail app with some mail servers.
It is also below port 1024 (most domestic routers have the ports above this figure closed) In some campus situations using port 443 will normally allow at least Login and Text chatting.
iChat 6 uses port 443 by default.
File Transfers (AIM)
When doing File Transfers with AIM Buddies iChat will move to using Port 5190 on the UDP Protocol.
This cannot be changed. (This invokes the little Message about Starting Direct IM in an open Chat)
It also uses this port for Pics-in-chats, dropping Files on a Buddy's name with out a Chat or sending other files that are not pics.
In the case of Port Forwarding some devices don't like port 5190 being forwarded "twice" which is another reason for moving the login and Text chat port.
Jabber Logins
No matter what Jabber server you use ichat will use one of two ports (5222 and 5223)
Which one it uses is dependent on whether it needs and is using an SSL Login or not.
SSL Logins use port 5223 and NON SSL one use 5222 (ticking or Unticking the SSL box on a Jabber account will automatically change the port).
Google Talk is the exception in that it allow a Login on port 443 as well.
The First Apple Doc I linked you to says iChat uses port 5220 in Jabber.
I run Little Snitch and have never seen any version of iChat use this port at any time.
Bonjour
Any Mac to Mac Connection or Mac to any Bonjour able peripheral will be on port 5353.
This is normally opened (Preset) in the Mac Firewall for the Finder/System side of Sharing.
iChat needs and uses two other ports (5297 UDP and 5298 on both TCP and UDP)
As they an LAN Side connections the router would normally pass them.
At iChat 3 there were issues with the Mac Firewall (it included UDP set up and the preset in the firewall only listed them and TCP so we had people add all the iChat ports (you had to manually enter them in Tiger)
A/V Chats
No matter which Buddy List you start from iChat will do A/V chats the same way.
The Visible Invite you or your Buddy sends is on port 5678 (UDP)
In iChat 3 and earlier iChat then moves to port 5060 to send the SIP Connection Process invite behind the scenes (SIP = Session Initiation Protocol)
Port 5060 is one of 4 ports internationally agreed for SIP (How VoIP phones connect) (5060-5063).
Although ISPs were not supposed to block Through traffic many started blocking End users and then Charging them to open these ports (Many ISP were telecom companies that were losing long distant Telephone calls monies).
The SIP process then in iChat 3 contacts a server run by Apple for this purpose (Snatmap.mac.com to give it it's full name).
This acts like a old fashioned telephone operator connecting the call.
SIP is a text based process.
Your end "Calls" the operator.
The Operator "Calls" Buddy.
Buddy Accepts
iChat then negotiates the ports to be used.
In iChat 2 and 3 it uses 4 ports (vid in Vid out, Audio In and Audio Out) from "the group of 20" starting at the bottom (16384 to 16387 normally)
Three and 4 way chats uses more ports (which is why 20 are set aside)
In iChat 4 Apple realised the issue with the 5060 port and changed the way iChat worked
Since then it has Sent the invite on Port 5678 but then moved to port 16402 (it starts at the top of a smaller group of 20)
All Video and Audio traffic is also now on one port (so no need for 20 ports and iChat now lists 10).
NOTES so Far.
File Sharing during a Chat converts the Chat to Direct IM for AIM Logins
This is Peer-to-Peer in AIM
A/V Chats are Peer-To-Peer and you can actually log out of the Buddy list and continue the chat. (The exception is using iChat 6's AIM Video relay option)
Screen Sharing
Screen Sharing is an Audio Chat with a VNC connection along side.
Both bits have to wok to avoid the Pop-up to send to Apple and the Log that contains.
The Audio part is on port 16402 and the VNC part is random. (So random it is different every time you do it)
The reason it is classed as an Audio Chat+ is so the AppleScript for Auto Accept can filter out Screen Sharing connection and Not Auto Accept them.
This does have a knock on effect as far as your Router is concerned as already mentioned earlier.
You cannot Forward or Trigger the random Port so you have to use UPnP in your router to open the ports.
NOTES
Jabber File sharing may possibly be on port 1080 as listed in the Server Article I linked you to (I have also seen it written about in other stuff I have come across)
However Little Snitch does not seem to confirm this either.
Most time it will be peer-to-peer like the AIM connections for this.
However some Jabber servers do not seem to allow this and have this Jabber65 Proxy set up which passes things Server to Server in between it leaving your end and arriving at a Buddy.
This on Port 7777 but you do not need to open this port (unless you are running a Jabber server)
I have yet to test File Transfers using a Yahoo Buddy List in iChat 6.
AppleCare and Geniuses.
Previously I have been contacted by Geniuses in Stores asking to test customer's iChat.
They and the Applecare people have details about Apple wants an designed the App to work.
What they don't have is the knowledge about what it takes to set it up in the "real world".
There are literally thousands of Makes and Models of routers.
Some like the Thomson-Alcatel brand state they are SIP/VoIP ready but this means the router strips out all SIP Data trying to send it to a Phone.
Early models of Alcatels can get around this with a tweak. Later models can't.
Motorola devices tend not to have UPnP.
Apple Base Stations have Port Mapping Protocol instead of UPnP and this needs setting up.
The Zyxel range definitely does not like the dual use of port 5190 and does much better using UPnP (You almost certainly have to do your AIM login on port 443 with these).
1. I have two computers (MacPro and MacBook Pro) that are both running Lion 10.7.2 and both running iChat 6.0.1. <<-- Fine
2. The Netgear router model is: WNDR3700.    <<<<--- With any Brand there are exceptions and I do wonder about this one
3. The firewall for both Macs is turned on and in the advanced area iChat is listed as being "allowed." <<<<---- Fine
4. In iChat, under the video options, "Screen Sharing Allowed" is checked.                                        <<<<<---- Fine
5. In System Preferences, "Screen Sharing" is checked and this is for "All Users" at present.               <<<<<---- Not Required
6. There are two separate AIM accounts being used for iChat purposes.                                            <<<<<---- OK
7. In iChat preferences, each AIM account is "Enabled" under "Account Information" and the "Server Settings" show the Server as "api.oscar.aol.com" and the Port is "443" and "Use SSL" is checked.                                <<<<---- As it should be
From this and the other info in the first port it was only the router set up that seem to throw some light on a possible cause (Port Forwarding and UPnP conflict)
If just doing Port Forwarding the ports listed would have covered things (Except the Screen Sharing's random port)
Regarding your latest post.
I have table similar to that on my Sagem 2504Fast Modem/router combined device and it too seems to list a different port on the external side on occasions.
I would try the router with the Disable SIP ALG unticked (so it is not disabled). If the Help info on the right gives any info about what this Netgear version does it would be helpful.
Some are like the Thomson-Alcatels I was talking about in that it points the SIP data to a specific place (Possibly a Phone socket on the device)
Others seem to provide an "boost" to enable SIP to work and don't seem to get in the way of iChat.
Try adding the Names in Table 1 from this page and see if you can Video to those.
There are 6 names in total (I am actually only seeing one on Line as I type)
9:19 PM      Wednesday; January 25, 2012
Please, if posting Logs, do not post any Log info after the line "Binary Images for iChat"
 iMac 2.5Ghz 5i 2011 (Lion 10.7.2)
 G4/1GhzDual MDD (Leopard 10.5.8)
 MacBookPro 2Gb (Snow Leopard 10.6.8)
 Mac OS X (10.6.8),
"Limit the Logs to the Bits above Binary Images."  No, Seriously

10.7.2 Breaks Screen Sharing Login

After updating to Lion 10.7.2 I receive a blank grey screen with no user login infomation when I access my MacBook Pro using TightVNC. 10.7.1 and prior releases worked correctly with user pictures painted onto the grey screen to allow login account selection.
I have stopped and started Screen Sharing multiple times with the same results.
Any suggestions?

Tight VNC Viewer runs on Windows 7 and is used to connect to PCs running VNC such as Mac OS X with Screen Sharing enabled. Tight VNC has never been installed on the Mac OS X box.
The only difference between when this worked and when it stopped working is the 10.7.2 update which seems to have broken VNC.

Start Screen Sharing Connection in Observe Mode?

Similar Messages

Maybe you are looking for