Problem with VERY slow and laggy Trainz 2012

OK - another Command Prompt command for you in that case. Enter the following then press Enter as before:

tracert download2.ts2009.com

This one will produce quite a bit more information but it will help identify if there's an issue somewhere between your system and N3V's servers.

Shane
 
The results:


C:\Users\Alex>tracert download2.ts2009.com

Tracing route to download2.ts2009.com [108.162.204.36]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.0.1
2 179 ms 40 ms 40 ms hlrn-dsl-gw06.hlrn.qwest.net [207.225.112.6]
3 50 ms 39 ms 40 ms hlrn-agw1.inet.qwest.net [71.217.188.41]
4 41 ms 40 ms 41 ms dvr-brdr-02.inet.qwest.net [67.14.24.118]
5 399 ms 686 ms 747 ms den-b1-link.telia.net [213.248.102.185]
6 508 ms 333 ms 337 ms chi-b21-link.telia.net [213.155.133.172]
7 387 ms 439 ms 153 ms cloudflare-ic-306330-chi-b21.c.telia.net [62.115
.44.10]
8 63 ms 63 ms 63 ms 108.162.204.36

Trace complete.
 
The results:


C:\Users\Alex>tracert download2.ts2009.com

Tracing route to download2.ts2009.com [108.162.204.36]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.0.1
2 179 ms 40 ms 40 ms hlrn-dsl-gw06.hlrn.qwest.net [207.225.112.6]
3 50 ms 39 ms 40 ms hlrn-agw1.inet.qwest.net [71.217.188.41]
4 41 ms 40 ms 41 ms dvr-brdr-02.inet.qwest.net [67.14.24.118]
5 399 ms 686 ms 747 ms den-b1-link.telia.net [213.248.102.185]
6 508 ms 333 ms 337 ms chi-b21-link.telia.net [213.155.133.172]
7 387 ms 439 ms 153 ms cloudflare-ic-306330-chi-b21.c.telia.net [62.115
.44.10]
8 63 ms 63 ms 63 ms 108.162.204.36

Trace complete.

Hi Alex,

These might be the problem...
5 399 ms 686 ms 747 ms den-b1-link.telia.net [213.248.102.185] <------ Really, really, really, long pings here and below.
6 508 ms 333 ms 337 ms chi-b21-link.telia.net [213.155.133.172]
7 387 ms 439 ms 153 ms cloudflare-ic-306330-chi-b21.c.telia.net [62.115.44.10]

These really, really, really, did I say really? long pings can cause timeouts when downloading files. This could be a problem with your ISP.

John
 
Does the command produce any results? If it does, the results shown will help pinpoint where it's timing out (usually indicated by three asterisks in a row).

Shane

EDIT: Just noticed your results above. Looks like a long ping time as JCitron has also said. There may be a way round this, but it may get technical.
 
Last edited:
I checked each address in my browser (chrome)
hlrn-dsl-gw06.hlrn.qwest.net - ERR_CONNECTION_TIMED_OUT
hlrn-agw1.inet.qwest.net - ERR_CONNECTION_TIMED_OUT
ms dvr-brdr-02.inet.qwest.net - Traced to no address at all (brought up forums on high pings)
747 ms den-b1-link.telia.net - Traced to no address (brought up forums on ping timeouts)
337 ms chi-b21-link.telia.net - Traced to no address (brought up forums on server disconnects)
153 ms cloudflare-ic-306330-chi-b21.c.telia.neta - Google had absolutely no search results for address

I think John might be correct about it being a problem with my ISP

Alex
 
Back
Top