AH2 is Beautiful...but cannot connect to Online Arenas

[Someone]

Hello Group,

Very strange thing.
I've forwarded ports 2000-6000 (tcp and udp) through my router.
I can play many other online games.
I have a very fast cable connection at my home.
AH2 runs smoothly on my machine.
I can ping the AH2 server addresses stated in another thread in these forums.

I simply can't figure out why I can't connect.
I enter my account ID and password given by hitechcreations and connection fails after 30 seconds.
I get an offer to try an alternative route but that fails too.

Any ideas on what I could try to troubleshoot this?
I'm stuck.

Thanks for your time and patience.

[Tigger29]

Just to check the obvious.. have you downloaded the latest version of the game from hitech's website (not from a 3rd party site?)

It seems to me that not too long ago they switched servers... if you're running an older version of the game, it maybe be trying to connect to the old servers.

Also, if you have Vista, make sure you install the game in a folder that IS NOT in "program files".  Example:  C:\Aces High..... *NOT*  C:\Program Files\Aces High

[Someone]

Just to check the obvious.. have you downloaded the latest version of the game from hitech's website (not from a 3rd party site?)

It seems to me that not too long ago they switched servers... if you're running an older version of the game, it maybe be trying to connect to the old servers.

Also, if you have Vista, make sure you install the game in a folder that IS NOT in "program files".  Example:  C:\Aces High..... *NOT*  C:\Program Files\Aces High

Thanks for the quick reply Mr. Tigger.
I'm using AH2 ver. 2.13 Patch 1 downloaded directly from hitechcreations website.
My OS is Win XP Pro w/SP2

[Kermit de frog]

Windows firewall may be enabled. If so, it may also not be allowing the internet to talk with Aces High.  Try going to your control panel, select firewall and IF it's enabled, allow AH to access the internet.

[Someone]

Windows firewall may be enabled. If so, it may also not be allowing the internet to talk with Aces High.  Try going to your control panel, select firewall and IF it's enabled, allow AH to access the internet.

Hmm, Win firewall is in fact on, but Aces High was already "checked" as an exception allowed through the firewall.
This is turning out to be very tricky, indeed.

Thank you for the thoughtful response.

[Denholm]

Do you have any other security software running? Anti-Virus (AVG, Avast, Norton, NOD, etc...), Anti-Spyware (Spybot (TeaTimer), Ad-Aware, Threatfire, Spyware doctor, etc...), or any other security software actively running in the background? If so, try disabling it for the time you're attempting to run Aces High.

If that doesn't do it, there is a possibility that you have a router connected to a router. For example, your Cable Modem is actually a router in itself, yet you have another router attached to the cable modem. So you have to configure two firewalls, not just one.

[Someone]

Do you have any other security software running? Anti-Virus (AVG, Avast, Norton, NOD, etc...), Anti-Spyware (Spybot (TeaTimer), Ad-Aware, Threatfire, Spyware doctor, etc...), or any other security software actively running in the background? If so, try disabling it for the time you're attempting to run Aces High.

If that doesn't do it, there is a possibility that you have a router connected to a router. For example, your Cable Modem is actually a router in itself, yet you have another router attached to the cable modem. So you have to configure two firewalls, not just one.

No anti-virus or anti-spyware software, nope.
Cable Modem is just a dumb off-the-shelf Motorola -- my ip address changes once every 3 or so months.
I can host simracing games and combat games.

Yeesh, I'm getting that sinking feeling......but it's got to be something simple.
Thanks for taking the time to help; it's greatly appreciated.

[fuzeman]

You can try and call HTC in the morning and see if Skuzzy can get you figured out. Might be the quickest and least painful method.

[Someone]

You can try and call HTC in the morning and see if Skuzzy can get you figured out. Might be the quickest and least painful method.

Sounds like a good idea.
I'll check the tech. support hours and go from there.

[Denholm]

Wow, that is odd. Could you run a ping-plot to one of the HTC servers (preferably the MA servers) just so we see what's happening on the way to the servers? It almost sounds as if your ISP is involved in this, although I can't say for certain.

[Skuzzy]

A Ping plot would be the next logical choice as you are on Comcast.  Many Comcast users have experienced a ton of problems due to a bad routing condition within Savvis (Comcast's ISP).  All the ISP's involved (AT&T, Comcast, Savvis) all acknowledge there is a problem, but none of them will step up to correct it.

Hopefully, after June 1, 2009, things will change.

For right now though, a Ping Plot would be very helpful.

[Dragon]

Hopefully, after June 1, 2009, things will change.

Hah, now we know when the update will be released. Thanks for slipping that info Skuzzy. 

[Denholm]

Skuzzy was referencing the end of the world.

[Someone]

A Ping plot would be the next logical choice as you are on Comcast.  Many Comcast users have experienced a ton of problems due to a bad routing condition within Savvis (Comcast's ISP).  All the ISP's involved (AT&T, Comcast, Savvis) all acknowledge there is a problem, but none of them will step up to correct it.

Hopefully, after June 1, 2009, things will change.

For right now though, a Ping Plot would be very helpful.

Yikes, sounds absolutely evil.  :-(
I couldn't find time to call today.....darn long day at work.
Me googling "ping plot how to" right now....
Thanks for hanging in with me.

[Someone]

Ping Plot below:
- - - - - - - - - -

Target Name: N/A
         IP: 206.16.60.39
  Date/Time: 5/19/2009 8:27:49 PM

 1    0 ms    0 ms    0 ms    0 ms  [199.201.13.200]
 2    7 ms    6 ms    7 ms   11 ms  [96.67.88.1]
 3    9 ms    6 ms    7 ms    6 ms  [68.85.187.181]
 4    9 ms    9 ms    9 ms   10 ms  be-52-ar99.chartford.ct.hartford.comcast.net [68.85.162.194]
 5   14 ms   11 ms   12 ms   11 ms  pos-2-5-0-0-cr01.newyork.ny.ibone.comcast.net [68.86.90.65]
 6   15 ms   13 ms   13 ms   13 ms  pos-0-1-0-0-pe01.111eighthave.ny.ibone.comcast.net [68.86.86.46]
 7   21 ms   18 ms   12 ms   10 ms  er2-tengig3-3.newyork.savvis.net [208.173.138.13]
 8   41 ms   37 ms  230 ms   37 ms  [192.205.35.9]
 9   89 ms   87 ms   88 ms   88 ms  cr2.n54ny.ip.att.net [12.122.130.98]
10   90 ms   88 ms   87 ms   90 ms  cr2.wswdc.ip.att.net [12.122.3.38]
11   88 ms   87 ms   88 ms   87 ms  cr1.attga.ip.att.net [12.122.1.173]
12   92 ms   88 ms   89 ms   89 ms  cr2.dlstx.ip.att.net [12.122.28.174]
13   90 ms  119 ms   88 ms  145 ms  gar23.dlstx.ip.att.net [12.122.138.161]
14   89 ms   88 ms   92 ms   89 ms  12-122-254-154.attens.net [12.122.254.154]
15   92 ms   87 ms   88 ms   88 ms  mdf1-bi8k-2-eth-1-2.dal1.attens.net [63.241.192.210]
16   91 ms   88 ms   91 ms   89 ms  [206.16.60.39]

Ping statistics for 206.16.60.39
Packets: Sent = 4, Received = 4, Lost = 0 (0.0%)
Round Trip Times: Minimum = 88ms, Maximum = 91ms, Average = 89ms