What Do TCP RESET And TCP TIMEOUT Mean?
The focus of Firebind is to test outbound connections from your IP device (PC, Mac, Mobile, etc.) to the Internet, with the idea being that if a test for a given TCP port passes, then your connection is “free and clear” of some intervening device like a firewall trying to block it. When Firebind tests an individual TCP port, the Firebind Web Client sends traffic back and forth to the Firebind Server on that given TCP port. If the communication is successful, the port passes. If the port doesn’t pass (meaning the communication failed), there are generally two types of failures: 1) The first failure scenario is a TCP TIMEOUT, whereby the Firebind Web Client sent traffic to the Server, but some device such as a firewall blocked that traffic (silently discarded it.) The Web Client waits 10 seconds and if no response is received from the Firebind Server, that port is categorized as a TCP TIMEOUT. 2) The second failure scenario is a TCP RESET. In this case, the intervening device (firewall,
