Reply to thread

Message

<blockquote data-quote="Phaedra" data-source="post: 719319" data-attributes="member: 110603">Thanks again for your support (and patience <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" /> )Meanwhile, I've retraced my steps, and found that I did change one setting : I switched the tuner from Generic to DVB.As soon as I reset this to Generic, everything seems to be functioning normally again.&nbsp; Thank God for that.When I use an MP client on the same PC as the server, everything seems OK now, including even WebEPG.I did get an occasional freeze though, and had to restart the service to get everything going again.Since I'm using version 1.1.3.0 now, I didn't apply the patch anymore.&nbsp; Default the timeshift buffer folder was set to my C drive, an Intel SSD.&nbsp; Changed it to the 7200 rpm drive as before, to be able to compare with previous experiments.Story changes however when I try a client from a remote PC.&nbsp; It seems that this client can not get access to the database and times out trying to do that : opening the client and &quot;loading plugins&quot;, and after a long timeout, when selecting TV-&gt;Guide.The log states an error saying the db can not be reached.As I said, I use MSSQL now, set the sa password to MediaPortal, and switched the MSSQL service to accepting local + remote connections, allowing both Windows + SQL authentication.Maybe a firewall issue ?<img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite8" alt=":D" title="Big Grin&nbsp; &nbsp; :D" loading="lazy" data-shortname=":D" />Edit : When I disable the Windows Firewall on the server, everything works.I then added rules for the SQl server ports 1433 and 1434 and enabled the firewall again, but then it failed to connect again.Disabling the firewall solves it again.During MP installation, I made sure to check the option to add firewall rules for MP itself, so that can't be the one missing.Anyone got any idea which rules I should add ?</blockquote>

[QUOTE="Phaedra, post: 719319, member: 110603"] Thanks again for your support (and patience :) ) Meanwhile, I've retraced my steps, and found that I did change one setting : I switched the tuner from Generic to DVB. As soon as I reset this to Generic, everything seems to be functioning normally again. Thank God for that. When I use an MP client on the same PC as the server, everything seems OK now, including even WebEPG. I did get an occasional freeze though, and had to restart the service to get everything going again. Since I'm using version 1.1.3.0 now, I didn't apply the patch anymore. Default the timeshift buffer folder was set to my C drive, an Intel SSD. Changed it to the 7200 rpm drive as before, to be able to compare with previous experiments. Story changes however when I try a client from a remote PC. It seems that this client can not get access to the database and times out trying to do that : opening the client and "loading plugins", and after a long timeout, when selecting TV->Guide. The log states an error saying the db can not be reached. As I said, I use MSSQL now, set the sa password to MediaPortal, and switched the MSSQL service to accepting local + remote connections, allowing both Windows + SQL authentication. Maybe a firewall issue ? :thx: Edit : When I disable the Windows Firewall on the server, everything works. I then added rules for the SQl server ports 1433 and 1434 and enabled the firewall again, but then it failed to connect again. Disabling the firewall solves it again. During MP installation, I made sure to check the option to add firewall rules for MP itself, so that can't be the one missing. Anyone got any idea which rules I should add ? [/QUOTE]

Verification