Nonis
@sbcglobal.net
| Speedstream 4100 any other firmware!
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:
»www.portforward.com/english/rout···raft.htm
Thanks! |
|
RadioDoc
Put Out The Cat
Premium,ExMod 2000-03
join:2000-05-11
Chicago, IL
 ·AT&T Midwest
edit:
May 8th, @11:56AM
| 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.
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?
--
Toolmaster of La Grange. |
|
Nonis
@sbcglobal.net
| 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:
Tracing route to useast.battle.net [63.240.202.138]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.1.1
2 1 ms 1 ms 1 ms 192.168.0.1
3 9 ms 9 ms 10 ms adsl-76-229-147-254.dsl.milwwi.sbcglobal.net [76.229.147.254]
4 10 ms 9 ms 9 ms dist1-vlan60.milwwi.ameritech.net [65.43.19.242]
5 10 ms 10 ms 9 ms bb2-p11-0.milwwi.ameritech.net [151.164.190.98]
6 11 ms 11 ms * 151.164.189.80
7 11 ms 12 ms 11 ms gar8.cgcil.ip.att.net [12.122.79.89]
8 34 ms 34 ms 34 ms tbr1.cgcil.ip.att.net [12.122.85.98]
9 34 ms 34 ms 34 ms cr1.cgcil.ip.att.net [12.122.17.161]
10 33 ms 34 ms 34 ms cr1.cl2oh.ip.att.net [12.122.2.206]
11 34 ms 33 ms 34 ms cr2.cl2oh.ip.att.net [12.122.2.126]
12 34 ms 34 ms 34 ms cr2.phlpa.ip.att.net [12.122.2.210]
13 34 ms 34 ms 33 ms cr1.wswdc.ip.att.net [12.122.4.54]
14 35 ms 34 ms 34 ms tbr1.wswdc.ip.att.net [12.122.16.26]
15 32 ms 33 ms 32 ms 12.123.8.33
16 34 ms * 37 ms 12-122-254-98.attens.net [12.122.254.98]
17 34 ms * 37 ms mdf001c7613r0003-gig-10-1.wdc1.attens.net [63.240.193.10]
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
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.
I do not have a static IP set. |
|
Nonis
@sbcglobal.net
| reply to Nonis
I thought that the ATT firmware was gimped and just did not allow those features. That site shows 4100/4200 in the images.
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:
Tracing route to battle.net [216.148.223.71]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.1.1
2 9 ms 9 ms 9 ms adsl-76-230-231-254.dsl.milwwi.sbcglobal.net [76.230.231.254]
3 10 ms 10 ms 10 ms dist2-vlan60.milwwi.ameritech.net [65.43.19.243]
4 10 ms 9 ms 9 ms 151.164.190.132
5 12 ms 11 ms 11 ms 151.164.189.80
6 12 ms 12 ms 11 ms gar8.cgcil.ip.att.net [12.122.79.89]
7 64 ms 64 ms 64 ms tbr2.cgcil.ip.att.net [12.122.85.106]
8 63 ms 63 ms 64 ms cr1.cgcil.ip.att.net [12.122.17.225]
9 63 ms 62 ms 63 ms cr1.sffca.ip.att.net [12.122.4.121]
10 65 ms 65 ms 64 ms tbr2.sffca.ip.att.net [12.122.19.90]
11 62 ms 62 ms 62 ms gar4.sffca.ip.att.net [12.123.13.178]
12 62 ms 62 ms 62 ms idf22-gsr12-1-pos-6-0.rwc1.attens.net [12.122.255.222]
13 319 ms 62 ms 62 ms mdf2-bi8k-1-eth-1-1.rwc1.attens.net [216.148.209.10]
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete. |
|
RadioDoc
Put Out The Cat
Premium,ExMod 2000-03
join:2000-05-11
Chicago, IL | That has nothing to do with your modem. Battle.net does not reply to ping packets.
--
Toolmaster of La Grange. |
|
Nonis
@sbcglobal.net
| reply to Nonis
I get the same thing when tracerting useast.battle.net
The battle.net tech support page says that this should be successful.
My first thoughts were that it wasn't the modem. Other applications work when used on port 6112 (the port that starcraft uses).
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. |
|
lev
Premium,Mod
join:2001-05-30
Chicago, IL
clubs: 
Host:
Efficient
Chicago
AT&T Midwest
| 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.
----
2 vl2.dsr02.dllstx2.theplanet.com (12.96.160.42) 0.608 ms 1.522 ms 0.418 ms
3 79.fd.5746.static.theplanet.com (70.87.253.121) 0.755 ms 1.688 ms 1.654 ms
4 et3-2.ibr04.dllstx3.theplanet.com (70.87.253.25) 0.572 ms 1.665 ms 0.534 ms
5 12.87.41.149 (12.87.41.149) 63.918 ms 3.479 ms 199.868 ms
Icmp checksum is wrong
6 tbr2.dlstx.ip.att.net (12.122.100.110) 40.098 msIcmp checksum is wrong
40.090 msIcmp checksum is wrong
41.138 ms
Icmp checksum is wrong
7 cr2.dlstx.ip.att.net (12.122.18.197) 40.485 msIcmp checksum is wrong
40.791 msIcmp checksum is wrong
39.432 ms
Icmp checksum is wrong
8 cr1.attga.ip.att.net (12.122.28.173) 39.572 msIcmp checksum is wrong
39.756 msIcmp checksum is wrong
40.352 ms
Icmp checksum is wrong
9 cr2.wswdc.ip.att.net (12.122.1.174) 40.343 msIcmp checksum is wrong
40.231 msIcmp checksum is wrong
40.147 ms
Icmp checksum is wrong
10 tbr2.wswdc.ip.att.net (12.122.16.70) 41.489 msIcmp checksum is wrong
40.774 msIcmp checksum is wrong
40.092 ms
11 12.123.8.37 (12.123.8.37) 40.033 ms 39.977 ms 40.215 ms
12 12-122-254-98.attens.net (12.122.254.98) 40.944 ms 40.928 ms 40.962 ms
13 mdf001c7613r0003-gig-10-1.wdc1.attens.net (63.240.193.10) 41.139 ms 40.187 ms 41.093 ms
14 * * * |
|
RadioDoc
Put Out The Cat
Premium,ExMod 2000-03
join:2000-05-11
Chicago, IL
·AT&T Midwest
edit:
May 9th, @01:37PM
| reply to Nonis
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.
Here are a few other traceroutes, not on AT&T DSL and in fact from disparate data centers, to prove my point:
tantale.fifi.org 0% 1 1 0.30 0.30 0.30
router-in.fifi.org 0% 1 1 5.34 5.34 5.34
er1.sfo1.speakeasy.net 0% 1 1 16.61 16.61 16.61
220.ge-0-1-0.cr2.sfo1.speakeasy.net 0% 1 1 30.61 30.61 30.61
pax-edge-01.inet.qwest.net 0% 1 1 33.56 33.56 33.56
svl-core-02.inet.qwest.net 0% 1 1 26.54 26.54 26.54
??? 100% 0 1 0.00 0.00 0.00
sjp-brdr-01.inet.qwest.net 0% 1 1 21.78 21.78 21.78
qwest-gw.sffca.ip.att.net 0% 1 1 45.76 45.76 45.76
tbr2.sffca.ip.att.net 0% 1 1 113.90 113.90 113.90
cr1.sffca.ip.att.net 0% 1 1 87.83 87.83 87.83
cr1.cgcil.ip.att.net 0% 1 1 96.82 96.82 96.82
cr1.cl2oh.ip.att.net 0% 1 1 98.81 98.81 98.81
cr2.cl2oh.ip.att.net 0% 1 1 90.90 90.90 90.90
cr2.phlpa.ip.att.net 0% 1 1 91.86 91.86 91.86
cr1.wswdc.ip.att.net 0% 1 1 101.91 101.91 101.91
tbr1.wswdc.ip.att.net 0% 1 1 93.87 93.87 93.87
12.123.8.33 0% 1 1 108.81 108.81 108.81
12-122-254-98.attens.net 0% 1 1 90.94 90.94 90.94
mdf001c7613r0003-gig-10-1.wdc1.attens.net 0% 1 1 89.71 89.71 89.71
??? 100% 0 1 0.00 0.00 0.00
TraceRoute to 63.240.202.138 [useast.battle.net]
Hop (ms) (ms) (ms) IP Address Host name
1 451 542 418 72.249.0.65 -
2 387 461 416 8.9.232.73 ge-6-18.car1.dallas1.level3.net
3 382 386 508 4.68.19.197 ae-43-99.car3.dallas1.level3.net
4 420 491 373 192.205.34.137 level3-gw.dlstx.ip.att.net
5 583 566 406 12.123.16.206 tbr2.dlstx.ip.att.net
6 401 458 496 12.122.18.213 cr2.dlstx.ip.att.net
7 417 519 512 12.122.28.173 cr1.attga.ip.att.net
8 408 547 618 12.122.1.174 cr2.wswdc.ip.att.net
9 522 487 508 12.122.16.126 tbr2.wswdc.ip.att.net
10 594 526 610 12.123.8.37 -
11 633 616 545 12.122.254.98 12-122-254-98.attens.net
12 645 608 570 63.240.193.10 mdf001c7613r0003-gig-10-1.wdc1.attens.net
13 Timed out Timed out Timed out -
14 Timed out Timed out Timed out -
15 Timed out Timed out Timed out -
Warning: multiple IP addresses found for useast.battle.net, using 63.240.202.131
tracing path from www.net.princeton.edu to 63.240.202.131 ...
traceroute to 63.240.202.131 (63.240.202.131), 30 hops max, 40 byte packets
1 gigagate1 (128.112.128.114) 0.484 ms 0.553 ms 0.334 ms
2 vgate1 (128.112.12.22) 0.358 ms 0.314 ms 0.347 ms
3 patriotgate (204.153.48.14) 1.074 ms 0.958 ms 0.939 ms
4 12.119.12.97 (12.119.12.97) 3.599 ms 3.766 ms 3.249 ms
5 12.123.219.186 (12.123.219.186) 10.803 ms 9.503 ms 9.702 ms
6 12.122.16.221 (12.122.16.221) 10.514 ms 8.785 ms 8.888 ms
7 12.122.3.38 (12.122.3.38) 8.726 ms 8.938 ms 8.703 ms
8 12.122.16.22 (12.122.16.22) 11.314 ms 9.434 ms 9.452 ms
9 12.123.8.33 (12.123.8.33) 64.217 ms 132.500 ms 223.472 ms
10 12-122-254-98.attens.net (12.122.254.98) 209.247 ms 88.885 ms 243.802 ms
11 mdf001c7613r0004-gig-12-1.wdc1.attens.net (63.240.193.14) 159.990 ms 24.867 ms 10.3 74 ms
12 * * *
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.
--
Toolmaster of La Grange. |
|
Nonis
@sbcglobal.net
| reply to Nonis
Oh, so is it normal for it to get stuck at attens for everyone? That would mean that this tracert shows me nothing. ]=
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... |
|
lev
Premium,Mod
join:2001-05-30
Chicago, IL
clubs:
Host:
Efficient
Chicago
AT&T Midwest
edit:
May 9th, @01:45PM
| Starcraft and Warcraft are both published by Blizzard.
Putting the modem into bridged mode and having your router handle PPPoE might help the problem.
Here's one thread talking about that problem.
»World of Warcraft, Team Fortress 2 kicks me offline!
---
edit: assuming you have a router |
|
RadioDoc
Put Out The Cat
Premium,ExMod 2000-03
join:2000-05-11
Chicago, IL
·AT&T Midwest
| reply to Nonis
said by Nonis :
Oh, so is it normal for it to get stuck at attens for everyone? That would mean that this tracert shows me nothing. ]=
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...
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.
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.
--
Toolmaster of La Grange. |
|
Nonis
@sbcglobal.net
| reply to Nonis
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.
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. |
|
