Slow Dsl Help
- joecool169
- Posts: 805
- Joined: Fri Nov 16, 2001 10:52 pm
- Location: Ohio
Slow Dsl Help
I got dsl a week ago and don't get me wrong it is fast.But I am paying for 1.5Mb and 128Kb but the most I see from downloads is 30 KB and I thought it should be 90-120KB. I got download accelerator plus which logs into multiple servers up to 7.I talked to my ISP who said they were going to put me on a different circuit? They do not know how long that will take. Verizon my phone provider not my ISP says that I'm sharing a T1 at the local office with 5 users. I thought a T1 was 1.5Mb so if I share it with 5 people yeah you do the math. Let me know if any of this makes sense to you or you can help thanks
Joe
-
- Senior Member
- Posts: 4438
- Joined: Wed Jun 07, 2000 12:00 pm
- Location: Columbus, Ohio
Welcome to Speedguide!
I'm going to move this over to the tweaking forum. Please add another message, let them know what town you are in, who your ISP is, and what protocol you are using, which is probably PPPoE.
The likelyhood that your phone company knows what your ISP is doing is pretty small. 5 people on 1 T1 is not that bad. Most Cable modem and DSL providers maintain a bandwidth to the internet of something like 10-20kbits per customer. That's great when you have 10,000 customers on 100 to 200 megabits, but not good if you are in a small town where they are just starting up, and the law of averages doesn't do much for you.
How's your passing accuracy? Open tryouts for the Buckeyes tomorrow. I think the new QB is from somewhere around your area.
Kip
I'm going to move this over to the tweaking forum. Please add another message, let them know what town you are in, who your ISP is, and what protocol you are using, which is probably PPPoE.
The likelyhood that your phone company knows what your ISP is doing is pretty small. 5 people on 1 T1 is not that bad. Most Cable modem and DSL providers maintain a bandwidth to the internet of something like 10-20kbits per customer. That's great when you have 10,000 customers on 100 to 200 megabits, but not good if you are in a small town where they are just starting up, and the law of averages doesn't do much for you.
How's your passing accuracy? Open tryouts for the Buckeyes tomorrow. I think the new QB is from somewhere around your area.
Kip
- joecool169
- Posts: 805
- Joined: Fri Nov 16, 2001 10:52 pm
- Location: Ohio
-
- Senior Member
- Posts: 4438
- Joined: Wed Jun 07, 2000 12:00 pm
- Location: Columbus, Ohio
- joecool169
- Posts: 805
- Joined: Fri Nov 16, 2001 10:52 pm
- Location: Ohio
TCP options string = 0204059001010402
MTU = 1464
MTU is not fully optimized for broadband. Consider increasing your MTU to 1500 for better throughput.
MSS = 1424
Maximum useful data in each packet = 1424, which is equal to MSS.
MSS is not fully optimized for broadband (although it might work well for slower connections). Consider increasing your MTU value.
Default Receive Window (RWIN) = 65504
RWIN Scaling (RFC1323) = 0 bits
Unscaled Receive Window = 65504
RWIN is a multiple of MSS
Other values for RWIN that might work well with your current MTU/MSS:
524032 (MSS x 46 * scale factor of 8)
262016 (MSS x 46 * scale factor of 4)
131008 (MSS x 46 * scale factor of 2)
bandwidth * delay product:
Your RcvWindow limits you to: 2620.16 kbps (327.52 KBytes/s) @ 200ms
Your RcvWindow limits you to: 1048.064 kbps (131.008 KBytes/s) @ 500ms
MTU Discovery (RFC1191) = ON
Time to live left = 114 hops
TTL value is ok.
Timestamps (RFC1323) = OFF
Selective Acknowledgements (RFC2018) = ON
IP type of service field (RFC1349)= 00000000
MTU = 1464
MTU is not fully optimized for broadband. Consider increasing your MTU to 1500 for better throughput.
MSS = 1424
Maximum useful data in each packet = 1424, which is equal to MSS.
MSS is not fully optimized for broadband (although it might work well for slower connections). Consider increasing your MTU value.
Default Receive Window (RWIN) = 65504
RWIN Scaling (RFC1323) = 0 bits
Unscaled Receive Window = 65504
RWIN is a multiple of MSS
Other values for RWIN that might work well with your current MTU/MSS:
524032 (MSS x 46 * scale factor of 8)
262016 (MSS x 46 * scale factor of 4)
131008 (MSS x 46 * scale factor of 2)
bandwidth * delay product:
Your RcvWindow limits you to: 2620.16 kbps (327.52 KBytes/s) @ 200ms
Your RcvWindow limits you to: 1048.064 kbps (131.008 KBytes/s) @ 500ms
MTU Discovery (RFC1191) = ON
Time to live left = 114 hops
TTL value is ok.
Timestamps (RFC1323) = OFF
Selective Acknowledgements (RFC2018) = ON
IP type of service field (RFC1349)= 00000000
Joe
When your service provider is refering to different circuit they may mean different "Pair". The phone company tech can look at your pair then check it for noise and then start looking for a pair with less noise. According too our standards 0-20db is acceptable, 20-30 is marginal and 30 db and up is considered unacceptable. If everyone in your neighborhood is hovering around 30 they will consider this acceptable simply because it is all that is available.
- joecool169
- Posts: 805
- Joined: Fri Nov 16, 2001 10:52 pm
- Location: Ohio
A guy at my ISP told me that they meaning my isp movrd all the dsl users to one t1. Whether or not they did I do not know but I just went to dsl reports.com and got 54/121 Kbps and that is typical unless it is 5:00 am. I am thinking of changing isp's because I know I have seen my line achieve 1.5Mbps/256Kbps it just has to be really offpeak times or my connection takes a poop.


Joe
- joecool169
- Posts: 805
- Joined: Fri Nov 16, 2001 10:52 pm
- Location: Ohio
- joecool169
- Posts: 805
- Joined: Fri Nov 16, 2001 10:52 pm
- Location: Ohio
TCP options string = 020405b401010402
MTU = 1500
MTU is fully optimized for broadband.
MSS = 1460
Maximum useful data in each packet = 1460, which is equal to MSS.
Default Receive Window (RWIN) = 65535
RWIN Scaling (RFC1323) = 0 bits
Unscaled Receive Window = 65535
Note: Under Windows 9x, if you have RWIN set to any other value, and the Analyzer reports 65535 you might need to install the MS Vtcp386 fix.
For optimum performance, consider changing RWIN to a multiple of MSS.
Other values for RWIN that might work well with your current MTU/MSS:
513920 (MSS x 44 * scale factor of 8)
256960 (MSS x 44 * scale factor of 4)
128480 (MSS x 44 * scale factor of 2)
64240 (MSS x 44)
bandwidth * delay product:
Your RcvWindow limits you to: 2621.4 kbps (327.675 KBytes/s) @ 200ms
Your RcvWindow limits you to: 1048.56 kbps (131.07 KBytes/s) @ 500ms
MTU Discovery (RFC1191) = ON
Time to live left = 34 hops
TTL value is ok.
Timestamps (RFC1323) = OFF
Selective Acknowledgements (RFC2018) = ON
IP type of service field (RFC1349)= 00000000
Still a bit slow on the downloads
MTU = 1500
MTU is fully optimized for broadband.
MSS = 1460
Maximum useful data in each packet = 1460, which is equal to MSS.
Default Receive Window (RWIN) = 65535
RWIN Scaling (RFC1323) = 0 bits
Unscaled Receive Window = 65535
Note: Under Windows 9x, if you have RWIN set to any other value, and the Analyzer reports 65535 you might need to install the MS Vtcp386 fix.
For optimum performance, consider changing RWIN to a multiple of MSS.
Other values for RWIN that might work well with your current MTU/MSS:
513920 (MSS x 44 * scale factor of 8)
256960 (MSS x 44 * scale factor of 4)
128480 (MSS x 44 * scale factor of 2)
64240 (MSS x 44)
bandwidth * delay product:
Your RcvWindow limits you to: 2621.4 kbps (327.675 KBytes/s) @ 200ms
Your RcvWindow limits you to: 1048.56 kbps (131.07 KBytes/s) @ 500ms
MTU Discovery (RFC1191) = ON
Time to live left = 34 hops
TTL value is ok.
Timestamps (RFC1323) = OFF
Selective Acknowledgements (RFC2018) = ON
IP type of service field (RFC1349)= 00000000
Still a bit slow on the downloads
Joe
I realize this isn't the case with you but I have seen "Load coils" drag bandwidth down as low as 70kbps. One of my tech buddies at work found a load coil on his circuit, his speed had been as low as 125kbps, I think he was able to get it up to about 500kbps after that. Remember, I'm talking LOAD COILS not HEAT COILS. Load COILS were used 70 to 30 years ago, there are still some out there. Heat coils are used for lightning protection at the CO and will not affect your speed.