WMP10 knocks on port 554...

From: Ravi Raman (ravira_at_online.microsoft.com)
Date: 10/26/04

  • Next message: Humphrey: "Re: MPEG Parser and server plugins"
    Date: Tue, 26 Oct 2004 12:05:50 -0700
    
    

    Hi Rich,

    This is to be expected. All clients from WMP9 onwards will
    connect to the WMS 9 server using RTSP instead of MMS as
    RTSP is the preferred protocl (this is even if MMS is
    specified as a protocol in the request URL). So, opening
    554 should solve your problem - your setup is working just
    fine.

    If MMS is used in the requesting URL, any WMP9 player
    connecting to WMS9 server will connect through RTSP.

    However, if WMP9 is connecting to a WMS4.1 server (which
    does not understand RTSP), it will connect using MMS.

    If MMS is used in requesting URL, any player shipped
    BEFORE WMP9 connecting to WMS9 server will connect using
    MMS (since the older players do not understand RTSP).

    Hope this helps.
    Ravi

    --
    This posting is provided "AS IS" with no warranties, and 
    confers no rights.
    >-----Original Message-----
    >Dear all,
    >
    >Like many of us, I am currently experimenting with WMS9 
    on Windows 2003 
    >server -  Enterprise. My goal is to finally broadcast my 
    own musical 
    >compositions on the web.
    >
    >I am in the test phase of setting up WMS9, with only one 
    PubPt, called 
    >"Test". This PubPt is configured as an on-demand PubPt, 
    just looping through 
    >1 directory of mp3's.
    >
    >On my LAN I have no problems connecting to the stream, 
    using WMP10, and an 
    >URL in the form: "mms://server-name/Test"
    >
    >WMS9 is setup to allow RTSP and MMS connections through 
    both of their 
    >default ports. i.e. 554 and 1755 respectively. (The below 
    described problem 
    >remains however when I disable RTSP and only want MMS to 
    be supported)
    >
    >Now, the difficulty I am facing is the following:
    >
    >- I have configured my firewall to accept packets on port 
    1755 (MMS-TCP), 
    >since I first want to have MMS working. So, I have not 
    enabled port 554, or 
    >any other ports for media streams on purpose. Just like 
    >http://www.microsoft.com/windows/windowsmedia/serve/firewa
    ll.aspx advises on 
    >streaming using TCP. ( I only want to get the different 
    streaming types 
    >working one at the time...)
    >
    >Now, I know that WMP10 uses port rollover by default and 
    the following is 
    >what happens when I try to connect from an "outside" 
    location using WMP10 and 
    >connect to my server using "mms://myserver_ip/Test"...:
    >
    >When I look at my firewall logs (remotely and at the same 
    time I am trying 
    >to connect), I see that my "outside" IP is blocked on 
    PORT 554 as soon as I 
    >try to connect to the server. 
    >This means that my MMS:-request is translated (rolled-
    over) into a TCP-RTSP 
    >request, while I expected the packets to arrive at my 
    firewall as being 
    >MMS-TCP packets on port 1755.
    >
    >Could anyone explain this symptom perhaps?
    >
    >I guess, therefore, my question will be, how to force 
    WMP10 to send MMS-TCP 
    >requests on port 1755?
    >
    >I expect (I haven't tried it yet) that,  when I open port 
    554 as well, all 
    >would work fine. But that is NOT what I don't understand. 
    I don't know why my 
    >WMP10 knocks on my door on port 554. Sure, when I open 
    all the ports, I would 
    >get to my content finally, but that will not explain my 
    problem.
    >
    >I have tried all posible Network options in WMP10, by 
    enabling and disabling 
    >the different supported protocols like Multi-cast, UDP, 
    TCP and HTTP, but in 
    >all cases, WMP10 keeps knocking on port 554.
    >
    >The only thing I can think of is, that my "outside" IP is 
    behind a firewall 
    >that translates all streaming media into TCP-RTSP 
    packets/requests...but I 
    >don;t have a way to verify this at the moment.
    >
    >All tips and comments are highly appreciated !
    >-- 
    >Cheers! Richard
    >.
    >
    

  • Next message: Humphrey: "Re: MPEG Parser and server plugins"

    Relevant Pages

    • RE: WMP10 knocks on port 554...
      ... I opened port TCP 554 and UDP 5004,5005, and I can connect to my Media ... came in on port 1755 (mms). ... > connect to the WMS 9 server using RTSP instead of MMS as ... > connecting to WMS9 server will connect through RTSP. ...
      (microsoft.public.windowsmedia.server)
    • RE: WMP10 knocks on port 554...
      ... firewall settings. ... bit obsolete when considering WMP9>...since the port settings for in/out TCP ... > connect to the WMS 9 server using RTSP instead of MMS as ...
      (microsoft.public.windowsmedia.server)
    • Re: Broadcast Error over Internet
      ... RTSP on Default Port - Allowed all IP addresses to use ... The server has two WAN IP Address on one NIC ... (I also tried to enable http protocol on port 81) ...
      (microsoft.public.windowsmedia.server)
    • Re: Broadcast Error over Internet
      ... In fact i have not enough knowledge to analyse it. ... RTSP on Default Port - Allowed all IP addresses to use ... The server has two WAN IP Address on one NIC ...
      (microsoft.public.windowsmedia.server)
    • Re: Broadcast Error over Internet
      ... Time to install WireShark and see what's happening on the network. ... RTSP on Default Port - Allowed all IP addresses to use ... the protocols enabled on WMS are MMS and RTSP ...
      (microsoft.public.windowsmedia.server)

    Loading