10-22-2001 10:55 AM - edited 02-20-2020 09:52 PM
when I ping from dmz to inside, i get "request timeout" periodically.
Reply from 172.18.0.67: bytes=32 time<10ms TTL=127
Reply from 172.18.0.67: bytes=32 time<10ms TTL=127
Reply from 172.18.0.67: bytes=32 time<10ms TTL=127
Request timed out.
Reply from 172.18.0.67: bytes=32 time<10ms TTL=127
Reply from 172.18.0.67: bytes=32 time<10ms TTL=127
Reply from 172.18.0.67: bytes=32 time<10ms TTL=127
Reply from 172.18.0.67: bytes=32 time<10ms TTL=127
Reply from 172.18.0.67: bytes=32 time<10ms TTL=127
Reply from 172.18.0.67: bytes=32 time<10ms TTL=127
Reply from 172.18.0.67: bytes=32 time<10ms TTL=127
Reply from 172.18.0.67: bytes=32 time<10ms TTL=127
Reply from 172.18.0.67: bytes=32 time<10ms TTL=127
Reply from 172.18.0.67: bytes=32 time<10ms TTL=127
Reply from 172.18.0.67: bytes=32 time<10ms TTL=127
Request timed out.
Reply from 172.18.0.67: bytes=32 time<10ms TTL=127
Reply from 172.18.0.67: bytes=32 time<10ms TTL=127
Reply from 172.18.0.67: bytes=32 time<10ms TTL=127
Does anyone has any idea?
10-30-2001 06:56 AM
Try locking your interface speeds/duplex down (instead of using auto sensing).
11-01-2001 05:13 PM
Do you have this command ?
i.e. static (inside, dmz1) x.x.x.x 172.18.0.67
conduit permit icmp any any
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide