Macromedia Flash Server - FMS2 NetConnection question

This is Interesting: Free IT Magazines  
Home > Archive > Macromedia Flash Server > June 2006 > FMS2 NetConnection question





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author FMS2 NetConnection question
Dave Williams

2006-06-14, 7:11 pm

Does anyone know where the script is on the FMS server that handles
the rtmp connection? I am having difficulty getting FMS to find Port
80 and I want to trace the actions in the script.

My understanding is that FCS1.5 looks first to Port 1935, then Port
443 and finally tunnels over to Port 80. Is it the same on FMS2?

I've discovered that my application with Simple Connect will find
Port 80 perfectly when the client is behind a firewall blocking Port
1935. However, when I instead use NetConnection(); and APP_ADDRESS =
"rtmp://12.34.56.77/global"; unfortunately, only Port 1935 is
accessible. Port 80 is never found.

I've already made sure the httpcfg.exe isolates Port 80 to IIS on my
first IP and FMS2 is bound to my second IP address.

In fms.ini I have inserted:
ADAPTOR.HOSTPORT = 12.34.56.77:1935,80,443

and in Adaptor.xml, I have inserted:
<HostPort> 12.34.56.77:1935,80,443 </HostPort>

Does anyone know how I can start to resolve my problem? Anyone tested
accessing Port 80 on FMS2 when a client is behind a firewall?

Thanks for the help... dave

--
________________________________________
_______
FlashComm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com

Vivek lakhanpal

2006-06-15, 1:11 am

Hi Dave,

Yes we have done it successfully. My understanding of listening on Port 80
is that you have to make your connection listen on Port 80 otherwise it will
always listen on Port 1935 which is the default.

The process i follow is first check if client is responding on 1935 if not
then try on Port 80. So you have to loop through for each port one by one.
Hope i am clear in my explanation.

So if you want to listen on Port 80 you always have to specify it in
connection string as rtmp://12.34.56.77:80/global.

Thanks
Vivek.


On 6/14/06, Dave Williams <dave-8PHf0o9tX6fO4pIUtvOOcmXnswh1EIUO@public.gmane.org> wrote:
>
> Does anyone know where the script is on the FMS server that handles
> the rtmp connection? I am having difficulty getting FMS to find Port
> 80 and I want to trace the actions in the script.
>
> My understanding is that FCS1.5 looks first to Port 1935, then Port
> 443 and finally tunnels over to Port 80. Is it the same on FMS2?
>
> I've discovered that my application with Simple Connect will find
> Port 80 perfectly when the client is behind a firewall blocking Port
> 1935. However, when I instead use NetConnection(); and APP_ADDRESS =
> "rtmp://12.34.56.77/global"; unfortunately, only Port 1935 is
> accessible. Port 80 is never found.
>
> I've already made sure the httpcfg.exe isolates Port 80 to IIS on my
> first IP and FMS2 is bound to my second IP address.
>
> In fms.ini I have inserted:
> ADAPTOR.HOSTPORT = 12.34.56.77:1935,80,443
>
> and in Adaptor.xml, I have inserted:
> <HostPort> 12.34.56.77:1935,80,443 </HostPort>
>
> Does anyone know how I can start to resolve my problem? Anyone tested
> accessing Port 80 on FMS2 when a client is behind a firewall?
>
> Thanks for the help... dave
>
> --
> ________________________________________
_______
> FlashComm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
> To change your subscription options or search the archive:
> http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
>
> Brought to you by Fig Leaf Software
> Premier Authorized Adobe Consulting and Training
> http://www.figleaf.com
> http://training.figleaf.com
>




--
VIVEK LAKHANPAL
Sr. Software Engineer
AuthorGEN Technologies Pvt. Ltd.
http://www.authorgen.com
________________________________________
_______
FlashComm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com

Dave Williams

2006-06-15, 1:11 am

Hi Vivek...

But on my FCS1.5 server, I didn't have to be concerned with setting
the Port in my rtmp statement. If 1935 wasn't available, FCS simply
looked at 443 and then 80.

Are you saying with FMS2 I have to write a script that checks for
Port availability... just like the Simple Connect component?? Has the
auto port search function been eliminated?

cheers... dave

At 6:58 AM +0530 6/15/06, Vivek lakhanpal wrote:[vbcol=seagreen]
>Hi Dave,
>
>Yes we have done it successfully. My understanding of listening on Port 80
>is that you have to make your connection listen on Port 80 otherwise it will
>always listen on Port 1935 which is the default.
>
>The process i follow is first check if client is responding on 1935 if not
>then try on Port 80. So you have to loop through for each port one by one.
>Hope i am clear in my explanation.
>
>So if you want to listen on Port 80 you always have to specify it in
>connection string as rtmp://12.34.56.77:80/global.
>
>Thanks
>Vivek.
>
>
>On 6/14/06, Dave Williams <dave-8PHf0o9tX6fO4pIUtvOOcmXnswh1EIUO@public.gmane.org> wrote:

--
________________________________________
_______
FlashComm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com

Jayson K Hanes

2006-06-15, 1:11 am

No server app can accept connections on a port it's not configured to
listen on.

Thus.. your fcs1.5 server worked on port 80 because it was listening on
port 80 (perhaps as well as the other ports, too)

FCS/FMS does not listen on port 80 by default -- it would conflict with
port 80 used by IIS or Apache etc and not start (in typical set-ups)..

Look more closely at your fcs1.5 configuration and you'll see..

-Jayson

> -----Original Message-----
> From: flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org [mailto:flashcomm-
> bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org] On Behalf Of Dave Williams
> Sent: Wednesday, June 14, 2006 10:35 PM
> To: FlashComm Mailing List
> Subject: Re: [FlashComm] FMS2 NetConnection question
>=20
> Hi Vivek...
>=20
> But on my FCS1.5 server, I didn't have to be concerned with setting
> the Port in my rtmp statement. If 1935 wasn't available, FCS simply
> looked at 443 and then 80.
>=20
> Are you saying with FMS2 I have to write a script that checks for
> Port availability... just like the Simple Connect component?? Has the
> auto port search function been eliminated?
>=20
> cheers... dave
>=20

________________________________________
_______
FlashComm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com

Stefan Richter

2006-06-15, 7:11 am

But I think Dave mentioned that he has configured FMS to listen on port 80
and has unbound IIS from that IP. So that's a good start.

First of all no, you do not need to write your own connection routine to
probe different ports, the Flash Player (not FMS!) will handle this for you.
However to make the connection as fast as possible you could fire several
connection attempts on different ports at once and accept the first one that
succeeds, canceling the others out.

But the issue here may be that you believe FMS is listening on 80 when in
fact it may not be. Have you tried restarting FMS and IIS? If you do and
there is no error (both services start up fine) then your configuration
should be fine.

Also if you are modifying fms.ini then you do not need to make changes to
Adaptor.xml as well. If you are just running the defaultVhost then I'd do
this:

In fms.ini:
ADAPTOR.HOSTPORT = 12.34.56.77:1935,80,443

In Adaptor.xml:
<HostPort name="edge1" ctl_channel=":19350">${ADAPTOR.HOSTPORT}</HostPort>

This last one tells Adaptor.xml to use the value that you've set in fms.ini

Now in theory (after you restart FMS) it should be listening on 3 ports.
Which IP did you assign to IIS?

Stefan


[vbcol=seagreen]
> -----Original Message-----
> From: flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
> [mailto:flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org] On Behalf Of
> Jayson K Hanes
> Sent: 15 June 2006 03:39
> To: FlashComm Mailing List
> Subject: RE: [FlashComm] FMS2 NetConnection question
>
> No server app can accept connections on a port it's not
> configured to listen on.
>
> Thus.. your fcs1.5 server worked on port 80 because it was
> listening on port 80 (perhaps as well as the other ports, too)
>
> FCS/FMS does not listen on port 80 by default -- it would
> conflict with port 80 used by IIS or Apache etc and not start
> (in typical set-ups)..
>
> Look more closely at your fcs1.5 configuration and you'll see..
>
> -Jayson
>
> FCS simply
> checks for Port
> Has the auto

________________________________________
_______
FlashComm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com

Dave Williams

2006-06-15, 1:11 pm

Hi Stefan...

Thanks for the direction to a new thought....

(A) When I run netstat I find:
1) my IIS IP 12.34.56.106:80 identified as LISTENING
2) my FMS2 IP 12.34.56.107:80, 12.34.56.107:443 and
12.34.56.107:1935 as LISTENING

(B) I have also restarted FMS and IIS without conflicts.

(C) An application using SimpleConnect works just fine when the
client is behind a firewall and Port 1935 is blocked.

Since you are telling me that port probing is being done with Flash
Player and not FMS2 could I be having a problem with the player?
Player 7 never gave me a problem... are there some new issues with
Player 8?

cheers... dave

At 9:39 AM +0100 6/15/06, Stefan Richter wrote:[vbcol=seagreen]
>But I think Dave mentioned that he has configured FMS to listen on port 80
>and has unbound IIS from that IP. So that's a good start.
>
>First of all no, you do not need to write your own connection routine to
>probe different ports, the Flash Player (not FMS!) will handle this for you.
>However to make the connection as fast as possible you could fire several
>connection attempts on different ports at once and accept the first one that
>succeeds, canceling the others out.
>
>But the issue here may be that you believe FMS is listening on 80 when in
>fact it may not be. Have you tried restarting FMS and IIS? If you do and
>there is no error (both services start up fine) then your configuration
>should be fine.
>
>Also if you are modifying fms.ini then you do not need to make changes to
>Adaptor.xml as well. If you are just running the defaultVhost then I'd do
>this:
>
>In fms.ini:
>ADAPTOR.HOSTPORT = 12.34.56.77:1935,80,443
>
>In Adaptor.xml:
><HostPort name="edge1" ctl_channel=":19350">${ADAPTOR.HOSTPORT}</HostPort>
>
>This last one tells Adaptor.xml to use the value that you've set in fms.ini
>
>Now in theory (after you restart FMS) it should be listening on 3 ports.
>Which IP did you assign to IIS?
>
>Stefan
>
>
>

--
________________________________________
_______
FlashComm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com

Stefan Richter

2006-06-15, 1:11 pm

I wouldn't say for sure that there are no issues with Player 8... I think I
remember that some Oss can take longer before trying the next connection.

What happens when you try and explicitly connect to FMS over port 80 from
your app?

Peldi posted this a long time ago, maybe worth running it:

> --- pseudo-very-ugly-code ---
>
> nc = new NetConnection();
> nc.onStatus = function(info) {
> trace("Port 1935 returned:"+info.code);
> }
> nc.connect("rtmp://server:1935/app");
>
> // add some interval here
>
> nc2 = new NetConnection();
> nc2.onStatus = function(info) {
> trace(Port 443 returned:"+info.code);
> }
> nc2.connect("rtmp://server:443/app");
>
> // add a little time interval here
>
> nc3 = new NetConnection();
> nc3.onStatus = function(info) {
> trace(Port 80 returned:"+info.code);
> }
> nc3.connect("rtmp://server:80/app");
>
> --- end of pseudo-very-ugly-code ---



Stefan




> -----Original Message-----
> From: flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
> [mailto:flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org] On Behalf Of
> Dave Williams
> Sent: 15 June 2006 15:45
> To: FlashComm Mailing List
> Subject: RE: [FlashComm] FMS2 NetConnection question
>
> Hi Stefan...
>
> Thanks for the direction to a new thought....
>
> (A) When I run netstat I find:
> 1) my IIS IP 12.34.56.106:80 identified as LISTENING
> 2) my FMS2 IP 12.34.56.107:80, 12.34.56.107:443 and
> 12.34.56.107:1935 as LISTENING
>
> (B) I have also restarted FMS and IIS without conflicts.
>
> (C) An application using SimpleConnect works just fine when
> the client is behind a firewall and Port 1935 is blocked.
>
> Since you are telling me that port probing is being done with
> Flash Player and not FMS2 could I be having a problem with
> the player?
> Player 7 never gave me a problem... are there some new issues
> with Player 8?
>
> cheers... dave
>
> At 9:39 AM +0100 6/15/06, Stefan Richter wrote:
> listen on port
> connection routine
> handle this for you.
> accept the
> on 80 when
> IIS? If you do
> make changes
> defaultVhost then
> on 3 ports.
> configured
> conflict
> [mailto:flashcomm-
> Williams > Sent:
> available,
> checks for
>
> --
> ________________________________________
_______
> FlashComm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
> To change your subscription options or search the archive:
> http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
>
> Brought to you by Fig Leaf Software
> Premier Authorized Adobe Consulting and Training
> http://www.figleaf.com http://training.figleaf.com
>


________________________________________
_______
FlashComm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com

Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com