| Can't play Black Ops II.. All others play fine.. For some odd reason, I can't play Call of Duty Black OPS II. My pings are too high and keep getting kicked from servers because of it. In Counter-Strike and other games, my pings are 20ms-60ms.. Any reason why I am only having an issue with Black Ops 2? |
|
Xander
join:2012-04-12
London, KY Reviews:
 ·Windstream
| What platform? I assume pc.
I have been kicked from Xbox 360 servers several times this week.I can always tell when its getting ready to happen,because i become pretty much untouchable then with in 1 min i get (Call of duty servers are unavailable).Most of the time i have to restart my xbox.
Do you have your ports forward or UPnP enabled? |
|
|
|
| yeah its PC, I have forwarded ports and everything..
However, I have done some investigating..
Using WireShark, I was able to get the IP of the server that the games are hosted on. 108.61.89.110 I did a tracert, and it seems somewhere between here and there, a hop times out.. my friend with Charter, does not have this issue.. Two other friends that have Windstream, both have the same high pings I do in blackops and the same time out in hop 6. It has to be something in Windstream routing.. If I VPN into Atlanta, my pings are lower and the game is playable.. »www.choopa.com/ is the company that host Black Ops II servers. |
|
| I used a website the other day to diagnose some problems I was having with League of Legends and it showed quite a bit of problems with Windstream routing.
"Your ISP's DNS server returns IP addresses even for domain names which should not resolve. Instead of an error, the DNS server returns an address of 66.152.109.60, which resolves to 66-152-109-60.tvc-ip.com. You can inspect the resulting HTML content here.
There are several possible explanations for this behavior. The most likely cause is that the ISP is attempting to profit from customer's typos by presenting advertisements in response to bad requests, but it could also be due to an error or misconfiguration in the DNS server.
The big problem with this behavior is that it can potentially break any network application which relies on DNS properly returning an error when a name does not exist.
The following lists your DNS server's behavior in more detail.
www.{random}.com is mapped to 66.152.109.60.
www.{random}.org is mapped to 66.152.109.60.
fubar.{random}.com is mapped to 66.152.109.60.
www.yahoo.cmo [sic] is mapped to 66.152.109.60.
nxdomain.{random}.netalyzr.icsi.berkeley.edu is mapped to 66.152.109.60."
Was the one that caused me most concern. |
|
