2 PC TV Server & Client setup - "Unable to play :stream2.0" (1 Viewer)

Hartz

Portal Member
August 17, 2010
7
0
Brisbane
Home Country
Hi everyone,

Short time user, first time poster in the forums.

Firstly big ups to the developers of MediaPortal. It has proven to be an amazing application.

I have been using MediaPortal for a while now in a client/server configuration to stream TV. Both PC's are Windows 7 with v1.1.0 FINAL. The server install is server only, the client is client only. Windows Media Center is still installed on the server. I have a Hauppage HVR-2200 dual DVB-T tuner. This configuration was working for me where I could watch TV on the client through MediaPortal & also on the server using Media Center, pending on what tuners were in use at the time once recording is factored in. Typically only one machine would be used at a time so there were generally no conflicts.

Over the last two days though I have been receiving "Unable to play :stream2.0 or 3.0" messages. I have tried reinstalling both client/server, disabling Media Center Services & ensuring the tuner has not been in use, all to no avail.

Does anyone know what might cause this to happen "all of a sudden" and for no apparent reason? I have not made any modifications to either system for the problem to occur, at least that I an recall.

Thanks in advance for any help provided.
 

woddog

Portal Pro
November 28, 2007
117
5
Townsville, QLD
Home Country
Are you using a hostname or IP address in the client setup? I kept getting this error and changed the server to a static IP and inputted that IP into the client setup. No problems since.
 

Hartz

Portal Member
August 17, 2010
7
0
Brisbane
Home Country
woddog i think i love you.

i am not able to confirm yet if this will solve the problem, but it makes sense. i am connecting via hostname & i turned on a server at home which doubles as a dns server, this may be conflicting with dns on my router.

jonm i have not checked out the logs yet. if the problem persists i will have a look and post here.
 

Hartz

Portal Member
August 17, 2010
7
0
Brisbane
Home Country
Well I have it fixed now. No bloody idea which of the following steps was the one to sort it out though :|

- Changed client connection string from hostname to IP address, no fix
- Shut down dns server, flushed dns cache on client, no fix
- Reinstalled client, restarted tv server service, rebooted router, tv stream works intermittently
- Rebooted everything... seems to be working with full success rate now.

If the client had trouble connecting to the server then I don't understand why it was able to grab the EPG ok. My head asplode from this. Anyway it is working for now, so thank you all for the comments.
 

charli181

Retired Team Member
  • Premium Supporter
  • August 3, 2007
    800
    111
    Sydney
    Home Country
    Australia Australia
    I was having the same issues for a very long time and although I attempted to run 1.1 final, rolled back to 1.0 RC2 as I found it more stable in my environment. I found that once i did get this message a full power down of the client wait 5 seconds and then power up was needed to get it working, a restart of the client did nothing to resolve.

    What seemed to fix it for me was putting the host name of the TV Sserver in the client hosts file on the client machine (c:\windows\system32\drivers\etc). My TV server is also a domain controller, DNS Server, Active Directory and found in the Mediaportal client logs that the stream location was a fully qualified domain name (garage10.skm.local), other times it would just be garage10. So I put both entries in the hosts file to ensure name resolution and have not had a failing since (now 5 weeks). I used to get it at least once or twice a week.
     

    thesystemera

    Portal Pro
    May 26, 2008
    807
    22
    44
    Auckland
    Home Country
    New Zealand New Zealand
    Know this sounds strange but if your running Fanart Handler, disable it... I was getting serious memory issue that were coming from this plugin, once disable the error went away... In saying that though, the latest Fanart Handler does not seem to be causing me these problems..
     

    Users who are viewing this thread

    Top Bottom