Reply to thread

Message

<blockquote data-quote="charli181" data-source="post: 656148" data-attributes="member: 54408">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.</blockquote>

[QUOTE="charli181, post: 656148, member: 54408"] 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. [/QUOTE]

Verification