Timeline for Ping IP returned "destination net unreachable", even with different network
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 8, 2021 at 16:52 | answer | added | poo24cisco | timeline score: 2 | |
| Oct 27, 2017 at 0:50 | answer | added | dsicari | timeline score: 0 | |
| Oct 27, 2017 at 0:39 | answer | added | Keith | timeline score: -2 | |
| Oct 25, 2016 at 5:33 | answer | added | VNCreeperGamer | timeline score: 1 | |
| Dec 19, 2013 at 8:56 | comment | added | Werner Henze | It is not surprising that you can ping 204.15.23.57 - this was the router that answered your ping to (fake) facebook that the destination net is unreachable, so this one is still reachable. You could thank that router for cutting the connection to the fake facebook, probably it prevented you from identity theft. | |
| Dec 19, 2013 at 8:17 | answer | added | r0berts | timeline score: 9 | |
| Dec 19, 2013 at 5:15 | comment | added | Choon Lim | I managed to found out that is some trojans which has edited windows host file, which points the facebook.com to another IP. | |
| Dec 19, 2013 at 4:27 | review | First posts | |||
| Dec 19, 2013 at 4:50 | |||||
| Dec 19, 2013 at 4:08 | history | asked | Choon Lim | CC BY-SA 3.0 |