Reply to thread

Message

<blockquote data-quote="Lehmden" data-source="post: 1189205" data-attributes="member: 109222">Hi.Did your Tuner / CI combo work before? I'm asking because on the Mystique website there is no DVB-S dual tuner card that can be used together with a CI at all... Only the KNC based Mystique cards have a connection for the CI module and they are single tuner only...As far as I know only DigitalDevices Dual Tuner cards are working with one CI for multiple tuner... All other dual solutions needs one CI per Tuner... Have you tried to remove the CI and see, if it is running again?In my DB there only is the SMB name of the server stored, not the IP address.Maybe this name now is bound to a different network adapter (e.g. 127.0.0.1 or similar...)As a second test (after removing the CI without success) I would stop the MP2 server if it's running, move the DB away (not delete it, just move it to a different place) and restart the MP2 server again. Now a new DB is created and you can compare what's different... I can imagine that you have more than one network card in your system. Even virtual ones can cause such issues, if the priority did change for what reason ever.&nbsp; If you don't find the db, it is in &quot;c:\ProgramData\Team MediaPortal\MP2-Server\Database\MP2TVE_3.s3db&quot;, if you don't alter the installation path manually.</blockquote>

[QUOTE="Lehmden, post: 1189205, member: 109222"] Hi. Did your Tuner / CI combo work before? I'm asking because on the Mystique website there is no DVB-S dual tuner card that can be used together with a CI at all... Only the KNC based Mystique cards have a connection for the CI module and they are single tuner only... As far as I know only DigitalDevices Dual Tuner cards are working with one CI for multiple tuner... All other dual solutions needs one CI per Tuner... Have you tried to remove the CI and see, if it is running again? In my DB there only is the SMB name of the server stored, not the IP address. Maybe this name now is bound to a different network adapter (e.g. 127.0.0.1 or similar...) As a second test (after removing the CI without success) I would stop the MP2 server if it's running, move the DB away (not delete it, just move it to a different place) and restart the MP2 server again. Now a new DB is created and you can compare what's different... I can imagine that you have more than one network card in your system. Even virtual ones can cause such issues, if the priority did change for what reason ever. If you don't find the db, it is in "c:\ProgramData\Team MediaPortal\MP2-Server\Database\MP2TVE_3.s3db", if you don't alter the installation path manually. [/QUOTE]

Verification