Ive been having a lot of the same issues too, forums, wiki and server being
slow past couple of weeks. Sometimes pages go unresponsive and I always have
to log in everytime - never used to have to do that, even if I navigate away
to like bbc.com then come back 2 secs later I’m logged out weird…
For fun I did the ICMP and TCP traces as well as a ping (all below) -
nothing looks out of the ordinary to me either speed wise, yet I can’t even
get in to a subforum right this very second on the website (just hanging.)
even though the traces look good. Almost like the server just isn’t
responding even though we are connecting
PS C:\Users\Tim> tracert vassalengine.org
Tracing route to 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 25 ms 25 ms 25 ms 70-138-80-3.lightspeed.hstntx.sbcglobal.net
[70.138.80.3]
3 25 ms 25 ms 30 ms 71.144.129.18
4 27 ms 27 ms 27 ms 12.83.36.5
5 31 ms 31 ms 35 ms ggr3.dlstx.ip.att.net [12.122.139.17]
6 31 ms 31 ms 33 ms 192.205.37.50
7 71 ms 70 ms 70 ms ash-bb3-link.telia.net [80.91.252.121]
8 173 ms 170 ms 166 ms prs-bb3-link.telia.net [80.91.251.99]
9 163 ms 164 ms 163 ms prs-b8-link.telia.net [213.155.131.1]
10 183 ms 181 ms 181 ms online-ic-305116-prs-b8.c.telia.net
[62.115.40.86]
11 189 ms 186 ms 190 ms 45x-s31-1-a9k2.dc3.poneytelecom.eu
[195.154.1.35]
12 166 ms 157 ms 156 ms one.vassalengine.org [62.210.178.7]
Trace complete.
PS C:\Users\Tim> ping vassalengine.org
Pinging vassalengine.org [62.210.178.7] with 32 bytes of data:
Request timed out.
Reply from 62.210.178.7: bytes=32 time=159ms TTL=50
Reply from 62.210.178.7: bytes=32 time=155ms TTL=50
Reply from 62.210.178.7: bytes=32 time=159ms TTL=50
Ping statistics for 62.210.178.7:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 155ms, Maximum = 159ms, Average = 157ms
PS C:\Users\Tim> tracetcp vassalengine.org
Tracing route to 62.210.178.7 [one.vassalengine.org] on port 80
Over a maximum of 30 hops.
1 3 ms 2 ms 2 ms 192.168.1.254 [homeportal]
2 26 ms 27 ms 26 ms 70.138.80.3
[70-138-80-3.lightspeed.hstntx.sbcglobal.net]
3 25 ms 31 ms 26 ms 71.144.129.18
4 29 ms 27 ms 25 ms 12.83.36.5
5 35 ms 34 ms 33 ms 12.122.139.17 [ggr3.dlstx.ip.att.net]
6 33 ms 32 ms 33 ms 192.205.37.50
7 122 ms 135 ms 79 ms 213.155.133.176 [nyk-bb1-link.telia.net]
8 173 ms 173 ms 173 ms 213.155.135.4 [prs-bb3-link.telia.net]
9 168 ms 172 ms 164 ms 213.155.131.3 [prs-b8-link.telia.net]
10 197 ms 204 ms 201 ms 62.115.40.86
[online-ic-305116-prs-b8.c.telia.net]
11 201 ms 201 ms 199 ms 195.154.1.35
[45x-s31-1-a9k2.dc3.poneytelecom.eu]
12 Destination Reached in 182 ms. Connection established to
62.210.178.7
Trace Complete.
PS C:\Users\Tim>
From: messages [mailto:messages-bounces@vassalengine.org] On Behalf Of Joel
Uckelman
Sent: Monday, March 02, 2015 5:36 AM
To: The mailing list for VASSAL
Subject: Re: [messages] [Technical Support & Bugs] Very slow response
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.)
–
J.