TCP Retransmission where it shouldn't be. Why?

Question

Computer networks

Good afternoon, comrades.
There is a simple program that polls a site with auto parts catalogs. The link carscats.ru/crc/crc.xml contains a list of remote desktop servers. The program accesses the site, reads the xml file, polls each server from the list and displays the available servers on its own (so that you can connect to the RDP of the remote service by clicking the button). The problem is that on one of the computers in the store, polling an inaccessible server in that list (92.242.44.134. Resolved from epc200.carscats.ru) occurs already 3 times. That is, under normal conditions (on other computers), Wireshark sees only one TCP packet being sent. There is no answer and the program continues to work (displays a list of what is available). On the problem computer, sending goes once ... and then 2 more times with a short interval, there is a re-sending (TCP Retransmission). It takes up to 15 seconds and all this time the program hangs, which causes some inconvenience. Is there a way to figure out why? All computers are connected to the same network (and some of the tested ones are even in the same switch with the problematic one).
Could this be due to some TCP stack settings in Windows 7?

Answer 1

The problem is that on one of the computers in the store, polling an inaccessible server in that list (92.242.44.134. Resolved from epc200.carscats.ru) occurs already 3 times

This is just the default behavior - 15 seconds timeout and 3 attempts to send a SYN packet ( for example , for Linux - it's not the point, for Windows it's the same).
In the case of other computers, apparently, not only there is no answer, but RST comes