[messages] [Technical Support & Bugs] Very slow response

Joel Uckelman uckelman at nomic.net
Mon Mar 2 12:36:24 CET 2015


Thus spake dsoukup:
> Below is a traceroute from tonight using the correct server address.
> 
> 
> Code:
> C:\Users\DSOUKU3>tracert game.vassalengine.org
> 
> Tracing route to one.vassalengine.org [62.210.178.7]
> over a maximum of 30 hops:
> 
>   1     2 ms     1 ms     1 ms  homeportal [192.168.1.254]
>   2     *        *        *     Request timed out.
>   3    20 ms    20 ms    21 ms  71.150.32.178
>   4    23 ms    21 ms    23 ms  12.83.42.153
>   5    37 ms    34 ms    42 ms  ggr3.dlstx.ip.att.net [12.122.138.17]
>   6    30 ms    31 ms    34 ms  192.205.37.50
>   7    67 ms    68 ms     *     ash-bb3-link.telia.net [80.91.252.121]
>   8   162 ms   164 ms   156 ms  prs-bb3-link.telia.net [80.91.252.37]
>   9   154 ms   153 ms   152 ms  prs-b8-link.telia.net [213.155.131.1]
>  10   155 ms   154 ms   155 ms  online-ic-305116-prs-b8.c.telia.net
> [62.115.40.8
> 6]
>  11   155 ms   156 ms   157 ms  45x-s31-1-a9k2.dc3.poneytelecom.eu
> [195.154.1.35
> ]
>  12   157 ms   160 ms   160 ms  one.vassalengine.org [62.210.178.7]
> 
> Trace complete.
> 

What this shows is that your packets are getting through unhindered. I
see one hop which didn't want to reply (which is not unusual) and one
packet which was dropped (to ash-bb3-link.telia.net---I believe
telia.net is a backbone provider). 160ms from you to our server is not
bad. Nothing looks wrong to me here.

I'm guessing that Windows tracert uses ICMP packets by default. Is
there a way to switch it to use TCP packets instead? (The Linux
traceroute has this as option -T.)

(Also, _please_ answer my question about the original trace containing
the bad IP and hostname. I need to know how you produced that trace if
I'm going to track down that problem.)

-- 
J.


More information about the messages mailing list