Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[alglove]

I have run into a problem on my home network that seems to be related to DLNA, which causes my computers' network connections to get bogged down with TIME_WAIT connections. It is rather confusing, so please bear with me.

---------------------------------------------------------------------------------------------------------------

We had been having problems with our computers' network connections getting bogged down, despite not really downloading or uploading anything major.  Eventually, I noticed that only certain computers running MC had this problem, while others were fine. Using TCPView from Sysinternals, I noticed that the computers that were bogged down had numerous TIME_WAIT connections, corresponding to the DLNA Media Renderer ports in MC.

Exiting MC and waiting several minutes for the TIME_WAIT connections to clear would fix the problem. But after about an hour after restarting MC, the TIME_WAIT connections would start to stack up again.

Looking at the Media Network logs, it appears that MC computers that are not bogged down would show the following incoming activity occurring every 9 minutes for the Media Renderers:

SUBSCRIBE: http://192.168.1.100:52015/AVTransport/event
SUBSCRIBE: http://192.168.1.100:52015/RenderingControl/event

However, computers that were getting bogged down would show those events coming in about every 30 seconds. Over time, those connections come in faster than the TIME_WAIT can expire, and the excessive TIME_WAIT connections start to interfere with other applications.

Something that is worth pointing out is that this seems to happen only when I stop MC and restart it soon thereafter.  It is as if the other MC computer on the network starts sending out extra queries.  If I wait about half an hour before restarting MC, I do not have this problem.

-----------------------------------------------------------------------------------------------------------------------------------------------------

I have 3 computers on my home network: two Windows 10 computers running MC24, and one Id running MC20.

One of the Windows computers has Norton Internet Security, the other one only has the standard Microsoft Defender and firewall.  As a test, I did a full uninstall of Norton, and even disabled the Microsoft antivirus/firewall.  It did not seem to make a difference.

I can reproduce this problem on both Windows 10 computers.  I turned the Id off during testing.

-----------------------------------------------------------------------------------------------------------------------------------------------------

Any ideas what may be causing this, or what to do? Rebooting the computers does not seem to help, because they reboot fast enough for the problem to reappear. (Media Center Server is set to start automatically on both computers, btw.)

Thanks to anyone who has read this far. 

[JimH]

What's the full version of MC?

If this is an MC problem, it may be in this area:

https://yabb.jriver.com/interact/index.php/topic,115328.0.html

[AndrewFG]

What renderer(s) are you using? i.e. what devices are trying to SUBSCRIBE to MCs state change event messages?

It sounds like you may have a firewall issue that is either blocking the incoming SUBSCRIBE, or it’s OK acceptance, or possibly the respective NOTIFY state change message.

You might try right clicking on the renderer in MC and select Ignore Transport Events..

[alglove]

Hi, Jim and Andrew. Thanks for your replies. I apologize for the long delay.

I am happy to report that this problem appears to have been FIXED, as of version 24.0.36.  The problem went away a couple of weeks ago, when I updated from 24.0.34 to 24.0.37, and has not come back since.  Going through the release notes, I am pretty sure it was note 11 that fixed the problem:

24.0.36 (6/20/2018)

10. Changed: DLNA, change SetNext controller option disabling so that device errors don't disable SetNext only disable it if the renderer reports that it's not implemented.
11. Changed: DLNA. Want to make sure that if a resubscribe fails we clear and do a subscribe. Have seen http error codes of 412 on resubscribe.
12. Changed: DLNA, Add a code that will do a manual transport state update if we look frozen at the end of a track (missed an event..)

Great job in finding this, and thank you all!