Outlets leaked into windows are not shown in netstat and tcpview

Question

Is it possible that windows are leaking socket connections and these sockets are not showing up in tcpview and netstat?

After running several applications that make many network connections, my Windows machine enters a state in which it cannot open any new socket connection. Even for myself (localhosts). For example, telnet for a local application failed because windows cannot create new sockets. Closing and restarting network applications does not help. The problem is only with the full launch of windows.

netstat (& tcpview) indicates that there are only a few dozen connections.

Thank you for your help.

Answer 1

No, these applications cannot miss connection leaks. Something else is happening. Perhaps you are not looking at their detailed views, for example, at closed sockets in the TIME_WAIT state. If you cannot open new connections to the socket, you are most likely running into port exhaustion . Wait for a while when the ports are disconnected and available again. Or stop wasting ports in the first place.