View Full Version : Yet Another Thread Asking For Help
doomsweek
01-24-08, 05:40 PM
Hello, I need help in tweaking my DSL connection. I'm from the Philippines and have a 387kbs plan from Globlines. The modem they provided me is a H9200 from Prolink and seems like I have the up to date firmware for it.
« SpeedGuide.net TCP Analyzer Results »
Tested on: 01.24.2008 17:37
IP address: 222.127.xxx.x
TCP options string: 0204058401010402
MSS: 1412
MTU: 1452
TCP Window: 33888 (multiple of MSS)
RWIN Scaling: 0
Unscaled RWIN : 33888
Reccomended RWINs: 64952, 129904, 259808, 519616
BDP limit (200ms): 1356kbps (169KBytes/s)
BDP limit (500ms): 542kbps (68KBytes/s)
MTU Discovery: ON
TTL: 44
Timestamps: OFF
SACKs: ON
IP ToS: 01010000 (80)
Precedence: 010 (immediate)
Delay: 1 (low delay)
Throughput: 0 (normal throughput)
Reliability: 0 (normal reliability)
Cost: 0 (normal cost)
Check bit: 0 (correct)
DiffServ: AF22 010100 (20) - Assured Forwarding class 2, medium drop precedence (RFC 2597).
Speed Test Result
http://www.speedtest.net/result/226187716.png (http://www.speedtest.net)
trogers
01-24-08, 08:13 PM
Do a tracert to www.yahoo.com and post.
doomsweek
01-24-08, 08:38 PM
Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.
C:\>tracert www.yahoo.com
Tracing route to www.yahoo-ht3.akadns.net [209.131.36.158]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms 192.168.1.1
2 18 ms 18 ms 19 ms 203.177.204.1
3 17 ms 17 ms 17 ms 222.127.228.33
4 * 94 ms 94 ms 124.6.148.229
5 201 ms 200 ms 200 ms so-1-2-0.gw4.mnl1.asianetcom.net [203.192.188.13
]
6 200 ms 201 ms 200 ms po1-0-0.cr1.nrt1.asianetcom.net [202.147.24.214]
7 198 ms 199 ms 199 ms po1-0.gw1.sjc1.asianetcom.net [202.147.50.133]
8 * * * Request timed out.
9 199 ms 203 ms 199 ms g-1-0-0-p160.msr1.sp1.yahoo.com [216.115.107.61]
10 201 ms 205 ms * te-8-1.bas-a2.sp1.yahoo.com [209.131.32.19]
11 200 ms 201 ms 199 ms f1.www.vip.sp1.yahoo.com [209.131.36.158]
Trace complete.
C:\>
trogers
01-24-08, 08:42 PM
Have you clean up your registry and scan for malware?
doomsweek
01-24-08, 08:48 PM
Yes, used CCleaner and Regcleaner.
*EDIT* Spybot S&D too.
trogers
01-24-08, 08:53 PM
Yes, used CCleaner and Regcleaner.
Scan for malware? Use AVG antispyware, SpyBot and Ad-Aware 2007.
doomsweek
01-24-08, 08:58 PM
I forgot to post that I also used Spybot today. Downloading AVG Antispyware at the moment.
doomsweek
01-24-08, 11:40 PM
Already got rid of any spy-ware that were detected by Spybot and AVG Anti spy-ware.
trogers
01-24-08, 11:43 PM
Your TCP settings are correct. Reboot comp and testing speed.
doomsweek
01-25-08, 02:13 AM
http://www.speedtest.net/result/226306600.png
Might be because it's peak time right now here.
doomsweek
01-25-08, 04:41 PM
After resetting the modem because of some config issues, it seems that the MTU has changed. I tried to change it back to 1492, but it returns to being 1392 after the modem successfully connects to the internet. Here are the results.
« SpeedGuide.net TCP Analyzer Results »
Tested on: 01.25.2008 16:40
IP address: 222.127.xxx.x
TCP options string: 0204054801010402
MSS: 1352
MTU: 1392
TCP Window: 33888 (NOT multiple of MSS)
RWIN Scaling: 0
Unscaled RWIN : 33888
Reccomended RWINs: 64896, 129792, 259584, 519168
BDP limit (200ms): 1356kbps (169KBytes/s)
BDP limit (500ms): 542kbps (68KBytes/s)
MTU Discovery: ON
TTL: 44
Timestamps: OFF
SACKs: ON
IP ToS: 01010000 (80)
Precedence: 010 (immediate)
Delay: 1 (low delay)
Throughput: 0 (normal throughput)
Reliability: 0 (normal reliability)
Cost: 0 (normal cost)
Check bit: 0 (correct)
DiffServ: AF22 010100 (20) - Assured Forwarding class 2, medium drop precedence (RFC 2597).
http://www.speedtest.net/result/226571320.png (http://www.speedtest.net)
trogers
01-25-08, 08:09 PM
Set TCP Window to 32448
doomsweek
01-26-08, 04:33 PM
http://www.speedtest.net/result/226942123.png (http://www.speedtest.net)
trogers
01-26-08, 10:04 PM
http://www.speedtest.net/result/226942123.png (http://www.speedtest.net)
The upload speed is now normal where before tweaks it was at 100 kbps.
The download is still lower than 300 kbps, probably due to an overloaded network node of your ISP.
vBulletin® v3.7.3, Copyright ©2000-2008, Jelsoft Enterprises Ltd.