Aces High Bulletin Board
Help and Support Forums => Technical Support => Topic started by: Someone on May 18, 2009, 07:22:33 PM
-
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.
-
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
-
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
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
Hopefully, after June 1, 2009, things will change.
Hah, now we know when the update will be released. Thanks for slipping that info Skuzzy. :pray
-
Skuzzy was referencing the end of the world.
-
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.
-
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
-
How long did you run the Ping Plot? For best results, let it run for about 10 minutes.
It looks like hop 8 could be causing an issue. However, no packet loss in this trace suggests there are no troubles between your connection and the server.
Is there a possibility that your ISP has its own firewall which is blocking the game's servers from communicating with your computer? Calling them and asking might be worth a shot.
-
How long did you run the Ping Plot? For best results, let it run for about 10 minutes.
Ahh, I see. I just let it grab a couple of samples and then shut it down.
I'll re-do sample right now.
-
The reverse or route back to you is what will be messed up more than anything as that is where Savvis's lousy routing problem shows up. I'll get the reverse done when I get to the office this morning.
-
62 trace samples spaced 10 secs. apart:
--------------------------------------
Host Information
1, -------------- ,199.201.13.200
2, -------------- ,96.67.88.1
3, -------------- ,68.85.187.181
4,be-52-ar99.chartford.ct.hartford.comcast.net,68.85.162.194
5,pos-2-5-0-0-cr01.newyork.ny.ibone.comcast.net,68.86.90.65
6,pos-0-1-0-0-pe01.111eighthave.ny.ibone.comcast.net,68.86.86.46
7,er2-tengig3-3.newyork.savvis.net,208.173.138.13
8, -------------- ,192.205.35.9
9,cr2.n54ny.ip.att.net,12.122.130.98
10,cr2.wswdc.ip.att.net,12.122.3.38
11,cr1.attga.ip.att.net,12.122.1.173
12,cr2.dlstx.ip.att.net,12.122.28.174
13,gar23.dlstx.ip.att.net,12.122.138.161
14,12-122-254-154.attens.net,12.122.254.154
15,mdf1-bi8k-2-eth-1-2.dal1.attens.net,63.241.192.210
16, -------------- ,206.16.60.39
-
The reverse or route back to you is what will be messed up more than anything as that is where Savvis's lousy routing problem shows up. I'll get the reverse done when I get to the office this morning.
Wow, a little googling reveals a long and rich history of Savvis weirdness and routing problems with many games, organizations, and communications networks throughout the last 5 years.
Please let me know if there is anything I can do to assist.
I'm running to work now, but will try to call Comcast tonight from home.
Maybe I can get it worked out with my ISP before you spend any more time on the issue?
I don't want to make extra work for anyone, and don't want to be a pest.
-
I try not to assume what the problem is. I am happy to run the reverse trace.
Hopefully all of this will cease being a problem after June 1.
-
...I'm running to work now, but will try to call Comcast tonight from home.
Maybe I can get it worked out with my ISP before you spend any more time on the issue?...
If you did, that would be a miracle!
-
If you did, that would be a miracle!
Haha, you are a man of wisdom!
I called my ISP and I was surprised that they wanted to review the result of my ping trace with me; I felt encouraged.
The tech. went through it step by step until it left the comcast network, and then the tech. said "Geeee, it looks like the problem is outside the comcast network."
It almost had that Office Space quality to it.
Oh well, I thanked them for their time, and I wasted no more of mine.
So I'm back in the support forum looking for pity...err, help i mean. <grin>
-
I apologize. I got side-tracked from getting the trace done. I will get at it first thing in the morning. Yes, the problem is outside of Comcast's network. The problem is in the network (Savvis) of the ISP Comcast has a contract with for service.
-
SAAVIS is the scourge of the Earth!
-
As I suspected. The routing issue within Savvis is the most likely culprit of the problem. Data being routed from Dallas to Los Angeles for 3 hops, then back to Dallas, before heading off to Atlanta, Chicago, Cleveland, then 4 hops in Comcast's network in Massachusetts, and finally to CT.
Insane.
traceroute 71.192.166.249
traceroute to 71.192.166.249 (71.192.166.249), 30 hops max, 40 byte packets
1 206.16.60.33 (206.16.60.33) 0.936 ms 0.425 ms 0.362 ms
2 mdf1-gsr12-1-gig-1-1.dal1.attens.net (63.241.192.201) 0.415 ms 0.307 ms 0.255 ms
3 12-122-254-29.attens.net (12.122.254.29) 24.861 ms 1.269 ms 5.818 ms
4 cr2.dlstx.ip.att.net (12.122.138.186) 1.330 ms 3.809 ms 1.449 ms
5 ggr3.dlstx.ip.att.net (12.122.138.17) 1.167 ms 1.137 ms 1.121 ms
6 cr2-pos-0-3-3-3.dallas.savvis.net (208.172.139.225) 1.659 ms 1.564 ms 1.414 ms
7 cr1-pos-0-0-3-0.losangeles.savvis.net (204.70.192.249) 33.751 ms 33.869 ms 33.748 ms
8 er2-tengig-2-1.lay.savvis.net (204.70.198.6) 33.563 ms 33.687 ms 33.659 ms
9 comcast-net.lay.savvis.net (208.173.55.218) 34.665 ms 34.427 ms 34.713 ms
10 pos-0-14-0-0-cr01.dallas.tx.ibone.comcast.net (68.86.85.142) 69.143 ms 69.247 ms 69.704 ms
11 pos-0-12-0-0-cr01.atlanta.ga.ibone.comcast.net (68.86.85.158) 69.569 ms 69.708 ms 69.426 ms
12 pos-1-7-0-0-cr01.chicago.il.ibone.comcast.net (68.86.85.165) 69.727 ms 69.821 ms 69.685 ms
13 pos-0-6-0-0-cr01.cleveland.oh.ibone.comcast.net (68.86.85.53) 79.141 ms 79.140 ms 79.277 ms
14 pos-0-14-0-0-crs01.woburn.ma.boston.comcast.net (68.86.90.6) 97.446 ms 97.682 ms 97.421 ms
15 po-16-ar01.berlin.ct.hartford.comcast.net (68.87.146.50) 97.299 ms 97.220 ms 97.233 ms
16 be-10-ar99.chartford.ct.hartford.comcast.net (68.87.146.29) 97.456 ms 97.544 ms 97.481 ms
17 po-52-ur01.newhaven.ct.hartford.comcast.net (68.85.162.193) 98.938 ms 98.923 ms 98.905 ms
18 68.85.187.182 (68.85.187.182) 98.959 ms 99.077 ms 99.087 ms
19 c-71-192-166-249.hsd1.ct.comcast.net (71.192.166.249) 114.178 ms 105.472 ms 105.980 ms
-
As I suspected. The routing issue within Savvis is the most likely culprit of the problem. Data being routed from Dallas to Los Angeles for 3 hops, then back to Dallas, before heading off to Atlanta, Chicago, Cleveland, then 4 hops in Comcast's network in Massachusetts, and finally to CT.
Insane.
Ouch, it sounds like this is completely outside of my control and/or hitechcreations' control.
Has anyone ever found a workaround for such a thing?
-
We are going to be trying something in conjunction with AT&T on June 1. Hopefully it will solve the problem. We will not know until it is done.
-
Ouch, it sounds like this is completely outside of my control and/or hitechcreations' control.
Has anyone ever found a workaround for such a thing?
I'm not sure where you are in CT, but I'm just over the border in MA about 5 minutes east of the I84. I use Charter to connect and have a solid connection to HTC. Boston (3 hops), NY (5 hops), Washington DC (1 hop), Atlanta (1 hop), then to Dallas (5 hops), then HTC. Average ping for 10 minutes, 53ms
Switching to Charter "might" be an option.
-
We are going to be trying something in conjunction with AT&T on June 1. Hopefully it will solve the problem.
Very cool. Please let me know if there is anything I can do to help test. I'd be glad to assist in any way.
-
Switching to Charter "might" be an option.
It's a good thought, so I checked, and unfortunately Charter Cable is not an option in my area -- Comcast only.