Forum Discussion
in video 9, I followed all the steps by Keith Barker but I was unable to ping 192.168.1.177
Showing as request timed out.
Any idea?
Hello Jackey,
Can you post your Virtual Server configuration? It may help to debug.
- VasimApr 19, 2020Altocumulus
Hi Lidev
I am same problem,,Attached my Vs configuration,,can u help me..
- VasimApr 19, 2020Altocumulus
- VasimApr 19, 2020Altocumulus
- VasimApr 19, 2020Altocumulus
am able to ping from local PC to Vs ip,,but when i try open in browser ,its show up error..some help me..pls
- LidevApr 20, 2020MVP
Hi Vasim,
Did you assign an HTTP profile on you Virtual Server ?
- VasimApr 20, 2020Altocumulus
Hi Lidev,
Thanks for your reply
Problem gets solved by selecting Auto Map in SNAT menu..
None i am able to reach 192.168.1.177 through local PC browser
- LidevApr 20, 2020MVP
Glad to hear that :) please mark this question as solved.
- Mostafa_ElsayedFeb 09, 2021Cirrus
Hi Vasim,
can u explain why after enabling "Auto Map", the issue solved
- LidevFeb 09, 2021MVP
Hi Mostaf,
with Auto Map enabled, there is no more asymmetric routing.
SNAT ensure that the response returns through the BIG-IP system instead of through the default gateway.
Regard
- Mostafa_ElsayedFeb 09, 2021Cirrus
Thanks for your reply.
ok but this issue should be appeared at one arm solution only, where the servers terminated at another device such as "Data center firewall", but at two arm design the servers terminated at F5 and we don't need a SRC NAT,
my reply is correct or wrong?