Curse

Cubanito · Apr 23, 2011, 03:16 PM // 15:16

I ran pathping -w 500 -q 3 -4 64.25.39.46 , upon logging in today to see what the problem is involving my high ping. If you guys need anymore info let me know, Just for clarity's sake i would like to find out what i can do tofix this issue before the weekend ends ^^

C:\Users\Santiago>pathping -w 500 -q 3 -4 64.25.39.46

Tracing route to 64.25.39.46 over a maximum of 30 hops

0 Santiago-PC [xxx.xxx.x.x]
1 xxx.xxx.x.x
2 xx.xxx.xxx.x
3 172.24.82.254
4 172.24.0.246
5 * border2.lacp-11.direcpathinc-12-13.acs002.pnap.net [216.52.194.221
]
6 core1.te2-2-bbnet2.acs002.pnap.net [64.94.0.79]
7 12.86.102.5
8 cr83.attga.ip.att.net [12.122.141.2]
9 cr1.attga.ip.att.net [12.123.22.109]
10 cr2.dlstx.ip.att.net [12.122.28.174]
11 cr81.ftwtx.ip.att.net [12.122.100.69]
12 * gar2.dlrtx.ip.att.net [12.122.100.29]
13 12.249.201.12
14 64.25.32.26
15 64.25.32.62
16 * * *
Computing statistics for 11 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Santiago-PC [xxx.xxx.x.x]
0/ 3 = 0% |
1 1ms 0/ 3 = 0% 0/ 3 = 0% xxx.xxx.x.x
0/ 3 = 0% |
2 49ms 0/ 3 = 0% 0/ 3 = 0% xx.xxx.xxx.x
0/ 3 = 0% |
3 39ms 0/ 3 = 0% 0/ 3 = 0% 172.24.82.254
0/ 3 = 0% |
4 51ms 0/ 3 = 0% 0/ 3 = 0% 172.24.0.246
0/ 3 = 0% |
5 50ms 0/ 3 = 0% 0/ 3 = 0% border2.lacp-11.direcpathinc-12-13
.acs002.pnap.net [216.52.194.221]
0/ 3 = 0% |
6 41ms 0/ 3 = 0% 0/ 3 = 0% core1.te2-2-bbnet2.acs002.pnap.net
[64.94.0.79]
1/ 3 = 33% |
7 43ms 1/ 3 = 33% 0/ 3 = 0% 12.86.102.5
2/ 3 = 66% |
8 --- 3/ 3 =100% 0/ 3 = 0% cr83.attga.ip.att.net [12.122.141.
2]
0/ 3 = 0% |
9 --- 3/ 3 =100% 0/ 3 = 0% cr1.attga.ip.att.net [12.123.22.10
9]
0/ 3 = 0% |
10 --- 3/ 3 =100% 0/ 3 = 0% cr2.dlstx.ip.att.net [12.122.28.17
4]
0/ 3 = 0% |
11 --- 3/ 3 =100% 0/ 3 = 0% cr81.ftwtx.ip.att.net [12.122.100.
69]
0/ 3 = 0% |
12 --- 3/ 3 =100% 0/ 3 = 0% gar2.dlrtx.ip.att.net [12.122.100.
29]
0/ 3 = 0% |
13 --- 3/ 3 =100% 0/ 3 = 0% 12.249.201.12
0/ 3 = 0% |
14 --- 3/ 3 =100% 0/ 3 = 0% 64.25.32.26
0/ 3 = 0% |
15 --- 3/ 3 =100% 0/ 3 = 0% 64.25.32.62

Trace complete.

Chthon · Apr 23, 2011, 04:12 PM // 16:12

1. You should delete the IP addresses on items 0, 1, & 2.

2. Looks like things are blowing up at AT&T.

Cubanito · Apr 23, 2011, 04:46 PM // 16:46

Thanks for the advice on hiding addresses, and so all i can do is wait it out?

Chthon · Apr 23, 2011, 10:31 PM // 22:31

Quote:

Originally Posted by Cubanito

Thanks for the advice on hiding addresses, and so all i can do is wait it out?

Unless you've got some kind of relationship w/ AT&T so that they'll take your phone calls seriously, yep, gonna have to wait it out.

Like most connectivity problems, it's not you, and it's not a-net, but rather some intermediate provider.

Draca · Apr 24, 2011, 06:59 AM // 06:59

Seems all our problems is connected with AT&T

Quaker · Apr 24, 2011, 03:24 PM // 15:24

Quote:

Originally Posted by Chthon

Like most connectivity problems, it's not you, and it's not a-net, but rather some intermediate provider.

This can not be stressed enough. It's amazing how many people say things like "The connection is fine on my end, it must be ANet's fault." or "My other online games work, it must be ANet's fault."
Different routes, different *frig* ups.

Tarun · Apr 24, 2011, 07:20 PM // 19:20

Quote:

Originally Posted by Chthon

1. You should delete the IP addresses on items 0, 1, & 2.

For what reason should they have been deleted? They're internal IP addresses. You should read more about it.

0 192.168.1.x
1 192.168.1.1
2 10.186.169.1

Oh no, 192.168 private internal IP addresses, and 10.x.x.x is generally a business LAN/Internal IP.

http://en.wikipedia.org/wiki/Private...address_spaces

Chthon · Apr 24, 2011, 08:27 PM // 20:27

Quote:

Originally Posted by Tarun

For what reason should they have been deleted? They're internal IP addresses. You should read more about it.

0 192.168.1.x
1 192.168.1.1
2 10.186.169.1

Oh no, 192.168 private internal IP addresses, and 10.x.x.x is generally a business LAN/Internal IP.

http://en.wikipedia.org/wiki/Private...address_spaces

You're right, I should have told him to block out 0-3 instead.

I'm sure you know that the rationale is to prevent unsavory types from picking up your IP from the forums and using it for a targeted attack.

Internal or external, those addresses help a potential attacker pinpoint OP's machine. An attacker who doesn't know where OP is on the local network has one extra step to complete.

But, more fundamentally than that, it's a matter of first principles: Don't publish any more potentially personally identifiable about yourself than strictly necessary to tell the reader what they need to know. Ever. We don't need to know the layout of OP's internal network to read a pathping. It is of no benefit to OP to publish that info. So the risk associated with it, no matter how small or how nebulous, is unjustified.

Crispie · Apr 24, 2011, 08:40 PM // 20:40

Quote:

Originally Posted by Quaker

This can not be stressed enough. It's amazing how many people say things like "The connection is fine on my end, it must be ANet's fault." or "My other online games work, it must be ANet's fault."
Different routes, different *frig* ups.

I can't help but think, isn't it NCSoft's responsibility to do whatever it takes to resolve this, including relocating some of their servers? I know if this happened to Google or one of Blizzard's games, they would have it fixed, regardless.

Tarun · Apr 25, 2011, 05:16 AM // 05:16

Quote:

Originally Posted by Chthon

You're right, I should have told him to block out 0-3 instead.

I'm sure you know that the rationale is to prevent unsavory types from picking up your IP from the forums and using it for a targeted attack.

Internal or external, those addresses help a potential attacker pinpoint OP's machine. An attacker who doesn't know where OP is on the local network has one extra step to complete.

But, more fundamentally than that, it's a matter of first principles: Don't publish any more potentially personally identifiable about yourself than strictly necessary to tell the reader what they need to know. Ever. We don't need to know the layout of OP's internal network to read a pathping. It is of no benefit to OP to publish that info. So the risk associated with it, no matter how small or how nebulous, is unjustified.

I've left you with the information you need to educate yourself. I would highly recommend it before you continue to spout this absurd paranoia.

Chthon's post, ladies and gentlemen; is why you should only follow and listen to the sound advice of a trusted technician. You can safely identify those technicians by their user title found under there names here on the forums.

dagrdagaz · Apr 25, 2011, 09:55 AM // 09:55

Really, and why should we believe u r a trustworthy technician?!
Becos u say so yourself ?! huhuh....sure

I agree with Chthon's comment to only post personal info if absolutely needed, nothing more.

Quaker · Apr 25, 2011, 02:05 PM // 14:05

Quote:

Originally Posted by Crispie

I can't help but think, isn't it NCSoft's responsibility to do whatever it takes to resolve this, including relocating some of their servers? I know if this happened to Google or one of Blizzard's games, they would have it fixed, regardless.

Under what sort of conditions do you think that ANet would "fix" AT&T's servers?

And, if you had that sort of problem with Google, you would just think that Google was a little slow that day - you wouldn't notice a 1000ms ping so much.

Cubanito · Apr 25, 2011, 05:47 PM // 17:47

Lets not turn this into a hate/fight thread now....
I Thank you all who helped me understand this....
Mods please close before the bickering continues

Tarun · Apr 25, 2011, 06:43 PM // 18:43

Quote:

Originally Posted by dagrdagaz

Really, and why should we believe u r a trustworthy technician?!
Becos u say so yourself ?! huhuh....sure

I agree with Chthon's comment to only post personal info if absolutely needed, nothing more.

See the title under my name? Technician's Corner Moderator? At one time my user title read Technician which is assigned by the administrative team here. One of the reasons I was appointed my position here is because I know my stuff. If you require further proof, however; I'll give you a few links upon request.

Quote:

Originally Posted by Cubanito

Lets not turn this into a hate/fight thread now....
I Thank you all who helped me understand this....
Mods please close before the bickering continues

Sure.

Another option you can also explore is contacting ArenaNet and let them know who your ISP is. From there they may be able to resolve the issue or let you know if it's a known issue.

Closed per request