Knowledge Base
Payload Receive Time Out
For TCP port testing, this indicates that the client was able to complete the 3-way handshake (establish a socket), however, after sending the test payload, the client timed out waiting for a reply. T
read more
Success (Port Status)
All TCP and UDP ports in the path test were successful in transmitting and receiving data to and from the Firebind servers.
read more
Handshake Connection Timed Out
For TCP port testing, this indicates that while the client was trying to establish a 3-way handshake with the server, upon sending the initial SYN packet, the client received no response from the serv
read more
Are There Any Web Browser Requirements or Limitations?
We recommend the Applet client since it has no limitations and provides a greater level of detail, however, if you prefer the web-based client, please note the following Minimum browser requirements.
read more
Handshake Connection Refused
For TCP port testing, this indicates that while the client was trying to establish a 3-way handshake with the server, upon sending the initial SYN packet, the client received back a TCP RESET (TCP RST
read more
Payload Receive Refused
For TCP port testing, this indicates the client was able to complete the 3-way handshake (establish a socket), however, after sending the test payload, the client received a TCP RESET (TCP RST) messag
read more
Firebind Launches new Java-based TCP and UDP Client for Comprehensive Port
Firebind has launched its new Internet Path Testing client with full support for both UDP and TCP.
read more
Port Triggering
Port triggering is a common feature on consumer broadband routers, it is used only open ports when applications need them, but beware, these ports do not remain open permanently.
read more
Payload Receive Error
For TCP or UDP port testing, this indicates some unknown error in the payload receive process. This error is possible but uncommon, and would be considered an edge case.
read more
Handshake Connection Initiation Failure
For TCP port testing, this indicates there was a client problem initiating the 3-way handshake with the server in order to establish a TCP socket (the client was unable to send the SYN packet to start
read more
- About Firebind
- Overview
- Blog
- Contact Us
- Firebind Apps
- Android
- iOS
- Applet
- Games, Apps and Protocols
- Support
- FAQs
- Knowledge Base
- Contact Us
- Privacy
- Terms