Aces High Bulletin Board

Help and Support Forums => Technical Support => Topic started by: TequilaChaser on March 22, 2008, 01:34:59 PM

Title: Major Disco problems since new version - help!
Post by: TequilaChaser on March 22, 2008, 01:34:59 PM
Any Help would be appreciated, nothing but dumps/ host connection lost since new version came out: below is  ping plotter results for all server addresses......

Target Name: Aces High II Special Events Arena Server Address:
         IP: 206.16.60.38
  Date/Time: 3/22/2008 2:26:08 PM

 1    0 ms    0 ms    0 ms    0 ms    0 ms  [192.168.0.1]
 2    5 ms    7 ms    6 ms    6 ms    7 ms  [73.20.152.1]
 3    8 ms    6 ms    7 ms    7 ms    7 ms  ge-3-37-ur01.edgewood.fl.jacksvil.comcast.net [68.86.170.165]
 4    8 ms    7 ms    8 ms    6 ms    8 ms  te-9-3-ar01.westside.fl.jacksvil.comcast.net [68.86.168.81]
 5    8 ms    9 ms   10 ms   10 ms    9 ms  [12.116.33.25]
 6   44 ms   44 ms   44 ms   44 ms   44 ms  tbr1.ormfl.ip.att.net [12.123.33.26]
 7   42 ms   44 ms   52 ms   43 ms   45 ms  cr1.ormfl.ip.att.net [12.122.21.9]
 8   46 ms   43 ms   45 ms   44 ms   43 ms  cr1.hs1tx.ip.att.net [12.122.31.241]
 9   44 ms   44 ms   42 ms   45 ms   44 ms  cr2.dlstx.ip.att.net [12.122.5.233]
10   43 ms   45 ms   45 ms   45 ms   45 ms  tbr2.dlstx.ip.att.net [12.122.18.214]
11   44 ms   43 ms   44 ms   43 ms   43 ms  br2.dlstx.ip.att.net [12.123.16.213]
12   45 ms   45 ms   53 ms   42 ms   44 ms  mdf1-gsr12-1-pos-7-0.dal1.attens.net [12.122.255.82]
13   43 ms   43 ms   50 ms   44 ms   *      mdf1-bi8k-2-eth-2-2.dal1.attens.net [63.241.192.218]
14   44 ms   43 ms   44 ms   46 ms   43 ms  [206.16.60.38]


Target Name: Aces High II Early, Mid, Late War Orange Main Arena's Server Address:
         IP: 206.16.60.39
  Date/Time: 3/22/2008 2:30:24 PM

 1    0 ms    0 ms    0 ms    0 ms    0 ms  [192.168.0.1]
 2    9 ms   10 ms    6 ms    6 ms    7 ms  [73.20.152.1]
 3    6 ms    6 ms    9 ms    7 ms    8 ms  ge-3-37-ur01.edgewood.fl.jacksvil.comcast.net [68.86.170.165]
 4    7 ms    7 ms    6 ms    7 ms    7 ms  te-9-3-ar01.westside.fl.jacksvil.comcast.net [68.86.168.81]
 5    9 ms    9 ms   10 ms   14 ms    9 ms  [12.116.33.25]
 6   44 ms   45 ms   61 ms   47 ms   44 ms  tbr1.ormfl.ip.att.net [12.123.33.26]
 7   44 ms   43 ms   44 ms   45 ms   45 ms  cr1.ormfl.ip.att.net [12.122.21.33]
 8   45 ms   43 ms   53 ms   44 ms   44 ms  cr1.hs1tx.ip.att.net [12.122.31.241]
 9   46 ms   46 ms   46 ms   43 ms   44 ms  cr2.dlstx.ip.att.net [12.122.5.233]
10   50 ms   44 ms   59 ms   46 ms   43 ms  tbr2.dlstx.ip.att.net [12.122.18.230]
11   43 ms   43 ms   48 ms   44 ms   43 ms  br2.dlstx.ip.att.net [12.123.16.213]
12   47 ms   44 ms   43 ms   44 ms   44 ms  mdf1-gsr12-1-pos-7-0.dal1.attens.net [12.122.255.82]
13   45 ms   44 ms   *       45 ms   44 ms  mdf1-bi8k-1-eth-1-4.dal1.attens.net [63.241.192.42]
14   43 ms   43 ms   44 ms   44 ms   44 ms  [206.16.60.39]



Target Name: Aces High II Axis vs Allies, Training, Dueling, Late War Blue Arena's Server Address:
         IP: 206.16.60.41
  Date/Time: 3/22/2008 2:33:09 PM

 1    0 ms    0 ms    0 ms    0 ms    0 ms  [192.168.0.1]
 2    5 ms   30 ms    8 ms    6 ms    7 ms  [73.20.152.1]
 3    7 ms    7 ms    7 ms    6 ms    6 ms  ge-3-37-ur01.edgewood.fl.jacksvil.comcast.net [68.86.170.165]
 4    7 ms    5 ms    6 ms    7 ms    7 ms  te-9-3-ar01.westside.fl.jacksvil.comcast.net [68.86.168.81]
 5    8 ms   11 ms   10 ms   10 ms    9 ms  [12.116.33.25]
 6   45 ms   45 ms   44 ms   43 ms   44 ms  tbr1.ormfl.ip.att.net [12.123.33.26]
 7   44 ms   45 ms   44 ms   44 ms   43 ms  cr1.ormfl.ip.att.net [12.122.21.25]
 8   49 ms   44 ms   44 ms   43 ms   44 ms  cr1.hs1tx.ip.att.net [12.122.31.241]
 9   44 ms   43 ms   42 ms   44 ms   43 ms  cr2.dlstx.ip.att.net [12.122.5.233]
10   44 ms   43 ms   45 ms   44 ms   43 ms  tbr2.dlstx.ip.att.net [12.122.18.198]
11   43 ms   44 ms   45 ms   43 ms   43 ms  br2.dlstx.ip.att.net [12.123.16.213]
12   45 ms   43 ms   44 ms   44 ms   44 ms  mdf1-gsr12-1-pos-7-0.dal1.attens.net [12.122.255.82]
13   43 ms   44 ms   49 ms   46 ms   43 ms  mdf1-bi8k-1-eth-1-4.dal1.attens.net [63.241.192.42]
14   44 ms   44 ms   45 ms   51 ms   43 ms  [206.16.60.41]

anyone notice anything bad or out of the ordinary?  this is driving me nutz..... :mad:
Title: Re: Major Disco problems since new version - help!
Post by: TequilaChaser on March 24, 2008, 10:35:45 AM
wow.......not 1 single response of help from anyone.........

I did a registry clean up, run spybot search & destroy, run Nod32 deep scan.......cleaned out my films folder & reloaded my Cache file........I lost UDP once yesterday but never got a discoe........seems it might have claered itself up for the most part, thankfully.......
Title: Re: Major Disco problems since new version - help!
Post by: fuzeman on March 24, 2008, 11:03:01 AM
Well that * in hop 13 is not good, same on both 38 and 39 pingplots. It's not in last one however, were you getting disco'ed there,Axis vs Allies, Training, Dueling, Late War Blue Arena , also?

You say it's slightly better? If you ping now, anything weird in that 13th hop now?

After the fact yes but we missed you in KOTH. Hope it continues to be better.
Title: Re: Major Disco problems since new version - help!
Post by: TequilaChaser on March 24, 2008, 02:55:22 PM
am at work right now Dave, but I was in the Blue Arena yesterday when I received the lost UDP message........yes seems like that   mdf1-bi8k-1-eth-1-4.dal1.attens.net [63.241.192.42]
   HOP  is or might be the culprit ....... will check them all again when I get home ......when ever that might turn out to be ...:-/
Title: Re: Major Disco problems since new version - help!
Post by: Skuzzy on March 25, 2008, 06:04:38 AM
Actually it is on the return trip, but I did not have time to run the trace and post it back to you.  Just ran out of time yesterday.
Title: Re: Major Disco problems since new version - help!
Post by: fuzeman on March 25, 2008, 10:14:17 AM
 I thought about that but thought if weirdness happens in last hop that indicated return trip.
As Skuzzy knows I'm getting stupider every minute. Last time he came into the arena to settle it down, he was typing on light Blue God channel.
D U M B fuzeman thinks its coming right to him so he PMs Skuzzy about it. Guess I wasn't the only one because he did say that he was transmitting to everyone as he got more feedbck like mine I assume.
Another good thing, my watch's battery has run down and it doesnt work. That means I don't get stupid as fast now. Bad part is the watch has a digital display so despite being broken it still doesnt tell the correct time 2x a day like an analog watch.
[ where's my 2nd cup of coffee?? ]

Skuzzy, on long days like that does HiTech try and pull a fast one and set the clocks back?
Title: Re: Major Disco problems since new version - help!
Post by: Skuzzy on March 25, 2008, 11:38:22 AM
I got nailed from abut 30 players.  Text in the radio was flying off the screen.  I did not even notice your name in the list fuze.  Never saw so many, "Hey!  Why you PM'ing me?!?!" messages.
Title: Re: Major Disco problems since new version - help!
Post by: fuzeman on March 25, 2008, 01:38:41 PM
We coostOOmers iz da schmart ones at tymes, isnt we.

So I don't offend anyone, the above refers to me and me only!
Title: Re: Major Disco problems since new version - help!
Post by: Bukrub on March 29, 2008, 02:49:49 PM
TC did you get this fixed. I notice your ping plotter are run fairly close together. Mine look good for five minutes or so, but after that they look like this. No one can seem to find the problem.

Target Name: N/A
         IP: 206.16.60.38
  Date/Time: 3/27/2008 7:20:57 PM

 1    0 ms    0 ms    0 ms    0 ms    0 ms    0 ms    0 ms    0 ms    0 ms  [192.168.11.1]
 2    6 ms    9 ms   25 ms   15 ms    8 ms    6 ms   20 ms    8 ms   18 ms  [10.244.32.1]
 3    7 ms    6 ms   11 ms    8 ms    8 ms   12 ms   10 ms    7 ms    8 ms  tera-24-206-186-65.kw.tx.cebridge.net [24.206.186.65]
 4   20 ms    8 ms    9 ms    6 ms   11 ms    9 ms   20 ms    6 ms   21 ms  [24.206.159.82]
 5    9 ms    8 ms    8 ms    8 ms    8 ms   24 ms  190 ms    9 ms    8 ms  [216.227.255.101]
 6   27 ms   18 ms -32764 ms -32764 ms -32764 ms -32764 ms  197 ms   18 ms   26 ms  [216.115.62.249]
 7 -32764 ms -32764 ms -32764 ms -32764 ms -32764 ms -32764 ms   19 ms   17 ms   29 ms  [216.115.62.254]
 8 -32764 ms -32764 ms -32764 ms -32764 ms -32764 ms -32764 ms   34 ms   *       *      [12.88.208.181]
 9 -32764 ms -32764 ms -32764 ms -32764 ms -32764 ms -32764 ms   28 ms   *       *      tbr2.hs1tx.ip.att.n et [12.122.103.78]
10 -32764 ms -32764 ms -32764 ms -32764 ms -32764 ms -32764 ms   31 ms   *       *      tbr1.dlstx.ip.att.n et [12.122.10.129]
11 -32764 ms -32764 ms -32764 ms -32764 ms -32764 ms -32764 ms   60 ms   *       *      gar5.dlstx.ip.att.n et [12.123.16.209]
12   19 ms   22 ms   26 ms   22 ms   38 ms   22 ms   43 ms   *       *      mdf1-gsr12-1-pos-6-0.dal1.attens.net [12.122.255.78]
13  465 ms   20 ms -32764 ms -32764 ms -32764 ms -32764 ms  464 ms   *       *      mdf1-bi8k-2-eth-2-2.dal1.attens.net [63.241.192.218]
14   16 ms   15 ms   21 ms   19 ms   17 ms   23 ms   27 ms   *       *      [206.16.60.38]

Buk
Title: Re: Major Disco problems since new version - help!
Post by: TequilaChaser on April 07, 2008, 07:05:21 PM

No Worries, Skuzzy.....I know how busy your plate is .is all good


TC did you get this fixed. I notice your ping plotter are run fairly close together. Mine look good for five minutes or so, but after that they look like this. No one can seem to find the problem.

Target Name: N/A
         IP: 206.16.60.38
  Date/Time: 3/27/2008 7:20:57 PM

 1    0 ms    0 ms    0 ms    0 ms    0 ms    0 ms    0 ms    0 ms    0 ms  [192.168.11.1]
 2    6 ms    9 ms   25 ms   15 ms    8 ms    6 ms   20 ms    8 ms   18 ms  [10.244.32.1]
 3    7 ms    6 ms   11 ms    8 ms    8 ms   12 ms   10 ms    7 ms    8 ms  tera-24-206-186-65.kw.tx.cebridge.net [24.206.186.65]
 4   20 ms    8 ms    9 ms    6 ms   11 ms    9 ms   20 ms    6 ms   21 ms  [24.206.159.82]
 5    9 ms    8 ms    8 ms    8 ms    8 ms   24 ms  190 ms    9 ms    8 ms  [216.227.255.101]
 6   27 ms   18 ms -32764 ms -32764 ms -32764 ms -32764 ms  197 ms   18 ms   26 ms  [216.115.62.249]
 7 -32764 ms -32764 ms -32764 ms -32764 ms -32764 ms -32764 ms   19 ms   17 ms   29 ms  [216.115.62.254]
 8 -32764 ms -32764 ms -32764 ms -32764 ms -32764 ms -32764 ms   34 ms   *       *      [12.88.208.181]
 9 -32764 ms -32764 ms -32764 ms -32764 ms -32764 ms -32764 ms   28 ms   *       *      tbr2.hs1tx.ip.att.n et [12.122.103.78]
10 -32764 ms -32764 ms -32764 ms -32764 ms -32764 ms -32764 ms   31 ms   *       *      tbr1.dlstx.ip.att.n et [12.122.10.129]
11 -32764 ms -32764 ms -32764 ms -32764 ms -32764 ms -32764 ms   60 ms   *       *      gar5.dlstx.ip.att.n et [12.123.16.209]
12   19 ms   22 ms   26 ms   22 ms   38 ms   22 ms   43 ms   *       *      mdf1-gsr12-1-pos-6-0.dal1.attens.net [12.122.255.78]
13  465 ms   20 ms -32764 ms -32764 ms -32764 ms -32764 ms  464 ms   *       *      mdf1-bi8k-2-eth-2-2.dal1.attens.net [63.241.192.218]
14   16 ms   15 ms   21 ms   19 ms   17 ms   23 ms   27 ms   *       *      [206.16.60.38]

Buk

I went thru everything , registry, flashing the router, clearing cache, reassuring Aces High has a dedicated straight thru in both the router & Zone alarm.......it still happened.

2 days later all is good again....stupid comcast I blame it on......fussed at them and they told me they let me try their new 8 meg connect for 2 months no charge......don't see any difference really......it has always been around 6500 to 9800 kbps connect
Title: Re: Major Disco problems since new version - help!
Post by: Skuzzy on April 08, 2008, 05:55:03 AM
Most of the connect issues have to do with the fact we happen to release the update at around spring break time, which is always a bad timne for the Internet.