Upvote Upvoted 3 Downvote Downvoted
High ping to ESEA servers and some random servers
posted in Q/A Help
1
#1
0 Frags +

Hey, the title is pretty explanatory, but it's pretty frustrating.

Basically my ping is very bipolar to some servers. I live in central Indiana, so my ping to Chicago can be very good, but sometimes it can be insane. For instance I ping 9 to DM but the ping in my scrim server goes from 60 to 150 to 350 to 200 within a minute of each other. My ping to ESEA seems especially awful with a fairly regular skipping between 150-200 back and forth about every second.

As far as diagnostic steps I have taken I'm pretty limited. I'm on university ethernet and they think for some reason a tracert in command prompt can lead to DDoS attacks on their network. Idk. So here is a trace from their shitty website to my scrim server:

http://puu.sh/kcWPF/e458c5fa82.png

I'll be honest. I don't know what this means. I have talked to NFO (our scrim server is accelerate, but another server I have the same problem is NFO) and the network help at my school. Both say they need more information from the other, information I just can't seem to be given.

At this point my desperation has reached the point of trying a VPN. While it seemed to help a bit (still mild spiking during a small test time) it adds to my base ping which obviously isn't ideal.

Any advice is very much appreciated! Sorry for the long post, but I want to spend as little time answering questions.

Hey, the title is pretty explanatory, but it's pretty frustrating.

Basically my ping is very bipolar to some servers. I live in central Indiana, so my ping to Chicago can be very good, but sometimes it can be insane. For instance I ping 9 to DM but the ping in my scrim server goes from 60 to 150 to 350 to 200 within a minute of each other. My ping to ESEA seems especially awful with a fairly regular skipping between 150-200 back and forth about every second.

As far as diagnostic steps I have taken I'm pretty limited. I'm on university ethernet and they think for some reason a tracert in command prompt can lead to DDoS attacks on their network. Idk. So here is a trace from their shitty website to my scrim server:
[img]http://puu.sh/kcWPF/e458c5fa82.png[/img]

I'll be honest. I don't know what this means. I have talked to NFO (our scrim server is accelerate, but another server I have the same problem is NFO) and the network help at my school. Both say they need more information from the other, information I just can't seem to be given.

At this point my desperation has reached the point of trying a VPN. While it seemed to help a bit (still mild spiking during a small test time) it adds to my base ping which obviously isn't ideal.

Any advice is very much appreciated! Sorry for the long post, but I want to spend as little time answering questions.
2
#2
2 Frags +

that one single traceroute isn't much help; idk what ports are blocked, or to what extent ICMP is blocked.

are you plugged straight into their system, are you wireless, and/or is your computer connected to your own router? if the latter, how is the router interfacing with their system? what is the make/model of your router, if connected to your own? were you explicitly warned to not run a tracert, and/or did it just straight up not work?

if none of the packets were properly received (the "just straight up didn't work" option), then we need to start identifying ways to work around this so we can get better stats:

try "pathping google.com >C:\outputPathPing.txt" in cmd, and copy-paste the output.
if that doesn't work, try visualroute & let me know if it establishes any connection to any of the nodes.

make sure you answer my questions as well!!!
we can proceed from there.

that one single traceroute isn't much help; idk what ports are blocked, or to what extent ICMP is blocked.

are you plugged straight into their system, are you wireless, and/or is your computer connected to your own router? if the latter, how is the router interfacing with their system? what is the make/model of your router, if connected to your own? were you explicitly warned to not run a tracert, and/or did it just straight up not work?

if none of the packets were properly received (the "just straight up didn't work" option), then we need to start identifying ways to work around this so we can get better stats:

try "pathping google.com >C:\outputPathPing.txt" in cmd, and copy-paste the output.
if that doesn't work, try visualroute & let me know if it establishes any connection to any of the nodes.

make sure you answer my questions as well!!!
we can proceed from there.
3
#3
1 Frags +

I can't seem to check what ports are open/blocked. I am plugged into a network switch straight into their connection, but the problem persists w/o the switch. Tracert doesn't work AND on their webpage they say that it is blocked.

result: http://pastebin.com/ZtLene2D

UAC is enabled on my machine

Visualroute cannot connect to any nodes.

I can't seem to check what ports are open/blocked. I am plugged into a network switch straight into their connection, but the problem persists w/o the switch. Tracert doesn't work AND on their webpage they say that it is blocked.

result: http://pastebin.com/ZtLene2D

UAC is enabled on my machine

Visualroute cannot connect to any nodes.
4
#4
0 Frags +

edit: OK, looks like they have strict ICMP rules. if you interface on a VPN and try either pathping or visualroute, what happens?

does this affect all ESEA servers, or just ones in the chicago area?

more often than not, this is just a peering issue between ISP's. even though it was one traceroute, the first hop out of your university's network is leaning towards that sentiment. how prevalent is this issue outside of chicago servers?

edit: OK, looks like they have strict ICMP rules. if you interface on a VPN and try either pathping or visualroute, what happens?

does this affect all ESEA servers, or just ones in the chicago area?

more often than not, this is just a peering issue between ISP's. even though it was one traceroute, the first hop out of your university's network is leaning towards that sentiment. how prevalent is this issue outside of chicago servers?
5
#5
1 Frags +

It's all servers. Tonight it seems to be better, but not great. PM'd my pathping on a vpn to you.

It's all servers. Tonight it seems to be better, but not great. PM'd my pathping on a vpn to you.
6
#6
Momentum Mod
-1 Frags +

how recent was this? ive been getting constant 130 to esea chicago since last week

how recent was this? ive been getting constant 130 to esea chicago since last week
Please sign in through STEAM to post a comment.