Free Allegiance Forums

Posted: **Wed Jul 23, 2008 2:31 pm**

It's working for me now.

Edit: Fail. Tracert went through just fine, but TS can't connect to server. >.<

Posted: **Sat Jul 26, 2008 1:07 am**

Just tried it and it's not working. I changed nothing on my end. If it is my ISP, my only question is "why?" they would block it. I'm stumped, I don't know what to do at this point. If I cannot get TS to run, there is no need for me to be in a squad anymore. I feel completely useless in a squad game with no TS, and I've given up trying to get TS to work.

Posted: **Sat Jul 26, 2008 2:47 pm**

It's working for me. Do tracert for 'ts.dras.us' or 'ts.alleg.net'. See if it fails at some hop?

Posted: **Sat Jul 26, 2008 2:56 pm**

Traces were posted. For Mes, they stop at the second hop (i.e., no ping returns after his router).

Posted: **Sat Jul 26, 2008 3:25 pm**

For me I can tracert to ts.dras.us, but I timeout on ts.alleg.net. (Just ran it quickly, as I have to head out.) I still can't connect though. *shrug*

Posted: **Sat Jul 26, 2008 3:43 pm**

FreeBeer wrote:QUOTE (FreeBeer @ Jul 26 2008, 09:25 AM) For me I can tracert to ts.dras.us, but I timeout on ts.alleg.net. (Just ran it quickly, as I have to head out.) I still can't connect though. *shrug*

Same here. ^

Posted: **Sat Jul 26, 2008 5:11 pm**

That makes absolutely no sense. ts.alleg.net is a CNAME for ts.dras.us.

In any event, download and use PingPlotter and use it to trace the route to the server. It gives you a much more accurate picture as it'll bypass routers that block pings and still spit out results.

Posted: **Sat Jul 26, 2008 8:08 pm**

Thanks for looking into it, aarm.

Here's the results of ts.dras.us: (10 traces)

Code: Select all

Target Name: ts.dras.us
         IP: 72.36.154.122
  Date/Time: 7/26/2008 4:48:15 PM to 7/26/2008 4:50:08 PM

 1   *       *       *       *       *       *       *      N/A      *       *       [-]
 2    6 ms    7 ms    6 ms    8 ms    6 ms    5 ms    7 ms  N/A       7 ms   14 ms  vl-201.gw03.nbfd.phub.net.cable.rogers.com [66.185.91.193]
 3    7 ms    7 ms    7 ms    8 ms    7 ms    7 ms    6 ms  N/A       7 ms    7 ms  gi-3-0.gw01.nbfd.phub.net.cable.rogers.com [64.71.240.125]
 4   25 ms   25 ms   25 ms   26 ms  118 ms   26 ms   24 ms  N/A      24 ms   25 ms  [66.185.82.158]
 5   28 ms   34 ms   27 ms   27 ms   27 ms   28 ms   28 ms  N/A      28 ms   27 ms  so-2-0-0.gw02.mtnk.phub.net.cable.rogers.com [66.185.80.185]
 6   96 ms   49 ms   51 ms   50 ms   49 ms   50 ms   51 ms  N/A      50 ms   53 ms  [24.153.5.238]
 7   49 ms   50 ms   50 ms   51 ms   50 ms   50 ms   51 ms  N/A      50 ms   50 ms  [64.71.240.18]
 8   *       *       *       *       *       *       *      N/A      *       *       [-]

Destination not reached in 35 hops

ts.alleg.net (10 traces):

Code: Select all

Target Name: ts.alleg.net
         IP: 72.36.154.122
  Date/Time: 7/26/2008 5:03:27 PM to 7/26/2008 5:05:42 PM

 1   *       *       *       *       *       *       *       *       *       *       [-]
 2    8 ms    6 ms   11 ms    7 ms    6 ms    6 ms    6 ms    6 ms   12 ms    8 ms  vl-201.gw03.nbfd.phub.net.cable.rogers.com [66.185.91.193]
 3    7 ms    6 ms    7 ms    7 ms    6 ms    7 ms    6 ms    8 ms    7 ms    8 ms  gi-3-0.gw01.nbfd.phub.net.cable.rogers.com [64.71.240.125]
 4   24 ms   26 ms   24 ms   25 ms   24 ms   26 ms   27 ms   25 ms   25 ms   24 ms  [66.185.82.158]
 5   27 ms   26 ms   26 ms   26 ms   27 ms   27 ms   26 ms   27 ms   26 ms   29 ms  so-2-0-0.gw02.mtnk.phub.net.cable.rogers.com [66.185.80.185]
 6   50 ms   50 ms   50 ms   52 ms   60 ms  140 ms   49 ms   50 ms   50 ms   52 ms  [24.153.5.238]
 7   51 ms   50 ms   51 ms   68 ms   50 ms   *       51 ms   50 ms   49 ms   49 ms  [64.71.240.18]
 8   *       *       *       *       *       *       *       *       *       *       [-]
 9   *       *       *       *       *       *       *       *       *       *       [-]

Destination not reached in 35 hops

So at least it's a little more consistent than MS's tracert. (I also tried Linux's version, with similar results.)

Posted: **Sat Jul 26, 2008 8:12 pm**

Tell you what, run the same trace to this IP and see what it gets:

72.36.234.74

Posted: **Sat Jul 26, 2008 8:22 pm**

Here joo go:

Code: Select all

Target Name: 74.234.36.72.static.reverse.ltdomains.com
         IP: 72.36.234.74
  Date/Time: 7/26/2008 5:15:41 PM to 7/26/2008 5:17:56 PM

 1   *       *       *       *       *       *       *       *       *       *       [-]
 2    8 ms    7 ms    7 ms    8 ms    6 ms    8 ms    5 ms   11 ms    7 ms    6 ms  vl-201.gw03.nbfd.phub.net.cable.rogers.com [66.185.91.193]
 3    6 ms   14 ms    8 ms    7 ms    7 ms    9 ms    6 ms    9 ms    8 ms    7 ms  [64.71.240.217]
 4   25 ms   26 ms   26 ms   27 ms   26 ms   26 ms   27 ms   26 ms   58 ms   27 ms  so-4-1-2.gw02.ym.phub.net.cable.rogers.com [66.185.82.81]
 5   31 ms   28 ms   30 ms   31 ms   29 ms   28 ms   29 ms   29 ms   28 ms   29 ms  so-2-1-0.gw02.mtnk.phub.net.cable.rogers.com [66.185.80.134]
 6   50 ms   52 ms   51 ms   50 ms   52 ms   51 ms   50 ms   51 ms   50 ms  128 ms  pos-1-0.igw01.ny8th.phub.net.cable.rogers.com [66.185.81.13]
 7   50 ms   51 ms   52 ms   50 ms   *       *       52 ms   *       50 ms   50 ms  [64.71.240.18]
 8   45 ms   46 ms   46 ms   46 ms   44 ms   45 ms   46 ms   45 ms   44 ms   46 ms  te9-2.ccr04.jfk02.atlas.cogentco.com [130.117.0.53]
 9   48 ms   48 ms   50 ms   49 ms   50 ms   54 ms   48 ms   49 ms   49 ms   49 ms  te2-1.ccr02.dca01.atlas.cogentco.com [154.54.6.13]
10   50 ms   50 ms   70 ms   66 ms   50 ms   51 ms   50 ms   51 ms   50 ms   50 ms  te4-3.mpd01.dca02.atlas.cogentco.com [154.54.7.2]
11   49 ms   49 ms   47 ms   48 ms   49 ms   49 ms   49 ms   49 ms   49 ms   49 ms  vl3494.mpd01.iad01.atlas.cogentco.com [154.54.5.42]
12   49 ms   57 ms   49 ms   48 ms   48 ms   50 ms   51 ms   49 ms   48 ms   49 ms  ber1-ge-7-43.virginiaequinix.savvis.net [208.173.10.181]
13   53 ms   49 ms   *       50 ms   49 ms   50 ms   49 ms   49 ms   49 ms   50 ms  cr1-tengig0-7-2-0.washington.savvis.net [204.70.197.242]
14  N/A      82 ms   76 ms   *      620 ms   81 ms   76 ms   76 ms  109 ms   84 ms  cr2-tengige0-7-5-0.dallas.savvis.net [204.70.196.29]
15   82 ms   75 ms   74 ms   75 ms   74 ms   74 ms   73 ms   73 ms   74 ms   77 ms  hr1-tengig-12-0-0.dallasda1.savvis.net [204.70.203.58]
16   82 ms   77 ms   77 ms   77 ms   79 ms   78 ms   77 ms   76 ms   77 ms   79 ms  [216.39.79.42]
17   75 ms   75 ms   75 ms   76 ms   75 ms   76 ms   81 ms   75 ms   75 ms   75 ms  [216.39.69.46]
18   *       *       *       *       *       *       *       *       *       *       [-]
19   80 ms   78 ms   81 ms   77 ms   78 ms   78 ms   78 ms   81 ms   77 ms   78 ms  74.234.36.72.static.reverse.ltdomains.com [72.36.234.74]

Ping statistics for 74.234.36.72.static.reverse.ltdomains.com
Packets: Sent = 10, Received = 10, Lost = 0 (0.0%)
Round Trip Times: Minimum = 77ms, Maximum = 81ms, Average = 78ms

I was getting errors at 64.71.240.18 and 204.70.197.242 and 204.70.196.29 (the latter two being Washington/Dallas) When I did my earlier pings and tracert I was suspecting the Washington link as I believe that is a common link for those affected.

Free Allegiance Forums

Teamspeak help