Three-way handshake in Computer Networks - Full Explanation

Introduction

Starting a conversation between two computers over the internet is tricky because both sides need to agree to talk and be ready. Without a clear way to open this communication, messages could get lost or misunderstood. The three-way handshake solves this by making sure both computers say hello and confirm they are ready before exchanging data.

Explanation

SYN: Initiating connection

The first computer sends a special message called SYN to the second computer. This message says, "I want to start talking and here is my initial sequence number." It is like knocking on the door to ask if the other side is ready.

The SYN message starts the connection by asking to communicate and sharing a starting point.

SYN-ACK: Acknowledging and agreeing

The second computer replies with a SYN-ACK message. This means it received the first message and agrees to connect. It also sends its own sequence number to the first computer. This step is like the other person opening the door and saying, "I’m ready too."

SYN-ACK confirms the request and shares readiness from the second computer.

ACK: Final confirmation

The first computer sends an ACK message back to the second computer. This message confirms it received the SYN-ACK and the connection is now fully established. After this, both computers can start sending actual data safely.

The ACK message completes the handshake and opens the communication channel.

Real World Analogy

Imagine two friends planning to meet. One calls and says, "Are you ready to meet?" The other replies, "Yes, I’m ready and here’s where I’ll be." Finally, the first friend says, "Great, I’m on my way!" Only after this exchange do they actually meet.

SYN: Initiating connection → First friend calling to ask if the other is ready to meet

SYN-ACK: Acknowledging and agreeing → Second friend replying that they are ready and sharing meeting details

ACK: Final confirmation → First friend confirming they received the reply and are coming

Diagram

Diagram

Computer A          Computer B
   │                    │
   │ ---- SYN ---------> │
   │                    │
   │ <--- SYN-ACK ------ │
   │                    │
   │ ------ ACK -------> │
   │                    │
Connection Established

This diagram shows the three messages exchanged between two computers to establish a connection.

Key Facts

SYN → A message sent to start a connection and share the initial sequence number.

SYN-ACK → A message acknowledging the SYN and agreeing to connect, also sharing a sequence number.

ACK → A message confirming receipt of SYN-ACK and completing the connection setup.

Sequence Number → A number used to keep track of the order of messages during communication.

Connection Establishment → The process of both computers agreeing to communicate before sending data.

Common Confusions

Believing the handshake happens instantly without message exchange.

Believing the handshake happens instantly without message exchange. The handshake requires three separate messages exchanged in order to ensure both sides are ready.

Thinking the handshake sends actual data.

Thinking the handshake sends actual data. The handshake only sets up the connection; actual data transfer happens after it completes.

Summary

The three-way handshake is a step-by-step greeting between two computers to start communication safely.

It involves sending SYN, receiving SYN-ACK, and replying with ACK messages in order.

This process ensures both sides are ready and agree on how to send data.

Practice

1. What is the main purpose of the three-way handshake in computer networks?

easy

A. To disconnect a network session

B. To encrypt data before sending

C. To establish a reliable connection between two computers

D. To assign IP addresses automatically

Solution

1. Step 1: Understand the role of the three-way handshake

   The three-way handshake is a process used in TCP to start a connection reliably.

2. Step 2: Identify the correct purpose

   It ensures both computers agree to communicate before data transfer begins.

3. Final Answer:

   To establish a reliable connection between two computers -> Option C

4. Quick Check:

   Three-way handshake = establish connection [OK]

Hint: Remember: handshake means starting a connection [OK]

Common Mistakes:

• Confusing handshake with encryption
• Thinking it disconnects sessions
• Mixing it up with IP address assignment

2. Which sequence correctly represents the messages exchanged during the TCP three-way handshake?

easy

A. SYN, SYN-ACK, ACK

B. ACK, SYN, SYN-ACK

C. SYN-ACK, ACK, SYN

D. ACK, ACK, SYN

Solution

1. Step 1: Recall the message order in TCP handshake

   The client first sends SYN to request connection.

2. Step 2: Identify the correct sequence

   The server replies with SYN-ACK, then client sends ACK to confirm.

3. Final Answer:

   SYN, SYN-ACK, ACK -> Option A

4. Quick Check:

   Order is SYN -> SYN-ACK -> ACK [OK]

Hint: Think: Client SYN, Server SYN-ACK, Client ACK [OK]

Common Mistakes:

• Mixing up the order of messages
• Forgetting the SYN-ACK step
• Assuming ACK comes first

3. If a client sends a SYN message but does not receive a SYN-ACK response, what will happen next?

medium

A. The client immediately sends an ACK message

B. The client will resend the SYN message after a timeout

C. The connection is established without confirmation

D. The client closes the connection instantly

Solution

1. Step 1: Understand client behavior on no response

   If the client does not get SYN-ACK, it assumes the message was lost or server is unreachable.

2. Step 2: Identify the retry mechanism

   The client waits for a timeout, then resends the SYN to try again.

3. Final Answer:

   The client will resend the SYN message after a timeout -> Option B

4. Quick Check:

   No SYN-ACK -> resend SYN [OK]

Hint: No reply? Client retries SYN after waiting [OK]

Common Mistakes:

• Assuming connection established without SYN-ACK
• Thinking client sends ACK first
• Believing client closes connection immediately

4. A network engineer notices that after sending SYN, the client never receives SYN-ACK. Which of these is the most likely cause?

medium

A. The server is not listening on the target port

B. The client sent an ACK instead of SYN

C. The client skipped sending SYN-ACK

D. The client closed the connection too early

Solution

1. Step 1: Analyze the missing SYN-ACK response

   If no SYN-ACK arrives, the server likely did not respond to SYN.

2. Step 2: Identify common reasons for no response

   One common reason is the server not listening on the requested port, so it ignores SYN.

3. Final Answer:

   The server is not listening on the target port -> Option A

4. Quick Check:

   No SYN-ACK means server not listening [OK]

Hint: No SYN-ACK? Check if server port is open [OK]

Common Mistakes:

• Blaming client for sending wrong message
• Thinking client sends SYN-ACK
• Assuming client closed connection early

5. During the three-way handshake, what could happen if the final ACK message is lost in transit?

hard

A. The server assumes connection is established without ACK

B. The client will resend SYN immediately

C. The connection will close automatically

D. The server will retransmit SYN-ACK until it receives ACK

Solution

1. Step 1: Understand the role of the final ACK

   The final ACK confirms the client received the server's SYN-ACK and completes the handshake.

2. Step 2: Identify server behavior if ACK is lost

   If the server does not get ACK, it will retransmit SYN-ACK to prompt the client again.

3. Final Answer:

   The server will retransmit SYN-ACK until it receives ACK -> Option D

4. Quick Check:

   Lost ACK -> server retries SYN-ACK [OK]

Hint: Lost ACK? Server keeps sending SYN-ACK [OK]

Common Mistakes:

• Thinking client resends SYN instead
• Assuming connection closes automatically
• Believing server accepts connection without ACK