Christian, you have been such a blessing to me. If it were not for your videos, I wouldn't make it through my CNT classes. Don't stop making videos. Your the best.
Como vas Master? Yo como siempre, por aqui apoyandome en tus videos y agradeciendote. ahi te dejo un tremendo like y estaremos pendientes a la proxima. Abrazos master.
I'm actually having the same issue while removing the link between R1 and S1 or shutting down R1. Tracert indicates the 1st hop to be 192.168.1.3 (i.e. R3), though after that it's just "Request timed out." messages. I assume there could be some inconsistencies with the OSPF or Default routes configured on the PT. Other than that, as Christian says - "Completion 100%" :D
@@romeroc24 I was not getting what was wrong with my config. Therefore I have downloaded the PT attached herein. Re-done the config and while removing the link between S1 and R1 HSRP was successful. Compared between the 2 configs and the only difference was on my PT I have also enabled cdp on R3 and R2, reverted it to original and after a couple of FastForwards after link removal, it was also successful! :) Still I don't believe cdp is to blame here, I'm just guessing I should have waited a couple of seconds longer prior to performing the tracert, right? ;)
maybe is going through R3-R1-R2, you can use the simulation mode to verify, but I agree that should be g0/0 10.1.1.5, maybe is a bug on packet tracer, please verify on simulation mode
Christian, you have been such a blessing to me. If it were not for your videos, I wouldn't make it through my CNT classes. Don't stop making videos. Your the best.
Thank you very much, I really appreciate all your support
You’re the best Christian. Your videos are very informative and educational. You’ve been a great help. Keep it up bud.
Thank you for all your support my friend!!!
Como vas Master?
Yo como siempre, por aqui apoyandome en tus videos y agradeciendote.
ahi te dejo un tremendo like y estaremos pendientes a la proxima.
Abrazos master.
GRacias por todo tu apoyo y comentarios
Thank you, Christian, once again ;-)
I love your works
..
Appreciate your comment, again
El mejor profe de todos, una vez mas gracias!!!
Gracias por todo tu apoyo, de verdad lo necesitaba , gracias
Thank you so much for your videos! I am a visual learner so your videos have helped me so much!
You are so welcome! I appreciate
Thank senor, you are great and helpful.
Than you for all your support
27:16 I love when you say this! haha Thank you very much
Jajaj I appreciate your comment
Thank you Christian
Thank you my friend!
When I do the very first step with the tracert 209.165.200.226 my tracing route [2] says “request timed out.”):?
Don't worry if one traceroute or ping fails, repeat then all will work
I'm actually having the same issue while removing the link between R1 and S1 or shutting down R1. Tracert indicates the 1st hop to be 192.168.1.3 (i.e. R3), though after that it's just "Request timed out." messages. I assume there could be some inconsistencies with the OSPF or Default routes configured on the PT. Other than that, as Christian says - "Completion 100%" :D
@@damasta.md.99 First step will fail because is not using HSRP, but last step shows how redundancy works
@@romeroc24 I was not getting what was wrong with my config. Therefore I have downloaded the PT attached herein. Re-done the config and while removing the link between S1 and R1 HSRP was successful. Compared between the 2 configs and the only difference was on my PT I have also enabled cdp on R3 and R2, reverted it to original and after a couple of FastForwards after link removal, it was also successful! :) Still I don't believe cdp is to blame here, I'm just guessing I should have waited a couple of seconds longer prior to performing the tracert, right? ;)
@@damasta.md.99 the connection will be lost for some seconds while HSRP can detect the failure
helpful....thank you
I really appreciate all your support
3:54 this is confusing. if r3 is plugged into r2 g0/1 how does it trace over g0/0. shouldnt it have hit the g0/0 ip of 10.1.1.5 ?
maybe is going through R3-R1-R2, you can use the simulation mode to verify, but I agree that should be g0/0 10.1.1.5, maybe is a bug on packet tracer, please verify on simulation mode
Does anyone know why R1 is not shown in the path from PC-B to the server since the path goes through g0/0 of R2?
Because physically R2 is the gateway and not R1
Gracias
Gracias a ti
Tienes este laboratorio en español?
No lo tengo, trataré de hacerlo lo antes posible