How to run Red 5 on a shared IIS server on port 80
Setting up Red5 on a box which also contains a web server can be a challenge if you are restricted to using specific ports because of a firewall. Here is how we set up Red5 on a Windows 2003 server which also contains a production IIS server.
Our firewall only allows traffic on ports 80 and 443. This is non-negotiable, so we needed to work around the requirement.
The folks – in particular Walter Tak – on the Red5 mailing list pointed me in the right direction: Make another IP (or two) for Red 5 to run under.
IIS was already using ports 80 and 443, so the system administrator made two additional IPs for Red5 to use, one for rtmp and one for http. He then changed the settings in the Default Website Properties in IIS Manager: In Web Site Identification: IP Address, instead of (All Unassigned), he selected the single IP which we wanted IIS to listen on. We did not want IIS to interfere with port 80 on the IPs used by Red5.
Continue reading