« previous next »
Pages: 1 [2] 3 4 5 6   Go Down

Author Topic: Unable to connect?  (Read 1705 times)

Offline 2Slow

  • Nickel Member
  • ***
  • Posts: 720
Unable to connect?
« Reply #15 on: November 06, 2005, 08:02:50 PM »
Me 2.  Can't get on.  Glad we went to ATT and a new server.
Logged
2Slow
Secundum mihi , urbanus resurrectio
TANSTAAFL

Offline Baine

  • Copper Member
  • **
  • Posts: 288
Unable to connect?
« Reply #16 on: November 06, 2005, 08:03:35 PM »
Can't get in either. First time this has happened to me:furious
Logged

Offline Billy Joe Bob

  • Nickel Member
  • ***
  • Posts: 470
Unable to connect?
« Reply #17 on: November 06, 2005, 08:07:49 PM »
Quote
Originally posted by Skilless
$15 a month figures out to be just over 2 cents an hour.  HiTech is working it's way to owing me 3.5 cents!!


errr im 14 i dont have a credit card and my parents dont really want to get full online :furious
Logged

Offline Morpheus

  • Plutonium Member
  • *******
  • Posts: 10224
Unable to connect?
« Reply #18 on: November 06, 2005, 08:11:36 PM »
Good thought it was just me.

The reason I found is this Equinox map sucks so bad the server doesnt even want to  log on.
Logged
If you don't receive Jesus Christ, you don't receive the gift of righteousness.

Be A WARRIOR NOT A WORRIER!

Offline ZZ3

  • Zinc Member
  • *
  • Posts: 71
Unable to connect?
« Reply #19 on: November 06, 2005, 08:11:52 PM »
Well the first request is timing out.
Pings are all good. That new AT&T service aint what it's cracked up to be.
1st trace with firewall.
2nd without, no difference.



Microsoft Windows XP [Version 5.1.2600]

(C) Copyright 1985-2001 Microsoft Corp.

C:\>tracert 206.16.60.38

Tracing route to 206.16.60.38 over a maximum of 30 hops

  1     *        *        *     Request timed out.
  2    14 ms    14 ms    13 ms  adsl-69-231-127-254.dsl.irvnca.pacbell.net [69.2
31.127.254]
  3    15 ms    14 ms    14 ms  dist4-vlan50.irvnca.sbcglobal.net [67.114.50.2]

  4    15 ms    15 ms    14 ms  bb2-g2-0.irvnca.sbcglobal.net [151.164.41.239]
  5    17 ms    17 ms    17 ms  151.164.42.75
  6    17 ms    17 ms    17 ms  bb1-p1-0.crrvca.sbcglobal.net [151.164.40.254]
  7    18 ms    18 ms    18 ms  ex2-p8-0.eqlaca.sbcglobal.net [151.164.41.33]
  8    18 ms    18 ms    17 ms  ex1-p2-0.eqlaca.sbcglobal.net [151.164.40.161]
  9    18 ms    18 ms    18 ms  sl-st20-la-4-0.sprintlink.net [144.232.154.229]

 10    18 ms    18 ms    19 ms  sl-bb21-ana-13-0.sprintlink.net [144.232.20.66]

 11    19 ms    18 ms    18 ms  sl-bb22-ana-15-0.sprintlink.net [144.232.1.174]

 12    42 ms    42 ms    43 ms  sprint-gw.la2ca.ip.att.net [192.205.32.185]
 13    73 ms    72 ms    75 ms  tbr1-p010301.la2ca.ip.att.net [12.122.81.242]
 14    74 ms    72 ms    73 ms  tbr1-cl20.dlstx.ip.att.net [12.122.10.49]
 15    72 ms    72 ms    72 ms  gbr2-p10.dlstx.ip.att.net [12.122.12.62]
 16    71 ms    71 ms    71 ms  gar1-p370.dlstx.ip.att.net [12.123.16.237]
 17    71 ms    71 ms    72 ms  mdf1-gsr12-2-pos-7-0.dal1.attens.net [12.122.255
.170]
 18    85 ms    84 ms    85 ms  mdf1-bi8k-1-eth-2-1.dal1.attens.net [63.241.192.
194]
 19    85 ms    85 ms    86 ms  206.16.60.38

Trace complete.

C:\>tracert 206.16.60.38

Tracing route to 206.16.60.38 over a maximum of 30 hops

  1     *        *        *     Request timed out.
  2    13 ms    14 ms    13 ms  adsl-69-231-127-254.dsl.irvnca.pacbell.net [69.2
31.127.254]
  3    15 ms    14 ms    15 ms  dist4-vlan50.irvnca.sbcglobal.net [67.114.50.2]

  4    14 ms    14 ms    15 ms  bb2-g2-0.irvnca.sbcglobal.net [151.164.41.239]
  5    17 ms    17 ms    17 ms  151.164.42.75
  6    17 ms    17 ms    17 ms  bb1-p1-0.crrvca.sbcglobal.net [151.164.40.254]
  7    19 ms    18 ms    18 ms  ex2-p8-0.eqlaca.sbcglobal.net [151.164.41.33]
  8    18 ms    18 ms    18 ms  ex1-p2-0.eqlaca.sbcglobal.net [151.164.40.161]
  9    18 ms    17 ms    18 ms  sl-st20-la-4-0.sprintlink.net [144.232.154.229]

 10    19 ms    19 ms    18 ms  sl-bb21-ana-13-0.sprintlink.net [144.232.20.66]

 11    18 ms    18 ms    19 ms  sl-bb22-ana-15-0.sprintlink.net [144.232.1.174]

 12    43 ms    43 ms    43 ms  sprint-gw.la2ca.ip.att.net [192.205.32.185]
 13    72 ms    72 ms    73 ms  tbr1-p010301.la2ca.ip.att.net [12.122.81.242]
 14    74 ms    72 ms    72 ms  tbr1-cl20.dlstx.ip.att.net [12.122.10.49]
 15    71 ms    71 ms    71 ms  gbr2-p10.dlstx.ip.att.net [12.122.12.62]
 16    69 ms    70 ms    70 ms  gar1-p370.dlstx.ip.att.net [12.123.16.237]
 17    71 ms    71 ms    72 ms  mdf1-gsr12-2-pos-7-0.dal1.attens.net [12.122.255
.170]
 18    85 ms    85 ms    85 ms  mdf1-bi8k-1-eth-2-1.dal1.attens.net [63.241.192.
194]
 19    86 ms    85 ms    86 ms  206.16.60.38

Trace complete.

C:\>ping 206.16.60.38

Pinging 206.16.60.38 with 32 bytes of data:

Reply from 206.16.60.38: bytes=32 time=85ms TTL=236
Reply from 206.16.60.38: bytes=32 time=84ms TTL=236
Reply from 206.16.60.38: bytes=32 time=85ms TTL=236
Reply from 206.16.60.38: bytes=32 time=85ms TTL=236

Ping statistics for 206.16.60.38:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 84ms, Maximum = 85ms, Average = 84ms

C:\>
Logged

Offline megadud

  • Gold Member
  • *****
  • Posts: 2935
Unable to connect?
« Reply #20 on: November 06, 2005, 08:13:20 PM »
i can't believe this it is squad nite!! BOO AT&T!
Logged

Offline Skilless

  • Persona Non Grata
  • Nickel Member
  • ***
  • Posts: 578
      • http://www.4remnants.com
Unable to connect?
« Reply #21 on: November 06, 2005, 08:14:00 PM »
Quote
Originally posted by ZZ3
Well the first request is timing out.
Pings are all good. That new AT&T service aint what it's cracked up to be.
1st trace with firewall.
2nd without, no difference.



Microsoft Windows XP [Version 5.1.2600]

(C) Copyright 1985-2001 Microsoft Corp.

C:\>tracert 206.16.60.38

Tracing route to 206.16.60.38 over a maximum of 30 hops

  1     *        *        *     Request timed out.
  2    14 ms    14 ms    13 ms  adsl-69-231-127-254.dsl.irvnca.pacbell.net [69.2
31.127.254]
  3    15 ms    14 ms    14 ms  dist4-vlan50.irvnca.sbcglobal.net [67.114.50.2]

  4    15 ms    15 ms    14 ms  bb2-g2-0.irvnca.sbcglobal.net [151.164.41.239]
  5    17 ms    17 ms    17 ms  151.164.42.75
  6    17 ms    17 ms    17 ms  bb1-p1-0.crrvca.sbcglobal.net [151.164.40.254]
  7    18 ms    18 ms    18 ms  ex2-p8-0.eqlaca.sbcglobal.net [151.164.41.33]
  8    18 ms    18 ms    17 ms  ex1-p2-0.eqlaca.sbcglobal.net [151.164.40.161]
  9    18 ms    18 ms    18 ms  sl-st20-la-4-0.sprintlink.net [144.232.154.229]

 10    18 ms    18 ms    19 ms  sl-bb21-ana-13-0.sprintlink.net [144.232.20.66]

 11    19 ms    18 ms    18 ms  sl-bb22-ana-15-0.sprintlink.net [144.232.1.174]

 12    42 ms    42 ms    43 ms  sprint-gw.la2ca.ip.att.net [192.205.32.185]
 13    73 ms    72 ms    75 ms  tbr1-p010301.la2ca.ip.att.net [12.122.81.242]
 14    74 ms    72 ms    73 ms  tbr1-cl20.dlstx.ip.att.net [12.122.10.49]
 15    72 ms    72 ms    72 ms  gbr2-p10.dlstx.ip.att.net [12.122.12.62]
 16    71 ms    71 ms    71 ms  gar1-p370.dlstx.ip.att.net [12.123.16.237]
 17    71 ms    71 ms    72 ms  mdf1-gsr12-2-pos-7-0.dal1.attens.net [12.122.255
.170]
 18    85 ms    84 ms    85 ms  mdf1-bi8k-1-eth-2-1.dal1.attens.net [63.241.192.
194]
 19    85 ms    85 ms    86 ms  206.16.60.38

Trace complete.

C:\>tracert 206.16.60.38

Tracing route to 206.16.60.38 over a maximum of 30 hops

  1     *        *        *     Request timed out.
  2    13 ms    14 ms    13 ms  adsl-69-231-127-254.dsl.irvnca.pacbell.net [69.2
31.127.254]
  3    15 ms    14 ms    15 ms  dist4-vlan50.irvnca.sbcglobal.net [67.114.50.2]

  4    14 ms    14 ms    15 ms  bb2-g2-0.irvnca.sbcglobal.net [151.164.41.239]
  5    17 ms    17 ms    17 ms  151.164.42.75
  6    17 ms    17 ms    17 ms  bb1-p1-0.crrvca.sbcglobal.net [151.164.40.254]
  7    19 ms    18 ms    18 ms  ex2-p8-0.eqlaca.sbcglobal.net [151.164.41.33]
  8    18 ms    18 ms    18 ms  ex1-p2-0.eqlaca.sbcglobal.net [151.164.40.161]
  9    18 ms    17 ms    18 ms  sl-st20-la-4-0.sprintlink.net [144.232.154.229]

 10    19 ms    19 ms    18 ms  sl-bb21-ana-13-0.sprintlink.net [144.232.20.66]

 11    18 ms    18 ms    19 ms  sl-bb22-ana-15-0.sprintlink.net [144.232.1.174]

 12    43 ms    43 ms    43 ms  sprint-gw.la2ca.ip.att.net [192.205.32.185]
 13    72 ms    72 ms    73 ms  tbr1-p010301.la2ca.ip.att.net [12.122.81.242]
 14    74 ms    72 ms    72 ms  tbr1-cl20.dlstx.ip.att.net [12.122.10.49]
 15    71 ms    71 ms    71 ms  gbr2-p10.dlstx.ip.att.net [12.122.12.62]
 16    69 ms    70 ms    70 ms  gar1-p370.dlstx.ip.att.net [12.123.16.237]
 17    71 ms    71 ms    72 ms  mdf1-gsr12-2-pos-7-0.dal1.attens.net [12.122.255
.170]
 18    85 ms    85 ms    85 ms  mdf1-bi8k-1-eth-2-1.dal1.attens.net [63.241.192.
194]
 19    86 ms    85 ms    86 ms  206.16.60.38

Trace complete.

C:\>ping 206.16.60.38

Pinging 206.16.60.38 with 32 bytes of data:

Reply from 206.16.60.38: bytes=32 time=85ms TTL=236
Reply from 206.16.60.38: bytes=32 time=84ms TTL=236
Reply from 206.16.60.38: bytes=32 time=85ms TTL=236
Reply from 206.16.60.38: bytes=32 time=85ms TTL=236

Ping statistics for 206.16.60.38:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 84ms, Maximum = 85ms, Average = 84ms

C:\>


Could you possibly translate that to english please?
Logged

Offline EagleEyes

  • Silver Member
  • ****
  • Posts: 1474
      • http://www.myspace.com/bassim
Unable to connect?
« Reply #22 on: November 06, 2005, 08:16:01 PM »
Well, i thought i was the only one having problems getting on, but it looks like a lot of people cant get on!  Im Pissed, finally have time after work to do some seriouse flying and i CANT!! GGGGRRRR!!!!! Hope HTC or AT&T gets it fixed SOON!:mad:
Logged
Joedog31

GL IV./JG4 for Red Storm Krupp Steel
***The Flying Circus*** MA
334th FS "The Eagles" - FSO

Offline Blixen

  • Silver Member
  • ****
  • Posts: 877
      • http://475thfg.bravehost.com/
Unable to connect?
« Reply #23 on: November 06, 2005, 08:16:57 PM »
ditto and had 0 perks in main lost 4500 fighter perks whats the dealio
Logged

Offline SkyRock

  • Platinum Member
  • ******
  • Posts: 7758
Unable to connect?
« Reply #24 on: November 06, 2005, 08:17:42 PM »
Quote
Originally posted by Morpheus
Good thought it was just me.

The reason I found is this Equinox map sucks so bad the server doesnt even want to  log on.
:rofl
Logged

Triton28 - "...his stats suggest he has a healthy combination of suck and sissy!"

Offline traps

  • Nickel Member
  • ***
  • Posts: 408
Unable to connect?
« Reply #25 on: November 06, 2005, 08:18:11 PM »
Quote
Originally posted by Skilless
Could you possibly translate that to english please?



 sure no problem it says: its broke and this sucks
Logged

Offline Bulz

  • Zinc Member
  • *
  • Posts: 47
Unable to connect?
« Reply #26 on: November 06, 2005, 08:18:15 PM »
Yep!  Seems the server is not allowing connections.
Logged

Offline ghi

  • Gold Member
  • *****
  • Posts: 2669
Unable to connect?
« Reply #27 on: November 06, 2005, 08:23:16 PM »
first  Boom was Perks reset to 0,( ZERO), now can't conect:mad: :mad:
Logged

Offline Skilless

  • Persona Non Grata
  • Nickel Member
  • ***
  • Posts: 578
      • http://www.4remnants.com
Unable to connect?
« Reply #28 on: November 06, 2005, 08:23:38 PM »
QUICK SOMEBODY OPEN A H2H ARENA!!!
Logged

Offline Dead Man Flying

  • Platinum Member
  • ******
  • Posts: 6301
Unable to connect?
« Reply #29 on: November 06, 2005, 08:23:46 PM »
Quote
Originally posted by megadud
i can't believe this it is squad nite!! BOO AT&T!


It is?  Why doesn't anyone tell me these things?

-- Todd/Leviathn
Logged
Pages: 1 [2] 3 4 5 6   Go Up
« previous next »