RTSPPlayer:Failed to open file:rtsp://server/stream2 (1 Viewer)

gibman

Retired Team Member
  • Premium Supporter
  • October 4, 2006
    2,998
    1,372
    Usa
    Home Country
    Ethiopia Ethiopia
    I am running tvserver on a dedicated machine.
    When I try and connect with a client I get this specific entry in my log:

    2006-11-19 13:48:56.875000 [ERROR][MPMain]: RTSPPlayer:Failed to open file:rtsp://server/stream2 :0x80004005

    Now I tried to open the stream directly with vlc player on the SERVER.
    rtsp://192.168.238.241/stream2
    this worked alright.

    Now when I try the same thing on VLC on the client I get nothing.

    "access_realrtsp error: cannot connect to 192.168.238.241:554
    access_realrtsp debug: could not connect to: 192.168.238.241/stream2
    vcd debug: trying .cue file: 192.168.238.cue
    access_file warning: 192.168.238.241/stream2: No such file or directory
    cdda debug: trying .cue file: 192.168.238.cue
    cdda warning: could not open 192.168.238.241/stream2
    main warning: no access2 module matching "rtsp" could be loaded
    main error: no suitable access module for `rtsp://192.168.238.241/stream2'
    main debug: thread times: real 0m47.156250s, kernel 0m0.015625s, user 0m0.015625s
    main debug: thread 3860 joined (input/input.c:399)
    main: nothing to play"

    I guess if VLC on the clients dont work then the MP client wont work as well.
    Any ideas ?

    No firewalls of any kind are installed on server/clients.
    Although it seems like the traffic is blocked some how.

    My LAN is in the 192.168.1.x range.
    Router is the famous linksys wrt54g with dd-wrt v23.sp2 Firmware.

    How do I test on the client if port 554 is opened or closed on the server ?
    Also, the adress: "rtsp://192.168.238.241/stream2" looks like a multicast type, is it not ?
    If yes, then I guess I have to make sure my router handles multicast as it should.
    Although when searching through the forum here, multicast is mentioned that much.

    /Gibman
     

    ArnoldGoat

    MP Donator
  • Premium Supporter
  • May 27, 2007
    110
    21
    78
    Lyttelton
    Home Country
    New Zealand New Zealand
    I have just encountered this problem. I ran 'Angry IP Scanner' on the server machine, and it shows that port 554 is open, but offered on 192.168.238.238, the address of the satellite card, and not the address on the LAN. If the client is on the same machine as the server, it can access that address, but not otherwise.

    I will try altering the card address so that it is on the same subnet as the LAN (when I find out how to do it!)
     

    mdsflyer

    Portal Pro
    November 14, 2005
    283
    6
    Home Country
    New Zealand New Zealand
    I can confirm the first post here on my network clients. They will work fine if the server has been rebooted but if it is woken from hibernate then it will not play with the RTSP player. If you look at the following log i try opening various video files and they work fine as it is gplayer which is being called to play the video files. The simpsons episode works if i access the recorded tv folder via my videos but not if i use the recorded tv tab on the live tv GUI. This is because the RTSP player is used. Something is going on but for the life of me i cant figure out why works fine after reboot and not after reawakening.
     

    mdsflyer

    Portal Pro
    November 14, 2005
    283
    6
    Home Country
    New Zealand New Zealand
    Hi there, the last post is not relevant to my problem i'm afraid. No firewalls and IP address is correct. Also would not explain why it works fine after reboot but not resume. I'll try standby instead and see if that makes a difference. Cheers m
     

    mdsflyer

    Portal Pro
    November 14, 2005
    283
    6
    Home Country
    New Zealand New Zealand
    Could you try manually stopping and then restarting the tvservice and see if this makes a difference. I've found with mine that after a resume from hibernate if i stop the tv service and then restart it that the client on another pc works fine for streaming. However if i dont restart then inevitably i end up with the problem that has been described above. It appears as if the tv service is starting too early, possibly before the network connection has been reestablished?

    Cheers
    m
     

    vvulture

    MP Donator
  • Premium Supporter
  • June 3, 2006
    483
    8
    53
    Sydney
    Home Country
    Australia Australia
    Could you try manually stopping and then restarting the tvservice and see if this makes a difference. I've found with mine that after a resume from hibernate if i stop the tv service and then restart it that the client on another pc works fine for streaming. However if i dont restart then inevitably i end up with the problem that has been described above. It appears as if the tv service is starting too early, possibly before the network connection has been reestablished?

    Cheers
    m

    Same here mdsflyer... The problem only occurs when resuming from standby.. If i restart the TV Service, it all works again..
     

    karhill

    Portal Member
    March 19, 2013
    24
    3
    75
    Home Country
    United States of America United States of America
    Could you try manually stopping and then restarting the tvservice and see if this makes a difference. I've found with mine that after a resume from hibernate if i stop the tv service and then restart it that the client on another pc works fine for streaming. However if i dont restart then inevitably i end up with the problem that has been described above. It appears as if the tv service is starting too early, possibly before the network connection has been reestablished?

    Cheers
    m
    Just to help anyone else. I'm using MP 1.3.0 with a server and a number of clients (multi-seat). Things were working fine for weeks, then live TV and playing recorded TV stopped working on the clients (but still worked on the server). The clients all reported the same error as the original poster. Starting and stopping the TV Service on the server fixed the issue. I changed the service properties of the TV Service to be a "Automatic, Delayed Start" service, which seems to have provided a permanent fix to the issue by ensuring that the TV Service starts late enough in the boot process that everything is ready for it.
     

    Users who are viewing this thread

    Top Bottom