Will Firefox Hello support screen sharing via video chat?

First of all let me say a BIG thank you to all the developers who contribute to Firefox (and all Mozilla projects for that matter). I know countless dev hours goes into the project and I really appreciate all your hard work.
To my question, I realize Firefox Hello is based on the webRTC standard and there are a many other options available for screencasting, but it would be incredibly convenient to have that feature natively built into Hello. Are there any plans to support screen sharing in the future?

hi, yes screensharing features are in the roadmap for firefox hello (and already present in development versions of the browser) - this feature might land in firefox 38.

Similar Messages

Screen Sharing and video chats don't work

I've been searching this forum for awhile and I haven't found a concrete answer to my problem, so if this question has been answered please excuse me. Ok, So here's my situation am running iChat on Mac OS 10.5.1. Whenever I am using my laptop at my school on the network their, I am able to use both screen sharing and video chat. But when I am at home, I am unable to use either one. It begins to try to start the session, but then i receive a message that tells me that a connection could not be established. I know that I have internet access, but I don't know what could be wrong with it.

After investing far to long in looking at this exact issue on my end, reading the seemingly endless threads on the exact same error, trying all the various tweeks and QT settings, bandwidth limit settings, etc etc. proposed here, I have now solved this problem, and the none of the above were part of the solution.
I have perhaps one of the the most common routers on the market, Linksys WRT54GL.
In a totally unrelated network problem (a printing issue), Linksys tech support advised me to reset my router. There is a small button on the bottom. I depressed it for 30 seconds. Rebooted everything and my printer miraculously worked. Yea, I had to reenter my WAP passkey, router admin password etc., but that took 2 secs. So, what does this have to do with iChat?.... The very next time I tried iChat video and turned on and enabled my camera, the recipient immedialty saw me. No connection error.
Problem solved, for me art least. Not sure if anyone has tried this, but makes sooooo much more sense than the other unApple like suggestions I previous tried. Hope this helps.

Screen sharing and video chatting

When i am video chatting with someone and i start sharing a screen with them the video chat goes away i can still talk with them but if i stop sharing the screen the call/video chat i started is ended is there any way to continue the video chat after i stop sharing screens without having to restart the chat

No sorry you have to restart the chat.

Screen Sharing and Video Chat

Hi! I have 2 computers right next to eachother, and I felt like testing out the new Video Effects and Screen Sharing abilities of Leopard.
So, I logged on to each of the computers in iChat (with 2 different accounts), and attempted to do this. However, whenever I attempt to Video Conference or Share Screen, I get an error, saying the other person (the one that accepted the request), cancelled the conference.
So what's up with that?!
I am sorry if this isn't clear, and I will post back with any additional info you need.
Thanks!

iChat requirements
* Audio chats require a microphone and a 56-Kbps Internet connection.
* Video chats require an iSight camera (built-in or external), USB video class (UVC) camera, or FireWire DV camcorder; and 128-Kbps upstream and downstream Internet connection.
* Photo Booth and backdrop effects require an Intel Core Duo or faster processor.
* Backdrop effects when using a DV camcorder require fixed focus, exposure, and white balance.
* Some iChat features offer better performance and quality with higher system capabilities.
More details
More Details went here
http://docs.info.apple.com/article.html?artnum=306687
The Tables can not be reproduced in the Discussions.
7:31 PM Monday; October 29, 2007
Message was edited by: Ralph Johns (UK)

Simultaneous screen sharing and video chatting?

So I already guess the answer is no, but is it possible to screen share while still video chatting? If not, how about document sharing with the ability for both sides to control the mouse?

Ok.
In the current version of iChat 4 the way the Document (file) "Sharing" happens is different depending on the capabilities of your Mac..
My Intel MacBook Pro will do it the way you describe - as a sort of halfway house thing towards a 3 way Video chat - with a friend who has a G5 Tower.
My G4/1Ghz Dual Processor though cannot do it this way and it appears more in the way of iUSBCam's Desktop view as feed (Last pic on Page). Or Desktop as Feed if you like.
I think this is still in the realms of Wish List Stuff.
CamCamX allows you to Mix two Video feeds and also as a result allows two apps to have access to the Camera at the same time.
CamCamX's site does say it will work with iUSBCam so you may be able to create the scenario you want.
If you have two Macs on could Share the Document and the other do the Video as one person can still do iChat Theatre.
One of the biggest problems is trying to share a 24" displayed screen on a 17"monitor. Obviously like for like is best for this. But size may need to be considered for some things.
7:55 PM Tuesday; January 13, 2009

Switching from screen share to video chat

I'm using iChat ver. 4.0.2 on an iMac. I collaborate with colleagues and we frequently use the screen sharing mode, but I cannot figure out how to change back to video chat direct from the screen sharing mode. If I click on the little video camera at the bottom of the iChat box, nothing happens. If I end the screen sharing, the entire iChat session shuts down. Any advice on switching from screen sharing to video chat mode without hanging up?
Thanks!

You have to End Screen Sharing and start a New Video chat.
There is no elegant way to do it.
In iChat go to the iChat menu and Feedback option send in a Wish List item. (there is a Free text Box and one of the Drop downs is for Enhancements Requests.)
11:19 PM Monday; May 26, 2008

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

Will Firefox 4 support autoconfig (aka Mission Control)?

I am interested in configuring Firefox for users and locking down certain settings. It appears that the folder referenced in http://mit.edu/~firefox/www/maintainers/autoconfig.html is not present on the Firefox 4 Beta install.
Will Firefox 4 support autoconfig, and if so will updated documentation be posted for that when Firefox 4.0 is released?

See [https://bugzilla.mozilla.org/show_bug.cgi?id=595522 Bug 595522] – Omnijar breaks prefs initialized via mozilla.cfg
''(please do not comment in bug reports; you can vote instead)''

HT202157 When will Apple TV support Amazon Prime Instant Video?

When will Apple TV support Amazon prime instant video?

Most of the YouTube video subtitles are inserted by flash. Unfortunately, ios OS products don't support flash. If you do want to play them with subtitle, maybe you can use a video converter to help you convert YouTube videos to Apple TV. The only thing you should make sure before the conversion is that the videos that you download is bearing the subtitle, then the converted files would have the substitles as well. Hope that would help.

How will you know if someone is using video chat?

How will you know if someone is using video chat? Does the green camera indicator turns red?

Hi,
You Buddy List will show two types of AV icons.
"Single" type which indicates the person can only do 1-1 Chats.
"Stacked" icons indicating they can do Multi-way chats.
Example pic
If they appear feint or "greyed out", so to speak, then they are Busy to someone else.
(if they are chatting with you they will appear dark again once connected)
9:01 PM Tuesday; November 15, 2011
Please, if posting Logs, do not post any Log info after the line "Binary Images for iChat"
 G4/1GhzDual MDD (Leopard 10.5.8)
 MacBookPro 2Gb( 10.6.8)
 Mac OS X (10.6.8),
"Limit the Logs to the Bits above Binary Images."  No, Seriously

Video/Screen Sharing via 3G connection not possible - port restrictions?

I'm running Jabber-based iChat AV 5.0.3 sessions from my MBP connected to the Internet via a wireless USB modem 3G/UMTS (German Telekom D1 network). My buddies are connected to the Internet via regular broadband connections (DSL). I have set up a hosted Jabber server via Dreamhost (without SSL, port 5222 used).
Status Quo:
- Contact status of remote Jabber users shows up properly. All buttons (text chat, screen sharing, video) are available (not greyed out) on both sides.
- Text chat works fine.
- Video chat and screen sharing can be invoked from both sides (confirmation window shows up), but after confirmation the initiation process doesn't finish successfully. The video/screen sharing session doesn't run. *iChat AV shows a message indicating that it doesn't receive an answer from the remote user device.* If the iChat session is initiated from a buddy's computer, the buddy gets the same message respectively.
- For testing purposes, I changed the internet connection on my MBP from the mobile 3G USB modem to a regular *DSL broadband connection (same ISP, German Telekom). In this scenario, video/audio calls and screen sharing work flawlessly!* Therefore, I assume that the problems in 3G connection mode is caused by the ISP (German Telekom) blocking/restricting ports required by iChat AV for initiating the video call and streaming the data on their 3G network.
Is there any way to bypass ISP restrictions, by either changing specific iChat AV port settings on both ends (client devices) or by port forwarding? If yes, which settings should I change? Unfortunately, it's couldn't find any document indicating which ports are opened/allowed by German Telekom's 2G/3G (GSM/UMTS) network.
Below is an excerpt of the error message produced by iChat AV:
iChat Connection Log:
2010-11-09 21:18:19 +0100: AVChat started with ID 494414145.
2010-11-09 21:18:19 +0100: [email protected]: State change from AVChatNoState to AVChatStateWaiting.
2010-11-09 21:18:19 +0100: 0x1a8bf8b0: State change from AVChatNoState to AVChatStateInvited.
2010-11-09 21:18:28 +0100: 0x1a8bf8b0: State change from AVChatStateInvited to AVChatStateConnecting.
2010-11-09 21:18:28 +0100: [email protected]: State change from AVChatStateWaiting to AVChatStateConnecting.
2010-11-09 21:18:48 +0100: 0x1a8bf8b0: State change from AVChatStateConnecting to AVChatStateEnded.
2010-11-09 21:18:48 +0100: 0x1a8bf8b0: Error -8 (Did not receive a response from 0x1a8bf8b0.)
2010-11-09 21:18:48 +0100: [email protected]: State change from AVChatStateConnecting to AVChatStateEnded.
2010-11-09 21:18:48 +0100: [email protected]: Error -8 (Did not receive a response from 0x1a8bf8b0.)
Video Conference Error Report:
0.000000 @/SourceCache/VideoConference/VideoConference-415.22/Video Conference/DotMacConfiguration.m:1039 type=4 (FFFFFFFF/2)
[HTTP GET failed (0)]
0.000627 @/SourceCache/VideoConference/VideoConference-415.22/Video Conference/DotMacConfiguration.m:758 type=4 (FFFFFFFF/0)
[HTTP GET failed (0)]
0.346813 @/SourceCache/VideoConference/VideoConference-415.22/Video Conference/DotMacConfiguration.m:758 type=4 (FFFFFFFF/0)
[HTTP GET failed (0)]
1331.086051 @/SourceCache/VideoConference/VideoConference-415.22/SIP/SIP.c:2917 type=4 (900A0015/0)
[SIPConnectIPPort failed]
1333.086142 @/SourceCache/VideoConference/VideoConference-415.22/SIP/SIP.c:2917 type=4 (900A0015/0)
[SIPConnectIPPort failed]
1335.086270 @/SourceCache/VideoConference/VideoConference-415.22/SIP/SIP.c:2917 type=4 (900A0015/0)
[SIPConnectIPPort failed]
1337.086603 @/SourceCache/VideoConference/VideoConference-415.22/SIP/SIP.c:2917 type=4 (900A0015/0)
[SIPConnectIPPort failed]
1339.087985 @/SourceCache/VideoConference/VideoConference-415.22/SIP/SIP.c:2917 type=4 (900A0015/0)
[SIPConnectIPPort failed]
1341.088212 @/SourceCache/VideoConference/VideoConference-415.22/SIP/SIP.c:2917 type=4 (900A0015/0)
[SIPConnectIPPort failed]
1343.088361 @/SourceCache/VideoConference/VideoConference-415.22/SIP/SIP.c:2917 type=4 (900A0015/0)
[SIPConnectIPPort failed]
Video Conference Support Report:
929.446913 @/SourceCache/VideoConference/VideoConference-415.22/Video Conference/VCInitiateConference.m:2059 type=2 (00000000/0)
[Connection Data for call id: 1 returns 1
934.996640 @/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
935.002114 @/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]
935.467624 @/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 lip:16402;branch=z9hG4bK0fdd30e326aa779b
Max-Forwards: 70
To: "u0" <sip:user@rip:16402>
From: "0" <sip:user@lip:16402>;tag=544473054
Call-ID: 9c7ecf46-ec3d-11df-8530-f81eeb5f4012@lip
CSeq: 1 INVITE
Contact: <sip:user@lip:16402>;isfocus
User-Agent: Viceroy 1.4
Content-Type: application/sdp
Content-Length: 708
Video Conference User Report:
928.427249 @:0 type=5 (00000000/16402)
[Local SIP port]
934.996832 @/SourceCache/VideoConference/VideoConference-415.22/Video Conference/VCInitiateConference.m:2171 type=5 (00000000/0)
*[Remote Router]*
*[PORT RESTRICTED]*
934.996842 @/SourceCache/VideoConference/VideoConference-415.22/Video Conference/VCInitiateConference.m:2173 type=5 (00000000/0)
[Remote CommNAT Result: 0x000000d0
936.003962 @:0 type=5 (00000000/60)
[Detected bandwidth (kbits/s): 2627 up, 2627 down. (00000000)
936.033015 @/SourceCache/VideoConference/VideoConference-415.22/Video Conference/VideoConferenceMultiController.m:2423 type=5 (00000000/0)
[Start Conference With UserID: u0]
978.787787 @:0 type=5 (00000000/16402)
[Local SIP port]
1014.011790 @/SourceCache/VideoConference/VideoConference-415.22/Video Conference/VCInitiateConference.m:2171 type=5 (00000000/0)
[Remote Router]
[PORT RESTRICTED]
1014.011800 @/SourceCache/VideoConference/VideoConference-415.22/Video Conference/VCInitiateConference.m:2173 type=5 (00000000/0)
[Remote CommNAT Result: 0x000000d0
1015.024555 @:0 type=5 (00000000/60)
[Detected bandwidth (kbits/s): 2627 up, 2627 down. (00000000)
1015.031800 @/SourceCache/VideoConference/VideoConference-415.22/Video Conference/VideoConferenceMultiController.m:2423 type=5 (00000000/0)
[Start Conference With UserID: u0]
1323.083386 @/SourceCache/VideoConference/VideoConference-415.22/Video Conference/VCInitiateConference.m:2171 type=5 (00000000/0)
[Remote Router]
[PORT RESTRICTED]
1323.083396 @/SourceCache/VideoConference/VideoConference-415.22/Video Conference/VCInitiateConference.m:2173 type=5 (00000000/0)
[Remote CommNAT Result: 0x000000d0
(…)

Hi,
Does this 3G device have any set up functions that are on your Mac ?
If it does not it is likely that it is wide open to all Port (65535 of them).
I presume that in System Preferences > Network you see a Public IP when using this device ?
Again this would tend to pint to all the ports being open.
Is there anything on the ISP's web site that suggests this device is unsuitable to be used with VoIP or SIP connections ?
VoIP (Voice over the Internet) uses the SIP connection process the way iChat does.
Most likely the issues is the way packets are sent.
When you do a download, for instance, do you find the speed increases in the first few minutes ?
When some data packets are sent over the Internet the next one is not sent until confirmation that the first has arrived.
This Latency effects Point to Point WiFi (antenna to Dish on House) and satellite connections mostly particularly when it is a two way thing.
It can effect Mobile/Cell phone type connections.
What sort of Speeds are you getting on the 3G device ?
http://www.speedtest.net/
Do these seem to get faster as the time proceeds ? (this can be difficult to spot).
The Log mentions one end being at just over 2Gbps although it does not make it clear which end.
As the Remote end is the end that reports "Router: Port Restricted" and it works over standard DSL we have to presume they have the ports open.
You could try restricting iChat 's Bandwidth in iChat menu > Preferences > Video Section to 500kbps (try it at both ends)
If that does not work try 200kbps
This may stop iChat from trying to send data too Fast for the Network Connections.
Realistically there are a few too many variables here.
It could be Speed of data throughout at the Initiation point. (Slow Start up of data transfer)
It could be an Internal setting preventing SIP.
It could be that the 3G network sends and receives data by different routes.
(I have seen this once when a ISP was repairing some Cabling. To maintain end user speeds they managed their own network to split Incoming and outgoing data to the end point.)
iChat does not like this as it checks the IPs and the Hops (number of intermediate stages/servers) and if the data is different it will not connect (Man in the Middle attack protection).
I can't remember the last time I knew of someone being successful with either an 3G USB dongle or a 3G phone as Modem (internet Sharing).
Despite my ideas I think you will be unlucky and this will not work.
10:31 PM Saturday; November 13, 2010
Please, if posting Logs, do not post any Log info after the line "Binary Images for iChat"

What ports do I need to open in a home router to support Screen Sharing?

I'm trying to support my 88 year-old dad who has totally messed up his iMac. We're both running 10.6.8. I went ahead and bought the Easy Remote Desktop app from the app store, since I don't need a heavy-duty admin tool, just to see and to remotely manipulate his screen. I tested it on my home LAN with my wife's computer and it works great. I did have to find out her IP address, and she did have to turn on Screen Sharing services open to just me first. The downside for Screen Sharing vs. Remote Administration is that there is no announcement that you're there.
So I'm thinking that I can just type in my dad's IP address. Of course he has a DSL router and probably has a DHCP address, so I found out about Dynamic DNS, and located a free Dynamic DNS service. I've already established (the functional equivalent of) a static IP for myself with this service, and I'm thinking the next step is to talk my dad through doing the same for himself. Then the next hurdle I think would be to talk him through opening the Screen Sharing service on his Mac, and to add me as a user. But the final hurdle I think would be to open inbound ports for Screen Sharing from my IP address. Since Screen Sharing is a native Mac OS function, I figure this is the place to ask that question. And to ask if I'm on the right track here...

Screen Sharing uses port 5900.
However, I'm going to suggest that you use TeamViewer.com as it will deal with all the networking issues much more easily and without needing to worry about opening ports in your router.

Screen sharing and video

Hello all.
video works fine at my house where I can turn on UPNP. However at work nothing works because UPNP isn't enabled. I have to forward all ports to my laptop. So my question is what ports to forward?

It is with the Screen Sharing side that we have real problems.
iChat 3 used
TCP 5190, 5220, 5222, 5223, 5298
UDP 5060, 5190, 5297, 5298, 5353, 5678, 16384-16403
This includes all the Jabber, Bonjour and A/V ports as well as the Login and File sending.
Leopard/iChat
Same until we get to that last group or twenty UDP ports
Port 5060 is dropped and the group becomes just 10 (16393-16402) still inside the iChat range if already done.
The Screen Sharing I have seen with Little Snitch running suggest this happens on three ports. Two for the Screen Sharing and one for the Audio part.
The Audio part remains where is does in Normal Audio or Video chats with it's first choice being 16402.
It's the other two ports.
Theses seem fairly random in the 50,000 range. They are widely dispersed as well which makes it difficult to suggest a small range that iChat might then use.
9:26 PM Monday; December 24, 2007

Screen Sharing via iCloud on Lion Freezes at Login Screen

After updating to OSX Lion 10.7.3, screen sharing between two computers via the Internet allows me to connect to the remote computer and see the remote user's login screen, but as soon as I click on a user to login, the screen share image freezes before I can enter the user password.
Using iCloud Back to My Mac because all machines have the same Apple ID & password. Exact same setup worked before the 10.7.3 upgrade, but it could be coincidence.
Details:
Can see the remote computers in my finder,
Can click on them and connect successfully using either the Apple ID or the name and password a user that is allowed under Sharing -> Screen Sharing,
When clicking on "Screen Share," the computers connect and I'm prompted to either "Ask to Share the Display" or "Connect to Virtual Display"Since there really isn't anyone using the computer, I select "Connect to Virtual Display"
After clicking "Connect to Virtual Display" the Screen Sharing window shows the remote computer's login screen, whcih shows the user names, their icons and "Sleep" "Restart" or "Shut Down" on the bottom of the screen. One user has an orange circle with a white checkmark next to it.
Previously, I could click a user's name or icon, enter the password and control the remote Mac. Now, not amount of clicking works.
Have tried disconnecting and reconnecting as different users or using Apple ID without changes in the perofmance. Have restarted both machines.
Any help?

I'm having the same problem screen sharing to a Lion 10.7.3 machine, I get this message.
However, it works just like it used to when I screen share from a 10.7.3 machine to another Mac running 10.6.8.
Any thoughts?
Thanks!

Screen sharing via iChat

Not really a server question I know, but I wondered if anyone was experimenting with iChat screen sharing as a support tool. Most of my customers are set up for iChat using my own server and IM me with questions from time to time. I've just started installing Leopard on a few clients and wanted to try out the screen sharing. My own machine is a 17 inch Powerbook and it is looking as if there's a limit to the desktop size of the remote machine. Trying it with this particular client's machine, which is a 15 inch Macbook Pro with an attached 20 inch Cinema display, iChat screen sharing never finishes initialising. But if I reduce the resolution of the Cinema display from its default to, say, 1344x840 it works - and shows both remote screens (the Macbook display and the Cinema display).
Am I discovering that it'll only work where there are no displays connected to the remote system that have a higher resolution than the local one(s), or is there a glitch here that can be fixed? Given that it just 'hangs' I'm tempted to think it's a glitch and not some designed-in limit.

...should have mentioned - the connection is jabber of course, the server is 10.4.11 and both machines are 10.5.1 with 2Gb RAM.

Will Firefox Hello support screen sharing via video chat?

Similar Messages

Maybe you are looking for