|
|
Subject:
Windows server 2003 IIS and Media Services on port 80
Category: Computers > Internet Asked by: stroltz-ga List Price: $40.00 |
Posted:
21 Apr 2004 22:01 PDT
Expires: 21 May 2004 22:01 PDT Question ID: 334166 |
I have setup Windows small business server 2003. I am using it to stream live video and use IIS. I am using a separate encoding machine and Windows media encoder. I need to stream over the net via Http on port 80 because some of the clients will be behind restrictive firewalls. I want to be able to run IIS as well as using the media services on the same machine. The problem I am experiencing is getting IIS and WMS to work together as they both want port 80. The server is behind a NAT firewall router (A Netgear FVS318) which has a single static IP address. I have installed 2 NICs on the server, assigned a local IP to each card and tried to get IIS and WMS to use port 80 on the separate cards to no avail. As per the article here; http://support.microsoft.com/default.aspx?scid=kb;en-us;328728&Product=wms I also followed a slightly separate article in the server help files. I also tried to shift IIS to using a different ports from 80. This is not ideal though because each client then has to know the port before it can connect. It did not work either, the HTTP plug-in on the server still would not start. I can get it to stream via Http on port 80, but only after disabling IIS. My question is this; Is there another port I can tell WMS to use over Http that is open on most firewalls negating the port 80 problem? If not then; Can I get a single server, behind a single router and one IP to serve both streaming media and IIS sites. If I can, then how best can I stop IIS and WMS from conflicting on port 80. If I can?t, then what is the best/easiest way to have at least local LAN IIS services and WAN WMS? Thanks. |
|
Subject:
Re: Windows server 2003 IIS and Media Services on port 80
Answered By: cerebrate-ga on 28 Apr 2004 17:31 PDT |
Dear stroltz-ga, It should certainly be possible for you to get WMS and IIS running together on the same server without much trouble. I've double-checked this procedure using a virtual Windows 2003 Server here, so this procedure should hopefully work for you. It requires that the server be configured with two IP addresses, either two separate NICs or one NIC with two virtual addresses (it's exactly the same whether both of these are WAN IPs, or one is LAN and one is WAN). In this example, I'm using 172.16.2.1 for IIS, and 172.16.2.2 for Media Services. 1. Double-check the configuration of every web site in IIS Administrator; every web site must be configured to run off the IIS address (172.16.2.1 in this case) only. Any left set to "All Unassigned" will cause trouble later on. (Note: the web site that contains the "Exchange" and "public" subfolders should be given 127.0.0.1 as a second IP address, otherwise Exchange System Manager will give errors.) 2. From the \inetpub\adminscripts folder, run the following command: cscript adsutil.vbs set w3svc/disablesocketpooling true 3. Stop the World Wide Web Publishing service, stop and restart the IIS Admin service, then restart the WWW Publishing Service. 4. Install the Support Tools from the original Windows Server disk (located in \support\\tools\suptools.msi ). 5. Stop the HTTP service (net stop http /y). This will also stop the WWW service and the HTTP SSL service. As it's technically a driver, rather than a service, this has to be done from the command line. 6. From the folder your installed the support tools in, run the following command (substituting your IIS address appropriately): httpcfg set iplisten -i 172.16.2.1 7. Restart the services you stopped. Starting the WWW service should automatically restart the others (net start w3svc). You may have to restart any Exchange services that got stopped earlier in this procedure manually. 8. You should then be able to set the WMS HTTP Server to use only the selected IP address in its properties on the default port 80, and enable it successfully. If you have any more trouble getting this working, please feel free to request a clarification. Hope this helps, cerebrate-ga Additional links: How To Disable Socket Pooling http://support.microsoft.com/default.aspx?scid=kb;EN-US;238131 IIS 6.0: Setting Metabase Property DisableSocketPooling Has No Effect http://support.microsoft.com/default.aspx?scid=kb;EN-US;813368 Search strategy: Personal knowledge as sysadmin, and reproduction of problem. |
|
Subject:
Re: Windows server 2003 IIS and Media Services on port 80
From: topbanana-ga on 24 Apr 2004 11:14 PDT |
Port 8080 is an alternative HTTP port which would be open on any secure firewall. Your point about having to point (sorry!) the client to that particular port number is valid, hence it'd be wise to configure wms to use 8080 rather than iis. |
If you feel that you have found inappropriate content, please let us know by emailing us at answers-support@google.com with the question ID listed above. Thank you. |
Search Google Answers for |
Google Home - Answers FAQ - Terms of Service - Privacy Policy |