Quote:
Originally Posted by martin
Latest Update. Clearly an OS re-install is not a good option and one we will try to avoid.
|
traceroute to eu.voxalot.com (85.17.19.194), 30 hops max, 38 byte packets
1 firewall (192.168.2.1) 1.712 ms 0.723 ms 0.685 ms
2 cisco (193.121.84.65) 1.444 ms 2.185 ms 1.431 ms
3 ser5-2-0.bel-pe06.mpl.scarlet.be (194.119.226.61) 17.334 ms 8.856 ms 10.105 ms
4 gig0-2-100.inx-pe01.mpl.scarlet.be (194.119.224.53) 10.072 ms 17.557 ms 17.987 ms
MPLS Label=218401 CoS=7 TTL=254 S=0
5 leaseweb.bnix.net (194.53.172.101) 24.218 ms 19.104 ms 25.784 ms
6 ten0-0-0-6.crs-evo.leaseweb.net (85.17.100.210) 27.995 ms 21.689 ms 11.756 ms
7 tenge1-0-0.r2.sbp.leaseweb.net (62.212.95.146) 11.913 ms 11.605 ms 12.122 ms
8 ****
So in other words, 7 is the last leaseweb router and 8 should be the endpoint (server) ? So or this router fails or the NIC of the server is damaged. An OS re-install could also be the solution if it's Windows :-)
Anyway, I'm not impressed with LeasWeb's investigation methods ...