On Thu, Aug 6, 2015 at 12:05 PM, Glen Kent <glen.k...@gmail.com> wrote: > I find this bizzare because even when the traceroute doesnt work, I am > actually able to ping and access the machine. > > I know that the VM responds to traceroutes, since it did respond to my > traceroute when i was on the other broadband network. > > So i really fail to understand why the traceroute on the other network > failed. > > Any pointers on this would be very helpful.
the las hop reported in the 'fails' traceroute is an amazon ip address, I suspect some miscarriage of packet-justice inside AWS is happening. You asked them already I guess?
