 MacLeechThe one and onlyPremium join:2001-07-14 SoCal kudos:3 | reply to kevlogan
Re: [TWC] TW SoCal roller coaster speeds UPDATE What's the results of your tweaks test? »/tweaks |
|
 BW9 join:2000-05-29 Beverly Hills, CA | 
This appears to be what my "normal" Turbo is for the moment. Just want to take a moment to thank all those who took time to respond to my original post. MacLeech: I, for one, do appreciate your contributions to the forum. There's comfort, no matter how small, in knowing there's at least one person inside TW who seems to care about their service and will put himself in the line of fire. |
|
 | reply to MacLeech I'm using vista and it said it's not advisable to run the tweaks test.
Here is my latest:

This I can live with. It just seems to be so random. When I upgraded to Turbo should I have gotten a different modem? Right now I have the Motorola SB5101 |
|
|
|
 MacLeechThe one and onlyPremium join:2001-07-14 SoCal kudos:3 2 edits | said by kevlogan: It just seems to be so random. When I upgraded to Turbo should I have gotten a different modem? Right now I have the Motorola SB5101 The Moto 5101 will run Turbo just fine. Adelphia was using them for 16/2 without issue (if the firmware was higher then 1.1.1.1 some shipped with).
If you log into the the RR account management page, what Bandwidth class does it say you're configured with? »provselfcare.orange.rr.com/
BTW, The tweaks page says "Vista TCP tuning (tweaking) is NOT advisable" but I'd still like to see the results of the test. It's the actual tweaking that's not advised, not the testing. |
|
 | Mac,
First off, thank you for taking the time to help me. I really appreciate it. Here are the results of the tweak test:
1. Your Tweakable SettingsReceive Window (RWIN): 261340 Window Scaling: 2 Path MTU Discovery: ON RFC1323 Window Scaling: ON RFC1323 Time Stamping: OFF Selective Acks: ON MSS requested: 1460 TTL: unknown TTL remaining: 111 TOS flags: none set
2. Test DownloadActual data bytes sent: 1024001 Actual data packets: 703 Max packet sent (MTU): 1500 Max packet recd (MTU): 1500 Retransmitted packets: 0 sacks you sent: 0 pushed data pkts: 107 data transmit time: 5.225 secs our max idletime: 230.9 ms transfer rate: 182165 bytes/sec transfer rate: 1457 kbits/sec transfer efficiency: 100%
3. ICMP (ping) check Target unpingable
If your IP could be pinged then we hit it with various streams to identify any loss, or exessive jitter from our server.
4. Notes and Recommendations Choose RWIN between 94900 and 251120 (FAQ #586) Vista has no tunable TCP settings Read the tweak FAQ
Observations: Good data stream (no/few rexmits)
Observations: Become pingable if you need basic packet loss tests done Check tweak FAQ
When I went to login to the RR Account Maintenance page the only option it gave me was to change password. I will try again later and let you know what my modem is provisioned for.
Thanks again! |
|
 MacLeechThe one and onlyPremium join:2001-07-14 SoCal kudos:3 | The tweak test results are good. Nothing unusual.
Can you post a tracert to 209.244.0.3 ?
How are pings to your 2nd hop from that trace?
Run "ping -n 100 ip address" and post the final results please. |
|
 1 edit | Modem Info:
Twenty-five (25) users authorized for Account Road Runner ISP Modem Support for one (1) IP Address Class of Service 3 Bandwidth service class (020)
Trace Results:
Pinging 209.244.0.3 with 32 bytes of data: Reply from 209.244.0.3: bytes=32 time=61ms TTL=53 Reply from 209.244.0.3: bytes=32 time=83ms TTL=53 Reply from 209.244.0.3: bytes=32 time=106ms TTL=53 Reply from 209.244.0.3: bytes=32 time=27ms TTL=53 Reply from 209.244.0.3: bytes=32 time=50ms TTL=53 Reply from 209.244.0.3: bytes=32 time=73ms TTL=53 Reply from 209.244.0.3: bytes=32 time=96ms TTL=53 Reply from 209.244.0.3: bytes=32 time=119ms TTL=53 Reply from 209.244.0.3: bytes=32 time=41ms TTL=53 Reply from 209.244.0.3: bytes=32 time=63ms TTL=53 Reply from 209.244.0.3: bytes=32 time=86ms TTL=53 Reply from 209.244.0.3: bytes=32 time=109ms TTL=53 Reply from 209.244.0.3: bytes=32 time=31ms TTL=53 Reply from 209.244.0.3: bytes=32 time=57ms TTL=53 Reply from 209.244.0.3: bytes=32 time=78ms TTL=53 Reply from 209.244.0.3: bytes=32 time=100ms TTL=53 Reply from 209.244.0.3: bytes=32 time=74ms TTL=53 Reply from 209.244.0.3: bytes=32 time=97ms TTL=53 Reply from 209.244.0.3: bytes=32 time=120ms TTL=53 Reply from 209.244.0.3: bytes=32 time=40ms TTL=53 Reply from 209.244.0.3: bytes=32 time=63ms TTL=53 Reply from 209.244.0.3: bytes=32 time=86ms TTL=53 Reply from 209.244.0.3: bytes=32 time=109ms TTL=53 Reply from 209.244.0.3: bytes=32 time=27ms TTL=53 Reply from 209.244.0.3: bytes=32 time=49ms TTL=53 Reply from 209.244.0.3: bytes=32 time=72ms TTL=53
 |
|
 | reply to MacLeech said by MacLeech:The tweak test results are good. Nothing unusual. Can you post a tracert to 209.244.0.3 ? How are pings to your 2nd hop from that trace? Run "ping -n 100 ip address" and post the final results please. I think he means for you to tracert 209.244.0.3
THEN ping the 2nd hop that shows up in tracert. You should post this information so that he doesn't have to ask you for it then you have to wait more time before he can help you out. |
|