Jump to content

Recommended Posts

Posted

If there is ever a time that the server is lagging and EVERYONE experiences it, not just you, I want you to do the following steps and send the information to me via the forums:

Step one > Click Start and click Run.

Step two > type cmd

Step three > type tracert 208.167.243.207

Step four > Copy and paste the information into a reply on this topic. Please also provide what country you are from, or general location for reference.

 

Example:

Quote

 

East Coast, US

 

Tracing route to 208.167.243.207.choopa.net [208.167.243.207]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2    11 ms     8 ms     7 ms  10.240.163.137
  3     9 ms     9 ms     9 ms  67.59.240.104
  4    13 ms    13 ms    12 ms  ool-4353f41c.dyn.optonline.net [67.83.244.28]
  5    12 ms    13 ms    14 ms  67.59.239.129
  6    12 ms    13 ms    11 ms  nycmny830sw.cv.net [65.19.113.3]
  7     *        *        *     Request timed out.
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10    14 ms    15 ms    13 ms  208.167.243.207.choopa.net [208.167.243.207]

Trace complete.

 

 

  • Replies 71
  • Created
  • Last Reply

Top Posters In This Topic

  • 6 months later...
Posted

We all hit some lag on the server today during Argentan but when I tried to run the tracert it came back with: Unable to resolve target system name 8.6.76.164:27015.

Then I tried using the pub servers IP and got the same message.

  • 2 weeks later...
Posted
We all hit some lag on the server today during Argentan but when I tried to run the tracert it came back with: Unable to resolve target system name 8.6.76.164:27015.

Then I tried using the pub servers IP and got the same message.

Me too

Posted

Major lag on the server just now. I hope this info will help you.

Microsoft Windows [Version 6.1.7600]

Copyright © 2009 Microsoft Corporation. All rights reserved.

C:\Users\Owner>tracert 208.167.243.207

Tracing route to 208.167.243.207.choopa.net [208.167.243.207]

over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1

2 7 ms 7 ms 7 ms 10.240.184.117

3 8 ms 7 ms 7 ms dstswr2-ge3-4.rh.frptny.cv.net [67.59.224.225]

4 * * * Request timed out.

5 17 ms 13 ms 11 ms rtr4-tg11-2.wan.hcvlny.cv.net [64.15.4.25]

6 * * * Request timed out.

7 * * * Request timed out.

8 28 ms 19 ms 19 ms vl52-cr2.ewr2.choopa.net [66.55.128.34]

9 12 ms 11 ms 12 ms 208.167.243.207.choopa.net [208.167.243.207]

Trace complete.

C:\Users\Owner>

Posted

Many people were complaining of server lag at 8:45 Eastern.

C:\Users\Owner>tracert 208.167.243.207

Tracing route to 208.167.243.207.choopa.net [208.167.243.207]

over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1

2 7 ms 8 ms 7 ms 10.240.184.117

3 8 ms 7 ms 7 ms dstswr2-ge3-4.rh.frptny.cv.net [67.59.224.225]

4 * * * Request timed out.

5 13 ms 12 ms 12 ms rtr4-tg11-2.wan.hcvlny.cv.net [64.15.4.25]

6 * * * Request timed out.

7 * * * Request timed out.

8 12 ms 11 ms 12 ms vl52-cr2.ewr2.choopa.net [66.55.128.34]

9 13 ms 11 ms 11 ms 208.167.243.207.choopa.net [208.167.243.207]

Trace complete.

C:\Users\Owner>ping 208.167.243.207

Pinging 208.167.243.207 with 32 bytes of data:

Reply from 208.167.243.207: bytes=32 time=12ms TTL=56

Reply from 208.167.243.207: bytes=32 time=12ms TTL=56

Reply from 208.167.243.207: bytes=32 time=12ms TTL=56

Reply from 208.167.243.207: bytes=32 time=13ms TTL=56

Ping statistics for 208.167.243.207:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 12ms, Maximum = 13ms, Average = 12ms

C:\Users\Owner>

  • 2 weeks later...
Posted

My ping has been going from 40 - 2500 on vent for most of the day.

These are the results from a tracert and a ping test

Microsoft Windows [Version 6.1.7600]

Copyright © 2009 Microsoft Corporation. All rights reserved.

C:\Users\Owner>tracert vent14.gameservers.com

Tracing route to vent14.gameservers.com [8.6.74.132]

over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1

2 20 ms 7 ms 7 ms 10.240.184.117

3 8 ms 7 ms 7 ms dstswr2-ge3-4.rh.frptny.cv.net [67.59.224.225]

4 * * * Request timed out.

5 11 ms 10 ms 23 ms rtr3-tg10-2.wan.hcvlny.cv.net [64.15.4.5]

6 * * * Request timed out.

7 * * * Request timed out.

8 10 ms 16 ms 17 ms vlan69.csw1.NewYork1.Level3.net [4.68.16.62]

9 10 ms 11 ms 11 ms ae-62-62.ebr2.NewYork1.Level3.net [4.69.148.33]

10 13 ms 11 ms 12 ms ae-6-6.ebr2.NewYork2.Level3.net [4.69.141.22]

11 35 ms 37 ms 36 ms ae-2-2.ebr1.Chicago1.Level3.net [4.69.132.65]

12 42 ms 36 ms 35 ms ae-1-100.ebr2.Chicago1.Level3.net [4.69.132.42]

13 37 ms 36 ms 37 ms ae-4-4.car2.StLouis1.Level3.net [4.69.132.189]

14 43 ms 43 ms 43 ms ge-10-2.hsa1.StLouis1.Level3.net [4.69.140.161]

15 * 50 ms 47 ms 8.6.74.132

Trace complete.

C:\Users\Owner>ping vent14.gameservers.com

Pinging vent14.gameservers.com [8.6.74.132] with 32 bytes of data:

Reply from 8.6.74.132: bytes=32 time=51ms TTL=50

Reply from 8.6.74.132: bytes=32 time=47ms TTL=50

Reply from 8.6.74.132: bytes=32 time=46ms TTL=50

Request timed out.

Ping statistics for 8.6.74.132:

Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),

Approximate round trip times in milli-seconds:

Minimum = 46ms, Maximum = 51ms, Average = 48ms

Posted

It looks like everything died today. The pub and vent. I had some pubbers message me about it so I ran the tests. I thought that it might just be my comp so I ran a ping test on yahoo.com too. Hope this helps.

Microsoft Windows [Version 6.1.7600]

Copyright © 2009 Microsoft Corporation. All rights reserved.

C:\Users\Owner>tracert 208.167.243.207

Tracing route to 208.167.243.207 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.0.1

2 7 ms 8 ms 7 ms 10.240.184.117

3 9 ms 7 ms 8 ms dstswr2-ge3-4.rh.frptny.cv.net [67.59.224.225]

4 * * * Request timed out.

5 13 ms 12 ms 11 ms rtr4-tg11-2.wan.hcvlny.cv.net [64.15.4.25]

6 * * * Request timed out.

7 * * * Request timed out.

8 * * * Request timed out.

9 * * * Request timed out.

10 * * * Request timed out.

11 * * * Request timed out.

12 * * * Request timed out.

13 * * * Request timed out.

14 * * * Request timed out.

15 * * * Request timed out.

16 * * * Request timed out.

17 * * * Request timed out.

18 * * * Request timed out.

19 * * * Request timed out.

20 * * * Request timed out.

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.

Trace complete.

C:\Users\Owner>ping 208.167.243.207

Pinging 208.167.243.207 with 32 bytes of data:

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Ping statistics for 208.167.243.207:

Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\Users\Owner>ping yahoo.com

Pinging yahoo.com [98.137.149.56] with 32 bytes of data:

Reply from 98.137.149.56: bytes=32 time=113ms TTL=49

Reply from 98.137.149.56: bytes=32 time=94ms TTL=50

Reply from 98.137.149.56: bytes=32 time=99ms TTL=50

Reply from 98.137.149.56: bytes=32 time=108ms TTL=50

Ping statistics for 98.137.149.56:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 94ms, Maximum = 113ms, Average = 103ms

C:\Users\Owner>tracert vent14.gameservers.com

Unable to resolve target system name vent14.gameservers.com.

C:\Users\Owner>ping vent14.gameservers.com

Ping request could not find host vent14.gameservers.com. Please check the name a

nd try again.

C:\Users\Owner>

Posted

The server keeps crapping out today. I haven't been on all day but so far I count 3 times that it has died while I was playing. It is also very choppy when it is not completely dead. And vent has died twice too.

  • 2 weeks later...
Posted

Almost the entire pub timed out today about 1:40 AM EST.

Microsoft Windows [Version 6.1.7600]

Copyright © 2009 Microsoft Corporation. All rights reserved.

C:\Users\Owner>tracert 208.167.243.207

Tracing route to 208.167.243.207.choopa.net [208.167.243.207]

over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1

2 8 ms 7 ms 7 ms 10.240.184.117

3 7 ms 9 ms 7 ms dstswr2-ge3-4.rh.frptny.cv.net [67.59.224.225]

4 * * * Request timed out.

5 13 ms 13 ms 12 ms rtr4-tg11-2.wan.hcvlny.cv.net [64.15.4.25]

6 * * * Request timed out.

7 * * * Request timed out.

8 * * * Request timed out.

9 * * * Request timed out.

10 * * * Request timed out.

11 * * * Request timed out.

12 * * * Request timed out.

13 * * * Request timed out.

14 * * * Request timed out.

15 * * * Request timed out.

16 * * * Request timed out.

17 * * * Request timed out.

18 * * * Request timed out.

19 * * * Request timed out.

20 * * * Request timed out.

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.

Trace complete.

C:\Users\Owner>

Posted

Ok, so its 12:08 AM

And the Lag Will not Stop.

Basically, Lag and then people will D/C.

Then they can not get back in the server. Period.

"Server Not Responding."

-This is the Error message.

I took a Demo of my rates and reviewed them they all seemed fine.

As far as this lagg i believe it is all ISP Related.

This happed more than 6 times tonight.

  • 2 weeks later...
Posted

Support came through and told me this:

There was a process on your machine that was eating up the resources, causing your server to perform less than perfectly. I have killed this process and you should now be all set to go.

If you have any further issues or questions, let me know.

Let me know how the server is doing and continue to post trace routes if there's any lag.

Posted

Seem to be getting pulled back a few feet here and there. Everyone was experiencing it.

C:\Users\Owner>tracert 208.167.243.207

Tracing route to 208.167.243.207.choopa.net [208.167.243.207]

over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1

2 8 ms 7 ms 9 ms 10.240.184.117

3 12 ms 8 ms 7 ms dstswr2-ge3-4.rh.frptny.cv.net [67.59.224.225]

4 * * * Request timed out.

5 14 ms 12 ms 11 ms rtr4-tg11-2.wan.hcvlny.cv.net [64.15.4.25]

6 * * * Request timed out.

7 * * * Request timed out.

8 13 ms 11 ms 17 ms tge1-4-cr2.ewr2.choopa.net [66.55.128.134]

9 12 ms 11 ms 11 ms 208.167.243.207.choopa.net [208.167.243.207]

Trace complete.

Posted

I remember right after I came into BAR we got a new provider and what not. It ran smooth, no lag what so ever. If there was it was the own Player's Lag. Now it randomly got worse. The problem is, it lags every 5-10mins at least and people warp around. Even when there is low players in the server (2-5) it still gets the most random spikes ever that make people leave. Can we please try and do something about this? =|

Posted
The problem is, it lags every 5-10mins at least and people warp around. Even when there is low players in the server (2-5) it still gets the most random spikes ever that make people leave. Can we please try and do something about this? =|

Agreed. The most noticeable lag spikes happen when people join and leave the server.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Recently Browsing   0 members

    • No registered users viewing this page.

  • Recent Posts

    • Its Friday Night Fight Night in HLL and me and Muthas are in different squads. We meet up while attacking a point: Me: Muthas! Let's go get the poiple toineps! Muthas: Hah poi....   We are immediately cut down by a MG.   Steam messages:  Muthas: LMFAOO Me:OMFG! ROFLMAO!
    • Name: elon musk   Steam I.D: STEAM_0:0:918906720   Duration of Ban: Permanent   Reasons for the Ban: Racist comments and Mass Team Killing   Demo Provided?: N   Comments: Keebler reported in public chat, sent screen shot of typed comments  
    • Hey Reis! Great to see you again, man. The unit means a lot to all of us and I know you were here for quite some time. There’s always room for you to come back   *Salute*
    • I dont know how many of the people that know me or what i did in the unit are still here. But i just wanted to leave a huge thank you on the forums to this unit, that i was a part of for so many years, and all the good times and hardships i shared with a lot of different people from all over the world.    Maybe i'll still see you in DoD:s   *Salute*
    • 2nd Platoon Weekly Attendance   Week of 10NOV2024   P = Present | E = Excused | A = Absent   Platoon Staff WO. A. Pitteway - Excused MSgt. J. Candy - Present TSgt. A Yoder - Present   1st Squad Squad leader:  SSgt. R. Fielding - Present Cpl. B. Grande - Present Pfc. R. Smith - Excused Pfc. M. Noel - Present Pfc. C. Keebler - Present Pvt. D. Moffat - Present Pvt. R. Zera - Absent Pvt. N. Clement - Excused       2nd Squad Squad leader:  Cpl. S. Holquist - Present Pfc. A. Cannon - Excused Pfc. T. Scary - Present Pfc. C. Marsh - Present Pfc. M. Oake - Excused Pvt. L. Whistle - Present Pvt. M. Clarkson - Excused Pvt. W. Swift - Present           Helpers: WO. S. Belcher
×
×
  • Create New...