Who knows why sometimes after a ping something starts to work that did not work before?

Question

Windows

This garbage happens to me from time to time: we launch a client-server application, it complains that it cannot contact the server with the database (ilpi does not start at all, but writes that the server is unavailable). We ping the server, it responds, everything is fine. Now we run the application again - everything works.
For unknown reasons, this behavior seems a little strange to me
Yes, there are different windows trucks everywhere (I don’t know which ones exactly

Answer 1

There may be a problem with ARP requests/ARP cache.

Answer 2

I also sometimes observe this strange phenomenon in various situations related to data transfer. I call it "fat"

Answer 3

As an option: it is possible that the call is made by the host name, and the DNS is slow (or, for example, the primary DNS has fallen, but the secondary is working). The application tries to access by name, the DNS request does not respond for a long time, the application crashes due to a timeout. While the bottom line is, the DNS query is completed (or sent to a second server), the IP address is cached. Therefore, the ping passes, and the application starts working.

Answer 4

one of the symptoms of DNS malfunctions. Recheck the primary server in the client settings - is it ok? After the ping, the record gets into the local DNS cache and therefore everything works.

Answer 5

I had a case that the network printer did not work until I went to the "ball"
in addition, the ball was a guest and opened without asking questions.