Quote:
Originally Posted by Sirius
fine here in Warrington
Tracing route to kundenserver.de [82.165.217.36]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 9 ms 35 ms 10 ms 10.2.96.1
3 31 ms 55 ms 14 ms bagu-t2cam1-a-v145.network.virginmedia.net [80.
.167.21]
4 8 ms 9 ms 10 ms bagu-t3core-1a-ae2-0.network.virginmedia.net [1
5.182.180.5]
5 10 ms 8 ms 9 ms man-bb-a-so-310-0.network.virginmedia.net [80.5
161.37]
6 19 ms 14 ms 15 ms gfd-bb-b-so-200-0.network.virginmedia.net [62.2
2.192.94]
Trace complete.
|
The reason your connection works fine is because the route it took to get to that address did not lie across the two Virgin machines I identified in my last post as being part of the problem:
7 12 ms 18 ms 12 ms gfd-bb-b-ge-000-0.network.virginmedia.net [213.105.172.6]
8 12 ms 11 ms 15 ms gfd-bb-a-ge-000-0.network.virginmedia.net [213.105.172.5]
Once the packet gets between those it just gets bounced between them infinitely until they both just give up.
Once again, I state that Virgin have a serious problem somewhere in their network, and will likely cause random sites to stop working for certain machines if they happen to be trying to route packets through those addresses.