---
title: "Discussion on \"Diagnosing a Failed TCP Handshake\" | Hashnode"
description: "Discussion on \"Diagnosing a Failed TCP Handshake\". Three ways a TCP handshake fails, and how to tell them apart in a packet capture"
url: "https://hashnode.com/posts/tcp-handshake-wireshark/6ad50995b1413071e4d7e3c3"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Diagnosing a Failed TCP Handshake](https://josephoshaughnessy.hashnode.dev/tcp-handshake-wireshark?utm_source=hashnode&utm_medium=feed)

Three ways a TCP handshake fails, and how to tell them apart in a packet capture

Oct 18 · 12 min read · josephoshaughnessy.hashnode.dev  
Updated Oct 25  
Read the article

-   [#networking](https://hashnode.com/tag/networking)
-   [#wireshark](https://hashnode.com/tag/wireshark)
-   [#troubleshooting](https://hashnode.com/tag/troubleshooting)
-   [#tcp](https://hashnode.com/tag/tcp)
-   [#linux](https://hashnode.com/tag/linux)

## Written by

[Joseph O'Shaughnessy](https://hashnode.com/@josephoshaughnessy)

@josephoshaughnessy · London, UK

  
[View profile](https://hashnode.com/@josephoshaughnessy)

Network engineer. Labs, packet captures and real-world troubleshooting.

Network engineer at an MSP, after starting out in the core network team at a small ISP. I lab things at home, break them, and write up what I learn, from packet captures and firewalls to routing and troubleshooting.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.