Imagine you're monitoring a network and notice that a client sends a SYN packet but doesn't receive a SYN-ACK response from the server. Instead, the client keeps retransmitting the SYN packet. What might be a likely reason for this behavior?

  • Firewall Blocking
  • MTU Mismatch
  • Network Congestion
  • Wrong IP Address
Network Congestion is a common reason for a client not receiving a SYN-ACK response. When the network is congested, packets may be dropped or delayed, leading to retransmissions. A SYN-ACK is the second step in the TCP three-way handshake, and if it's not received, the client will retransmit the SYN packet.
Add your answer
Loading...

Leave a comment

Your email address will not be published. Required fields are marked *