1
00:00:01,030 --> 00:00:07,090
Transmission control protocol operates in various states throughout the life cycle of a connection.

2
00:00:07,120 --> 00:00:12,640
Understanding these states is crucial for analyzing network traffic and troubleshooting connectivity

3
00:00:12,670 --> 00:00:13,330
issues.

4
00:00:13,360 --> 00:00:16,420
Now let's delve deeper into the TCP state.

5
00:00:16,450 --> 00:00:23,770
The first lesson in this state, The system is waiting for connection requests from a remote host,

6
00:00:23,770 --> 00:00:29,140
and it typically occurs on servers that are ready to accept incoming connection.

7
00:00:30,230 --> 00:00:31,940
Synchronize send.

8
00:00:31,970 --> 00:00:40,040
After the client initiates a connection request by sending synchronized packet, it enters the synchronized

9
00:00:40,040 --> 00:00:45,230
send state and the client waits for a response from the server in that state.

10
00:00:46,530 --> 00:00:47,970
Sin received.

11
00:00:47,970 --> 00:00:55,710
When the server receives this packet, it sends back the synchronized acknowledge packet to the clients

12
00:00:55,710 --> 00:00:56,250
request.

13
00:00:56,400 --> 00:01:04,770
So the server then enters the synchronized received states waiting for the final knowledge from the

14
00:01:04,770 --> 00:01:07,020
client established.

15
00:01:08,210 --> 00:01:14,870
Once a client receives a synchronized acknowledged packet, it sends the acknowledged packet to the

16
00:01:14,870 --> 00:01:18,780
server and indicating that the connection is established.

17
00:01:18,800 --> 00:01:25,970
Both the client and server enter the established state loving bidirectional communication.

18
00:01:27,480 --> 00:01:34,320
Finweight won when one side of the connection wishes to terminate the session, it sends a thin packet

19
00:01:34,320 --> 00:01:36,230
to initiate the closure.

20
00:01:36,240 --> 00:01:43,020
The side sending the thin packet enters the finweight one state waiting for acknowledgement from the

21
00:01:43,020 --> 00:01:43,980
other side.

22
00:01:44,910 --> 00:01:45,960
Thin weight, too.

23
00:01:46,080 --> 00:01:52,710
After sending the thin packet, the side initiating the termination enters the thin weight two state.

24
00:01:52,740 --> 00:01:58,170
It waits for a thin packet from the remote host to confirm the termination request.

25
00:01:59,350 --> 00:02:00,460
Claws weight.

26
00:02:00,580 --> 00:02:05,640
When one side receives a fin packet from the other side, it enters the claws.

27
00:02:05,650 --> 00:02:06,580
Wait state.

28
00:02:06,610 --> 00:02:09,040
The side acknowledges the.

29
00:02:10,000 --> 00:02:15,160
Termination request and waits for the own application to close the connection.

30
00:02:15,770 --> 00:02:18,350
Closing in the closing state.

31
00:02:18,380 --> 00:02:24,170
A host has sent thin packet and is in the process of closing the connection.

32
00:02:24,170 --> 00:02:29,090
It waits for acknowledgement from the remote host to complete the closure.

33
00:02:29,990 --> 00:02:36,710
Last acknowledgement, after receiving a thin packet and sending its acknowledgement, the host enters

34
00:02:36,710 --> 00:02:39,360
the last acknowledgement state.

35
00:02:39,380 --> 00:02:43,880
It waits for a final acknowledgement from the remote host to confirm the termination.

36
00:02:45,180 --> 00:02:46,190
Time wait.

37
00:02:46,200 --> 00:02:52,680
In the time wait state, a host has sent a termination request and is waiting to ensure that the remote

38
00:02:52,710 --> 00:02:55,170
host receives the request.

39
00:02:55,200 --> 00:03:01,350
This state has helps to prevent a premature connection termination due to the delayed packets.

40
00:03:02,180 --> 00:03:04,310
And lastly clause.

41
00:03:04,730 --> 00:03:10,160
The clause state does not represent any active state but indicates a closed connection.

42
00:03:10,190 --> 00:03:16,460
Understanding these TCP states is crucial for network administrators and analysts when troubleshooting

43
00:03:16,460 --> 00:03:21,020
network connectivity issues or analyzing network traffic using tools like Wireshark.

44
00:03:22,060 --> 00:03:28,390
By examining this state transitions and associated packets, they can identify potential problems and

45
00:03:28,390 --> 00:03:31,630
ensure smooth communication between hosts.

46
00:03:31,660 --> 00:03:40,930
TCP reliability sequencing and error recovery mechanisms make it ideal for connection oriented sessions

47
00:03:40,930 --> 00:03:43,660
where data integrity is critical.

48
00:03:43,690 --> 00:03:49,630
However, for applications where speed is paramount and real time communication is more important than

49
00:03:49,630 --> 00:03:55,690
reliability protocols like UDP user datagram protocol may be more suitable.