Answer should be obvious, but I don't have a way to test. I have FMIS running on a 2003 server with IIS (on 80). Can someone connect to FMIS over port 80 if their firewall blocks 1935? Or do I need to have FMIS on it's own server without IIS using port 80?

I've modified the adapter.xml file to include:
<HostPort name="edge1" ctl_channel="localhost:19350">${ADAPTOR.HOSTPORT} :1935,80,443</HostPort>

Thanks for any help you can provide,

Steve

Actually, I just found another post that says you can't use 80 if IIS is bound to it. That makes sense, but what puzzles me is that I did a test and closed port 1935. Shouldn't it have rolled over to the SSL port (443)? I wasn't able to connect and I know that 443 is open.

Thanks again!

you may try to connect using -rtmpe- instead of -rtmp-

Nice thought... but that didn't work either. Made sure 443 was not in IIS's properties and rebooted the server just to make sure.

Steve

I would just test with 1935 for the time being. If that works then you know that FMS and IIS are both trying to bind to port 80 of the particular IP. IIS will bind to all IP numbers if you let it, there are some settings to change that, I just don't remember them offhand... sorry. If IIS beats FMS to the binding then FMS binding will fail, you should see something in the event viewer for that I think.

Thanks! Here's what I've got...

- Two IP's for the server xx.xx.xx.219 and xx.xx.xx.188
- 1935 works with no problem
- Rather than all IP's, IIS is bound to one (xx.xx.xx.219)
(default web site properties, web site tab)
- Changed adaptor.xml to:
<HostPort name="edge1" ctl_channel="localhost:19350">${ADAPTOR.HOSTPORT} xx.xx.xx.188:80,1935,443</HostPort>
- In server.xml, localhost changed to:
<Localhost>xx.xx.xx.188</Localhost>
<PublicIP>xx.xx.xx.188</PublicIP>

Event log is showing errors:
Failed to create listener for adaptor _defaultRoot_, IP xx.xx.xx.188, port 80:
Failed to create listener for adaptor _defaultRoot_, IP xx.xx.xx.188, port 443:

So it appears that IIS still has hold of the ports somehow.

I'll try a reboot when no one is on the system, but I'm guessing that's not going to help.

Thanks again!

Some progress, no longer reporting errors in the error log. I'm now getting:

Listener started(_defaultRoot__edge1):x.x.x.188:1935/v4
Listener started(_defaultRoot__edge1):x.x.x.188:80/v4
Listener started(_defaultRoot__edge1):x.x.x.188:443/v4

I found a very good resource for configuring IIS and FMIS together at:

http://www.flashcomguru.com/tutorials/fcs_iis.cfm

If you are on a 2003 server, you'll need this too:

http://support.microsoft.com/kb/813368

I noticed that Graeme had responded to a similar post "Port 80" and mentioned you needed a change to fms.ini. So, I changed it to:

ADAPTOR.HOSTPORT = xx.xx.xx.188:1935,80,443

I've now tried to connect explicitly on ports 80 and 443 with:

rtmp://xx.xx.xx.188:80
rtmp://xx.xx.xx.188:443
rtmpe://xx.xx.xx.188:443

But I get the same "NetConnection.Connect.Failed" error each time.

I also noticed in the fms.ini comments that it said:

# This section contains configurable parameters in Adaptor.xml #

So, my questions boil down to:

1. Do I need to change Adaptor.xml back to original?
2. Do I need to change both fms.ini and Adaptor.xml?
3. If the log shows I'm binding to 443 and 80 successfully, what else could stop a connection (we know FW is open)

And a big #4...

Do I need to explicitly conntect to port 80 or 443 when I detect a connection error or is there a mechanism for it to automatically rollover to the next port?

Thanks... we're close... I hope!! ;-)

sr

Working!!!

In desperation, I rebooted the server rather than start and stop services and it worked. I closed 1935 on the firewall and can access either port on 80 or 443 without explicitly selecting a port. However, rollover is very slow so maybe it's best to default to 1935.

Does anyone have any recommendations for this sort of thing? Is it best to default to 80 rather than mess with going to 1935 first? What's the benefits/pitfalls of using one approach over the other?

Thanks, hope this all has helped some others!

Steve

Hi Steve, Hi Graeme,

I also had the same problems. Now i changed my website services to a different IP.

So the FMS is exclusively working on the IP. I changed the fms.ini but it doesn´t work over rtmp://xx.xx.xx.74:80

Did you restart the complete server and not only the application over stop/start?

Maybe that solves my problem. Where the swf-file is placed does not matter or?

OK. One last question, hopefully ;-)

I´ve everything configurated. The only point i´ve to do is to say the fms that it only should work with one specific ip-adress. Where and how can I configurate this?

Many many thanks in advance!

Tobi

Ok.

I changed both xml-files. Although I did not find the <HostPort>:1935</HostPort> in the adaptor.xml.

In my case the line looks like this:

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

To test I changed everything like Steve but after the changes the streaming didn´t work anymore.

How can I go on?

If you want FMS to work with only one IP number, then specify that in the fms.ini file.

At this line ADAPTOR.HOSTPORT = :1935,80,443 ?

And then restart the whole system?

When I change this line and restart the FMS nothing works. Do I have to restart the whole system then?

Hope can give me a short answer.

Tobi

Everythign works now. It was a problem with the windows 2003 sever.

thanks everyone for teh support!

Hi Tobbis,

we have the same issue, my application is connecting to port 1935, when i change the fms.ini with port 80 ,after restarting the fms , i am able to connect to port 1935, but i am not able to connect to port 80. can i now the problem can be, tobbis you told you have same problem and it is problem with windows 2003 server, we have same server, can i now what that problem is.....

thanks,
ram.

Most likely port 80 is being used by another application on the server. Like IIS perhaps or another web server.

That´s totally right. It´s not possible to share port80 over one IP with the FMS and an other application.

I'm having this same issue - can you guys let me know what resolved the issue for you?

Use a dedicated IP for FMS.