<?xml version="1.0" encoding="UTF-8"?>

<rss version="2.0" xmlns:blogChannel="http://backend.userland.com/blogChannelModule">

<channel>
<title>Re: Speedstream 4100 any other firmware! in AT&#x26;T Midwest</title>
<link>http://www.dslreports.com/forum/r20453034</link>
<description></description>
<language>en</language>
<pubDate>Thu, 21 Aug 2008 01:07:07 EDT</pubDate>
<lastBuildDate>Thu, 21 Aug 2008 01:07:07 EDT</lastBuildDate>

<item>
<title>Re: Speedstream 4100 any other firmware!</title>
<link>http://www.dslreports.com/forum/remark,20498897</link>
<description><![CDATA[<A HREF="/useremail/u/1175917"><b>k1ll3rdr4g0n</b></A> : <div class="bquote"><small>said by Nonis :</small><br><br>Yeah, I understand what tracert does now. I was instructed to try it by a member of the open tech support forum on battle.net.<br><br>I have tried with no router and PPP on the modem, and I have also tried the modem bridged with PPP on the router and the port forwarded to my IP on the router. Neither have worked.<br> </div>This sounds like a firewall issue to me.<br>Could be wrong, but if you plug directly into the modem there is no reason why it shouldn't work.<br>My suggestion is goto another machine (or laptop) and test it out. This way we can rule out some assumptions. If it works on the other computer/laptop then there is someone bad funny on your computer. If it doesn't work on another computer/laptop, then my guess is that there is something bad funny with the modem. But be sure your game will work on that computer/laptop on another connection before (B4) you test it on yours. Because if it doesn't work on your friend's connection, and you are using that to test on yours...you can't draw any good conclusions. Now, if it still doesn't work, I will point my finger at the modem....but I still doubt that would be the case...unless it got zapped in a storm...and I am even doubting that because if you can do basic webbrowsing then it should be fine.<br><br>I am pointing my finger at a firewall on his machine. Or could be some spyware/adware. It's too early to assume bad funny like spyware/adware but for now I am eyeing the firewall.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,20498897</guid>
<pubDate>Sat, 17 May 2008 17:53:22 EDT</pubDate>
</item>

<item>
<title>Re: Speedstream 4100 any other firmware!</title>
<link>http://www.dslreports.com/forum/remark,20458359</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> : Yeah, I understand what tracert does now. I was instructed to try it by a member of the open tech support forum on battle.net.<br><br>I have tried with no router and PPP on the modem, and I have also tried the modem bridged with PPP on the router and the port forwarded to my IP on the router. Neither have worked.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,20458359</guid>
<pubDate>Fri, 09 May 2008 17:43:35 EDT</pubDate>
</item>

<item>
<title>Re: Speedstream 4100 any other firmware!</title>
<link>http://www.dslreports.com/forum/remark,20457281</link>
<description><![CDATA[<A HREF="/useremail/u/157889"><b>RadioDoc</b></A> : <div class="bquote"><small>said by Nonis :</small><br><br>Oh, so is it normal for it to get stuck at attens for everyone? That would mean that this tracert shows me nothing. ]=<br><br>But it does seem to be a problem with att dsl, because I also have a friend who has ATT dsl with a different modem and has the same problem...<br> </div> They have to actually respond to your ping packet or you won't know they are there.  They don't, so you don't.  It doesn't matter who you are, where you are coming from or what service you use.  Their equipment ignores ping packets.  You're not getting "stuck" anywhere.<br><br>Since thousands of people with AT&T DSL play these games you can pretty much assume whatever issues you are having are on your end.<br><small>--<br>Toolmaster of La Grange.</small>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,20457281</guid>
<pubDate>Fri, 09 May 2008 13:51:16 EDT</pubDate>
</item>

<item>
<title>Re: Speedstream 4100 any other firmware!</title>
<link>http://www.dslreports.com/forum/remark,20457245</link>
<description><![CDATA[<A HREF="/useremail/u/399707"><b>lev</b></A> : Starcraft and Warcraft are both published by Blizzard.<br><br>Putting the modem into bridged mode and having your router handle PPPoE might help the problem.<br><br>Here's one thread talking about that problem.<br><br>&raquo;<A HREF="/forum/r19298607-World-of-Warcraft-Team-Fortress-2-kicks-me-offline">World of Warcraft, Team Fortress 2 kicks me offline!</A><br><br>---<br><br>edit: assuming you have a router]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,20457245</guid>
<pubDate>Fri, 09 May 2008 13:44:06 EDT</pubDate>
</item>

<item>
<title>Re: Speedstream 4100 any other firmware!</title>
<link>http://www.dslreports.com/forum/remark,20457209</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> : Oh, so is it normal for it to get stuck at attens for everyone? That would mean that this tracert shows me nothing. ]=<br><br>But it does seem to be a problem with att dsl, because I also have a friend who has ATT dsl with a different modem and has the same problem...]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,20457209</guid>
<pubDate>Fri, 09 May 2008 13:39:45 EDT</pubDate>
</item>

<item>
<title>Re: Speedstream 4100 any other firmware!</title>
<link>http://www.dslreports.com/forum/remark,20457186</link>
<description><![CDATA[<A HREF="/useremail/u/157889"><b>RadioDoc</b></A> : Battle.net does not respond to pings.  That includes whatever they have attached to those subdomain names.  Running a trace to their servers is not going to tell you much of anything.<br><br>Here are a few other traceroutes, not on AT&T DSL and in fact from disparate data centers, to prove my point:<br><pre><br>tantale.fifi.org &#9;0% &#9;1 &#9;1 &#9;0.30 &#9;0.30 &#9;0.30<br>router-in.fifi.org &#9;0% &#9;1 &#9;1 &#9;5.34 &#9;5.34 &#9;5.34<br>er1.sfo1.speakeasy.net &#9;0% &#9;1 &#9;1 &#9;16.61 &#9;16.61 &#9;16.61<br>220.ge-0-1-0.cr2.sfo1.speakeasy.net &#9;0% &#9;1 &#9;1 &#9;30.61 &#9;30.61 &#9;30.61<br>pax-edge-01.inet.qwest.net &#9;0% &#9;1 &#9;1 &#9;33.56 &#9;33.56 &#9;33.56<br>svl-core-02.inet.qwest.net &#9;0% &#9;1 &#9;1 &#9;26.54 &#9;26.54 &#9;26.54<br>??? &#9;100% &#9;0 &#9;1 &#9;0.00 &#9;0.00 &#9;0.00<br>sjp-brdr-01.inet.qwest.net &#9;0% &#9;1 &#9;1 &#9;21.78 &#9;21.78 &#9;21.78<br>qwest-gw.sffca.ip.att.net &#9;0% &#9;1 &#9;1 &#9;45.76 &#9;45.76 &#9;45.76<br>tbr2.sffca.ip.att.net &#9;0% &#9;1 &#9;1 &#9;113.90 &#9;113.90 &#9;113.90<br>cr1.sffca.ip.att.net &#9;0% &#9;1 &#9;1 &#9;87.83 &#9;87.83 &#9;87.83<br>cr1.cgcil.ip.att.net &#9;0% &#9;1 &#9;1 &#9;96.82 &#9;96.82 &#9;96.82<br>cr1.cl2oh.ip.att.net &#9;0% &#9;1 &#9;1 &#9;98.81 &#9;98.81 &#9;98.81<br>cr2.cl2oh.ip.att.net &#9;0% &#9;1 &#9;1 &#9;90.90 &#9;90.90 &#9;90.90<br>cr2.phlpa.ip.att.net &#9;0% &#9;1 &#9;1 &#9;91.86 &#9;91.86 &#9;91.86<br>cr1.wswdc.ip.att.net &#9;0% &#9;1 &#9;1 &#9;101.91 &#9;101.91 &#9;101.91<br>tbr1.wswdc.ip.att.net &#9;0% &#9;1 &#9;1 &#9;93.87 &#9;93.87 &#9;93.87<br>12.123.8.33 &#9;0% &#9;1 &#9;1 &#9;108.81 &#9;108.81 &#9;108.81<br>12-122-254-98.attens.net &#9;0% &#9;1 &#9;1 &#9;90.94 &#9;90.94 &#9;90.94<br>mdf001c7613r0003-gig-10-1.wdc1.attens.net &#9;0% &#9;1 &#9;1 &#9;89.71 &#9;89.71 &#9;89.71<br>??? &#9;100% &#9;0 &#9;1 &#9;0.00 &#9;0.00 &#9;0.00<br> <br>TraceRoute to 63.240.202.138 [useast.battle.net]<br>Hop&#9;(ms)&#9;(ms)&#9;(ms)&#9;&#9;IP Address&#9;Host name<br>1&#9;451&#9;542&#9;418&#9;&#9;72.249.0.65&#9;-<br>2&#9;387&#9;461&#9;416&#9;&#9;8.9.232.73&#9;ge-6-18.car1.dallas1.level3.net<br>3&#9;382&#9;386&#9;508&#9;&#9;4.68.19.197&#9;ae-43-99.car3.dallas1.level3.net<br>4&#9;420&#9;491&#9;373&#9;&#9;192.205.34.137&#9;level3-gw.dlstx.ip.att.net<br>5&#9;583&#9;566&#9;406&#9;&#9;12.123.16.206&#9;tbr2.dlstx.ip.att.net<br>6&#9;401&#9;458&#9;496&#9;&#9;12.122.18.213&#9;cr2.dlstx.ip.att.net<br>7&#9;417&#9;519&#9;512&#9;&#9;12.122.28.173&#9;cr1.attga.ip.att.net<br>8&#9;408&#9;547&#9;618&#9;&#9;12.122.1.174&#9;cr2.wswdc.ip.att.net<br>9&#9;522&#9;487&#9;508&#9;&#9;12.122.16.126&#9;tbr2.wswdc.ip.att.net<br>10&#9;594&#9;526&#9;610&#9;&#9;12.123.8.37&#9;-<br>11&#9;633&#9;616&#9;545&#9;&#9;12.122.254.98&#9;12-122-254-98.attens.net<br>12&#9;645&#9;608&#9;570&#9;&#9;63.240.193.10&#9;mdf001c7613r0003-gig-10-1.wdc1.attens.net<br>13&#9;Timed out&#9;Timed out&#9;Timed out&#9;&#9;&#9;-<br>14&#9;Timed out&#9;Timed out&#9;Timed out&#9;&#9;&#9;-<br>15&#9;Timed out&#9;Timed out&#9;Timed out&#9;&#9;&#9;-<br> <br>Warning: multiple IP addresses found for useast.battle.net, using 63.240.202.131<br> <br>tracing path from www.net.princeton.edu to 63.240.202.131 ...<br> <br>traceroute to 63.240.202.131 (63.240.202.131), 30 hops max, 40 byte packets<br> 1  gigagate1 (128.112.128.114)  0.484 ms  0.553 ms  0.334 ms<br> 2  vgate1 (128.112.12.22)  0.358 ms  0.314 ms  0.347 ms<br> 3  patriotgate (204.153.48.14)  1.074 ms  0.958 ms  0.939 ms<br> 4  12.119.12.97 (12.119.12.97)  3.599 ms  3.766 ms  3.249 ms<br> 5  12.123.219.186 (12.123.219.186)  10.803 ms  9.503 ms  9.702 ms<br> 6  12.122.16.221 (12.122.16.221)  10.514 ms  8.785 ms  8.888 ms<br> 7  12.122.3.38 (12.122.3.38)  8.726 ms  8.938 ms  8.703 ms<br> 8  12.122.16.22 (12.122.16.22)  11.314 ms  9.434 ms  9.452 ms<br> 9  12.123.8.33 (12.123.8.33)  64.217 ms  132.500 ms  223.472 ms<br>10  12-122-254-98.attens.net (12.122.254.98)  209.247 ms  88.885 ms  243.802 ms<br>11  mdf001c7613r0004-gig-12-1.wdc1.attens.net (63.240.193.14)  159.990 ms  24.867 ms  10.3  74 ms<br>12  * * *<br></pre><br>Sorry, but you don't seem to have even a marginal grasp on how this all works.  That makes it very difficult to begin to troubleshoot.<br><br><small>--<br>Toolmaster of La Grange.</small><br>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,20457186</guid>
<pubDate>Fri, 09 May 2008 13:35:28 EDT</pubDate>
</item>

<item>
<title>Re: Speedstream 4100 any other firmware!</title>
<link>http://www.dslreports.com/forum/remark,20457040</link>
<description><![CDATA[<A HREF="/useremail/u/399707"><b>lev</b></A> : I just tracerouted to useast.battle.net from a T1 hosted machine in Texas that has nothing to do with AT&T.  Note there is no line-wrapping below; this is the output as I saw it.  Seems there may be other problems along the way.<br><br>----<br><br> 2  vl2.dsr02.dllstx2.theplanet.com (12.96.160.42)  0.608 ms  1.522 ms  0.418 ms<br> 3  79.fd.5746.static.theplanet.com (70.87.253.121)  0.755 ms  1.688 ms  1.654 ms<br> 4  et3-2.ibr04.dllstx3.theplanet.com (70.87.253.25)  0.572 ms  1.665 ms  0.534 ms<br> 5  12.87.41.149 (12.87.41.149)  63.918 ms  3.479 ms  199.868 ms<br>Icmp checksum is wrong<br> 6  tbr2.dlstx.ip.att.net (12.122.100.110)  40.098 msIcmp checksum is wrong<br>  40.090 msIcmp checksum is wrong<br>  41.138 ms<br>Icmp checksum is wrong<br> 7  cr2.dlstx.ip.att.net (12.122.18.197)  40.485 msIcmp checksum is wrong<br>  40.791 msIcmp checksum is wrong<br>  39.432 ms<br>Icmp checksum is wrong<br> 8  cr1.attga.ip.att.net (12.122.28.173)  39.572 msIcmp checksum is wrong<br>  39.756 msIcmp checksum is wrong<br>  40.352 ms<br>Icmp checksum is wrong<br> 9  cr2.wswdc.ip.att.net (12.122.1.174)  40.343 msIcmp checksum is wrong<br>  40.231 msIcmp checksum is wrong<br>  40.147 ms<br>Icmp checksum is wrong<br>10  tbr2.wswdc.ip.att.net (12.122.16.70)  41.489 msIcmp checksum is wrong<br>  40.774 msIcmp checksum is wrong<br>  40.092 ms<br>11  12.123.8.37 (12.123.8.37)  40.033 ms  39.977 ms  40.215 ms<br>12  12-122-254-98.attens.net (12.122.254.98)  40.944 ms  40.928 ms  40.962 ms<br>13  mdf001c7613r0003-gig-10-1.wdc1.attens.net (63.240.193.10)  41.139 ms  40.187 ms  41.093 ms<br>14  * * *]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,20457040</guid>
<pubDate>Fri, 09 May 2008 13:12:17 EDT</pubDate>
</item>

<item>
<title>Re: Speedstream 4100 any other firmware!</title>
<link>http://www.dslreports.com/forum/remark,20453517</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> : I get the same thing when tracerting useast.battle.net<br><br>The battle.net tech support page says that this should be successful.<br><br>My first thoughts were that it wasn't the modem. Other applications work when used on port 6112 (the port that starcraft uses).<br><br>But what else could be the issue? I found out today that my friend who has ATT DSL has the same problem, even though he has a Motorola modem from ATT.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,20453517</guid>
<pubDate>Thu, 08 May 2008 19:27:51 EDT</pubDate>
</item>

<item>
<title>Re: Speedstream 4100 any other firmware!</title>
<link>http://www.dslreports.com/forum/remark,20453458</link>
<description><![CDATA[<A HREF="/useremail/u/157889"><b>RadioDoc</b></A> : That has nothing to do with your modem.  Battle.net does not reply to ping packets.<br><small>--<br>Toolmaster of La Grange.</small>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,20453458</guid>
<pubDate>Thu, 08 May 2008 19:10:55 EDT</pubDate>
</item>

<item>
<title>Re: Speedstream 4100 any other firmware!</title>
<link>http://www.dslreports.com/forum/remark,20453386</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> : I thought that the ATT firmware was gimped and just did not allow those features. That site shows 4100/4200 in the images.<br><br>Anyway, my problem is that I am not able to play starcraft using my ATT DSL. Even plugged directly into the modem, with no static IP. If I tracert google it works, but if I tracert useast.battle.net (the server the game is played on) it gives this:<br><br>Tracing route to battle.net [216.148.223.71]<br>over a maximum of 30 hops:<br>  1     1 ms    1 ms    1 ms  192.168.1.1 <br>  2     9 ms     9 ms     9 ms  adsl-76-230-231-254.dsl.milwwi.sbcglobal.net [76.230.231.254] <br>  3    10 ms    10 ms    10 ms  dist2-vlan60.milwwi.ameritech.net [65.43.19.243] <br>  4    10 ms     9 ms     9 ms  151.164.190.132 <br>  5    12 ms    11 ms    11 ms  151.164.189.80 <br>  6    12 ms    12 ms    11 ms  gar8.cgcil.ip.att.net [12.122.79.89] <br>  7    64 ms    64 ms    64 ms  tbr2.cgcil.ip.att.net [12.122.85.106] <br>  8    63 ms    63 ms    64 ms  cr1.cgcil.ip.att.net [12.122.17.225] <br>  9    63 ms    62 ms    63 ms  cr1.sffca.ip.att.net [12.122.4.121] <br> 10    65 ms    65 ms    64 ms  tbr2.sffca.ip.att.net [12.122.19.90] <br> 11    62 ms    62 ms    62 ms  gar4.sffca.ip.att.net [12.123.13.178] <br> 12    62 ms    62 ms    62 ms  idf22-gsr12-1-pos-6-0.rwc1.attens.net [12.122.255.222] <br> 13   319 ms    62 ms    62 ms  mdf2-bi8k-1-eth-1-1.rwc1.attens.net [216.148.209.10] <br> 14     *        *        *     Request timed out.<br> 15     *        *        *     Request timed out.<br> 16     *        *        *     Request timed out.<br> 17     *        *        *     Request timed out.<br> 18     *        *        *     Request timed out.<br> 19     *        *        *     Request timed out.<br> 20     *        *        *     Request timed out.<br> 21     *        *        *     Request timed out.<br> 22     *        *        *     Request timed out.<br> 23     *        *        *     Request timed out.<br> 24     *        *        *     Request timed out.<br> 25     *        *        *     Request timed out.<br> 26     *        *        *     Request timed out.<br> 27     *        *        *     Request timed out.<br> 28     *        *        *     Request timed out.<br> 29     *        *        *     Request timed out.<br> 30     *        *        *     Request timed out.<br>Trace complete.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,20453386</guid>
<pubDate>Thu, 08 May 2008 18:53:56 EDT</pubDate>
</item>

<item>
<title>Re: Speedstream 4100 any other firmware!</title>
<link>http://www.dslreports.com/forum/remark,20453034</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> : In the screenshots in that link it shows 4100/4200. Anyway, I have read that the SBC version of the firmware is gimped. The problem is that I can't play the game starcraft. It seems to lose packets or something Here's a tracert report:<br><br> Tracing route to useast.battle.net [63.240.202.138]<br><br>over a maximum of 30 hops:<br><br>1 1 ms 1 ms 1 ms 192.168.1.1<br>2 1 ms 1 ms 1 ms 192.168.0.1<br>3 9 ms 9 ms 10 ms adsl-76-229-147-254.dsl.milwwi.sbcglobal.net [76.229.147.254]<br>4 10 ms 9 ms 9 ms dist1-vlan60.milwwi.ameritech.net [65.43.19.242]<br>5 10 ms 10 ms 9 ms bb2-p11-0.milwwi.ameritech.net [151.164.190.98]<br>6 11 ms 11 ms * 151.164.189.80<br>7 11 ms 12 ms 11 ms gar8.cgcil.ip.att.net [12.122.79.89]<br>8 34 ms 34 ms 34 ms tbr1.cgcil.ip.att.net [12.122.85.98]<br>9 34 ms 34 ms 34 ms cr1.cgcil.ip.att.net [12.122.17.161]<br>10 33 ms 34 ms 34 ms cr1.cl2oh.ip.att.net [12.122.2.206]<br>11 34 ms 33 ms 34 ms cr2.cl2oh.ip.att.net [12.122.2.126]<br>12 34 ms 34 ms 34 ms cr2.phlpa.ip.att.net [12.122.2.210]<br>13 34 ms 34 ms 33 ms cr1.wswdc.ip.att.net [12.122.4.54]<br>14 35 ms 34 ms 34 ms tbr1.wswdc.ip.att.net [12.122.16.26]<br>15 32 ms 33 ms 32 ms 12.123.8.33<br>16 34 ms * 37 ms 12-122-254-98.attens.net [12.122.254.98]<br>17 34 ms * 37 ms mdf001c7613r0003-gig-10-1.wdc1.attens.net [63.240.193.10]<br>18 * * * Request timed out.<br>19 * * * Request timed out.<br>20 * * * Request timed out.<br>21 * * * Request timed out.<br>22 * * * Request timed out.<br>23 * * * Request timed out.<br>24 * * * Request timed out.<br>25 * * * Request timed out.<br>26 * * * Request timed out.<br>27 * * * Request timed out.<br>28 * * * Request timed out.<br>29 * * * Request timed out.<br>30 * * * Request timed out.<br><br>Trace complete.<br><br>I don't really understand how tracert works, but someone on Battle.net's tech support told me that it's a port forwarding issue, yet even when I'm plugged straight into the modem it does not work.<br><br>I do not have a static IP set.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,20453034</guid>
<pubDate>Thu, 08 May 2008 18:10:48 EDT</pubDate>
</item>

<item>
<title>Re: Speedstream 4100 any other firmware!</title>
<link>http://www.dslreports.com/forum/remark,20451180</link>
<description><![CDATA[<A HREF="/useremail/u/157889"><b>RadioDoc</b></A> : What "routing capabilities" are you trying to set up?  The 4100 by default sends all inbound traffic to the local port.  Unless you did something it should be working just fine out of the box under its default settings.<br><br>Your link refers to the 4200, which is a router supporting multiple LAN clients and indeed needs the port forwarding configuration so you can tell it what unsolicited inbound traffic goes to which computer.  The 4100 sends everything to 192.168.1.64, which is the only address it gives out on the LAN side, and has no real need for port forwarding as you know it.  Did you set a static address at your computer?<br><small>--<br>Toolmaster of La Grange.</small>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,20451180</guid>
<pubDate>Thu, 08 May 2008 11:55:28 EDT</pubDate>
</item>

<item>
<title>Speedstream 4100 any other firmware!</title>
<link>http://www.dslreports.com/forum/remark,20449716</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> : I have an ATT/SBC speedstream 4100. I can not play starcraft. It is extremely annoying. I think the problem has to do with not being able to set up the routing capabilities of the modem do to the firmware. Is there anywhere I can get any other firmware besides the crippled 1.0.0.53 SBC firmware? Maybe even the firmware in these pictures:<br>&raquo;<A HREF="http://www.portforward.com/english/routers/port_forwarding/Siemens/4100/Starcraft.htm" >www.portforward.com/english/rout&middot;&middot;&middot;raft.htm</A> <br>Thanks!]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,20449716</guid>
<pubDate>Thu, 08 May 2008 01:55:28 EDT</pubDate>
</item>

</channel>
</rss>
