| Author |
QoD - Dec 4 - Wednesday
|
|
| frazang 2002-12-04, 11:28 am |
| You are the Network Analyst for WTF? Company. You have implemented a small departmental LAN that has two segments. The router used to pass traffic back and forth between the two networks is a multi-homed Windows 2000 server. The two networks connected to this server are 220.125.26.0/24 and 220.125.27.0/24. The correct routing table entries are automatically established.
A client machine on the 220.125.26.0/24 network has an IP address of 220.125.26.100/24 and is configured to use a default gateway of 220.125.26.1. This client machine is attempting to connect to an FTP Server on the 220.125.27.0/24 network that has an IP address of 220.125.27.200/16. The FTP Server is configured with a default gateway of 220.125.27.1. When the client machine attempts to connect to the FTP Server, the client receives "request timed out" errors.
What is the reason the client and server are unable to communicate?
A) The FTP Server is unable to reach its default gateway.
B) The FTP Server is unable to return TCP acknowledgements to the remote network.
C) The client is unable to reach its default gateway.
D) The client is unable to return TCP acknowledgements to the remote network.
Good luck everyone!  | |
| jocampo 2002-12-04, 1:06 pm |
| quote:
Originally posted by frazang
You are the Network Analyst for WTF? Company. You have implemented a small departmental LAN that has two segments. The router used to pass traffic back and forth between the two networks is a multi-homed Windows 2000 server. The two networks connected to this server are 220.125.26.0/24 and 220.125.27.0/24. The correct routing table entries are automatically established.
A client machine on the 220.125.26.0/24 network has an IP address of 220.125.26.100/24 and is configured to use a default gateway of 220.125.26.1. This client machine is attempting to connect to an FTP Server on the 220.125.27.0/24 network that has an IP address of 220.125.27.200/16. The FTP Server is configured with a default gateway of 220.125.27.1. When the client machine attempts to connect to the FTP Server, the client receives "request timed out" errors.
What is the reason the client and server are unable to communicate?
A) The FTP Server is unable to reach its default gateway.
B) The FTP Server is unable to return TCP acknowledgements to the remote network.
C) The client is unable to reach its default gateway.
D) The client is unable to return TCP acknowledgements to the remote network.
Good luck everyone!
Hi Michelle.
I'll go with "A"....look the FTP Server IP:
220.125.27.200/16  | |
| namrak 2002-12-04, 1:23 pm |
| Going with answer (A) as well for my two bits worth. | |
| ruscorp 2002-12-04, 1:51 pm |
| A.) | |
|
|
| frazang 2002-12-04, 7:12 pm |
| Correct Answer: B) The FTP Server is unable to return TCP acknowledgements to the remote network.
Explanation: The server actually has a Subnet Mask of 255.255.0.0. As a result, the IP stack only looks at the first two octets to determine if the IP Address to which it is to return a response or data is on the same or a different network. Therefore, the FTP server believes the client is on the 220.125.0.0 network. As a result, the FTP server is able to receive the request from the client, but is unable to return a TCP acknowledgement to complete the three-way TCP handshake.
Let the discussion begin... | |
| namrak 2002-12-05, 2:39 am |
| D'oh! I see it now. The FTP server was configured with 220.125.27.200/16 which breaks down to a subnet mask of 255.255.0.0
I did not pick out that piece of information. Good question! Of course, had you simply stated the variance in subnet mask, the question would have been much easier. | |
| cm2gj 2002-12-05, 11:54 am |
| quote:
Originally posted by frazang
Correct Answer: B) The FTP Server is unable to return TCP acknowledgements to the remote network.
Explanation: The server actually has a Subnet Mask of 255.255.0.0. As a result, the IP stack only looks at the first two octets to determine if the IP Address to which it is to return a response or data is on the same or a different network. Therefore, the FTP server believes the client is on the 220.125.0.0 network. As a result, the FTP server is able to receive the request from the client, but is unable to return a TCP acknowledgement to complete the three-way TCP handshake.
Let the discussion begin...
i put your enviroment on paper and see the B like the right choice but i have some doubts.... so i feel a little poor confident and select A...
i put a simple subnet question with the same issue and Jcampo now is trying to get the logic, and the logic was explained by you right here... |
|
|
|