VanBuren Posted June 1, 2005 CID Share Posted June 1, 2005 Hsinchu, Taiwan http://ndt-hc.twaren.net:7123 found this NDT server pretty far away for most ppl here post score and traceroute 1 1 ms <10 ms <10 ms ua-213-115-113-2.cust.bredbandsbolaget.se [213.1 15.113.2] 2 1 ms 1 ms <10 ms vlan2.dr2.lul10.se.bredband.com [195.54.119.238] 3 1 ms 1 ms 2 ms vlan3.dr1.lul1.se.bredband.com [195.54.119.233] 4 1 ms <10 ms <10 ms ge1-2.cr1.lul1.se.bredband.com [195.54.120.225] 5 11 ms 11 ms 11 ms pos4-0.cr2.svl1.se.bredband.com [195.54.124.134] 6 11 ms 11 ms 11 ms srp9-0.cr1.svl1.se.bredband.com [195.54.123.177] 7 21 ms 21 ms 21 ms pos6-0.cr2.sto1.se.bredband.com [195.54.123.181] 8 21 ms 21 ms 21 ms pos13-0.cr1.sto2.se.bredband.com [195.54.123.122 ] 9 21 ms 21 ms 21 ms pos14-0.cr2.sto2.se.bredband.com [195.54.123.126 ] 10 38 ms 38 ms 38 ms pos1-0.br1.ams1.se.bredband.com [195.54.123.150] 11 45 ms 45 ms 44 ms ge-1-0-0.br0.amx.nl.rt.ascc.net [195.69.144.184] 12 221 ms 151 ms 152 ms s16-0-0-0.br0.chi.us.rt.ascc.net [140.109.251.12 6] 13 343 ms 347 ms 346 ms s16-6-0-0.br0.tpe.tw.rt.ascc.net [140.109.251.62 ] 14 344 ms 347 ms 347 ms ae-1-10.r1.TaipeiGigaPoP.rt.ascc.net [140.109.25 1.49] 15 336 ms 339 ms 342 ms twaren.taipeigigapop.rt.ascc.net [140.109.251.89 ] 16 344 ms 348 ms 348 ms 10G-10GE-EBT-R1.TPC-ASCCE.twaren.net [211.79.59. 77] 17 344 ms 346 ms 343 ms S16-POS-EBT-R1.HCC-TPC.twaren.net [211.79.59.181 ] 18 348 ms 347 ms 343 ms 211.79.59.194 19 * * * Beg Quote Link to comment Share on other sites More sharing options...
Wesker Posted June 1, 2005 CID Share Posted June 1, 2005 TCP/Web100 Network Diagnostic Tool v5.3.3a click START to begin Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done running 10s outbound test (client to server) . . . . . 241.34Kb/s running 10s inbound test (server to client) . . . . . . 916.06kb/s Your PC is connected to a Cable/DSL modem Information: Other network traffic is congesting the link click START to re-test Tracing route to 213.151.113.2 over a maximum of 30 hops 1 * 10 ms * 65.118.26.1 2 8 ms 7 ms 9 ms 192.168.2.1 3 31 ms 83 ms 55 ms cer-edge-01.inet.qwest.net [67.129.212.121] 4 30 ms 31 ms 30 ms cer-core-01.inet.qwest.net [205.171.139.13] 5 195 ms 173 ms 131 ms chp-brdr-01.inet.qwest.net [205.171.139.146] 6 33 ms 33 ms 44 ms 205.171.1.138 7 32 ms 40 ms 44 ms sl-bb22-chi-2-0.sprintlink.net [144.232.20.20] 8 353 ms 298 ms 307 ms sl-bb21-chi-14-0.sprintlink.net [144.232.26.98] 9 47 ms 53 ms 59 ms sl-bb22-nyc-15-0.sprintlink.net [144.232.9.148] 10 61 ms 52 ms 65 ms sl-bb21-nyc-14-0.sprintlink.net [144.232.7.101] 11 301 ms 216 ms 238 ms sl-gw37-nyc-0-0.sprintlink.net [144.232.13.64] 12 75 ms 75 ms 67 ms sl-cwame-1-0.sprintlink.net [144.223.27.146] 13 60 ms 84 ms 56 ms so-7-0-0-dcr1.was.cw.net [195.2.3.1] 14 141 ms 163 ms 154 ms so-0-0-0-dcr1.par.cw.net [195.2.10.118] 15 442 ms 597 ms 686 ms so-1-0-0-ycr2.bap.cw.net [195.2.2.30] 16 540 ms 152 ms 456 ms ge-1-3-0-zar1.bap.cw.net [208.175.154.147] 17 611 ms 434 ms 466 ms 208.175.154.114 18 293 ms 292 ms 339 ms 212.31.32.10 19 156 ms 156 ms 195 ms 213.151.100.41 20 * * * Request timed out. 21 198 ms 155 ms 158 ms 213.151.100.41 22 * * * Request timed out. 23 168 ms 224 ms 164 ms 213.151.100.41 24 * * * Request timed out. 25 174 ms 187 ms 176 ms 213.151.100.41 26 * * * Request timed out. 27 163 ms 168 ms 171 ms 213.151.100.41 28 * * * Request timed out. 29 188 ms 197 ms 185 ms 213.151.100.41 30 * * * Request timed out. Trace complete. Quote Link to comment Share on other sites More sharing options...
just- Posted June 1, 2005 CID Share Posted June 1, 2005 TCP/Web100 Network Diagnostic Tool v5.3.3a click START to begin Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done running 10s outbound test (client to server) . . . . . 180.39Kb/s running 10s inbound test (server to client) . . . . . . 1.26Mb/s Your PC is connected to a Cable/DSL modem Information: The receive buffer should be 124.244384765625 Kbytes to maximize throughput click START to re-test NeoTrace Trace Version 3.25 - TRIAL Results Target: ndt-hc.twaren.net Date: 6/1/2005 (Wednesday), 9:26:48 PM Nodes: 28 Node Data Node Net Reg IP Address Location Node Name 1 - - 192.168.0.3 Bournemouth Just- 2 1 - 192.168.0.1 Unknown 3 2 - 10.115.0.1 Unknown 4 3 1 80.5.168.1 Poole pool-t2cam1-a-ge92.inet.ntl.com 5 3 1 80.4.225.9 Portsmouth sot3-t2core-a-pos71.inet.ntl.com 6 4 1 62.253.185.49 Wokingham win-bb-a-so-020-0.inet.ntl.com 7 4 1 213.105.172.162 Wokingham win-bb-b-ae0-0.inet.ntl.com 8 4 1 62.253.185.197 Ealing bre-bb-a-so-100-0.inet.ntl.com 9 5 2 213.206.159.37 Southwark sl-gw23-lon-11-0.sprintlink.net 10 5 2 213.206.128.62 Southwark sl-bb23-lon-8-0.sprintlink.net 11 5 2 213.206.128.55 Southwark sl-bb21-lon-13-0.sprintlink.net 12 6 2 144.232.19.69 39.617N, 74.383W sl-bb21-tuk-10-0.sprintlink.net 13 6 2 144.232.20.132 39.617N, 74.383W sl-bb20-tuk-15-0.sprintlink.net 14 6 2 144.232.20.136 39.617N, 74.383W sl-bb20-rly-11-0.sprintlink.net 15 6 2 144.232.25.18 Baltimore sl-bb27-rly-9-0.sprintlink.net 16 6 2 144.232.14.177 Baltimore sl-bb22-rly-10-0.sprintlink.net 17 6 2 144.232.20.186 San Jose sl-bb22-sj-10-0.sprintlink.net 18 6 2 144.232.3.210 San Jose sl-bb25-sj-12-0.sprintlink.net 19 6 - 144.232.20.7 Chicago 20 7 2 144.223.243.86 Sunnyvale sl-chung-1-0.sprintlink.net 21 8 - 203.160.225.61 Taipei 22 8 - 203.160.225.129 Taipei 23 8 - 203.160.227.229 Taipei 24 8 - 203.160.226.42 Taipei 25 9 3 211.79.59.69 24.800N, 120.983E 1g-ge-r1.tpc-tpb.twaren.net 26 9 3 211.79.59.181 24.800N, 120.983E s16-pos-ebt-r1.hcc-tpc.twaren.net 27 9 - 211.79.59.194 24.800N, 120.983E 28 9 3 211.79.59.246 24.800N, 120.983E ndt-hc.twaren.net.twaren.net Quote Link to comment Share on other sites More sharing options...
dn0 Posted June 2, 2005 CID Share Posted June 2, 2005 Not bad: WEB100 Enabled Statistics: Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done running 10s outbound test (client to server) . . . . . 427.83Kb/s running 10s inbound test (server to client) . . . . . . 2.16Mb/s ------ Client System Details ------ OS data: Name = Windows XP, Architecture = x86, Version = 5.1 Java data: Vendor = Sun Microsystems Inc., Version = 1.5.0_02 ------ Web100 Detailed Analysis ------ Cable modem/DSL/T1 link found. Link set to Full Duplex mode No network congestion discovered. Good network cable(s) found Normal duplex operation found. Web100 reports the Round trip time = 213.52 msec; the Packet size = 1460 Bytes; and No packet loss was observed. This connection is receiver limited 83.28% of the time. This connection is network limited 16.68% of the time. Contact your local network administrator to report a network problem Web100 reports TCP negotiated the optional Performance Settings to: RFC 2018 Selective Acknowledgment: ON RFC 896 Nagle Algorithm: ON RFC 3168 Explicit Congestion Notification: OFF RFC 1323 Time Stamping: OFF RFC 1323 Window Scaling: OFF Packet size is preserved End-to-End Server IP addresses are preserved End-to-End Information: Network Address Translation (NAT) box is modifying the Client's IP address Van- Nice upload - better than the download Quote Link to comment Share on other sites More sharing options...
reno Posted June 2, 2005 CID Share Posted June 2, 2005 TCP/Web100 Network Diagnostic Tool v5.3.3a click START to begin Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done running 10s outbound test (client to server) . . . . . 367.00Kb/s running 10s inbound test (server to client) . . . . . . 4.03Mb/s Your PC is connected to a Cable/DSL modem Information: Other network traffic is congesting the link Tracing route to 213.151.113.2 over a maximum of 30 hops 1 5 ms 5 ms 5 ms 10.114.144.1 2 7 ms 6 ms 5 ms fas4-3.bnghnycrn-rtr01.nyroc.rr.com [24.94.34.65 ] 3 25 ms 21 ms 20 ms pos0-0.bnghnycpe-rtr04.nyroc.rr.com [24.94.32.29 ] 4 9 ms 10 ms 12 ms srp8-0.bnghnyplz-rtr02.nyroc.rr.com [24.94.32.90 ] 5 11 ms 10 ms 10 ms srp8-0.bnghnyplz-rtr01.nyroc.rr.com [24.94.32.89 ] 6 17 ms 16 ms 17 ms son0-0-0.syrcnyspp-rtr06.nyroc.rr.com [24.92.224 .57] 7 30 ms 28 ms 27 ms so-2-0-0-0.gar1.Philadelphia1.Level3.net [4.78.1 48.1] 8 33 ms 29 ms 29 ms so-7-0-0.mp2.Philadelphia1.Level3.net [209.247.9 .253] 9 32 ms 32 ms 33 ms ae-0-0.bbr1.NewYork1.Level3.net [64.159.1.41] 10 29 ms 29 ms 30 ms ge-3-0-0-51.gar1.NewYork1.Level3.net [4.68.97.2] 11 41 ms 37 ms 36 ms 65.59.192.14 12 34 ms 37 ms 32 ms so-7-0-0-dcr1.was.cw.net [195.2.3.1] 13 119 ms 114 ms 115 ms so-0-0-0-dcr1.par.cw.net [195.2.10.118] 14 137 ms 138 ms 138 ms so-1-0-0-ycr2.bap.cw.net [195.2.2.30] 15 142 ms 129 ms 131 ms ge-0-3-0-zar1.bap.cw.net [208.175.154.131] 16 130 ms 128 ms 128 ms 208.175.154.114 17 137 ms 137 ms 137 ms 212.31.32.10 18 136 ms 137 ms 146 ms 213.151.100.41 19 * * * Request timed out. 20 138 ms 155 ms 138 ms 213.151.100.41 21 * * * Request timed out. 22 137 ms 138 ms 139 ms 213.151.100.41 23 * * * Request timed out. 24 147 ms 152 ms 137 ms 213.151.100.41 25 * * * Request timed out. 26 137 ms 137 ms 138 ms 213.151.100.41 27 * * * Request timed out. 28 138 ms 137 ms 139 ms 213.151.100.41 29 * * * Request timed out. 30 196 ms 139 ms 137 ms 213.151.100.41 Quote Link to comment Share on other sites More sharing options...
coknuck Posted June 2, 2005 CID Share Posted June 2, 2005 TWAREN Web100 based Network Diagnostic Tool (NDT) Located at Hsinchu,Taiwan; 1000Mbps (Gigabit Ethernet) network connection This java applet was developed to test the reliablity and operational status of your desktop computer and network connection. It does this by sending data between your computer and this remote NDT server. These tests will determine: The slowest link in the end-to-end path (Dial-up modem to 10 Gbps Ethernet/OC-192) The Ethernet duplex setting (full or half); If congestion is limiting end-to-end throughput. It can also identify 2 serious error conditions: Duplex Mismatch Excessive packet loss due to faulty cables. A test takes about 20 seconds. Click on "start" to begin. TCP/Web100 Network Diagnostic Tool v5.3.3a click START to begin Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done running 10s outbound test (client to server) . . . . . 274.83Kb/s running 10s inbound test (server to client) . . . . . . 3.23Mb/s Your PC is connected to a Cable/DSL modem Information: Other network traffic is congesting the link Quote Link to comment Share on other sites More sharing options...
cholla Posted June 2, 2005 CID Share Posted June 2, 2005 I couldn't get my copy & paste to work at this site so I had to do a screen shot .It's working fine at testmy. The link below gives several links to different NDT test sites including the Taiwan one. http://e2epi.internet2.edu/ndt/ndt-server-list.html Quote Link to comment Share on other sites More sharing options...
VanBuren Posted June 2, 2005 Author CID Share Posted June 2, 2005 guys, make sure to use this link http://ndt-hc.twaren.net:7123/ i can see some of you posting scores and trace from another NDT server Located in spain... the topic is "speed to asia" here is my trace to that unknown server VanBuren Quote Link to comment Share on other sites More sharing options...
xs1 Posted June 5, 2005 CID Share Posted June 5, 2005 These java tests never work for me .. 5000/386 TCP/Web100 Network Diagnostic Tool v5.3.3a click START to begin Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done running 10s outbound test (client to server) . . . . . 854.39Kb/s running 10s inbound test (server to client) . . . . . . 2.89Mb/s Your PC is connected to a Cable/DSL modem Information: Other network traffic is congesting the link click START to re-test Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done running 10s outbound test (client to server) . . . . . 850.44Kb/s running 10s inbound test (server to client) . . . . . . 2.71Mb/s Your PC is connected to a Cable/DSL modem Information: Other network traffic is congesting the link click START to re-test Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done running 10s outbound test (client to server) . . . . . 850.44Kb/s running 10s inbound test (server to client) . . . . . . 2.70Mb/s Your PC is connected to a Cable/DSL modem Information: Other network traffic is congesting the link click START to re-test Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done running 10s outbound test (client to server) . . . . . 850.44Kb/s running 10s inbound test (server to client) . . . . . . 2.67Mb/s Your PC is connected to a Cable/DSL modem Information: Other network traffic is congesting the link click START to re-test Tracing route to ndt-hc.twaren.net [211.79.59.246] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 192.168.1.1 2 6 ms 5 ms 5 ms 10.102.192.1 3 8 ms 9 ms 7 ms atm5-0-644.tampflerl-rtr1.tampabay.rr.com [24.92.7.42] 4 8 ms 7 ms 7 ms 65.32.8.133 5 8 ms 7 ms 7 ms pop1-tby-P0-1.atdn.net [66.185.136.169] 6 12 ms 7 ms 9 ms bb1-tby-P0-2.atdn.net [66.185.136.164] 7 26 ms 26 ms 25 ms bb2-atm-P7-0.atdn.net [66.185.152.245] 8 27 ms 25 ms 26 ms pop1-atm-P4-1.atdn.net [66.185.150.3] 9 25 ms 25 ms 26 ms sl-bb23-atl-10-2.sprintlink.net [144.232.8.209] 10 28 ms 25 ms 25 ms sl-bb20-atl-9-0.sprintlink.net [144.232.12.13] 11 26 ms 25 ms 26 ms sl-bb22-atl-14-0.sprintlink.net [144.232.12.146] 12 38 ms 41 ms 40 ms sl-bb23-fw-13-0.sprintlink.net [144.232.8.67] 13 69 ms 68 ms 68 ms sl-bb23-ana-11-2.sprintlink.net [144.232.8.77] 14 77 ms 76 ms 77 ms sl-bb25-sj-9-0.sprintlink.net [144.232.20.159] 15 78 ms 78 ms 78 ms 144.232.20.7 16 77 ms 78 ms 78 ms sl-chung-1-0.sprintlink.net [144.223.243.86] 17 202 ms 200 ms 199 ms 203.160.225.61 18 211 ms 200 ms 198 ms 203.160.225.129 19 205 ms 200 ms 201 ms 203.160.227.229 20 201 ms 201 ms 199 ms 203.160.226.42 21 199 ms 199 ms 198 ms 1G-GE-R1.TPC-TPB.twaren.net [211.79.59.69] 22 201 ms 200 ms 208 ms S16-POS-EBT-R1.HCC-TPC.twaren.net [211.79.59.181] 23 202 ms 202 ms 204 ms 211.79.59.194 24 * * * Request timed out. 25 * * * Request timed out. 26 * * * Request timed out. Quote Link to comment Share on other sites More sharing options...
gotmilk Posted June 6, 2005 CID Share Posted June 6, 2005 Whoooooooooooo!!! Not slow for my 2024/128 at all! TCP/Web100 Network Diagnostic Tool v5.3.3a click START to begin Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done running 10s outbound test (client to server) . . . . . 128.07Kb/s running 10s inbound test (server to client) . . . . . . 1.78Mb/s Your PC is connected to a Cable/DSL modem click START to re-test Quote Link to comment Share on other sites More sharing options...
pitbull481 Posted June 6, 2005 CID Share Posted June 6, 2005 here is mine TCP/Web100 Network Diagnostic Tool v5.3.3a click START to begin Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done running 10s outbound test (client to server) . . . . . 764.40Kb/s running 10s inbound test (server to client) . . . . . . 2.36Mb/s Your PC is connected to a Cable/DSL modem Information: Other network traffic is congesting the link click START to re-test Quote Link to comment Share on other sites More sharing options...
pitbull481 Posted June 6, 2005 CID Share Posted June 6, 2005 how i do a trace route? Quote Link to comment Share on other sites More sharing options...
coknuck Posted June 6, 2005 CID Share Posted June 6, 2005 TWAREN Web100 based Network Diagnostic Tool (NDT) Located at Hsinchu,Taiwan; 1000Mbps (Gigabit Ethernet) network connection This java applet was developed to test the reliablity and operational status of your desktop computer and network connection. It does this by sending data between your computer and this remote NDT server. These tests will determine: The slowest link in the end-to-end path (Dial-up modem to 10 Gbps Ethernet/OC-192) The Ethernet duplex setting (full or half); If congestion is limiting end-to-end throughput. It can also identify 2 serious error conditions: Duplex Mismatch Excessive packet loss due to faulty cables. A test takes about 20 seconds. Click on "start" to begin. TCP/Web100 Network Diagnostic Tool v5.3.3a click START to re-test Checking for Middleboxes . . . . . . . . . . . . . . . . . . Quote Link to comment Share on other sites More sharing options...
netmasta Posted June 6, 2005 CID Share Posted June 6, 2005 how i do a trace route? Click on Start>>Run... type in cmd in XP or command in Win 9x Type "tracert insert-site-name-here.com" without the "'s to copy it into a post, RIGHT-click, select Mark and highlight the text to be copied and press Enter. Press Ctrl+V to post into a message. Quote Link to comment Share on other sites More sharing options...
pitbull481 Posted June 6, 2005 CID Share Posted June 6, 2005 Here it is. Is this good or bad? Tracing route to ndt-hc.twaren.net [211.79.59.246] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 192.168.1.1 2 * * * Request timed out. 3 10 ms 12 ms 9 ms 68.86.117.229 4 10 ms 9 ms 10 ms 68.87.230.45 5 55 ms 13 ms 9 ms 68.87.230.250 6 11 ms 12 ms 10 ms 12.125.194.9 7 14 ms 34 ms 11 ms 12.123.4.230 8 18 ms 16 ms 18 ms tbr2-cl7.sl9mo.ip.att.net [12.122.10.46] 9 56 ms 57 ms 81 ms tbr2-cl2.la2ca.ip.att.net [12.122.10.14] 10 66 ms 86 ms 57 ms 12.123.28.61 11 107 ms 59 ms 59 ms 12.118.42.14 12 182 ms 185 ms 182 ms 203.160.225.233 13 191 ms 186 ms 183 ms 203.160.228.245 14 185 ms 182 ms 188 ms 203.160.227.229 15 185 ms 185 ms 187 ms 203.160.226.42 16 186 ms 184 ms 188 ms 1G-GE-R1.TPC-TPB.twaren.net [211.79.59.69] 17 186 ms 186 ms 185 ms S16-POS-EBT-R1.HCC-TPC.twaren.net [211.79.59.181 ] 18 187 ms 189 ms 185 ms 211.79.59.194 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. thanx netmasta Quote Link to comment Share on other sites More sharing options...
netmasta Posted June 6, 2005 CID Share Posted June 6, 2005 Usually it's bad when you get " * * * Request timed out." to a site, but most of us have gotten the same results when tracert ing that site. The lower the number of hops and lower ##ms (the time it takes to get from one hop to the next) you have are better. Quote Link to comment Share on other sites More sharing options...
cappy Posted June 7, 2005 CID Share Posted June 7, 2005 TCP/Web100 Network Diagnostic Tool v5.3.3a click START to begin Checking for Middleboxes . . . . . . . . . . . . . . . . . . Quote Link to comment Share on other sites More sharing options...
gotmilk Posted June 8, 2005 CID Share Posted June 8, 2005 Not losing much speed at all considering it's in asia. (I'm on 2024/128) click START to re-test Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done running 10s outbound test (client to server) . . . . . 127.87Kb/s running 10s inbound test (server to client) . . . . . . 1.73Mb/s Your PC is connected to a Cable/DSL modem EDIT: Sorry I forgot I already posted in this topic. Tracing route to ndt-hc.twaren.net [211.79.59.246] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 192.168.0.1 2 * * * Request timed out. 3 7 ms 7 ms 7 ms io1.conwaycorp.net [24.144.0.2] 4 13 ms 10 ms 12 ms 151.164.66.133 5 11 ms 11 ms 13 ms bb1-g2-0.ltrkar.sbcglobal.net [151.164.64.246] 6 25 ms 26 ms 24 ms bb1-p10-0.ksc2mo.sbcglobal.net [151.164.243.193] 7 23 ms 26 ms 25 ms core1-p6-0.crkcmo.sbcglobal.net [151.164.188.62] 8 34 ms 37 ms 35 ms core2-p11-0.crchil.sbcglobal.net [151.164.240.11 8] 9 40 ms 37 ms 35 ms 151.164.240.194 10 37 ms 37 ms 36 ms bb2-p13-0.emhril.ameritech.net [151.164.191.174] 11 38 ms 36 ms 38 ms ex2-p5-0.eqchil.sbcglobal.net [151.164.42.139] 12 40 ms 35 ms 36 ms ex1-p6-0.eqchil.sbcglobal.net [151.164.40.125] 13 38 ms 35 ms 37 ms chi-eqix-peer.twgate.net [206.223.119.51] 14 96 ms 97 ms 96 ms 203.160.228.218 15 95 ms 100 ms 95 ms 203.160.228.189 16 94 ms 95 ms 96 ms la_c124_1.twgate.net [203.160.225.234] 17 95 ms 95 ms 96 ms 203.160.228.194 18 240 ms 241 ms 244 ms S1-GE-CHTI-RI2.HCC-LA.twaren.net [211.79.48.213] 19 241 ms 241 ms 240 ms 211.79.59.194 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. Quote Link to comment Share on other sites More sharing options...
VanBuren Posted June 8, 2005 Author CID Share Posted June 8, 2005 dern nice speed guys, the server is probl tweaked for high ping transfers, but i guess my 350 ms is too much for it to handle my route goes via US and from that to that server so i add approx 120 ms from eastcoast VanBuren Quote Link to comment Share on other sites More sharing options...
cholla Posted June 8, 2005 CID Share Posted June 8, 2005 This is mine done from the link Van Buren gave at the start of the topic. http://ndt-hc.twaren.net:7123/ TWAREN Web100 based Network Diagnostic Tool (NDT) TCP/Web100 Network Diagnostic Tool v5.3.3a click START to begin Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done running 10s outbound test (client to server) . . . . . 118.70Kb/s running 10s inbound test (server to client) . . . . . . 114.12kb/s Your PC is connected to a Cable/DSL modem Information: Other network traffic is congesting the link Information: The receive buffer should be 616.9189453125 Kbytes to maximize throughpu Quote Link to comment Share on other sites More sharing options...
VanBuren Posted June 8, 2005 Author CID Share Posted June 8, 2005 dern cholla you win 2 x your cap to asia, thats amazing VanBuren Quote Link to comment Share on other sites More sharing options...
cholla Posted June 8, 2005 CID Share Posted June 8, 2005 VanBuren: Did you notice it reads my dial-up as this: Your PC is connected to a Cable/DSL modem. It is a 56K modem but I have to take out some tweaks to get the test to read that way.The test will read as a 56K modem though if I tweak down.It won't test as fast though. I wish I could get it to do the same on a testmy test. Quote Link to comment Share on other sites More sharing options...
VanBuren Posted June 8, 2005 Author CID Share Posted June 8, 2005 yea, its probl not very accurate too, those test a built to test fat fiber connections VanBuren Quote Link to comment Share on other sites More sharing options...
wingzero2309 Posted June 14, 2005 CID Share Posted June 14, 2005 TCP/Web100 Network Diagnostic Tool v5.3.3a click START to begin Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done running 10s outbound test (client to server) . . . . . 437.03Kb/s running 10s inbound test (server to client) . . . . . . 3.14Mb/s Your PC is connected to a Cable/DSL modem Information: Other network traffic is congesting the link Tracing route to ndt-hc.twaren.net [211.79.59.246] over a maximum of 30 hops: 1 13 ms 1 ms 1 ms 192.168.1.1 2 9 ms 7 ms 8 ms 10.38.0.1 3 8 ms 8 ms 6 ms srp4-0.austtxc-rtr1.austin.rr.com [66.68.2.238] 4 11 ms 10 ms 9 ms srp0-0.austtxrdc-rtr2.austin.rr.com [66.68.1.253 ] 5 8 ms 7 ms 16 ms pos1-0.austtxrdc-rtr4.texas.rr.com [66.68.1.110] 6 17 ms 16 ms 15 ms son0-0-0.hstqtxl3-rtr1.texas.rr.com [24.93.33.15 3] 7 16 ms 15 ms 15 ms pop1-hou-P0-3.atdn.net [66.185.133.149] 8 17 ms 19 ms 15 ms bb1-hou-P2-0.atdn.net [66.185.150.148] 9 22 ms 21 ms 21 ms bb1-dls-P6-0.atdn.net [66.185.152.132] 10 21 ms 22 ms 20 ms pop1-dls-P0-0.atdn.net [66.185.133.81] 11 18 ms 19 ms 17 ms ATT.atdn.net [66.185.134.38] 12 50 ms 48 ms 48 ms tbr1-p012101.dlstx.ip.att.net [12.123.17.82] 13 49 ms 47 ms 50 ms tbr1-cl2.la2ca.ip.att.net [12.122.10.50] 14 48 ms 46 ms 45 ms 12.123.28.57 15 50 ms 46 ms 47 ms 12.118.42.14 16 46 ms 92 ms 47 ms 203.160.228.194 17 194 ms 193 ms 194 ms S1-GE-CHTI-RI2.HCC-LA.twaren.net [211.79.48.213] 18 194 ms 194 ms 195 ms 211.79.59.194 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. Quote Link to comment Share on other sites More sharing options...
TriRan Posted June 22, 2005 CID Share Posted June 22, 2005 TCP/Web100 Network Diagnostic Tool v5.3.3a click START to begin Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done running 10s outbound test (client to server) . . . . . 398.53Kb/s running 10s inbound test (server to client) . . . . . . 1.23Mb/s Your PC is connected to a Cable/DSL modem Information: The receive buffer should be 140.181884765625 Kbytes to maximize throughput click START to re-test Tracing route to ndt-hc.twaren.net [211.79.59.246] over a maximum of 30 hops: 1 1 ms <1 ms <1 ms 192.168.2.1 2 * 15 ms 16 ms customer115_254.grm.net [216.139.115.254] 3 15 ms 16 ms 18 ms customer110_117.grm.net [216.139.110.117] 4 20 ms 18 ms 21 ms 65.255.143.9 5 81 ms 18 ms 18 ms f13.ba01.b005948-0.mci01.atlas.cogentco.com [38. 112.3.9] 6 17 ms 16 ms 20 ms g0-1.core01.mci01.atlas.cogentco.com [66.28.5.89 ] 7 31 ms 30 ms 73 ms p5-0.core02.ord01.atlas.cogentco.com [66.28.4.34 ] 8 54 ms 57 ms 56 ms p6-0.core02.jfk02.atlas.cogentco.com [66.28.4.85 ] 9 55 ms 57 ms 56 ms p15-0.core01.jfk02.atlas.cogentco.com [66.28.4.1 3] 10 96 ms 96 ms 95 ms ny-paix-gni.twgate.net [198.32.118.41] 11 92 ms 99 ms 95 ms 203.160.228.98 12 247 ms 274 ms 247 ms S4-GE-CHTI-RI1.TNC-NY.twaren.net [211.79.48.201] 13 248 ms 251 ms 255 ms S16-POS-EBT-R1.HCC-TNC.twaren.net [211.79.59.185 ] 14 250 ms 251 ms 253 ms 211.79.59.194 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. seems to have went overseas on hop 12 man thats a pretty big time for dsl Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.