Re: Speedstream 4100 any other firmware!

Author	All Replies
RadioDoc Sortofadog Premium,ExMod 2000-03 join:2000-05-11 Chicago, IL ·AT&T Midwest edit: May 8th, @11:56AM	reply to Nonis Re: Speedstream 4100 any other firmware! 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.
	to forum · permalink · · 2008-05-08 11:55:28 ·
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	to forum · permalink · 2008-05-08 18:10:48 ·


Thursday, 08-Jan 01:28:51	Terms of Use \| Privacy Policy \| Hosting by www.nac.net - DSL,Hosting & Co-lo \| feedback \| contact over 9 years online! © 1999-2009 dslreports.com. page compression OFF