10/13/2026 [22:35:29] GMT Home .:. Logout
Forums
Hardmaps.com :: Forums :: HardMaps Public Forum :: Hardmaps VON Server
 
<< Previous thread | Next thread >>
Problems with the ventrilo server?
Moderators: Hardmaps Administrator, *HmS*Wedge, *HmS*grunt, *HmS*Trevor, *HmS*LongBow
Author Post
John_Doe
Sat Mar 31 2007
Registered Member #735
Joined: Fri Jul 29 2005
Location: Israel
Posts: 75
In the last days I'm having troubles connecting to vt.
And if I can connect (after tons of retries) I'm having a huge lag of 15-20 seconds, and every couple minutes the connection is lost (which cause another set of retries).

Is I'm the only one that experiencing this problem?
Back to top
*HmS*Wedge
Sun Apr 01 2007
Captain Slow

Registered Member #3
Joined: Fri Dec 19 2003
Location: Scotland
Posts: 4651
The server has had one maintenence session and is due some network maintenance scheduled to take place on Sunday, April 1st, 2007 starting at approximately 09:00 AM EDT, but i have not heard of anyone else having your sort of problems lately.

Try a trace route to the server and see what you get, it would tell you where the lag is occuring and if your getting any packet loss.
Back to top
Website
John_Doe
Sun Apr 01 2007
Registered Member #735
Joined: Fri Jul 29 2005
Location: Israel
Posts: 75
Well, I'd just ran some checks and there are the results:
Ping check:

C:\>ping -a 74.200.95.99

Pinging ventrilo2.ecgnetwork.com [74.200.95.99] with 32 bytes of data:

Reply from 74.200.95.99: bytes=32 time=306ms TTL=49
Reply from 74.200.95.99: bytes=32 time=261ms TTL=49
Reply from 74.200.95.99: bytes=32 time=284ms TTL=49
Reply from 74.200.95.99: bytes=32 time=290ms TTL=49

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


Trace route results:

C:\>tracert -h 70 75.200.95.99

Tracing route to 99.sub-75-200-95.myvzw.com [75.200.95.99]
over a maximum of 70 hops:

  1     6 ms     5 ms     6 ms  10.234.180.1
  2     8 ms     9 ms     9 ms  172.18.10.41
  3    10 ms    10 ms    13 ms  172.17.0.141
  4    10 ms     9 ms     9 ms  172.17.0.53
  5     *        *        *     Request timed out.
  6     *        9 ms    10 ms  213.8.228.2
  7     *        *        *     Request timed out.
  8    10 ms    13 ms     9 ms  may-gig4-2.inter.net.il [192.117.180.210]
  9    85 ms    83 ms    84 ms  nirit-pos6-0.inter.net.il [213.8.8.226]
 10   281 ms   278 ms   270 ms  62.189.84.225
 11   244 ms   242 ms   264 ms  so-4-0-0.xr1.lnd9.alter.net [158.43.150.157]
 12   288 ms   286 ms   285 ms  so-0-1-0.tr2.lnd9.alter.net [146.188.15.41]
 13   326 ms   293 ms   288 ms  so-6-0-0.ir2.nyc12.alter.net [146.188.15.54]
 14   387 ms   402 ms   362 ms  0.so-1-0-0.il2.nyc9.alter.net [152.63.23.69]
 15   474 ms   422 ms   392 ms  0.so-4-0-2.xl2.gso1.alter.net [152.63.27.158]
 16   344 ms   304 ms   316 ms  pos7-0.gw2.gso1.alter.net [152.63.36.141]
 17   349 ms   320 ms   326 ms  verizonwireless-gso-gw.customer.alter.net [157.130.75.82]
 18   346 ms   330 ms   360 ms  194.sub-66-174-26.myvzw.com [66.174.26.194]
 19   390 ms   373 ms   412 ms  100.sub-66-174-38.myvzw.com [66.174.38.100]
 20   310 ms   355 ms   365 ms  81.sub-66-174-38.myvzw.com [66.174.38.81]
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.
 31     *        *        *     Request timed out.
 32     *        *        *     Request timed out.
 33     *        *        *     Request timed out.
 34     *        *        *     Request timed out.
 35     *        *        *     Request timed out.
 36     *        *        *     Request timed out.
 37     *        *        *     Request timed out.
 38     *        *        *     Request timed out.
 39     *        *        *     Request timed out.
 40     *        *        *     Request timed out.
 41     *        *        *     Request timed out.
 42     *        *        *     Request timed out.
 43     *        *        *     Request timed out.
 44     *        *        *     Request timed out.
 45     *        *        *     Request timed out.
 46     *        *        *     Request timed out.
 47     *        *        *     Request timed out.
 48     *        *     ^C


According to the traceroute output we can see that my packets are arriving to the host company and from then stuck in the router 66.174.38.81. It might be because mis-configuration of the routes in the router, or because traceroute (which based on ICMP Echo replies) is blocked (the more relevant option because ping does return).
Although, you can see that it's seems to be not a problem at my side. The replies of the routers between me and the server are low, so as the ping to the server (285ms approximate).

Maybe the network maintenance scheduled for today will solve this problem...
Back to top
*HmS*Quick
Sun Apr 01 2007
Registered Member #143
Joined: Mon Mar 29 2004
Location: Georgia, USA
Posts: 1700
A few things here John-

I don't see from your tracert that the signal is reaching the Ventrillo host. The last ip on that list is not that of the Ventrillo server. I see it is timing out, but kinda looks to me like it's dropping somewhere between you and the Ventrillo server. I am certainly NOT sure that this is right, but that's how I read those results. Looks more likely that some router between you and the VT server is not pingable, and that's why you are getting the request timed out message. Also looks like one particular router in between you and the VT server is creating the high ping- the jump to almost 300 ms.

The ping that you are getting to VT isn't good or normal. The average VT ping for most players is around 100 ms. You are almost three times as high. That high ping could be a symptom of the connection problem, or it could just be a crappy route between your PC and the VT server.

Finally, we are happy to help you if we can. Hopefully the maintenance will correct the situation. However, if you are the only one having trouble connecting, then it is more likely something particular to the way your PC connects to VT than some problem that we could cure.
Back to top
John_Doe
Sun Apr 01 2007
Registered Member #735
Joined: Fri Jul 29 2005
Location: Israel
Posts: 75
It's looks like that the maintenance did the job.
My ping to the server is now approximate 160ms. And trace route now reachs it's destination after 15 hops only.

Thanks for the help, Both of you.
Back to top
John_Doe
Thu Apr 05 2007
Registered Member #735
Joined: Fri Jul 29 2005
Location: Israel
Posts: 75
The new traceroute:

C:\>tracert 74.200.95.99

Tracing route to ventrilo2.ecgnetwork.com [74.200.95.99]
over a maximum of 30 hops:

  1     6 ms     5 ms     6 ms  10.234.180.1
  2     9 ms     7 ms     7 ms  172.18.10.41
  3    10 ms    10 ms     9 ms  172.17.0.141
  4    20 ms     9 ms     9 ms  172.17.0.53
  5     *        *        *     Request timed out.
  6     *        9 ms    11 ms  213.8.228.2
  7     8 ms     *        *     left720-gig3-14.inter.net.il [213.8.228.18]
  8     *        *        *     Request timed out.
  9    10 ms     9 ms    11 ms  ariela01-gig2-0.inter.net.il [213.8.205.34]
 10     9 ms     9 ms    15 ms  ariela02-gig2-3_2.inter.net.il [192.116.203.38]
 11    64 ms    66 ms    65 ms  lital-gsr-pos7-2.inter.net.il [213.8.8.58]
 12    66 ms    66 ms    65 ms  ge5-4.br02.frf02.pccwbtn.net [63.218.15.49]
 13   163 ms   162 ms   164 ms  dtg.ge10-2.br02.ash01.pccwbtn.net [63.218.94.150]
 14   164 ms   161 ms   163 ms  colo16a.iad.defenderhosting.com [69.65.112.38]
 15   163 ms   161 ms   162 ms  ventrilo2.ecgnetwork.com [74.200.95.99]

Trace complete.
Back to top
*HmS*Wedge
Thu Apr 05 2007
Captain Slow

Registered Member #3
Joined: Fri Dec 19 2003
Location: Scotland
Posts: 4651
Your getting request timed out on hops 5 and 8 and a partial problem on hop 7, I would think this could cause packet loss and lag at times even with a good ping John, its really a matter for your ISP now I think, as as far as I can see thats where the problem is, give them the address and your trace route results.
Back to top
Website
John_Doe
Thu Apr 05 2007
Registered Member #735
Joined: Fri Jul 29 2005
Location: Israel
Posts: 75
That "problem" on hops: 5,7,8 is on every traceroute which i'm doing to every site.
This is the network structure of my ISP response.

Anyway, as we spoke on the night on vt, I'll give them another week before I'll call them. It's the holiday season and it's might be the reason (btw, my ping to the server is lower then my ping to google.com!). For a proof, in the night when I'd spoke with you the lag suddenly drop from 25secs to 0.5-1.5secs only (which might considered as a good result due to the previous results I'd posted here).

Thanks you all for trying to help me solve this problem. (Wedge, Quick, grunt, Ranger Six, hardazz and anyone that I might forgetten by mistake)
Back to top
 

Jump:     Back to top

Syndicate this thread: rss 0.92 Syndicate this thread: rss 2.0 Syndicate this thread: RDF
Powered by e107 Forum System
All trademarks are copyright their respective owners.
This site is best viewed using 1280-1024 screen resolution.
{THEMEDISCLAIMER}
Render time: 0.1354 sec, 0.0240 of that for queries.