Re: Windows Media Server deployment
- From: "Igor" <Igor@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 30 Jan 2006 08:11:27 -0800
Hi Neil !
Server is in datacenter so we don’t need firewall on every machine.
We tested ports with www.grc.com shields up and there is definitely firewall
somewhere in between. When we try to access windows media service locally
mms://eridani/Sample_Broadcast everything works fine, but from outside we can
not access it. Windows firewall is turned off, Tcp/Ip filtering is disabled.
All those ports are opened, but when we try to telnet or connect via http,
mms, or rtsp connection fails.
Is there any different way to disable ports on win 2003 ???
Can you help us to determine problem.
Thanks
Igor
"Neil Smith [MVP Digital Media]" wrote:
> Hmmm, odd (not that I'd run a server without a firewall anyway).
>
> If you get a command line up and do
>
> netstat -an
>
> Can you see the service listening on ports
>
> 80 TCP
> 554 TCP, UDP
> 1755 TCP, UDP
>
> Or is something else hogging those services such as ISA server (1755)
> or a web server (80) or Helix Server / Darwin Streaming Server (554) ?
>
> Cheers - Neil
>
>
> On Mon, 30 Jan 2006 04:16:29 -0800, "Igor"
> <Igor@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
>
> >Windows firewall was switched off before i installed WMS.
> >
> >Control panel/Windows firewall/Off
> >
> >I'm sure about that.
> >
> >Any ideas ???
> >
> >"Neil Smith [MVP Digital Media]" wrote:
> >
> >> On Mon, 30 Jan 2006 01:16:27 -0800, "Igor"
> >> <Igor@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
> >>
> >> >Hello,
> >> >
> >> >We have successfully installed WMS on machine. We are running PLESK on same
> >> >machine with WMS, but problem is that we cannot access to WMS stream from
> >> >outside with mms:// or http:// protocol. Control protocols (http,mms,rtsp)
> >> >are enabled. WMS http port is different then IIS http port. WMS works on http
> >> >port 8000.
> >> >
> >> >We have multiple Ips and vhosts on that machine. Locally everything works
> >> >perfect , but from outside ( as mentioned before ) nothing works as it
> >> >should, and we do not have any firewall.
> >>
> >> ______________^^^ Are you *sure* about that ???
> >>
> >> Windows Server 2003 release 2 comes with the windows firewall switched
> >> on by default, and WMS is not enabled to traverse that until you
> >> specifically enable it. This is a perfectly reasonable security
> >> measure to keep the box locked down until a server role is configured
> >> and access permissions are set to your satisfaction.
> >>
> >> If in doubt, so to the firewall and the easiest way is to add
> >> wmservices.exe to the exceptions list, as stated in this document
> >> http://www.microsoft.com/windows/windowsmedia/serve/firewall.aspx#WindowsFirewall
> >>
> >> HTH
> >> Cheers - Neil
> >>
>
.
- Follow-Ups:
- Re: Windows Media Server deployment
- From: Neil Smith [MVP Digital Media]
- Re: Windows Media Server deployment
- References:
- Re: Windows Media Server deployment
- From: Neil Smith [MVP Digital Media]
- Re: Windows Media Server deployment
- From: Neil Smith [MVP Digital Media]
- Re: Windows Media Server deployment
- Prev by Date: RE: can some one help me
- Next by Date: Re: Windows Media Server deployment
- Previous by thread: Re: Windows Media Server deployment
- Next by thread: Re: Windows Media Server deployment
- Index(es):
Relevant Pages
|
Loading