- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
What I should be getting:
Speed(Down/Up): | 3360 / 768 Kbps | |
ISP Protocol: | DHCP |
What I am getting:
[URL=http://www.speedtest.net][IMG]http://www.speedtest.net/result/1777997611.png[/IMG][/URL]
rebooted, everything, checked for issues on my end, cleaned up, switched to google's DNS and nothing is changing.
Your system: Windows 7 version 6.1
Java version: 1.6.0_29 (x86)
TCP receive window: 272896 current, 302080 maximum
7.8064E-4 packets lost during test
Round trip time: 86 msec (minimum), 619 msec (maximum), 324.28 msec (average)
Jitter: 533 msec
0 seconds spend waiting following a timeout
TCP time-out counter: 665
89 selective acknowledgement packets received
No duplex mismatch condition was detected.
The test did not detect a cable fault.
Network congestion may be limiting the connection.
No network address translation appliance was detected.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
more:
<html><head><title>WinMTR Statistics</title></head><body bgcolor="white">
<center><h2>WinMTR statistics</h2></center>
<p align="center"> <table border="1" align="center">
<tr><td>Host</td> <td>%</td> <td>Sent</td> <td>Recv</td> <td>Best</td> <td>Avrg</td> <td>Wrst</td> <td>Last</td></tr>
<tr><td>dslmodem.domain</td> <td> 0</td> <td> 60</td> <td> 60</td> <td> 0</td> <td> 139</td> <td>1323</td> <td> 0</td></tr>
<tr><td>L100.HERNTX-DSL-01.verizon-gni.net</td> <td> 0</td> <td> 60</td> <td> 60</td> <td> 25</td> <td> 234</td> <td>1462</td> <td> 25</td></tr>
<tr><td>at-4-2-0-1713.DFW01-CORE-RTR2.verizon-gni.net</td> <td> 0</td> <td> 60</td> <td> 60</td> <td> 29</td> <td> 242</td> <td>1456</td> <td> 31</td></tr>
<tr><td>as0-0.DFW01-BB-RTR2.verizon-gni.net</td> <td> 0</td> <td> 60</td> <td> 60</td> <td> 31</td> <td> 235</td> <td>1472</td> <td> 31</td></tr>
<tr><td>0.so-7-0-0.XL4.DFW7.ALTER.NET</td> <td> 0</td> <td> 60</td> <td> 60</td> <td> 30</td> <td> 233</td> <td>1484</td> <td> 31</td></tr>
<tr><td>TenGigE0-7-4-0.GW4.DFW13.ALTER.NET</td> <td> 0</td> <td> 60</td> <td> 60</td> <td> 31</td> <td> 234</td> <td>1473</td> <td> 31</td></tr>
<tr><td>google-gw.customer.alter.net</td> <td> 0</td> <td> 60</td> <td> 60</td> <td> 31</td> <td> 235</td> <td>1472</td> <td> 44</td></tr>
<tr><td>72.14.233.77</td> <td> 0</td> <td> 60</td> <td> 60</td> <td> 30</td> <td> 243</td> <td>1495</td> <td> 51</td></tr>
<tr><td>209.85.250.77</td> <td> 0</td> <td> 60</td> <td> 60</td> <td> 30</td> <td> 235</td> <td>1473</td> <td> 32</td></tr>
<tr><td>www.google.com</td> <td> 0</td> <td> 60</td> <td> 60</td> <td> 30</td> <td> 234</td> <td>1440</td> <td> 32</td></tr>
</table></body></html>
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Let me try that again
WinMTR Statistics
Host | % | Sent | Recv | Best | Avrg | Wrst | Last |
dslmodem.domain | 0 | 60 | 60 | 0 | 139 | 1323 | 0 |
L100.HERNTX-DSL-01.verizon-gni.net | 0 | 60 | 60 | 25 | 234 | 1462 | 25 |
at-4-2-0-1713.DFW01-CORE-RTR2.verizon-gni.net | 0 | 60 | 60 | 29 | 242 | 1456 | 31 |
as0-0.DFW01-BB-RTR2.verizon-gni.net | 0 | 60 | 60 | 31 | 235 | 1472 | 31 |
0.so-7-0-0.XL4.DFW7.ALTER.NET | 0 | 60 | 60 | 30 | 233 | 1484 | 31 |
TenGigE0-7-4-0.GW4.DFW13.ALTER.NET | 0 | 60 | 60 | 31 | 234 | 1473 | 31 |
google-gw.customer.alter.net | 0 | 60 | 60 | 31 | 235 | 1472 | 44 |
72.14.233.77 | 0 | 60 | 60 | 30 | 243 | 1495 | 51 |
209.85.250.77 | 0 | 60 | 60 | 30 | 235 | 1473 | 32 |
www.google.com | 0 | 60 | 60 | 30 | 234 | 1440 | 32 |
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
#1 Visit http://www.giganews.com/line_info.html and post up the Traceroute the page shows, if you wish. Be aware that the final hop (bottom-most line of the trace) will contain a hop with your IP address in it. Remove that line. What I'm looking for is a line that mentions "ERX" in it's name towards the end. If for some reason the trace does not complete (two lines full of Stars), keep the trace route intact.
#2 Can you provide the Transceiver Statistics from you modem?
If you don't know how to get the Transceiver Statistics from your modem: What is the brand and model of your modem?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You appear to have a really shoddy connection to your router. Even though you are getting 0ms latency to it (realisically someting less than 1, which is most likely an Ethernet connection in this case), the average being in the 100s and spiking to the thousands is unacceptable. Latency to the router should never get that high. Any higher than 10ms indicates a faulty link or something that is past saturation.
I would start off by pinging your modem/router 60 times, and displaying the average. If the average on an idle connection is not 1ms or less on Ethernet, you need to troubleshoot it. Try changing Ethernet cables to see if a faulty cable is the culprit, try other computers, and also try another modem or router. Also, check to make sure P2P programs are not running on the machine as they can reduce upload when in seed mode, and the connections they create can load down weaker routers, such as those found in modems.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@Smith6612 wrote:
I would start off by pinging your modem/router 60 times, and displaying the average.
I am just wondering, so how will they do that because in the test results it clealy said
No network address translation appliance was detected.
??
To me, it only can mean one of two things.
#1 Their modem is a dumb modem
#2 OR if their modem is a modem combo, it is in bridge mode.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The NDT Tests sometimes do not detect NATs. In his traceroute he is showing a hop called dslrouter.domain , which is most likely his modem. His located and traceroute suggests he is in a DHCP area, not a PPPoE area, so he does not have a BRAS or other appliance acting as a PPPoE server or midway point. Since he was able to log into his modem to get the sync speed, he should be able to ping the same IP he logged into to get those values.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Oh, ok - carry on...
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
news.giganews.com
1 gw1-g-vlan201.dca.giganews.com (216.196.98.4) 0 ms 0 ms 0 ms
2 g3-0.bb1.dca.giganews.com (216.196.96.62) 0 ms 0 ms 0 ms
3 xe-8-0-7.ar2.iad1.us.nlayer.net (69.31.10.97) 1 ms 1 ms 6 ms
4 ae4-40g.cr2.iad1.us.nlayer.net (69.31.31.185) 20 ms 0 ms 0 ms
5 xe-3-3-0.cr1.atl1.us.nlayer.net (69.22.142.105) 13 ms 13 ms 13 ms
MPLS Label=787292 CoS=1 TTL=0 S=1
6 xe-0-0-3.cr1.iah1.us.nlayer.net (69.22.142.117) 27 ms 27 ms 27 ms
MPLS Label=373091 CoS=1 TTL=0 S=1
7 xe-3-1-1.cr1.dfw1.us.nlayer.net (69.22.142.3) 33 ms 33 ms 33 ms
8 ae1-50g.ar1.dfw1.us.nlayer.net (69.31.63.126) 34 ms 34 ms 36 ms
9 TenGigE0-0-2-0.GW5.DFW13.ALTER.NET (152.179.51.41) 33 ms 34 ms 33 ms
10 0.xe-3-1-0.XL4.DFW7.ALTER.NET (152.63.99.2) 33 ms 33 ms 34 ms
11 0.ge-6-3-0.DFW01-BB-RTR2.verizon-gni.net (152.63.96.50) 36 ms 0.ge-3-2-0.DFW01-BB-RTR2.verizon-gni.net (152.63.2.186) 35 ms 38 ms
12 A12-0-1713.HERNTX-DSL-01.verizon-gni.net (130.81.36.95) 42 ms 47 ms 44 ms
13 pool-71-113-247-129.herntx.dsl-w.verizon.net{edited for privacy}) 267 ms 66 ms 66 ms
news-europe.giganews.com
1 vl201.gw1.ams.giganews.com (216.196.110.3) 1 ms 0 ms 0 ms
2 208.174.50.33 (208.174.50.33) 0 ms 0 ms 0 ms
3 esr1-xe-11-0-0.parispar.savvis.net (204.70.207.214) 9 ms 9 ms 10 ms
4 cr1-tengig-0-1-2-0.londonuk1.savvis.net (204.70.207.177) 16 ms 16 ms 25 ms
5 cr2-tengig-0-15-0-0.NewYork.savvis.net (204.70.196.118) 162 ms 87 ms 87 ms
6 er2-tengig-3-1.NewYork.savvis.net (204.70.198.18) 87 ms 91 ms 87 ms
7 0.xe-9-2-0.BR2.NYC4.ALTER.NET (204.255.168.89) 87 ms 87 ms 86 ms
8 0.ge-8-1-0.NY325-BB-RTR1.verizon-gni.NET (152.63.18.38) 87 ms 87 ms 87 ms
9 as0-0.DFW01-CORE-RTR1.verizon-gni.net (130.81.20.61) 134 ms 236 ms 140 ms
10 A8-0-1710.HERNTX-DSL-01.verizon-gni.net (130.81.135.59) 141 ms 139 ms 139 ms
11 pool-71-113-247-129.herntx.dsl-w.verizon.net ({edited for privacy}) 164 ms 164 ms 165 ms
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I didn't get an answer for a while, so I gave up. Going to get the info now for you.