Random "Failed to connect to 127.0.0.1 port 32400: Address already in use" errors during scan

[daveiver]

It appears that I’m running into the same issue as the following post, netstat is showing thousands of connections to 127.0.0.1:32400 in TIME_WAIT state:

Plex Library Scans Initiate Hundreds of TCP_WAIT Sessions using up all available ports?

Server Version#: 1.14.1.5488 My setup is as follows: Windows 10 Pro running Plex media server. My media files are stored on a Synology NAS and the volumes are mapped on the windows PC running plex. I am using a AQUANTIA 10 Gigabit NIC running to a Netgear 10gbe switch (SX10). My Synology does not have 10gbe (yet), so it has 2 ethernet ports in link aggregation to the same switch. I recently moved my server to this setup and ever since then my mapped drives are becoming inaccessible until the r…

I’ve increased my ephemeral port limit and now the scan ran without errors. Is it normal for Plex to be creating so many lingering connections during scans?

I also decreased my Windows 10 TcpTimedWaitDelay OS setting (registry setting) to make the lingering connections go away faster.

It appears that both these settings (TCP port limit and TcpTimedWaitDelay) need to be adjusted when you have a large library, otherwise scans can fail.