Learn / Answers

Why does a connection request get no response?

When a connection request (SYN) gets no reply at all, neither a SYN/ACK nor a reset, the packet was dropped somewhere: by a firewall, a wrong route, or a host that's down. Unlike a refusal, silence points at the network path or a firewall rather than the application.

What it looks like in the packets

  • The client sends a SYN, then resends it after about 1, 2, and 4 seconds (exponential backoff).
  • Nothing comes back from the server's address.
  • The app eventually reports a timeout.

Common causes

  • A firewall or security group silently drops the port.
  • The server is down or the address is wrong.
  • A routing problem or VPN sends the packets nowhere.
  • The capture only sees one direction (check that first).

What to check

  1. Make sure the capture shows replies for other connections, so missing replies are real.
  2. Test the port from another network, and check firewall and security-group rules for it.
  3. Run a traceroute to see where packets stop.

Wireshark display filters

  • tcp.flags.syn == 1 && tcp.flags.ack == 0connection requests
  • tcp.analysis.retransmission && tcp.flags.syn == 1resent connection requests

How Blame Finder flags it

Warning for two or more unanswered SYNs to the same target; Low for one; Informational in one-sided captures. Upload a capture and the finding links straight to the packets behind it, with the most likely culprit at the top.