Why would stop/starting IIS fix this Socket issue?
I have a Signalr web app that is using sockets to interact with a server application I can’t control (nore have a source code / a protocol for). Each Signalr client sends a command to a Signalr Hub which sends opens a socket, sends a command to the server app then gets one or more responses back, which get sent back to the signalr client.