Re: Media services - cannot connect to media from internet



I am having a similar issue (I think)

If I disable HTTP and RTSP on the server, and only have MMS enabled, then I
try to "test" a file in my publishing point (we are only doing On Demand), it
fails.

This is even on the local server.

I try all the IP addresses (2 NIC's and 127.0.0.1) and the computer UNC name
- all fails.

The Windows firewall is disabled, we have a nice Cisco PIX - and 1755 is
open for both UDP and TCP, no ports are being blocked outbound.

HTTP and RTSP work like a champ.

*stumped*

"Neil Smith [MVP Digital Media]" wrote:

> This page probably explains the options for firewalling rtsp and other
> media traffic : http://support.microsoft.com/kb/883831
>
> Are you sure there aren't supposed to be spaces in the string `5000 -
> 5100` ? Does it work with a comma instead ? I don't use the windows
> firewall, as I have my own arrangements - there must be a generic
> howto out there somewhere though.
>
> Cheers - Neil
>
> On Thu, 11 Aug 2005 12:56:08 -0700, "Paul"
> <Paul@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
>
> >Yes, you are absolutely correct and this is not an option. Okay, I have
> >reverted to Windows firewall. When I try to enter any character aside from a
> >number (such as the dash), it gives me a pop up box saying that only
> >characters from 0-9 are valid. How do I open a range of ports in Server 2003
> >other than one at a time? I read an article that explains this way for a
> >different application.
> >
> >1. Add the Internet key under: HKEY_LOCAL_MACHINE\Software\Microsoft\Rpc
> >2. Under the Internet key, add the values "Ports" (MULTI_SZ),
> >"PortsInternetAvailable" (REG_SZ), and "UseInternetPorts" (REG_SZ).
> >In this example, use ports 5000 through 5100 inclusive, so the new registry
> >key appears as follows:
> >Ports: REG_MULTI_SZ: 5000-5100
> >PortsInternetAvailable: REG_SZ: Y
> >UseInternetPorts: REG_SZ: Y
> >3. Restart the server. All applications that use RPC dynamic port
> >allocation use ports 5000 through 5100, inclusive. In most environments, a
> >minimum of 100 ports should be opened, because several system services rely
> >on these RPC ports to communicate with each other.
> >
> >So I created an Internet Key and I have my entries which looks like:
> >HKEY_LOCAL_MACHINE\Software\Microsoft\Rpc\Internet
> >
> >(Default) REG_SZ (value not set)
> >Ports REG_MULTI_SZ 1024-5000
> >PortsInternetAvailable REG_SZ Y
> >UseInternetPorts REG_SZ Y
> >
> >This still does not solve the UDP problem as I still have to turn it off.
> >I looked at the keys for other ports in my Globally Open Ports list and they
> >all are similar to:
> >3389:TCP REG_SZ 3389:TCP:*:Enabled:@xpsp2res.dll,-22009
> >
> >In the entry I made, I can’t see how the system would know they are UDP
> >ports. I don’t know how I can check to see what is open when I do make this
> >change.
> >I try netstat –an but they are not listed there.
> >
> >Oh, so my questions were, am I doing this wrong?
> >Am I putting these entries into the wrong key?
> >-Paul
> >
> >"Neil Smith [MVP Digital Media]" wrote:
> >
> >> On Mon, 8 Aug 2005 20:53:05 -0700, "Paul"
> >> <Paul@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
> >>
> >> >After four nights of pulling my hair out, I think we finally have it! All
> >> >along, this was a Media Player 10 issue. I didn't discover it until I was
> >> >writing my last reply but I did a little more research and came upon this
> >> >posting. In desperation, I decided to try it and wow, it works. It's amazing
> >> >how you can overlook the obvious. Neil, thank you so much for taking time out
> >> >and trying to assist me with dilemma.
> >> >Here is the posting:
> >> >
> >> >Error C00D11D4 or Invalid Request can be solved many times by un-checking
> >> >UDP under Tools>>Options>>Network. Then Close WMP then re-open it. Try to
> >> >access the content again. This error has also been linked to bad proxy
> >> >settings. You might also make sure that you don't have a firewall blocking
> >> >WMP access to the internet. I have also seen people report check "Connect to
> >> >the Internet" under the main
> >> >options of WMP fixed this.
> >>
> >> Ahh but all you've done is to force the player to use http over TCP.
> >>
> >> The reason UDP is used is because it has much less overhead than TCP -
> >> it's a "not-reliable" transport, but the media server is designed to
> >> retransmit missing packets during poor network conditions, in
> >> conjunction with the player which reassembles and interpolates the
> >> missing packets.
> >>
> >> In general what you've done is made the player look at the mms:// URL
> >> and then switch to http:// at the same IP address, which as I've said,
> >> incurs a significant network traffic overhead.
> >>
> >> Probably you need to work out with your router, how to forward UDP
> >> requests to the server box as well as TCP ones.
> >>
> >> Although it works for now, it might not work for other users as they'd
> >> haev to also change their settings (and I'd generally discourage
> >> unchecking the UDP box *unless* the viewer is on a corporate network
> >> which is *known* to block outgoing UDP requests)
> >>
> >> HTH
> >> Cheers - Neil
> >>
>
>
.



Relevant Pages

  • Re: RPC over HTTP - one server scenario no ISA
    ... If you have verified that your "Valid Ports" key is set correctly, ... You should get a 403.2 HTTP Error, this means that you are accessing the ... I've been able to connect to the server from an XP ...
    (microsoft.public.exchange.connectivity)
  • Re: Upgrading to WMP11 has stopped streamed video playing.
    ... mms protocol has implemented a rollover to rtsp or http ... depending on firewall and remote source server support. ...
    (microsoft.public.windowsmedia.player)
  • Re: RCP/HTTPS on SBS 2003 Server
    ... Certianly not needed for RPC over HTTP. ... Did you open the correct ports on your server's router as well? ... So we know all the server components are installed> correctly. ...
    (microsoft.public.windows.server.sbs)
  • Re: Windows 2003 remote admin access
    ... The server sits behind a hardware firewall which is only allowing those ... particular ports inbound so access on any other ports shouldn't be possible. ... The user does have HTTP and FTP web authoring access but this should (as I ...
    (microsoft.public.security)
  • Re: Wrapping TCP communications in HTTP
    ... We're using Winsock2 sockets with overlapped I/O through completion ports. ... HTTP won't help you a bit since it's not a secure protocol. ... >>> establishes a TCP socket connection to a server, ...
    (microsoft.public.win32.programmer.networks)