Technical definition
The TCP/IP Transport layer provides communication between application endpoints on hosts. Protocols such as TCP and UDP use port numbers together with IP addresses to distinguish endpoints, with delivery and connection services defined by the selected protocol.
In plain English: Provides communication between application endpoints using transport protocols such as TCP and UDP.
What this layer does
TCP and UDP ports help distinguish endpoints. An IP address and port together identify an endpoint within a transport protocol; the source and destination endpoints identify a conversation. TCP numbers bytes, acknowledges received data and retransmits missing data.
UDP sends datagrams without those built-in delivery guarantees. Applications can add reliability above UDP, so the application requirement determines the choice rather than a rule that one protocol is simply better.
A successful TCP connection test does not prove that TLS or HTTP succeeds.
Follow one request from PC-1
PC-1 is a user's computer opening a page on the lab web server. Its IPv4 address is 192.168.1.20/24 and its gateway is R1 at 192.168.1.1. The server is on another subnet, at 203.0.113.20/24, with gateway 203.0.113.1. The /24 means that the first 24 bits identify each subnet. R1 joins the two subnets.
On small screens, swipe sideways or focus the diagram and use the arrow keys.
In this request: In the TCP example, PC-1 uses 192.168.1.20:51524 to contact 203.0.113.20:443. Port 443 is the server's listening endpoint; 51524 is the client's selected source port. This illustration assumes no address translation.
The interface labels identify the ends of the cables: Eth0 is the example Ethernet interface on each host, while Gi0/0 and Gi0/1 are R1's two Gigabit Ethernet interfaces. Actual device names vary. An IP address identifies an interface; TCP port 443 identifies the HTTPS service endpoint. It is not a physical socket on the router.
Where it fits in the other model
This layer corresponds closely to OSI layer 4. TCP/IP groups application-level representation and session functions above it rather than defining separate Session and Presentation layers.
The trade-off is between a more detailed vocabulary and a simpler description of deployed protocols. OSI names seven responsibilities; the four-layer TCP/IP model groups some of them together. Neither view requires a separate header for every named responsibility.
When it does not work
If ping succeeds but the TCP connection fails, avoid concluding that the cable is broken. ICMP and TCP may be treated differently. Check whether the server is listening on the requested port and whether host or network firewalls allow the connection. TCP can recover some loss, but repeated retransmissions and a connection timeout do not identify the cause on their own.
Try a practical check
Use PowerShell on Windows for this observation exercise. These commands inspect your own connection or request a public example service; they do not configure R1 or contact the documentation server in the figure.
Test-NetConnection example.com -Port 443In Windows PowerShell, inspect RemoteAddress and TcpTestSucceeded. True means this TCP connection test to port 443 succeeded at that time. It does not prove that TLS certificate validation or an HTTP request succeeds. False needs investigation: a service may be stopped, a policy may block the connection, or a path may be unavailable. This test does not test UDP.
Your task: identify one useful field in the result, state what it shows, then name something it cannot prove. If the command is unavailable or a request is blocked, record that limitation rather than treating it as proof of a failed layer.
Check your understanding
Ping works, but a TCP connection to port 443 fails. What is the useful next check?