TV Server is running, recording, can see tv guide but not watch anything on clients (1 Viewer)

TommySharp

MP Donator
  • Premium Supporter
  • January 15, 2007
    322
    7
    43
    Auckland
    Home Country
    New Zealand New Zealand
    The TVService.log file shows it starting up and assigning the 127.0.0.1 IP address....

    [2013-10-28 05:17:26,839] [Log ] [TVService] [INFO ] - Controller: started at ROSIE
    [2013-10-28 05:17:26,839] [Log ] [TVService] [INFO ] - Controller: local ip address:127.0.0.1
    [2013-10-28 05:17:26,886] [Log ] [TVService] [INFO ] - Controller: server running on ROSIE

    If I manually restart the TV Service then the log shows....

    [2013-10-31 10:56:54,809] [Log ] [TVService] [INFO ] - Controller: started at ROSIE
    [2013-10-31 10:56:54,809] [Log ] [TVService] [INFO ] - Controller: local ip address:192.168.1.99
    [2013-10-31 10:56:54,887] [Log ] [TVService] [INFO ] - Controller: server running on ROSIE

    Will reboot the server now and see what the log says after a fresh reboot....[DOUBLEPOST=1383170925][/DOUBLEPOST]Okay, after a fresh reboot of the server I get this in the log..... That IP address means that clients will not be able to stream from it.

    [2013-10-31 11:04:52,166] [Log ] [TVService] [INFO ] - Controller: started at ROSIE
    [2013-10-31 11:04:52,166] [Log ] [TVService] [INFO ] - Controller: local ip address:127.0.0.1
    [2013-10-31 11:04:52,229] [Log ] [TVService] [INFO ] - Controller: server running on ROSIE

    Will no see how I can delay the start of the TV service and see what that does....
     
    Last edited:

    mm1352000

    Retired Team Member
  • Premium Supporter
  • September 1, 2008
    21,577
    8,224
    Home Country
    New Zealand New Zealand
    I've just cracked open some of the older streaming server.log files and the ip address in there is my static one of 192.168.1.99.... But in the latest log file it seems to be 127.0.0.1.... The client must be trying to access the stream on 127.0.0.1 which wouldn't work....
    Yep - you're right, and that is also what I suspected.

    Is there any way to make sure that the tv server stops trying to broadcast on 127.0.0.1?
    As per my previous post: the fact that the streaming server (and probably the TV service itself) is binding to localhost indicates your NIC hadn't received its proper IP address before the TV service started.

    Did you configure the static IP address in Windows, or did you assign a permanent lease (or similar) via your router? The first is better than the second.

    To solve the problem, you probably just need to delay the start of the TV service by a few seconds. There are many ways to do this. One way might be to change the TVService startup mode to manual, then use task scheduler to start the service by scheduling a bat file with the following commands:
    ping 192.0.2.2 -n 1 -w 10000 > nul
    net start TVService

    ...where 192... is an IP address that does not exist and 10000 is the delay in milliseconds.
     

    TommySharp

    MP Donator
  • Premium Supporter
  • January 15, 2007
    322
    7
    43
    Auckland
    Home Country
    New Zealand New Zealand
    Okay changed the service to have a startup of "Automatic(Delayed)" and this at least appears to work.... The static IP address is configured in my router and not the server itself....

    [2013-10-31 11:13:49,104] [Log ] [TVService] [INFO ] - Controller: started at ROSIE
    [2013-10-31 11:13:49,104] [Log ] [TVService] [INFO ] - Controller: local ip address:192.168.1.99
    [2013-10-31 11:13:49,260] [Log ] [TVService] [INFO ] - Controller: server running on ROSIE

    Will do some testing this evening from the client and see if this is the issue.... Might see if removing the delayed start causes my issue to occur again which will hopefully confirm that is the actual issue....

    Thanks for your help!
     

    Users who are viewing this thread

    Top Bottom