200-201 · Question #184
An engineer is addressing a connectivity issue between two servers where the remote server is unable to establish a successful session. Initial checks show that the remote server is not receiving an…
The correct answer is A. incorrect TCP handshake. The remote server not receiving an SYN-ACK after sending an SYN indicates an issue with the TCP handshake, as the SYN-ACK is the second step in establishing a TCP connection.
Question
An engineer is addressing a connectivity issue between two servers where the remote server is unable to establish a successful session. Initial checks show that the remote server is not receiving an SYN-ACK while establishing a session by sending the first SYN. What is causing this issue?
Options
- Aincorrect TCP handshake
- Bincorrect UDP handshake
- Cincorrect OSI configuration
- Dincorrect snaplen configuration
How the community answered
(20 responses)- A85% (17)
- B10% (2)
- D5% (1)
Why each option
The remote server not receiving an SYN-ACK after sending an SYN indicates an issue with the TCP handshake, as the SYN-ACK is the second step in establishing a TCP connection.
The TCP three-way handshake involves a SYN from the client, followed by a SYN-ACK from the server, and finally an ACK from the client. If the SYN-ACK is not received after the initial SYN, it signifies a failure in establishing the TCP session.
UDP is a connectionless protocol and does not utilize a handshake process with SYN or SYN-ACK packets.
OSI configuration is a very broad term; while TCP operates at Layer 4 of the OSI model, 'incorrect OSI configuration' is too general and less specific than an incorrect TCP handshake.
Snaplen (snapshot length) is a setting for packet capture tools that defines the maximum number of bytes to capture per packet, and it does not directly cause handshake failures.
Concept tested: TCP three-way handshake failure
Source: https://learn.microsoft.com/en-us/troubleshoot/windows-server/networking/description-of-tcp-ip-and-ospf-traffic
Topics
Community Discussion
No community discussion yet for this question.