Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
ar562
#1
IP addressing problem in diagram. Are both devices directly connected but in different subnets?


It is not the filename.
Switch is a tftp client, no need to configure it for server function.


Not sure about the other two.  
Adding a route in the switch won't help if there is no router.  I suppose you could specify an exit interface of e0/1 but then you would have to do the same in the server.

Using TFTP Server IP address 10.0.0.0.1?  THats the switch address but who knows the ip addressing in the exhibit seems wrong.

IF this is how the question is intended than an better explanation is warranted.
Reply
#2
It looks like there is something wrong with this question. The TFTP server and the Switch are on different subnets but directly connected.
But if we consider this question as it is, the given answer is correct because for the switch to communicate with the TFTP server that is on a different subnet (10.0.0.0/24), it needs to have a route to reach that network. Without a route to the server's subnet, the switch does not know how to reach the server, assuming the switch is a layer 3 switch.
All other answers are incorrect.
Reply
#3
None of the answers are correct.

How does the TFTP Server send a packet back to the switch? The example and diagram are wrong.

Diagram shows the remote host address of 10.10.0.1 but the error message says "error opening tftp://10.0.0.1"

Which address are is the Switch trying to connect to ? 10.10.0.1 or 10.0.0.1?
Reply
#4
There was a typo in the diagram which has been corrected. We are sorry for the inconvenience. Thank you!
Reply


Forum Jump:


Users browsing this thread: 3 Guest(s)