“The name limit for the local computer network adapter card was exceeded” error message

I started having this same exact issue on a Windows Server 2016 Hypervisor. My netstat results show me about the same as the original post as far as established/listening connections - nothing out of the ordinary.

Here's where things get interesting: I had set this hypervisor up as a Watchguard logging repository for the firewall and noticed that when the problematic connectivity issue kicks in, an element of this logging service has also failed. Not sure whether this failure is the chicken or the egg but the logging service uses PostgreSQL-8.2 and runs it as a service set to start 'Automatic'. The service is found to not be running and when I try to manually start it in this state it starts then stops. I noticed a few hung instances of postgres.exe process still running even though the service is stopped. If I end those processes, I can start the PostgreSQL-8.2 service and the server's network connectivity suddenly becomes normal again.

I'm not sure yet how to keep this from happening, though, or whether the PostgreSQL service is causing this or just a domino in a cascade of failures.

This might not be exactly what to look for in most cases but could be a clue to others to look for a service or process that has hung up network connectivity.