Author Topic: SERIOUS PROBLEM WITH CONNECT  (Read 248 times)

Offline Tuck

  • Copper Member
  • **
  • Posts: 225
      • http://hometown.aol.com/tuck0006/
SERIOUS PROBLEM WITH CONNECT
« on: December 27, 2001, 04:07:00 PM »
ok...i'm going to try to be calm and not rant and rave in this post, because i really need some serious input as to what to do here...

for the past two weeks (and i had the same problem for about three days the week prior to this instance) i've not been able to connect to the server for the main arena, although i can get into the other arenas (ct, etc)  according to the traces that i've done (thanks to pyro for the "tracert" thingie knowledge), my attempt to connect is screwed, most of the time, at an at&t router/hop...99% of the time at the same one.  also, in the last couple of days, my attempt to connect is timing out at a couple of more routers/hops, just before reaching the destination (theplanet.com).

i've sent emails out the wazoo about this...to htc, theplanet, my isp...and keep getting the same responses: "...we'll see what we can do..." and "there's nothing we can do, because it's not on our "end""...

does anyone know of anything at all i can do?  i've talke to some people about this at work, and they said something about screwing with my network adapter settings? (i dunno...don't claim to be a computer expert by any means, but is this possible?)

this is probably a sure sign of having no life, but i really enjoy coming home and playing ah, and being as i can't log into the ma, i'm really starting to get pissed.  this wouldn't even be a problem really IF more people flew in the ct, but as everyone knows, there's usually a handful of players on at any given time which does me no good.

so again, does anyone know of anything i can do? (besides get the physical address of the routers and go postal on them?)    :confused:

i've about had it!    :mad:   :mad:   :mad:

by the way...i'm posting the last trace that i did (about 5 minutes ago) so you can see what i mean.

Tracing route to core0.theplanet.com [216.234.234.1]

over a maximum of 30 hops:

  1    46 ms    27 ms    13 ms  10.100.144.1

  2    19 ms    61 ms     9 ms  sw.chartertn.net [24.158.96.6]

  3    16 ms    10 ms    44 ms  chartertn-gw1.chartertn.net [24.158.96.226]

  4    69 ms    25 ms    71 ms  12.127.29.145

  5   101 ms    29 ms    94 ms  gbr5-p50.attga.ip.att.net [12.123.197.42]

  6    32 ms    32 ms    59 ms  gbr4-p100.attga.ip.att.net [12.122.5.42]

  7    68 ms    80 ms   113 ms  gbr3-p10.dlstx.ip.att.net [12.122.3.37]

  8    70 ms   124 ms    57 ms  gbr6-p60.dlstx.ip.att.net [12.122.5.81]

  9    41 ms    86 ms    46 ms  gar2-p370.dlstx.ip.att.net [12.123.17.29]

 10    38 ms    41 ms    46 ms  12.124.211.58

 11    81 ms    43 ms    42 ms  border3.ge4-1-bbnet2.ext1.dal.pnap.net [216.52.191.83]

 12    42 ms    88 ms    41 ms  core0.theplanet.com [216.234.234.1]

Trace complete.
Tracing route to core1.theplanet.com [216.234.234.253]

over a maximum of 30 hops:

  1    13 ms    12 ms     8 ms  10.100.144.1

  2     9 ms    47 ms    41 ms  sw.chartertn.net [24.158.96.6]

  3    12 ms    23 ms    21 ms  chartertn-gw1.chartertn.net [24.158.96.226]

  4    15 ms    20 ms    20 ms  12.127.29.245

  5    65 ms    42 ms    64 ms  gbr6-p50.attga.ip.att.net [12.123.197.50]

  6     *        *        *     Request timed out.

  7    38 ms    53 ms    88 ms  gbr3-p10.dlstx.ip.att.net [12.122.3.37]

  8    79 ms    78 ms    91 ms  gbr5-p60.dlstx.ip.att.net [12.122.5.73]

  9    73 ms    85 ms    46 ms  gar2-p360.dlstx.ip.att.net [12.123.17.25]

 10    85 ms    82 ms    46 ms  12.124.211.58

 11    46 ms    43 ms    39 ms  border3.ge3-1-bbnet1.ext1.dal.pnap.net [216.52.191.22]

 12     *        *        *     Request timed out.

 13     *        *       51 ms  core1.theplanet.com [216.234.234.253]

Trace complete.
Tracing route to core2.theplanet.com [216.234.234.252]

over a maximum of 30 hops:

  1    17 ms    30 ms    19 ms  10.100.144.1

  2    13 ms    11 ms    13 ms  sw.chartertn.net [24.158.96.6]

  3     9 ms    15 ms    11 ms  chartertn-gw1.chartertn.net [24.158.96.226]

  4    16 ms    51 ms   110 ms  12.127.29.145

  5   109 ms    71 ms    36 ms  gbr5-p50.attga.ip.att.net [12.123.197.42]

  6    68 ms    36 ms   110 ms  gbr4-p100.attga.ip.att.net [12.122.5.42]

  7   105 ms   143 ms    80 ms  gbr3-p10.dlstx.ip.att.net [12.122.3.37]

  8    62 ms    73 ms    78 ms  gbr6-p60.dlstx.ip.att.net [12.122.5.81]

  9    46 ms    47 ms    41 ms  gar2-p370.dlstx.ip.att.net [12.123.17.29]

 10    53 ms    50 ms    51 ms  12.124.211.58

 11    74 ms    54 ms    81 ms  border3.ge4-1-bbnet2.ext1.dal.pnap.net [216.52.191.83]

 12     *        *        *     Request timed out.

 13    86 ms    91 ms   122 ms  core2.theplanet.com [216.234.234.252]

Trace complete.

The Tuckster

"The first time I ever saw a jet, I shot it down."
Col. Chuck Yeager, USAAF

 
 

Offline Am0n

  • Nickel Member
  • ***
  • Posts: 764
SERIOUS PROBLEM WITH CONNECT
« Reply #1 on: December 28, 2001, 10:37:00 AM »
Tuck

What you need is a proxy server to route through, so it changes the path of the routing table (also can mask your IP, but thas a whole other purpose). There are programs you can download for free that will route you through a proxy, the only problem is that they normaly require a log in, but that is not always the case. there are some anaonymous proxies you can route through w/o log in, i'll see what i can find for you..

this has got to be a real drag for you.

Let me take a look around the net and i'll let your know. A proxy routing program i used a long time ago is A4Proxy, but it is for advanced users, no offense you may need something a lil easier to configure.

do you use a firewall or router?

Offline Am0n

  • Nickel Member
  • ***
  • Posts: 764
SERIOUS PROBLEM WITH CONNECT
« Reply #2 on: December 28, 2001, 10:45:00 AM »
Also ave your tried the "alt-route" to the server?

Offline Skuzzy

  • Support Member
  • Administrator
  • *****
  • Posts: 31462
      • HiTech Creations Home Page
SERIOUS PROBLEM WITH CONNECT
« Reply #3 on: December 28, 2001, 12:34:00 PM »
Tuck,..I see you are one of the @home refugees, relagated to Charter.  Charter is till trying to figure out how to run its network, as such, they are probably messing up the BGP tables which handles all the routing over the Internet.
I know Charter has had some issues in this regard.  Messing up BGP tables will propogate bad routing information to the Internet, which may appear to be some other backbone providers fault, but in fact it started at the source.
Sprint is notorious for these types of problems, SWBell has had its fair share too.  I am not really sure if this is the problem, but it is a possibility.
Roy "Skuzzy" Neese
support@hitechcreations.com

Offline Tuck

  • Copper Member
  • **
  • Posts: 225
      • http://hometown.aol.com/tuck0006/
SERIOUS PROBLEM WITH CONNECT
« Reply #4 on: December 28, 2001, 04:27:00 PM »


[ 12-28-2001: Message edited by: Tuck ]

Offline Tuck

  • Copper Member
  • **
  • Posts: 225
      • http://hometown.aol.com/tuck0006/
SERIOUS PROBLEM WITH CONNECT
« Reply #5 on: December 28, 2001, 04:56:00 PM »
hey skuzzymiester!    :D

so far, what you stated makes the most sense.

i spoke with the chuckleheads at charter just a few minutes ago and got the (in a deep tennessee accent) "well, there's nuttin' we can dew..." response, because it's not on "their end".

do you think, with your position and such (you big stud you) that you can slap some sense into someone's head...and at least get them on it?

i've tried everything i can possibly think of, and i'm still running into a brick wall.    :mad:

i'm on annual leave this next week...what in the hell am i gonna do for 9 days without ah?!    :confused: the sheer thought of it is driving me mad...MAD i tell you!    :eek:

The Tuckster

"The first time I ever saw a jet, I shot it down."
Col. Chuck Yeager, USAAF