Skip to main content
W
whycantijuzusemyname
Participating Frequently
January 12, 2009
Question

Connecting to FMSS 3 and Port Tunneling

  • January 12, 2009
  • 2 replies
  • 706 views
Hello

I am having problems connecting to Flash Media Streaming Server 3 with port tunneling.

I ran the FMS Port Connection Survey on two computers in my office. On one I am able to successfully connect across all ports, on the other I can only connect over port 80.

Seeing that, I thought I should configure port tunneling on my FMS server and have done so following this great article.

I've tested on the computer that can only accept a connection over port 80 by forcing the connection to port 80 like so: nc.connect ("rtmp://server.com:80/vod/");. This works fine on all computers.

Then I read here that if I leave out the port number it will yield 2 connection attempts (one over port 1935 and then over 80). First it attempts to connect over 1935, if unsucessful it will connect over 80. This sounds logical and something I should do but this is also where the problem lies. On the computer that only accepts connections over port 80, it will not connect. It seems that the FMS is not attempting to connect the second time.

Is this 2nd connection attempt something that should happen automatically?

Did I miss out something when I was configurating the FMS?

Looking forward to your comments.

Thanks,
Ryan

    This topic has been closed for replies.

    2 replies

    W
    whycantijuzusemynameAuthor
    Participating Frequently
    January 15, 2009
    Thanks for your reply. I dont have any other servers running (including any web server) on the computer except FMS.

    There's actually two FMS servers running through a load balancer and I'm connecting to them (well, connecting to the first one unless there's a problem with it) via a virtual IP address.. I wonder if this can be causing the problem?

    What's even more strange is when run the FMS port survey test at home all connection attempts are successful but when try to connect to my FMS server through my site at home it will not work unless I remove the port number from the URL or I put 1935 - it will not connect over 80.

    What I think might be the problem is - the FMS is not timing out on the connection attempts and therefore is not switching ports after a failed attempt (it just sits there). My plan now is to put in my own checks .. first attempting a connection over 1935 (this will work at home, and on my computer in the office) and if I get back a failed attempt then I'll try to connect over 80 (which works on the other computers in my office).

    I dont understand why it wont work at home over port 80 though when the port survey tells me that I'm able to connect over it..
    A
    Anonymous
    January 12, 2009
    On the question about the flashplayer attempting port 80 automatically... yes, it will, after about 20 seconds or so (the first attempt on port 1935 has to time out before the port 80 attempt is made).

    I've found that in a lot of cases, failed RTMPT connections on port 80 are due to server misconfiguration. The most common problem I've seen is people having FMS and an HTTP server (IIS, Apache, etc) installed on the same server and bound to the same IP address. If you're in that boat, you need to do one of two things:

    1. Remove the HTTP server from the box FMS is on
    2. Add a second IP address for FMS.

    With a second IP address, you can bind FMS to one and he HTTP server to the other. That way, you have a port 80 on each IP, and you don't have device conflicts.

    If you're running IIS 6 on Windows, you'll need to disable socket pooling on IIS so it doesn't bind to port 80 on all IP's. To do this, you'll need to use httpcfg.exe
    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices