home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
Support
Watch / Listen Media
Television (MyTV frontend and TV-Server)
Live TV Stopped Due To TCP/IP Error
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="CyberSimian" data-source="post: 1103728" data-attributes="member: 141969"><p>Thank you for taking the time to look at this.</p><p></p><p></p><p></p><p>I read both of the above references, but unfortunately I have not yet experienced the "lightbulb" moment. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite3" alt=":(" title="Frown :(" loading="lazy" data-shortname=":(" /> None of the possible causes seem to relate to my case.</p><p></p><p>I checked the current port settings for TCP and UDP ports, and both are the expected 49152 and 16384. The NETSTAT command this morning did not show an excessive number of ports in use (but, of course, I have rebooted since the problem occurred). The system is a dedicated HTPC, and it is not used for gaming, or browsing the web, or streaming content from the web. I have just checked, and the only applications that I have installed (apart from those that are part of MediaPortal) are: AutoHotkey, Nvidia Control Panel, Open Object REXX, Recuva, VideoReDo.</p><p></p><p>I have not tried the registry updates suggested in the references, as I don't think that increasing the number of ports, and/or decreasing the wait time before re-use, is the right solution (it addresses the symptom and not the cause). I have created a BAT file containing the NETSTAT command, and will run that the next time that this problem occurs.</p><p></p><p>One question: when the TCP error occurred, I could not decide whether TV Server had stopped recording (so I rebooted). If this problem occurs again when TV Server is recording, will TV Server continue recording successfully, or will it abort recording? (If TV Server continues recording, I would defer the reboot until the recordings finish.)</p><p></p><p></p><p>When an inexplicable error occurs, I usually prefer to reboot, in order to restart with a "clean slate". If the problem had been (say) a corrupted value in a TV Server control block, restarting TV Server would not necessarily fix it (depending on what the restart does). Do you think that restarting TV Server would be worth trying if the problem occurs again? Presumably that would interrupt any recordings that were being made?</p><p></p><p>-- from CyberSimian in the UK</p></blockquote><p></p>
[QUOTE="CyberSimian, post: 1103728, member: 141969"] Thank you for taking the time to look at this. I read both of the above references, but unfortunately I have not yet experienced the "lightbulb" moment. :( None of the possible causes seem to relate to my case. I checked the current port settings for TCP and UDP ports, and both are the expected 49152 and 16384. The NETSTAT command this morning did not show an excessive number of ports in use (but, of course, I have rebooted since the problem occurred). The system is a dedicated HTPC, and it is not used for gaming, or browsing the web, or streaming content from the web. I have just checked, and the only applications that I have installed (apart from those that are part of MediaPortal) are: AutoHotkey, Nvidia Control Panel, Open Object REXX, Recuva, VideoReDo. I have not tried the registry updates suggested in the references, as I don't think that increasing the number of ports, and/or decreasing the wait time before re-use, is the right solution (it addresses the symptom and not the cause). I have created a BAT file containing the NETSTAT command, and will run that the next time that this problem occurs. One question: when the TCP error occurred, I could not decide whether TV Server had stopped recording (so I rebooted). If this problem occurs again when TV Server is recording, will TV Server continue recording successfully, or will it abort recording? (If TV Server continues recording, I would defer the reboot until the recordings finish.) When an inexplicable error occurs, I usually prefer to reboot, in order to restart with a "clean slate". If the problem had been (say) a corrupted value in a TV Server control block, restarting TV Server would not necessarily fix it (depending on what the restart does). Do you think that restarting TV Server would be worth trying if the problem occurs again? Presumably that would interrupt any recordings that were being made? -- from CyberSimian in the UK [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Support
Watch / Listen Media
Television (MyTV frontend and TV-Server)
Live TV Stopped Due To TCP/IP Error
Contact us
RSS
Top
Bottom