How to fix ENT autohost lag

[xITMxWarden]

I know a lot of people complained, but I'm pinging a casual 150-350ms in your games. and I LOVE Ent, i dont wanna leave it. Is there a server IP I can probably add to my router so it gives it full access. Any help would be accepted. I live up in New Jersey

[gkgough]

I am guessing you use Verizon Fios for your internet service provider? Its related to one of the stops on your path to the ENT s5 server it looks like. One of the admins here figured that out today through viewing my tracert, and is looking into if there is anything they can do.

[gkgough]

Go to the forum titled Massive Lag Issue thread, and in the last posting of that thread Uakf.b has the solution to the problem!

[xITMxWarden]

I use regular Verizon DSL. Average speed is usually 400-500 kbps. More then enough for this game. I also run a very high end computer that i made my self. I just play DoTA 1 because literally like 15 of my mates play it.

here is the ping test using the command prompt.

Code: Select all

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\K0BRA>ping s5.clanent.net

Pinging s5.clanent.net [192.30.34.50] with 32 bytes of data:
Reply from 192.30.34.50: bytes=32 time=150ms TTL=55
Reply from 192.30.34.50: bytes=32 time=163ms TTL=55
Reply from 192.30.34.50: bytes=32 time=171ms TTL=55
Reply from 192.30.34.50: bytes=32 time=171ms TTL=55

Ping statistics for 192.30.34.50:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 150ms, Maximum = 171ms, Average = 163ms

C:\Users\K0BRA>tracert s5.clanent.net

Tracing route to s5.clanent.net [192.30.34.50]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.0.0.1
  2     1 ms     1 ms     1 ms  dslrouter [192.168.1.1]
  3    22 ms    22 ms    22 ms  10.5.74.1
  4    24 ms    23 ms    28 ms  P0-3-1-3.NWRKNJ-LCR-21.verizon-gni.net [130.81.1
36.162]
  5    22 ms    22 ms    22 ms  ae0-0.NWRK-BB-RTR1.verizon-gni.net [130.81.209.1
54]
  6    27 ms    27 ms    28 ms  xe-1-0-3-0.NY5030-BB-RTR1.verizon-gni.net [130.8
1.23.186]
  7    28 ms    28 ms    28 ms  0.so-7-0-0.XT1.NYC4.ALTER.NET [152.63.17.89]
  8    35 ms    35 ms    35 ms  TenGigE0-4-4-0.GW8.NYC4.ALTER.NET [152.63.18.202
]
  9   119 ms   120 ms   165 ms  tinet-gw.customer.alter.net [152.179.72.122]
 10   175 ms   174 ms   211 ms  xe-5-0-0.atl11.ip4.tinet.net [89.149.180.206]
 11   170 ms   151 ms   149 ms  ramnode-gw.ip4.tinet.net [77.67.78.254]
 12   168 ms   171 ms   173 ms  192.30.33.8
 13     *        *      159 ms  S5 [192.30.34.50]

Trace complete.

C:\Users\K0BRA>

Code: Select all

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\K0BRA>ping s10.clanent.net

Pinging s10.clanent.net [198.23.154.229] with 32 bytes of data:
Reply from 198.23.154.229: bytes=32 time=125ms TTL=50
Reply from 198.23.154.229: bytes=32 time=120ms TTL=50
Reply from 198.23.154.229: bytes=32 time=112ms TTL=50
Reply from 198.23.154.229: bytes=32 time=123ms TTL=50

Ping statistics for 198.23.154.229:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 112ms, Maximum = 125ms, Average = 120ms

C:\Users\K0BRA>tracert s10.clanent.net

Tracing route to s10.clanent.net [198.23.154.229]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.0.0.1
  2     1 ms     1 ms     1 ms  dslrouter [192.168.1.1]
  3    23 ms    22 ms    22 ms  10.5.74.1
  4    26 ms    28 ms    27 ms  P0-3-0-3.NWRKNJ-LCR-22.verizon-gni.net [130.81.1
93.42]
  5    93 ms    24 ms    24 ms  so-4-0-0-0.NWRK-BB-RTR2.verizon-gni.net [130.81.
22.64]
  6    27 ms    28 ms    27 ms  0.xe-3-1-0.BR3.NYC4.ALTER.NET [152.63.26.117]
  7    66 ms    66 ms    66 ms  204.255.168.66
  8    39 ms    38 ms    38 ms  ae-2.r23.nycmny01.us.bb.gin.ntt.net [129.250.4.1
48]
  9    52 ms    97 ms    51 ms  ae-3.r20.chcgil09.us.bb.gin.ntt.net [129.250.2.4
0]
 10    53 ms    53 ms    52 ms  ae-1.r06.chcgil09.us.bb.gin.ntt.net [129.250.4.1
46]
 11   114 ms   115 ms   116 ms  xe-0-0-0-12.r06.chcgil09.us.ce.gin.ntt.net [129.
250.193.2]
 12    51 ms    71 ms    52 ms  ae4.cr1.ord6.us.scnet.net [204.93.204.85]
 13   120 ms    94 ms    96 ms  ae3.ar6.ord6.us.scnet.net [204.93.204.49]
 14   158 ms   152 ms   155 ms  as36352.xe-2-0-2.ar6.ord6.us.scnet.net [50.31.15
4.182]
 15   157 ms   156 ms   157 ms  10ge-1-3-1.fz146.cr1.chi.colocrossing.com [206.2
17.130.114]
 16   160 ms   154 ms   156 ms  ae1015-fu174.chi.colocrossing.com [206.217.131.1
42]
 17   157 ms   158 ms   157 ms  chinode1.ugvps.com [198.144.186.66]
 18   118 ms   116 ms   116 ms  host.colocrossing.com [198.23.154.229]

Trace complete.

C:\Users\K0BRA>

Code: Select all

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\K0BRA>ping eihl.clanent.net

Pinging eihl.clanent.net [18.181.6.185] with 32 bytes of data:
Reply from 18.181.6.185: bytes=32 time=31ms TTL=48
Reply from 18.181.6.185: bytes=32 time=31ms TTL=48
Reply from 18.181.6.185: bytes=32 time=32ms TTL=48
Reply from 18.181.6.185: bytes=32 time=32ms TTL=48

Ping statistics for 18.181.6.185:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 31ms, Maximum = 32ms, Average = 31ms

C:\Users\K0BRA>tracert eihl.clanent.net

Tracing route to eihl.clanent.net [18.181.6.185]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.0.0.1
  2     2 ms     1 ms     1 ms  dslrouter [192.168.1.1]
  3    23 ms    22 ms    22 ms  10.5.74.1
  4    24 ms    24 ms    27 ms  P0-3-0-3.NWRKNJ-LCR-22.verizon-gni.net [130.81.1
93.42]
  5    22 ms    22 ms    23 ms  so-6-1-0-0.NWRK-BB-RTR2.verizon-gni.net [130.81.
199.16]
  6    27 ms    27 ms    28 ms  0.xe-11-1-0.BR1.NYC1.ALTER.NET [152.63.4.237]
  7     *       54 ms    54 ms  ae11.edge2.NewYork.Level3.net [4.68.62.41]
  8    84 ms    84 ms    85 ms  vlan51.ebr1.NewYork2.Level3.net [4.69.138.222]
  9    32 ms    31 ms    31 ms  ae-4-4.ebr1.NewYork1.Level3.net [4.69.141.17]
 10     *        *        *     Request timed out.
 11    89 ms    92 ms    90 ms  ae-0-11.bar1.Boston1.Level3.net [4.69.140.89]
 12    32 ms    32 ms    33 ms  ae-7-7.car1.Boston1.Level3.net [4.69.132.241]
 13    32 ms    32 ms    33 ms  MASSACHUSET.car1.Boston1.Level3.net [4.53.48.98]

 14    33 ms    33 ms    33 ms  DMZ-RTR-1-EXTERNAL-RTR-1.MIT.EDU [18.192.9.1]
 15    50 ms    50 ms    47 ms  BACKBONE-RTR-1-DMZ-RTR-1.MIT.EDU [18.168.5.1]
 16    50 ms    49 ms    50 ms  W92-RTR-1-BACKBONE-2.MIT.EDU [18.168.1.25]
 17    33 ms    33 ms    33 ms  GLOBAL-DYNAMICS.MIT.EDU [18.181.0.99]
 18    31 ms    32 ms    31 ms  XVM-SIX-185.MIT.EDU [18.181.6.185]

Trace complete.

C:\Users\K0BRA>

Please help =[

[Sn00be]

I agree that tinet.net have a issue with multiple gateways.
I did a traceroute to s5.clanent.net my self.
This hop along the way made it go up 100ms
5 137 ms 195 ms 137 ms xe-4-3-0.atl11.ip4.tinet.net [141.136.108.134]
note that is a diffrent hop the xITMxWarden postet,
but still same company.
for note its the same with S10 this time its scnet.net that have high ping on their hops.
(ofc there is many out there with inet knowgled) ICMP packets might be priortied down, as it diffrent hops with high ms.

But to defend clanent, if it's the isp's that have the issue, they can write / call them,
but its deepling into there routing network, so if there is a problem, the isp should be aware of they trying to fix or reroute it.

Hope this helped a bit
/-Sn00be - LTD gamer

[xITMxWarden]

I agree that this could be a problem with the ISP. But I am not going to just change my internet service just because this game server coincides with it. This lag started about late december, prior to that I had been playing a massive amount of DoTA on this server (I had a lot of ELO with other accounts as well as this one), and I never had that lag before it. Now when I play since late december, the lag and delay has been incrementing on a serious level each week. The first week of lag was not that bad, it was a casual massive spike in gameplay every 2 -3 minutes but nothing too catastrophic. Then it started giving me minor delay. Then the lag started spiking every 50-70 seconds. Then the delay went up even more. Now its to the point to huge spikes and lag, and unplayable delay. Non of the other game servers give me this problem, and I really find it sad to see that they already gave up on trying to fix it.

[uakf.b]

We did post a fix, try the proxy setting on ENT Connect (go to ENT Connect tab, click enable proxy settings, and then use ENT Connect to join games through the Warcraft III LAN menu).

[xITMxWarden]

I did use Ent connect through LAN and pings were the exact same

[uakf.b]

Did you enable the proxy settings? Because you're going through the exact same routing node as the other guy, which is causing your lag; and everyone else says that the proxy is fixing all the problems for them. The default is proxy settings are disabled, so you have to enable it.

You probably also want to contact Verizon or whoever your ISP is so that they fix their node.

When you connect to certain other game servers, because of their geographic location, you don't have to go through this slow routing node. Other game servers not having this problem has nothing to do with us, it has to do with your ISP.

[scooby]

I use regular Verizon DSL. Average speed is usually 400-500 kbps. More then enough for this game. I also run a very high end computer that i made my self. I just play DoTA 1 because literally like 15 of my mates play it.

here is the ping test using the command prompt.

Code: Select all

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\K0BRA>ping s5.clanent.net

Pinging s5.clanent.net [192.30.34.50] with 32 bytes of data:
Reply from 192.30.34.50: bytes=32 time=150ms TTL=55
Reply from 192.30.34.50: bytes=32 time=163ms TTL=55
Reply from 192.30.34.50: bytes=32 time=171ms TTL=55
Reply from 192.30.34.50: bytes=32 time=171ms TTL=55

Ping statistics for 192.30.34.50:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 150ms, Maximum = 171ms, Average = 163ms

C:\Users\K0BRA>tracert s5.clanent.net

Tracing route to s5.clanent.net [192.30.34.50]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.0.0.1
  2     1 ms     1 ms     1 ms  dslrouter [192.168.1.1]
  3    22 ms    22 ms    22 ms  10.5.74.1
  4    24 ms    23 ms    28 ms  P0-3-1-3.NWRKNJ-LCR-21.verizon-gni.net [130.81.1
36.162]
  5    22 ms    22 ms    22 ms  ae0-0.NWRK-BB-RTR1.verizon-gni.net [130.81.209.1
54]
  6    27 ms    27 ms    28 ms  xe-1-0-3-0.NY5030-BB-RTR1.verizon-gni.net [130.8
1.23.186]
  7    28 ms    28 ms    28 ms  0.so-7-0-0.XT1.NYC4.ALTER.NET [152.63.17.89]
  8    35 ms    35 ms    35 ms  TenGigE0-4-4-0.GW8.NYC4.ALTER.NET [152.63.18.202
]
  9   119 ms   120 ms   165 ms  tinet-gw.customer.alter.net [152.179.72.122]
 10   175 ms   174 ms   211 ms  xe-5-0-0.atl11.ip4.tinet.net [89.149.180.206]
 11   170 ms   151 ms   149 ms  ramnode-gw.ip4.tinet.net [77.67.78.254]
 12   168 ms   171 ms   173 ms  192.30.33.8
 13     *        *      159 ms  S5 [192.30.34.50]

Trace complete.

C:\Users\K0BRA>

Code: Select all

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\K0BRA>ping s10.clanent.net

Pinging s10.clanent.net [198.23.154.229] with 32 bytes of data:
Reply from 198.23.154.229: bytes=32 time=125ms TTL=50
Reply from 198.23.154.229: bytes=32 time=120ms TTL=50
Reply from 198.23.154.229: bytes=32 time=112ms TTL=50
Reply from 198.23.154.229: bytes=32 time=123ms TTL=50

Ping statistics for 198.23.154.229:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 112ms, Maximum = 125ms, Average = 120ms

C:\Users\K0BRA>tracert s10.clanent.net

Tracing route to s10.clanent.net [198.23.154.229]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.0.0.1
  2     1 ms     1 ms     1 ms  dslrouter [192.168.1.1]
  3    23 ms    22 ms    22 ms  10.5.74.1
  4    26 ms    28 ms    27 ms  P0-3-0-3.NWRKNJ-LCR-22.verizon-gni.net [130.81.1
93.42]
  5    93 ms    24 ms    24 ms  so-4-0-0-0.NWRK-BB-RTR2.verizon-gni.net [130.81.
22.64]
  6    27 ms    28 ms    27 ms  0.xe-3-1-0.BR3.NYC4.ALTER.NET [152.63.26.117]
  7    66 ms    66 ms    66 ms  204.255.168.66
  8    39 ms    38 ms    38 ms  ae-2.r23.nycmny01.us.bb.gin.ntt.net [129.250.4.1
48]
  9    52 ms    97 ms    51 ms  ae-3.r20.chcgil09.us.bb.gin.ntt.net [129.250.2.4
0]
 10    53 ms    53 ms    52 ms  ae-1.r06.chcgil09.us.bb.gin.ntt.net [129.250.4.1
46]
 11   114 ms   115 ms   116 ms  xe-0-0-0-12.r06.chcgil09.us.ce.gin.ntt.net [129.
250.193.2]
 12    51 ms    71 ms    52 ms  ae4.cr1.ord6.us.scnet.net [204.93.204.85]
 13   120 ms    94 ms    96 ms  ae3.ar6.ord6.us.scnet.net [204.93.204.49]
 14   158 ms   152 ms   155 ms  as36352.xe-2-0-2.ar6.ord6.us.scnet.net [50.31.15
4.182]
 15   157 ms   156 ms   157 ms  10ge-1-3-1.fz146.cr1.chi.colocrossing.com [206.2
17.130.114]
 16   160 ms   154 ms   156 ms  ae1015-fu174.chi.colocrossing.com [206.217.131.1
42]
 17   157 ms   158 ms   157 ms  chinode1.ugvps.com [198.144.186.66]
 18   118 ms   116 ms   116 ms  host.colocrossing.com [198.23.154.229]

Trace complete.

C:\Users\K0BRA>

Code: Select all

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\K0BRA>ping eihl.clanent.net

Pinging eihl.clanent.net [18.181.6.185] with 32 bytes of data:
Reply from 18.181.6.185: bytes=32 time=31ms TTL=48
Reply from 18.181.6.185: bytes=32 time=31ms TTL=48
Reply from 18.181.6.185: bytes=32 time=32ms TTL=48
Reply from 18.181.6.185: bytes=32 time=32ms TTL=48

Ping statistics for 18.181.6.185:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 31ms, Maximum = 32ms, Average = 31ms

C:\Users\K0BRA>tracert eihl.clanent.net

Tracing route to eihl.clanent.net [18.181.6.185]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.0.0.1
  2     2 ms     1 ms     1 ms  dslrouter [192.168.1.1]
  3    23 ms    22 ms    22 ms  10.5.74.1
  4    24 ms    24 ms    27 ms  P0-3-0-3.NWRKNJ-LCR-22.verizon-gni.net [130.81.1
93.42]
  5    22 ms    22 ms    23 ms  so-6-1-0-0.NWRK-BB-RTR2.verizon-gni.net [130.81.
199.16]
  6    27 ms    27 ms    28 ms  0.xe-11-1-0.BR1.NYC1.ALTER.NET [152.63.4.237]
  7     *       54 ms    54 ms  ae11.edge2.NewYork.Level3.net [4.68.62.41]
  8    84 ms    84 ms    85 ms  vlan51.ebr1.NewYork2.Level3.net [4.69.138.222]
  9    32 ms    31 ms    31 ms  ae-4-4.ebr1.NewYork1.Level3.net [4.69.141.17]
 10     *        *        *     Request timed out.
 11    89 ms    92 ms    90 ms  ae-0-11.bar1.Boston1.Level3.net [4.69.140.89]
 12    32 ms    32 ms    33 ms  ae-7-7.car1.Boston1.Level3.net [4.69.132.241]
 13    32 ms    32 ms    33 ms  MASSACHUSET.car1.Boston1.Level3.net [4.53.48.98]

 14    33 ms    33 ms    33 ms  DMZ-RTR-1-EXTERNAL-RTR-1.MIT.EDU [18.192.9.1]
 15    50 ms    50 ms    47 ms  BACKBONE-RTR-1-DMZ-RTR-1.MIT.EDU [18.168.5.1]
 16    50 ms    49 ms    50 ms  W92-RTR-1-BACKBONE-2.MIT.EDU [18.168.1.25]
 17    33 ms    33 ms    33 ms  GLOBAL-DYNAMICS.MIT.EDU [18.181.0.99]
 18    31 ms    32 ms    31 ms  XVM-SIX-185.MIT.EDU [18.181.6.185]

Trace complete.

C:\Users\K0BRA>

Please help =[

Well ! PING response from the server s5.clanent.net .


Pinging s5.clanent.net [192.30.34.50] with 32 bytes of data:
Reply from 192.30.34.50: bytes=32 time=67ms TTL=53
Reply from 192.30.34.50: bytes=32 time=67ms TTL=53
Reply from 192.30.34.50: bytes=32 time=67ms TTL=53
Reply from 192.30.34.50: bytes=32 time=67ms TTL=53
Ping statistics for 192.30.34.50:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 67ms, Maximum = 67ms, Average = 67ms


PING response from the server s10.clanent.net


Pinging s10.clanent.net [37.247.53.188] with 32 bytes of data:
Reply from 37.247.53.188: bytes=32 time=147ms TTL=46
Reply from 37.247.53.188: bytes=32 time=147ms TTL=46
Reply from 37.247.53.188: bytes=32 time=147ms TTL=46
Reply from 37.247.53.188: bytes=32 time=147ms TTL=46
Ping statistics for 37.247.53.188:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 147ms, Maximum = 147ms, Average = 147ms


PING response from the server eihl.clanent.net


Pinging eihl.clanent.net [18.181.6.185] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 18.181.6.185:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss)

I did this ping test using whoisxy.com. this test results shows connection problem occured in eihl.clanet.net during ping .