Connection issues please help

[47RSnowman]

Hi.. I am a regular player/admin on the 47 Ronin server.. (IP is 66.151.135.51)
I have AT&T DSL service in Missouri.. (iknow.. way out herre)
but alas.. I'm having issues.. please help...
Here is My tracert...


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

C:\Users\X>tracert 66.151.135.51

Tracing route to 66.151.135.51 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.0.1
2 1 ms 1 ms 1 ms 192.168.1.254
3 46 ms 45 ms 47 ms bras1-l0.ksc2mo.sbcglobal.net [151.164.182.68]
4 44 ms 43 ms 44 ms dist1-vlan60.ksc2mo.sbcglobal.net [151.164.29.13
0]
5 44 ms 44 ms 44 ms 151.164.103.121
6 77 ms 77 ms 113 ms ppp-151-164-55-186.eulstx.swbell.net [151.164.55
.186]
7 77 ms 77 ms 78 ms as2914-ntt.eqchil.sbcglobal.net [151.164.251.114
]
8 79 ms 78 ms 79 ms ae-2.r21.chcgil09.us.bb.gin.ntt.net [129.250.3.1
]
9 135 ms 119 ms 115 ms ae-5.r20.snjsca04.us.bb.gin.ntt.net [129.250.3.1
07]
10 119 ms 119 ms 114 ms ae-1.r06.snjsca04.us.bb.gin.ntt.net [129.250.5.1
3]
11 113 ms 118 ms 113 ms xe-0-0-0-4.r06.snjsca04.us.ce.gin.ntt.net [128.2
41.219.130]
12 113 ms 134 ms 119 ms border1.t8-1-bbnet2.sje.pnap.net [66.151.144.68]

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.

Again.. Any Help would be greatly appreciated..

[kraze]

Hi do you currently rent a server from us?

I am going to be honest with you. AT&T DSL is not to good. I was with them for a long time and it was horrible and not to ideal for gaming. I experienced the same issues you were. I live in California and was pinging 150ms to Chicago on a good day.


I am not to experienced with trace routes and it seems that you are only seeing high pings at the 9th and back. From first look I do not see anything wrong with the trace route at all. That actually looks about right for the internet you have. If you take in account the distance along with the fact that you are running DSL of course. Like I said I was with AT&T DSL service for years and you are pinging a little better then what I would to Chicago. Personally from being with the company and seeing what my ping was and so on I don't think their is to much of a problem. However why don't you go to:

speedtest.net

Take several speed test from as close as you can then take several in other states such as locations of where you game. Post the results here and see what you get. One last thing. Use the site I post below and run some test to Ip's of game servers or domains such as nfoservers.com. Their is no way to let us see these results easily but you will be able to see where the problem lies. It should tell you that hop 9 is acting weird and so on.

http://tinyurl.com/46swd7u

If their is truly a problem and you are a customer of NFO or a friends buddy who rents from us we may be able to do some re routing.

Best of luck

[Edge100x]

Is the issue that you're seeing in-game that of higher than expected latencies, or is it something else?

Do you have lower pings at other San Jose servers?

It looks like you have a 40ms delay on your first hop, which is unusual, but the rest of the trace looks fairly normal for the distance. It could be that your DSL provider has you in a mode that has a high interleave interval, and you might be able to get them to adjust this for you if you give them a call (whether they can depends on the type of equipment they use and your line quality/distance from the DSLAM).

[47RSnowman]

Thank you again for your Help and Assistance..

I had AT&T respond to my request this morning and as suggested I asked to have my DSL connection taken out of "Interleave" Mode and Put back into "FastPath" mode.. and as a result ..... Current Tracert from me to dslam.. look at first hop now

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

C:\Users\X>tracert 66.151.138.51

Tracing route to c-66-151-138-51.internap-sj.nfoservers.com [66.151.138.51]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 1 ms 1 ms <1 ms 192.168.1.254
3 12 ms 11 ms 11 ms bras1-l0.ksc2mo.sbcglobal.net [151.164.182.68]
4 10 ms 10 ms 9 ms dist1-vlan60.ksc2mo.sbcglobal.net [151.164.29.13
0]
5 9 ms 10 ms 9 ms 151.164.103.121
6 45 ms 45 ms 44 ms ppp-151-164-55-186.eulstx.swbell.net [151.164.55
.186]
7 45 ms 45 ms 45 ms xe-7-1.r01.chcgil09.us.bb.gin.ntt.net [129.250.8
.53]
8 45 ms 45 ms 45 ms ae-2.r21.chcgil09.us.bb.gin.ntt.net [129.250.3.1
]
9 81 ms 88 ms 76 ms ae-5.r20.snjsca04.us.bb.gin.ntt.net [129.250.3.1
07]
10 75 ms 77 ms 77 ms ae-1.r06.snjsca04.us.bb.gin.ntt.net [129.250.5.1
3]
11 81 ms 77 ms 81 ms xe-0-0-0-4.r06.snjsca04.us.ce.gin.ntt.net [128.2
41.219.130]
12 76 ms 82 ms 77 ms border1.t3-1-bbnet1.sje003.pnap.net [66.151.144.
27]
13 75 ms 81 ms 75 ms c-66-151-138-51.internap-sj.nfoservers.com [66.1
51.138.51]

Trace complete.

I will be checking how this connection now "feels" later today.. but having a 30-50 ms DROP was very promising.

Wish me Luck
and Thnx Again!

[Edge100x]

Great! I'm glad you got someone on the phone who understood what I meant .

[kraze]

Looks better! Glad you were able to get it working.