Frag Infinity Tournament, Inc. - FITES LAN Party - www.fites.net

LAN Party Forums => Support Group => Started by: Czar on August 09, 2009, 10:07:54 PM

Title: Comcast / Steam issue?
Post by: Czar on August 09, 2009, 10:07:54 PM
So last night, (Saturday) I was unable to connect to Steam. Instead of getting the normal rejection message, this was a little different and stated that Steam was unable to connect to the Steam servers..which appeared after about 40 seconds of it trying to connect.

I tried to ipconfig /release, /renew, bypass my router, all that. No change. Then I found this:

http://forums.steampowered.com/forums/showthread.php?p=10840874

Anyone know a work around? SuperSully? :)
Title: Re: Comcast / Steam issue?
Post by: sully! on August 10, 2009, 09:54:02 AM
I'm seeing this too with the rig I have on my office on a cable modem. It may not be a Comcast issue, however, as from that tracert in the link you posted, at hop 10 the traffic is leaving the Comcast network and jumping over to Qwest/GBLX. It goes one more hop (again, on Qwest's network) and then it fails.

Here's the tracert to the same IP from my end:

Code: [Select]
C:\Windows\system32>tracert 72.165.61.138

Tracing route to 72-165-61-138.dia.static.qwest.net [72.165.61.138]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  fitesip01.fites.lan [10.0.0.1]
  2     *        *        *     Request timed out.
  3     9 ms    16 ms    11 ms  GE-1-2-ur02.hersheymills.pa.panjde.comcast.net [68.86.156.253]
  4     7 ms     9 ms    14 ms  68.86.153.121
  5     8 ms     7 ms     9 ms  te-9-1-ur01.lowerpaxton.pa.panjde.comcast.net [68.86.208.197]
  6     8 ms     9 ms    11 ms  te-8-1-ar01.lowerpaxton.pa.panjde.comcast.net [68.86.208.193]
  7    13 ms    12 ms    11 ms  68.85.158.186
  8    12 ms    21 ms    13 ms  68.85.159.229
  9    13 ms    14 ms    14 ms  be-40-crs01.401nbroadst.pa.panjde.comcast.net [68.86.208.33]
 10    31 ms    18 ms    16 ms  pos-1-9-0-0-cr01.mclean.va.ibone.comcast.net [68.86.90.13]
 11    18 ms    21 ms    18 ms  TenGigabitEthernet3-2.ar3.DCA3.gblx.net [64.213.33.57]
 12    20 ms    18 ms    19 ms  te1-3-10g.ar2.DCA3.gblx.net [67.17.108.145]
 13    51 ms    18 ms    18 ms  qwest-1.ar2.DCA3.gblx.net [64.208.110.30]
 14     *        *        *     Request timed out.
 15   106 ms   105 ms   105 ms  tuk-edge-06.inet.qwest.net [205.171.11.22]
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *     ^C
C:\Windows\system32>

I've found that this is the same IP my Steam client is trying to connect to also.
Title: Re: Comcast / Steam issue?
Post by: Czar on August 10, 2009, 10:00:30 AM
Whats the next step then? Probably sit and wait?
Title: Re: Comcast / Steam issue?
Post by: zx2slow on August 10, 2009, 11:02:08 AM
If this is the result of the /b/astards in 4chan.....
Title: Re: Comcast / Steam issue?
Post by: Czar on August 10, 2009, 11:06:04 AM
Meh. I just want to play my games.
Title: Re: Comcast / Steam issue?
Post by: {ShadowWX} on August 10, 2009, 12:04:14 PM
yeah me and my wife are having the same issue here. I just wanna play mah damn gamez!!!!!!!
hell you can't even access the support area on the steampowered website.
Title: Re: Comcast / Steam issue?
Post by: sully! on August 10, 2009, 01:33:52 PM
This appears to have been fixed. I just tried again and logged into Steam fine.

For comparison to above:

Code: [Select]
C:\Windows\system32>tracert 72.165.61.138

Tracing route to 72-165-61-138.dia.static.qwest.net [72.165.61.138]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  fitesip01.fites.lan [10.0.0.1]
  2     *        *        *     Request timed out.
  3     9 ms     8 ms     8 ms  GE-1-2-ur02.hersheymills.pa.panjde.comcast.net [68.86.156.253]
  4     9 ms     9 ms     9 ms  68.86.153.121
  5    10 ms    10 ms     9 ms  te-9-1-ur01.lowerpaxton.pa.panjde.comcast.net [68.86.208.197]
  6    12 ms     8 ms     9 ms  te-8-1-ar01.lowerpaxton.pa.panjde.comcast.net [68.86.208.193]
  7    12 ms    11 ms    11 ms  68.85.158.186
  8    14 ms    14 ms    28 ms  68.85.159.229
  9    13 ms    14 ms    16 ms  be-40-crs01.401nbroadst.pa.panjde.comcast.net [68.86.208.33]
 10    20 ms    20 ms    16 ms  pos-1-9-0-0-cr01.mclean.va.ibone.comcast.net [68.86.90.13]
 11    19 ms    18 ms    45 ms  TenGigabitEthernet3-2.ar3.DCA3.gblx.net [64.213.33.57]
 12    21 ms    20 ms    21 ms  te1-3-10g.ar2.DCA3.gblx.net [67.17.108.145]
 13    19 ms    17 ms    21 ms  qwest-1.ar2.DCA3.gblx.net [64.208.110.30]
 14   177 ms   171 ms   167 ms  tuk-core-01.inet.qwest.net [67.14.4.106]
 15   187 ms   187 ms   180 ms  tuk-edge-06.inet.qwest.net [205.171.11.22]
 16   187 ms   179 ms   177 ms  72-165-61-138.dia.static.qwest.net [72.165.61.138]

Trace complete.

The missing link is at hop 14, "tuk-core-01.inet.qwest.net [67.14.4.106]"...that wasn't in the trace I did earlier.