#1 2009-03-25 00:45:46

**_jason.chan_**

How to resolve if 'Connect Pro Connection Test' fails?

Hi,

I have a user who fails the 2nd test 'Connect Pro Connection Test' while doing the test for meeting connection. Tried the workaround mentioned under 'My company uses a proxy server to control internet access' but that does not help.

Any advice is greatly appreciated.

Cheers,
Jason

**_michael_**

Re: How to resolve if 'Connect Pro Connection Test' fails?

What do the details of the test indicate? Somewhat hidden, so you need to click on "send email" and then "show details." 

What protocol is being used?  And what is the user's latency/connection speed look like?

**_gajett_**

Re: How to resolve if 'Connect Pro Connection Test' fails?

My first thought is that port 1935 is blocked on that user's end of things....  Also interested in seeing  the report results.

Greg

**_jason.chan_**

Re: How to resolve if 'Connect Pro Connection Test' fails?

Thanks Michael and gajett for both your replies.

Here are the details:

=======================
Player Version: WIN 10,0,22,87

App-Server returned: code:ok,
servers=rtmp://flolive.flinders.edu.au:1935/_rtmp://localhost:8506/,rtmpt://flolive.flinders.edu.au:443/_rtmp://localhost:8506/

ERROR: FMS Server did not return correctly!
=======================

Based on the details above, can I say that ports 1935, 8506 and 443 is used?

Cheers,
Jason

**_gajett_**

Re: How to resolve if 'Connect Pro Connection Test' fails?

Jason,
Those are the ports Connect wants to use/configured by you to deliver the service.  Port 80 is also used to serve web pages.  That's not part of the test, since if people can get to the test, port 80 is working.
This looks like port 1935 is blocked or otherwise restricted on the user end --
here's a good test from your Connect server:

App-Server returned: code:ok, servers=rtmp://flolive.flinders.edu.au:1935/_rtmp://localhost:8506/,rtmpt://flolive.flinders.edu.au:443/_rtmp://localhost:8506/

FMS Server connected with protocol: rtmp

BW Test Results: = _ latency=168 msec, down=703.9 kbit/s, up=271.8 kbit/s _

Add-in Installed

Add-in version:9,1,299,0

-- the FMS server runs through 1935.  Since your results indicate a fail, i'd start w/ 1935. The other ports are 443 for ssl, 8506 is being used internally by the connect server, not out to the world.

Send this person a link to a recording.  If 1935 is blocked, they'll see the loading screen, then hang.

Greg

**_alanvanwyk_**

Re: How to resolve if 'Connect Pro Connection Test' fails?

OK - the user is blocked on 1935 as they are on a corprate network, that requires high levels of security (think stock exchange / investment bank etc)

How do I get around it and force traffic to be tunneled over http or https? At the moment, all working connections to my meeting server return a port 1935 direct connection when I run netstat and all failed connection return 'SYN_SENT' to port 1935 in netstat output.

**_alanvanwyk_**

Re: How to resolve if 'Connect Pro Connection Test' fails?

Oh, also, these users are able to hit the connection test on the Adobe site and connect Ok - but get FMS server issues on my Metting server!

Really, all I need, is to understand how the box at Adobe is set up?

**_anhyzer_**

Re: How to resolve if 'Connect Pro Connection Test' fails?

We're still on Connect 6, SP3, but this TechNote describes the way in which we allow connections on ports 1935, 443, and 80:

   http://kb2.adobe.com/cps/240/2405470e.html

I'm not certain if the same method is used for Connect 7 since the technote doesn't explicitly state that it works with Connect 7.

--Chris

Last edited by **_anhyzer_** (2009-05-18 15:10:39)