We are having some problems with Winsock after releasing a new version of our software. We currently have 16 servers running Windows Server 2016 that all run an instance of this software. All these servers communicate to yet another server that acts as a gate way of sorts.
All servers experience the same problem, which occurs after a few hours:
ipconfig /flushdns
and/or ipconfig /release
I ran the PortQuery tool from mirosoft and saw the following error on most ports:
Starting portqry.exe -n 127.0.0.1 -e 135 -p TCP ...
Querying target system called:
127.0.0.1
Attempting to resolve IP address to a name...
IP address resolved to testserver15.test.com
querying...
Cannot use specified source port Winsock error 10055
portqry.exe -n 127.0.0.1 -e 135 -p TCP exits with return code 0x00000063.
If i keep querying the return code vil alternate between 0x00000063 and 0 every second.
I have no clue what is going on here. Googling suggest looking into the number of open ports, but I can't find any issues here. Any idea to help steer us in the right direction would be greatly appreciated
User contributions licensed under CC BY-SA 3.0