Xobile Posted April 3, 2005 CID Share Posted April 3, 2005 Im running intel pentium 4 processor 2.8GHz with xp sp2 1024mb ram Comcast cable 6000/768, im using the cable settings from the cable nut settings that i got from your file and i seem to get 5.5 constant. the thing is i still manage to get choke and lag when i play my video games. i don't have a fiewall or anyhng installed and i don't have no routers or nothing. please help. :::.. Download Stats ..::: Connection is:: 5409 Kbps about 5.4 Mbps (tested with 2992 kB) Download Speed is:: 660 kB/s Tested From:: http://www.testmy.net/ Test Time:: Sat Apr 02 2005 22:39:10 GMT-0500 (Eastern Standard Time) Bottom Line:: 97X faster than 56K 1MB download in 1.55 sec Diagnosis: Awesome! 20% + : 64.16 % faster than the average for host (Comcast.net) Validation Link:: https://testmy.net/stats/id-ASZ015HQF ==================================================== Microsoft Windows XP [Version 5.1.2600] © Copyright 1985-2001 Microsoft Corp. C:Documents and SettingsDee Money>tracert testmy.net Tracing route to testmy.net [67.19.36.6] over a maximum of 30 hops: 1 10 ms 9 ms 9 ms 10.216.104.1 2 9 ms 9 ms 9 ms 68.87.151.1 3 11 ms 12 ms 12 ms 10g-9-4-ar02.needham.ma.boston.Comcast.net [68.8 7.144.29] 4 12 ms 10 ms 10 ms 12.125.47.49 5 14 ms 15 ms 12 ms 12.123.40.222 6 34 ms 33 ms 34 ms tbr2-cl5.cgcil.ip.att.net [12.122.10.106] 7 44 ms 44 ms 42 ms tbr2-cl7.sl9mo.ip.att.net [12.122.10.46] 8 55 ms 55 ms 55 ms tbr2-cl6.dlstx.ip.att.net [12.122.10.90] 9 54 ms 54 ms 61 ms gar1-p370.dlrtx.ip.att.net [12.123.196.97] 10 56 ms 56 ms 55 ms 12.119.136.14 11 64 ms 54 ms 56 ms dist-vlan31.dsr3-1.dllstx3.theplanet.com [70.85. 127.29] 12 55 ms 56 ms 58 ms dist-vlan-42.dsr2-2.dllstx4.theplanet.com [70.85 .127.91] 13 61 ms 55 ms 55 ms gig1-0-2.tp-car9-1.dllstx4.theplanet.com [67.18. 116.85] 14 55 ms 55 ms 56 ms 6.67-19-36.reverse.theplanet.com [67.19.36.6] Trace complete. C:Documents and SettingsDee Money> ======================================= Tracing route to testmy.net [67.19.36.6] over a maximum of 30 hops: 0 david.hsd1.ma.Comcast.net. [24.34.10.207] 1 10.216.104.1 2 68.87.151.1 3 10g-9-4-ar02.needham.ma.boston.Comcast.net [68.87.144.29] 4 12.125.47.49 5 12.123.40.222 6 tbr2-cl5.cgcil.ip.att.net [12.122.10.106] 7 tbr2-cl7.sl9mo.ip.att.net [12.122.10.46] 8 tbr2-cl6.dlstx.ip.att.net [12.122.10.90] 9 gar1-p370.dlrtx.ip.att.net [12.123.196.97] 10 12.119.136.14 11 dist-vlan31.dsr3-1.dllstx3.theplanet.com [70.85.127.29] 12 dist-vlan41.dsr2-1.dllstx4.theplanet.com [70.85.127.83] 13 gig1-0-1.tp-car9-1.dllstx4.theplanet.com [67.18.116.69] 14 6.67-19-36.reverse.theplanet.com [67.19.36.6] Computing statistics for 350 seconds... Source to Here This Node/Link Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address 0 david.hsd1.ma.Comcast.net. [24.34. 10.207] 0/ 100 = 0% | 1 10ms 0/ 100 = 0% 0/ 100 = 0% 10.216.104.1 0/ 100 = 0% | 2 10ms 0/ 100 = 0% 0/ 100 = 0% 68.87.151.1 0/ 100 = 0% | 3 17ms 0/ 100 = 0% 0/ 100 = 0% 10g-9-4-ar02.needham.ma.boston.com cast.net [68.87.144.29] 0/ 100 = 0% | 4 12ms 0/ 100 = 0% 0/ 100 = 0% 12.125.47.49 0/ 100 = 0% | 5 --- 100/ 100 =100% 100/ 100 =100% 12.123.40.222 0/ 100 = 0% | 6 --- 100/ 100 =100% 100/ 100 =100% tbr2-cl5.cgcil.ip.att.net [12.122. 10.106] 0/ 100 = 0% | 7 --- 100/ 100 =100% 100/ 100 =100% tbr2-cl7.sl9mo.ip.att.net [12.122. 10.46] 0/ 100 = 0% | 8 --- 100/ 100 =100% 100/ 100 =100% tbr2-cl6.dlstx.ip.att.net [12.122. 10.90] 0/ 100 = 0% | 9 --- 100/ 100 =100% 100/ 100 =100% gar1-p370.dlrtx.ip.att.net [12.123 .196.97] 0/ 100 = 0% | 10 58ms 68/ 100 = 68% 68/ 100 = 68% 12.119.136.14 0/ 100 = 0% | 11 --- 100/ 100 =100% 100/ 100 =100% dist-vlan31.dsr3-1.dllstx3.theplan et.com [70.85.127.29] 0/ 100 = 0% | 12 --- 100/ 100 =100% 100/ 100 =100% dist-vlan41.dsr2-1.dllstx4.theplan et.com [70.85.127.83] 0/ 100 = 0% | 13 58ms 0/ 100 = 0% 0/ 100 = 0% gig1-0-1.tp-car9-1.dllstx4.theplan et.com [67.18.116.69] 0/ 100 = 0% | 14 56ms 0/ 100 = 0% 0/ 100 = 0% 6.67-19-36.reverse.theplanet.com [ 67.19.36.6] Trace complete. Quote Link to comment Share on other sites More sharing options...
VanBuren Posted April 3, 2005 CID Share Posted April 3, 2005 hey Xobile and welcome to the forum it might be the route to the server you play on, make tracerts and pathping, to the server and post em here VanBuren Quote Link to comment Share on other sites More sharing options...
Xobile Posted April 3, 2005 Author CID Share Posted April 3, 2005 Server 1 Tracing route to 36.67-19-204.reverse.theplanet.com [67.19.204.36] over a maximum of 30 hops: 0 david.hsd1.ma.comcast.net. [24.34.10.207] 1 10.216.104.1 2 68.87.151.5 3 10g-9-4-ar02.woburn.ma.boston.comcast.net [68.87.144.41] 4 12.118.88.9 5 12.123.40.214 6 tbr2-cl5.cgcil.ip.att.net [12.122.10.106] 7 tbr2-cl7.sl9mo.ip.att.net [12.122.10.46] 8 tbr2-cl6.dlstx.ip.att.net [12.122.10.90] 9 gar1-p370.dlrtx.ip.att.net [12.123.196.97] 10 12.119.136.14 11 dist-vlan32.dsr3-1.dllstx3.theplanet.com [70.85.127.61] 12 dist-vlan41.dsr2-1.dllstx4.theplanet.com [70.85.127.83] 13 gig1-0-2.tp-car8-1.dllstx4.theplanet.com [67.18.116.83] 14 36.67-19-204.reverse.theplanet.com [67.19.204.36] Computing statistics for 140 seconds... Source to Here This Node/Link Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address 0 david.hsd1.ma.comcast.net. [24.34. 10.207] 0/ 100 = 0% | 1 10ms 0/ 100 = 0% 0/ 100 = 0% 10.216.104.1 0/ 100 = 0% | 2 11ms 0/ 100 = 0% 0/ 100 = 0% 68.87.151.5 0/ 100 = 0% | 3 16ms 0/ 100 = 0% 0/ 100 = 0% 10g-9-4-ar02.woburn.ma.boston.comc ast.net [68.87.144.41] 0/ 100 = 0% | 4 12ms 0/ 100 = 0% 0/ 100 = 0% 12.118.88.9 0/ 100 = 0% | 5 --- 100/ 100 =100% 100/ 100 =100% 12.123.40.214 0/ 100 = 0% | 6 --- 100/ 100 =100% 100/ 100 =100% tbr2-cl5.cgcil.ip.att.net [12.122. 10.106] 0/ 100 = 0% | 7 --- 100/ 100 =100% 100/ 100 =100% tbr2-cl7.sl9mo.ip.att.net [12.122. 10.46] 0/ 100 = 0% | 8 --- 100/ 100 =100% 100/ 100 =100% tbr2-cl6.dlstx.ip.att.net [12.122. 10.90] 0/ 100 = 0% | 9 --- 100/ 100 =100% 100/ 100 =100% gar1-p370.dlrtx.ip.att.net [12.123 .196.97] 0/ 100 = 0% | 10 57ms 66/ 100 = 66% 66/ 100 = 66% 12.119.136.14 0/ 100 = 0% | 11 --- 100/ 100 =100% 100/ 100 =100% dist-vlan32.dsr3-1.dllstx3.theplan et.com [70.85.127.61] 0/ 100 = 0% | 12 --- 100/ 100 =100% 100/ 100 =100% dist-vlan41.dsr2-1.dllstx4.theplan et.com [70.85.127.83] 0/ 100 = 0% | 13 57ms 0/ 100 = 0% 0/ 100 = 0% gig1-0-2.tp-car8-1.dllstx4.theplan et.com [67.18.116.83] 0/ 100 = 0% | 14 56ms 0/ 100 = 0% 0/ 100 = 0% 36.67-19-204.reverse.theplanet.com [67.19.204.36] Trace complete. =================================================== C:Documents and SettingsDee Money>tracert 67.19.204.36 Tracing route to 36.67-19-204.reverse.theplanet.com [67.19.204.36] over a maximum of 30 hops: 1 9 ms 11 ms 9 ms 10.216.104.1 2 11 ms 10 ms 11 ms 68.87.151.5 3 11 ms 12 ms 11 ms 10g-9-4-ar02.woburn.ma.boston.comcast.net [68.87 .144.41] 4 9 ms 10 ms 12 ms 12.118.88.9 5 14 ms 14 ms 11 ms 12.123.40.214 6 41 ms 39 ms 37 ms tbr2-cl5.cgcil.ip.att.net [12.122.10.106] 7 43 ms 40 ms 42 ms tbr2-cl7.sl9mo.ip.att.net [12.122.10.46] 8 55 ms 57 ms 57 ms tbr2-cl6.dlstx.ip.att.net [12.122.10.90] 9 54 ms 56 ms 54 ms gar1-p370.dlrtx.ip.att.net [12.123.196.97] 10 55 ms 59 ms 55 ms 12.119.136.14 11 53 ms 56 ms 54 ms dist-vlan32.dsr3-2.dllstx3.theplanet.com [70.85. 127.62] 12 57 ms 55 ms 55 ms dist-vlan41.dsr2-1.dllstx4.theplanet.com [70.85. 127.83] 13 55 ms 60 ms 57 ms gig1-0-2.tp-car8-1.dllstx4.theplanet.com [67.18. 116.83] 14 59 ms 59 ms 55 ms 36.67-19-204.reverse.theplanet.com [67.19.204.36 ] Trace complete. ===================================================== Server 2 C:Documents and SettingsDee Money>pathping 67.19.204.37 -p 50 Tracing route to 37.67-19-204.reverse.theplanet.com [67.19.204.37] over a maximum of 30 hops: 0 david.hsd1.ma.comcast.net. [24.34.10.207] 1 10.216.104.1 2 68.87.151.5 3 10g-9-4-ar02.woburn.ma.boston.comcast.net [68.87.144.41] 4 12.118.88.9 5 12.123.40.214 6 tbr2-cl5.cgcil.ip.att.net [12.122.10.106] 7 tbr2-cl7.sl9mo.ip.att.net [12.122.10.46] 8 tbr2-cl6.dlstx.ip.att.net [12.122.10.90] 9 gar1-p370.dlrtx.ip.att.net [12.123.196.97] 10 12.119.136.14 11 dist-vlan32.dsr3-1.dllstx3.theplanet.com [70.85.127.61] 12 dist-vlan41.dsr2-1.dllstx4.theplanet.com [70.85.127.83] 13 gig1-0-1.tp-car8-1.dllstx4.theplanet.com [67.18.116.67] 14 37.67-19-204.reverse.theplanet.com [67.19.204.37] Computing statistics for 70 seconds... Source to Here This Node/Link Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address 0 david.hsd1.ma.comcast.net. [24.34. 10.207] 0/ 100 = 0% | 1 9ms 0/ 100 = 0% 0/ 100 = 0% 10.216.104.1 0/ 100 = 0% | 2 10ms 0/ 100 = 0% 0/ 100 = 0% 68.87.151.5 0/ 100 = 0% | 3 14ms 0/ 100 = 0% 0/ 100 = 0% 10g-9-4-ar02.woburn.ma.boston.comc ast.net [68.87.144.41] 0/ 100 = 0% | 4 11ms 0/ 100 = 0% 0/ 100 = 0% 12.118.88.9 0/ 100 = 0% | 5 --- 100/ 100 =100% 100/ 100 =100% 12.123.40.214 0/ 100 = 0% | 6 --- 100/ 100 =100% 100/ 100 =100% tbr2-cl5.cgcil.ip.att.net [12.122. 10.106] 0/ 100 = 0% | 7 --- 100/ 100 =100% 100/ 100 =100% tbr2-cl7.sl9mo.ip.att.net [12.122. 10.46] 0/ 100 = 0% | 8 --- 100/ 100 =100% 100/ 100 =100% tbr2-cl6.dlstx.ip.att.net [12.122. 10.90] 0/ 100 = 0% | 9 --- 100/ 100 =100% 100/ 100 =100% gar1-p370.dlrtx.ip.att.net [12.123 .196.97] 0/ 100 = 0% | 10 57ms 65/ 100 = 65% 65/ 100 = 65% 12.119.136.14 0/ 100 = 0% | 11 --- 100/ 100 =100% 100/ 100 =100% dist-vlan32.dsr3-1.dllstx3.theplan et.com [70.85.127.61] 0/ 100 = 0% | 12 --- 100/ 100 =100% 100/ 100 =100% dist-vlan41.dsr2-1.dllstx4.theplan et.com [70.85.127.83] 0/ 100 = 0% | 13 56ms 0/ 100 = 0% 0/ 100 = 0% gig1-0-1.tp-car8-1.dllstx4.theplan et.com [67.18.116.67] 0/ 100 = 0% | 14 56ms 0/ 100 = 0% 0/ 100 = 0% 37.67-19-204.reverse.theplanet.com [67.19.204.37] Trace complete. =============================================== C:Documents and SettingsDee Money>tracert 67.19.204.37 Tracing route to 37.67-19-204.reverse.theplanet.com [67.19.204.37] over a maximum of 30 hops: 1 13 ms 11 ms 8 ms 10.216.104.1 2 9 ms 9 ms 13 ms 68.87.151.5 3 14 ms 11 ms 11 ms 10g-9-4-ar02.woburn.ma.boston.comcast.net [68.87 .144.41] 4 12 ms 13 ms 11 ms 12.118.88.9 5 12 ms 14 ms 12 ms 12.123.40.214 6 35 ms 35 ms 36 ms tbr2-cl5.cgcil.ip.att.net [12.122.10.106] 7 44 ms 43 ms 44 ms tbr2-cl7.sl9mo.ip.att.net [12.122.10.46] 8 58 ms 56 ms 60 ms tbr2-cl6.dlstx.ip.att.net [12.122.10.90] 9 53 ms 57 ms 55 ms gar1-p370.dlrtx.ip.att.net [12.123.196.97] 10 54 ms 55 ms 55 ms 12.119.136.14 11 55 ms 55 ms 55 ms dist-vlan32.dsr3-1.dllstx3.theplanet.com [70.85. 127.61] 12 54 ms 56 ms 56 ms dist-vlan41.dsr2-1.dllstx4.theplanet.com [70.85. 127.83] 13 76 ms 56 ms 57 ms gig1-0-1.tp-car8-1.dllstx4.theplanet.com [67.18. 116.67] 14 54 ms 56 ms 54 ms 37.67-19-204.reverse.theplanet.com [67.19.204.37 ] Trace complete. I also did evertying i thought that would make the connection better, i rewired so its only one coaxial wire to the computer, new ethernet wire with gold for better performance and i even got a trapper too. Quote Link to comment Share on other sites More sharing options...
VanBuren Posted April 3, 2005 CID Share Posted April 3, 2005 you have alot of loss to 0/ 100 = 0% | 10 57ms 65/ 100 = 65% 65/ 100 = 65% 12.119.136.14 try this start-run-cmd ping -n 100 12.119.136.14 VanBuren Quote Link to comment Share on other sites More sharing options...
Xobile Posted April 3, 2005 Author CID Share Posted April 3, 2005 C:Documents and SettingsDee Money>ping -n 100 12.119.136.14 Pinging 12.119.136.14 with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Reply from 12.119.136.14: bytes=32 time=62ms TTL=244 Request timed out. Reply from 12.119.136.14: bytes=32 time=57ms TTL=244 Request timed out. Reply from 12.119.136.14: bytes=32 time=57ms TTL=244 Reply from 12.119.136.14: bytes=32 time=55ms TTL=244 Reply from 12.119.136.14: bytes=32 time=56ms TTL=244 Reply from 12.119.136.14: bytes=32 time=56ms TTL=244 Request timed out. Reply from 12.119.136.14: bytes=32 time=56ms TTL=244 Request timed out. Reply from 12.119.136.14: bytes=32 time=57ms TTL=244 Reply from 12.119.136.14: bytes=32 time=59ms TTL=244 Request timed out. Request timed out. Request timed out. Request timed out. Reply from 12.119.136.14: bytes=32 time=57ms TTL=244 Request timed out. Request timed out. Reply from 12.119.136.14: bytes=32 time=57ms TTL=244 Request timed out. Request timed out. Reply from 12.119.136.14: bytes=32 time=59ms TTL=244 Request timed out. Reply from 12.119.136.14: bytes=32 time=58ms TTL=244 Reply from 12.119.136.14: bytes=32 time=55ms TTL=244 Request timed out. Reply from 12.119.136.14: bytes=32 time=57ms TTL=244 Reply from 12.119.136.14: bytes=32 time=58ms TTL=244 Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Reply from 12.119.136.14: bytes=32 time=57ms TTL=244 Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Reply from 12.119.136.14: bytes=32 time=57ms TTL=244 Reply from 12.119.136.14: bytes=32 time=59ms TTL=244 Request timed out. Reply from 12.119.136.14: bytes=32 time=62ms TTL=244 Request timed out. Request timed out. Request timed out. Reply from 12.119.136.14: bytes=32 time=57ms TTL=244 Reply from 12.119.136.14: bytes=32 time=58ms TTL=244 Reply from 12.119.136.14: bytes=32 time=66ms TTL=244 Request timed out. Request timed out. Reply from 12.119.136.14: bytes=32 time=57ms TTL=244 Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Reply from 12.119.136.14: bytes=32 time=56ms TTL=244 Reply from 12.119.136.14: bytes=32 time=56ms TTL=244 Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Reply from 12.119.136.14: bytes=32 time=56ms TTL=244 Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Reply from 12.119.136.14: bytes=32 time=59ms TTL=244 Request timed out. Request timed out. Request timed out. Reply from 12.119.136.14: bytes=32 time=63ms TTL=244 Reply from 12.119.136.14: bytes=32 time=61ms TTL=244 Request timed out. Reply from 12.119.136.14: bytes=32 time=63ms TTL=244 Reply from 12.119.136.14: bytes=32 time=64ms TTL=244 Request timed out. Ping statistics for 12.119.136.14: Packets: Sent = 100, Received = 32, Lost = 68 (68% loss), Approximate round trip times in milli-seconds: Minimum = 55ms, Maximum = 66ms, Average = 58ms Quote Link to comment Share on other sites More sharing options...
VanBuren Posted April 3, 2005 CID Share Posted April 3, 2005 Skickar signaler till 12.119.136.14 med 32 byte data: Svar fr Quote Link to comment Share on other sites More sharing options...
Xobile Posted April 3, 2005 Author CID Share Posted April 3, 2005 C:Documents and SettingsDee Money>ping -n 100 12.118.88.9 Pinging 12.118.88.9 with 32 bytes of data: Reply from 12.118.88.9: bytes=32 time=33ms TTL=248 Reply from 12.118.88.9: bytes=32 time=13ms TTL=248 Reply from 12.118.88.9: bytes=32 time=10ms TTL=248 Reply from 12.118.88.9: bytes=32 time=22ms TTL=248 Reply from 12.118.88.9: bytes=32 time=14ms TTL=248 Reply from 12.118.88.9: bytes=32 time=14ms TTL=248 Reply from 12.118.88.9: bytes=32 time=11ms TTL=248 Reply from 12.118.88.9: bytes=32 time=11ms TTL=248 Reply from 12.118.88.9: bytes=32 time=14ms TTL=248 Reply from 12.118.88.9: bytes=32 time=12ms TTL=248 Reply from 12.118.88.9: bytes=32 time=21ms TTL=248 Reply from 12.118.88.9: bytes=32 time=13ms TTL=248 Reply from 12.118.88.9: bytes=32 time=10ms TTL=248 Reply from 12.118.88.9: bytes=32 time=10ms TTL=248 Reply from 12.118.88.9: bytes=32 time=13ms TTL=248 Reply from 12.118.88.9: bytes=32 time=13ms TTL=248 Reply from 12.118.88.9: bytes=32 time=19ms TTL=248 Reply from 12.118.88.9: bytes=32 time=14ms TTL=248 Reply from 12.118.88.9: bytes=32 time=11ms TTL=248 Reply from 12.118.88.9: bytes=32 time=14ms TTL=248 Reply from 12.118.88.9: bytes=32 time=13ms TTL=248 Reply from 12.118.88.9: bytes=32 time=11ms TTL=248 Reply from 12.118.88.9: bytes=32 time=11ms TTL=248 Reply from 12.118.88.9: bytes=32 time=23ms TTL=248 Reply from 12.118.88.9: bytes=32 time=11ms TTL=248 Reply from 12.118.88.9: bytes=32 time=12ms TTL=248 Reply from 12.118.88.9: bytes=32 time=11ms TTL=248 Reply from 12.118.88.9: bytes=32 time=14ms TTL=248 Reply from 12.118.88.9: bytes=32 time=11ms TTL=248 Reply from 12.118.88.9: bytes=32 time=11ms TTL=248 Reply from 12.118.88.9: bytes=32 time=11ms TTL=248 Reply from 12.118.88.9: bytes=32 time=15ms TTL=248 Reply from 12.118.88.9: bytes=32 time=11ms TTL=248 Reply from 12.118.88.9: bytes=32 time=11ms TTL=248 Reply from 12.118.88.9: bytes=32 time=14ms TTL=248 Reply from 12.118.88.9: bytes=32 time=12ms TTL=248 Reply from 12.118.88.9: bytes=32 time=11ms TTL=248 Reply from 12.118.88.9: bytes=32 time=13ms TTL=248 Reply from 12.118.88.9: bytes=32 time=14ms TTL=248 Reply from 12.118.88.9: bytes=32 time=13ms TTL=248 Reply from 12.118.88.9: bytes=32 time=11ms TTL=248 Reply from 12.118.88.9: bytes=32 time=13ms TTL=248 Reply from 12.118.88.9: bytes=32 time=11ms TTL=248 Reply from 12.118.88.9: bytes=32 time=11ms TTL=248 Reply from 12.118.88.9: bytes=32 time=12ms TTL=248 Reply from 12.118.88.9: bytes=32 time=11ms TTL=248 Reply from 12.118.88.9: bytes=32 time=14ms TTL=248 Reply from 12.118.88.9: bytes=32 time=13ms TTL=248 Reply from 12.118.88.9: bytes=32 time=15ms TTL=248 Reply from 12.118.88.9: bytes=32 time=13ms TTL=248 Reply from 12.118.88.9: bytes=32 time=22ms TTL=248 Reply from 12.118.88.9: bytes=32 time=22ms TTL=248 Reply from 12.118.88.9: bytes=32 time=15ms TTL=248 Reply from 12.118.88.9: bytes=32 time=19ms TTL=248 Reply from 12.118.88.9: bytes=32 time=14ms TTL=248 Reply from 12.118.88.9: bytes=32 time=13ms TTL=248 Reply from 12.118.88.9: bytes=32 time=11ms TTL=248 Reply from 12.118.88.9: bytes=32 time=12ms TTL=248 Reply from 12.118.88.9: bytes=32 time=15ms TTL=248 Reply from 12.118.88.9: bytes=32 time=12ms TTL=248 Reply from 12.118.88.9: bytes=32 time=10ms TTL=248 Reply from 12.118.88.9: bytes=32 time=11ms TTL=248 Reply from 12.118.88.9: bytes=32 time=12ms TTL=248 Reply from 12.118.88.9: bytes=32 time=14ms TTL=248 Reply from 12.118.88.9: bytes=32 time=11ms TTL=248 Reply from 12.118.88.9: bytes=32 time=14ms TTL=248 Reply from 12.118.88.9: bytes=32 time=12ms TTL=248 Reply from 12.118.88.9: bytes=32 time=12ms TTL=248 Reply from 12.118.88.9: bytes=32 time=10ms TTL=248 Reply from 12.118.88.9: bytes=32 time=15ms TTL=248 Reply from 12.118.88.9: bytes=32 time=11ms TTL=248 Reply from 12.118.88.9: bytes=32 time=11ms TTL=248 Reply from 12.118.88.9: bytes=32 time=12ms TTL=248 Reply from 12.118.88.9: bytes=32 time=11ms TTL=248 Reply from 12.118.88.9: bytes=32 time=11ms TTL=248 Reply from 12.118.88.9: bytes=32 time=20ms TTL=248 Reply from 12.118.88.9: bytes=32 time=11ms TTL=248 Reply from 12.118.88.9: bytes=32 time=12ms TTL=248 Reply from 12.118.88.9: bytes=32 time=16ms TTL=248 Reply from 12.118.88.9: bytes=32 time=11ms TTL=248 Reply from 12.118.88.9: bytes=32 time=28ms TTL=248 Reply from 12.118.88.9: bytes=32 time=11ms TTL=248 Reply from 12.118.88.9: bytes=32 time=14ms TTL=248 Reply from 12.118.88.9: bytes=32 time=12ms TTL=248 Reply from 12.118.88.9: bytes=32 time=11ms TTL=248 Reply from 12.118.88.9: bytes=32 time=21ms TTL=248 Reply from 12.118.88.9: bytes=32 time=16ms TTL=248 Reply from 12.118.88.9: bytes=32 time=15ms TTL=248 Reply from 12.118.88.9: bytes=32 time=12ms TTL=248 Reply from 12.118.88.9: bytes=32 time=12ms TTL=248 Reply from 12.118.88.9: bytes=32 time=12ms TTL=248 Reply from 12.118.88.9: bytes=32 time=12ms TTL=248 Reply from 12.118.88.9: bytes=32 time=11ms TTL=248 Reply from 12.118.88.9: bytes=32 time=13ms TTL=248 Reply from 12.118.88.9: bytes=32 time=11ms TTL=248 Reply from 12.118.88.9: bytes=32 time=12ms TTL=248 Reply from 12.118.88.9: bytes=32 time=13ms TTL=248 Reply from 12.118.88.9: bytes=32 time=12ms TTL=248 Reply from 12.118.88.9: bytes=32 time=13ms TTL=248 Reply from 12.118.88.9: bytes=32 time=11ms TTL=248 Ping statistics for 12.118.88.9: Packets: Sent = 100, Received = 100, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 10ms, Maximum = 33ms, Average = 13ms Quote Link to comment Share on other sites More sharing options...
VanBuren Posted April 3, 2005 CID Share Posted April 3, 2005 then the problem is in one of these nodes 5 12 ms 14 ms 12 ms 12.123.40.214 6 35 ms 35 ms 36 ms tbr2-cl5.cgcil.ip.att.net [12.122.10.106] 7 44 ms 43 ms 44 ms tbr2-cl7.sl9mo.ip.att.net [12.122.10.46] 8 58 ms 56 ms 60 ms tbr2-cl6.dlstx.ip.att.net [12.122.10.90] 9 53 ms 57 ms 55 ms gar1-p370.dlrtx.ip.att.net [12.123.196.97] 10 54 ms 55 ms 55 ms 12.119.136.14 call your ISP and ask em, you can also test ping em all VanBuren Quote Link to comment Share on other sites More sharing options...
Xobile Posted April 3, 2005 Author CID Share Posted April 3, 2005 thank you and i willl do, but what does all those 5 mean? Quote Link to comment Share on other sites More sharing options...
VanBuren Posted April 3, 2005 CID Share Posted April 3, 2005 thank you and i willl do, but what does all those 5 mean? those 5? I dont know what you mean but i pinged 12.119.136.14 and had no loss at all, that means that node is ok, even tho you had a 60% loss so the problem might be between 12.119.136.14 and gar1-p370.dlrtx.ip.att.net [12.123.196.97] VanBuren Quote Link to comment Share on other sites More sharing options...
Xobile Posted April 3, 2005 Author CID Share Posted April 3, 2005 C:Documents and SettingsDee Money>ping -n 20 12.123.40.214 Pinging 12.123.40.214 with 32 bytes of data: Reply from 12.118.88.9: Destination net unreachable. Reply from 12.118.88.9: Destination net unreachable. Request timed out. Request timed out. Request timed out. Request timed out. Reply from 12.118.88.9: Destination net unreachable. Reply from 12.118.88.9: Destination net unreachable. Request timed out. Request timed out. Reply from 12.118.88.9: Destination net unreachable. Reply from 12.118.88.9: Destination net unreachable. Reply from 12.118.88.9: Destination net unreachable. Reply from 12.118.88.9: Destination net unreachable. Request timed out. Request timed out. Reply from 12.118.88.9: Destination net unreachable. Reply from 12.118.88.9: Destination net unreachable. Request timed out. Reply from 12.118.88.9: Destination net unreachable. Ping statistics for 12.123.40.214: Packets: Sent = 20, Received = 11, Lost = 9 (45% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms C:Documents and SettingsDee Money>ping -n 20 12.122.10.106 Pinging 12.122.10.106 with 32 bytes of data: Request timed out. Request timed out. Request timed out. Reply from 12.118.88.9: Destination net unreachable. Reply from 12.118.88.9: Destination net unreachable. Reply from 12.118.88.9: Destination net unreachable. Request timed out. Request timed out. Reply from 12.118.88.9: Destination net unreachable. Reply from 12.118.88.9: Destination net unreachable. Request timed out. Reply from 12.118.88.9: Destination net unreachable. Request timed out. Reply from 12.118.88.9: Destination net unreachable. Request timed out. Reply from 12.118.88.9: Destination net unreachable. Reply from 12.118.88.9: Destination net unreachable. Request timed out. Reply from 12.118.88.9: Destination net unreachable. Request timed out. Ping statistics for 12.122.10.106: Packets: Sent = 20, Received = 10, Lost = 10 (50% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms i pinged 2 of them and got that destination net unreachable, what does that mean? and the 5 was those 6 ips, what are they and what do they have to do with me. Quote Link to comment Share on other sites More sharing options...
Xobile Posted April 3, 2005 Author CID Share Posted April 3, 2005 lol comcast. Stephen > Thank you for contacting Comcast, my name is Stephen. How can I help you today? David > I seem to be having alot of loss on my connection Stephen > Thank you David. I am sorry to hear about this connection issue. I will be happy to assist you. One moment please while I test this. Stephen > There are no problems with the cable modem or line. There are no outages in your area at the moment. I suggest that you disable or uninstall and firewall software that you are using. Also if you are using a router or networking device, please connect the computer directly into the cable modem and test that further. If the problem persists call our voice support at 1-888-COMCAST when the problem occurs so that we can identify what is causing the issue. Stephen > Is there anything else I can assist you with today? David > yes David > hold on second David > 5 --- 100/ 100 =100% 100/ 100 =100% 12.123.40.214 0/ 100 = 0% | David > im getting lose to that ip, and 100 percent David > and there is still more David > i just can't paste them all David > loss* Stephen > I do not know what that IP address is or what it has been assigned to, however I have tested your connection and it is working fine. If you are able to connect to this chat, then there are no connection problems. If your connection goes down, please call our voice support so that we can properly identify the problem. Stephen > Thank you for contacting comcast, have a good day. Stephen > Analyst has closed chat and left the room Quote Link to comment Share on other sites More sharing options...
VanBuren Posted April 3, 2005 CID Share Posted April 3, 2005 they block ping, but 12.119.136.14 do not block ping the ping has to go all the way via all the nodes from your pc to a certain node eg 12.119.136.14 if there is a problem between 12.119.136.14 and gar1-p370.dlrtx.ip.att.net [12.123.196.97] you will loos packets and thats goin to be reported as loss to 12.119.136.14 unfortunelly, 12.123.196.97 block ping, thats why you need to call your ISP and ask cos your end seems fine, since you had no loss to C:Documents and SettingsDee Money>ping -n 100 12.118.88.9 Pinging 12.118.88.9 with 32 bytes of data: Reply from 12.118.88.9: bytes=32 time=33ms TTL=248 Reply from 12.118.88.9: bytes=32 time=13ms TTL=248 Reply from 12.118.88.9: bytes=32 time=10ms TTL=248 Reply from 12.118.88.9: bytes=32 time=22ms TTL=248 Reply from 12.118.88.9: bytes=32 time=14ms TTL=248 Reply from 12.118.88.9: bytes=32 time=14ms TTL=248 Reply from 12.118.88.9: bytes=32 time=11ms TTL=248 Reply from 12.118.88.9: bytes=32 time=11ms TTL=248 Reply from 12.118.88.9: bytes=32 time=14ms TTL=248 Reply from 12.118.88.9: bytes=32 time=12ms TTL=248 Reply from 12.118.88.9: bytes=32 time=21ms TTL=248 Reply from 12.118.88.9: bytes=32 time=13ms TTL=248 Reply from 12.118.88.9: bytes=32 time=10ms TTL=248 Reply from 12.118.88.9: bytes=32 time=10ms TTL=248 Reply from 12.118.88.9: bytes=32 time=13ms TTL=248 Reply from 12.118.88.9: bytes=32 time=13ms TTL=248 Reply from 12.118.88.9: bytes=32 time=19ms TTL=248 Reply from 12.118.88.9: bytes=32 time=14ms TTL=248 Reply from 12.118.88.9: bytes=32 time=11ms TTL=248 Reply from 12.118.88.9: bytes=32 time=14ms TTL=248 Reply from 12.118.88.9: bytes=32 time=13ms TTL=248 Reply from 12.118.88.9: bytes=32 time=11ms TTL=248 Reply from 12.118.88.9: bytes=32 time=11ms TTL=248 Reply from 12.118.88.9: bytes=32 time=23ms TTL=248 Reply from 12.118.88.9: bytes=32 time=11ms TTL=248 Reply from 12.118.88.9: bytes=32 time=12ms TTL=248 Reply from 12.118.88.9: bytes=32 time=11ms TTL=248 Reply from 12.118.88.9: bytes=32 time=14ms TTL=248 Reply from 12.118.88.9: bytes=32 time=11ms TTL=248 Reply from 12.118.88.9: bytes=32 time=11ms TTL=248 Reply from 12.118.88.9: bytes=32 time=11ms TTL=248 Reply from 12.118.88.9: bytes=32 time=15ms TTL=248 Reply from 12.118.88.9: bytes=32 time=11ms TTL=248 Reply from 12.118.88.9: bytes=32 time=11ms TTL=248 Reply from 12.118.88.9: bytes=32 time=14ms TTL=248 Reply from 12.118.88.9: bytes=32 time=12ms TTL=248 Reply from 12.118.88.9: bytes=32 time=11ms TTL=248 Reply from 12.118.88.9: bytes=32 time=13ms TTL=248 Reply from 12.118.88.9: bytes=32 time=14ms TTL=248 Reply from 12.118.88.9: bytes=32 time=13ms TTL=248 Reply from 12.118.88.9: bytes=32 time=11ms TTL=248 Reply from 12.118.88.9: bytes=32 time=13ms TTL=248 Reply from 12.118.88.9: bytes=32 time=11ms TTL=248 Reply from 12.118.88.9: bytes=32 time=11ms TTL=248 Reply from 12.118.88.9: bytes=32 time=12ms TTL=248 Reply from 12.118.88.9: bytes=32 time=11ms TTL=248 Reply from 12.118.88.9: bytes=32 time=14ms TTL=248 Reply from 12.118.88.9: bytes=32 time=13ms TTL=248 Reply from 12.118.88.9: bytes=32 time=15ms TTL=248 Reply from 12.118.88.9: bytes=32 time=13ms TTL=248 Reply from 12.118.88.9: bytes=32 time=22ms TTL=248 Reply from 12.118.88.9: bytes=32 time=22ms TTL=248 Reply from 12.118.88.9: bytes=32 time=15ms TTL=248 Reply from 12.118.88.9: bytes=32 time=19ms TTL=248 Reply from 12.118.88.9: bytes=32 time=14ms TTL=248 Reply from 12.118.88.9: bytes=32 time=13ms TTL=248 Reply from 12.118.88.9: bytes=32 time=11ms TTL=248 Reply from 12.118.88.9: bytes=32 time=12ms TTL=248 Reply from 12.118.88.9: bytes=32 time=15ms TTL=248 Reply from 12.118.88.9: bytes=32 time=12ms TTL=248 Reply from 12.118.88.9: bytes=32 time=10ms TTL=248 Reply from 12.118.88.9: bytes=32 time=11ms TTL=248 Reply from 12.118.88.9: bytes=32 time=12ms TTL=248 Reply from 12.118.88.9: bytes=32 time=14ms TTL=248 Reply from 12.118.88.9: bytes=32 time=11ms TTL=248 Reply from 12.118.88.9: bytes=32 time=14ms TTL=248 Reply from 12.118.88.9: bytes=32 time=12ms TTL=248 Reply from 12.118.88.9: bytes=32 time=12ms TTL=248 Reply from 12.118.88.9: bytes=32 time=10ms TTL=248 Reply from 12.118.88.9: bytes=32 time=15ms TTL=248 Reply from 12.118.88.9: bytes=32 time=11ms TTL=248 Reply from 12.118.88.9: bytes=32 time=11ms TTL=248 Reply from 12.118.88.9: bytes=32 time=12ms TTL=248 Reply from 12.118.88.9: bytes=32 time=11ms TTL=248 Reply from 12.118.88.9: bytes=32 time=11ms TTL=248 Reply from 12.118.88.9: bytes=32 time=20ms TTL=248 Reply from 12.118.88.9: bytes=32 time=11ms TTL=248 Reply from 12.118.88.9: bytes=32 time=12ms TTL=248 Reply from 12.118.88.9: bytes=32 time=16ms TTL=248 Reply from 12.118.88.9: bytes=32 time=11ms TTL=248 Reply from 12.118.88.9: bytes=32 time=28ms TTL=248 Reply from 12.118.88.9: bytes=32 time=11ms TTL=248 Reply from 12.118.88.9: bytes=32 time=14ms TTL=248 Reply from 12.118.88.9: bytes=32 time=12ms TTL=248 Reply from 12.118.88.9: bytes=32 time=11ms TTL=248 Reply from 12.118.88.9: bytes=32 time=21ms TTL=248 Reply from 12.118.88.9: bytes=32 time=16ms TTL=248 Reply from 12.118.88.9: bytes=32 time=15ms TTL=248 Reply from 12.118.88.9: bytes=32 time=12ms TTL=248 Reply from 12.118.88.9: bytes=32 time=12ms TTL=248 Reply from 12.118.88.9: bytes=32 time=12ms TTL=248 Reply from 12.118.88.9: bytes=32 time=12ms TTL=248 Reply from 12.118.88.9: bytes=32 time=11ms TTL=248 Reply from 12.118.88.9: bytes=32 time=13ms TTL=248 Reply from 12.118.88.9: bytes=32 time=11ms TTL=248 Reply from 12.118.88.9: bytes=32 time=12ms TTL=248 Reply from 12.118.88.9: bytes=32 time=13ms TTL=248 Reply from 12.118.88.9: bytes=32 time=12ms TTL=248 Reply from 12.118.88.9: bytes=32 time=13ms TTL=248 Reply from 12.118.88.9: bytes=32 time=11ms TTL=248 Ping statistics for 12.118.88.9: Quote Link to comment Share on other sites More sharing options...
Xobile Posted April 3, 2005 Author CID Share Posted April 3, 2005 thx for your help van buren, ima call Comcast after and see what happens. since onlin esupport is being Quote Link to comment Share on other sites More sharing options...
Xobile Posted April 3, 2005 Author CID Share Posted April 3, 2005 i tried the same thing on my cousin and seem to get the same results. C:Documents and SettingsAndrew>pathping 67.19.204.37 -p 50 Tracing route to 37.67-19-204.reverse.theplanet.com [67.19.204.37] over a maximum of 30 hops: 0 andrew.hsd1.ma.comcast.net. [24.34.4.1] 1 10.216.104.1 2 68.87.151.1 3 10g-9-4-ar02.needham.ma.boston.comcast.net [68.87.144.29] 4 12.125.47.49 5 12.123.40.222 6 tbr2-cl5.cgcil.ip.att.net [12.122.10.106] 7 tbr2-cl7.sl9mo.ip.att.net [12.122.10.46] 8 tbr2-cl6.dlstx.ip.att.net [12.122.10.90] 9 gar1-p370.dlrtx.ip.att.net [12.123.196.97] 10 12.119.136.14 11 dist-vlan32.dsr3-1.dllstx3.theplanet.com [70.85.127.61] 12 dist-vlan41.dsr2-1.dllstx4.theplanet.com [70.85.127.83] 13 gig1-0-1.tp-car8-1.dllstx4.theplanet.com [67.18.116.67] 14 37.67-19-204.reverse.theplanet.com [67.19.204.37] Computing statistics for 70 seconds... Source to Here This Node/Link Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address 0 andrew.hsd1.ma.comcast.net. [24.34 .4.1] 0/ 100 = 0% | 1 9ms 0/ 100 = 0% 0/ 100 = 0% 10.216.104.1 0/ 100 = 0% | 2 9ms 0/ 100 = 0% 0/ 100 = 0% 68.87.151.1 0/ 100 = 0% | 3 17ms 0/ 100 = 0% 0/ 100 = 0% 10g-9-4-ar02.needham.ma.boston.com cast.net [68.87.144.29] 0/ 100 = 0% | 4 11ms 0/ 100 = 0% 0/ 100 = 0% 12.125.47.49 0/ 100 = 0% | 5 --- 100/ 100 =100% 100/ 100 =100% 12.123.40.222 0/ 100 = 0% | 6 --- 100/ 100 =100% 100/ 100 =100% tbr2-cl5.cgcil.ip.att.net [12.122. 10.106] 0/ 100 = 0% | 7 --- 100/ 100 =100% 100/ 100 =100% tbr2-cl7.sl9mo.ip.att.net [12.122. 10.46] 0/ 100 = 0% | 8 --- 100/ 100 =100% 100/ 100 =100% tbr2-cl6.dlstx.ip.att.net [12.122. 10.90] 0/ 100 = 0% | 9 --- 100/ 100 =100% 100/ 100 =100% gar1-p370.dlrtx.ip.att.net [12.123 .196.97] 0/ 100 = 0% | 10 55ms 73/ 100 = 73% 73/ 100 = 73% 12.119.136.14 0/ 100 = 0% | 11 --- 100/ 100 =100% 100/ 100 =100% dist-vlan32.dsr3-1.dllstx3.theplan et.com [70.85.127.61] 0/ 100 = 0% | 12 --- 100/ 100 =100% 100/ 100 =100% dist-vlan41.dsr2-1.dllstx4.theplan et.com [70.85.127.83] 0/ 100 = 0% | 13 57ms 0/ 100 = 0% 0/ 100 = 0% gig1-0-1.tp-car8-1.dllstx4.theplan et.com [67.18.116.67] 0/ 100 = 0% | 14 55ms 0/ 100 = 0% 0/ 100 = 0% 37.67-19-204.reverse.theplanet.com [67.19.204.37] Trace complete. =========================================================== C:Documents and SettingsAndrew>tracert 69.19.204.37 Tracing route to host-69-19-204-37.rev.o1.com [69.19.204.37] over a maximum of 30 hops: 1 9 ms 10 ms 9 ms 10.216.104.1 2 8 ms 9 ms 9 ms 68.87.151.5 3 11 ms 10 ms 10 ms 10g-9-4-ar02.woburn.ma.boston.comcast.net [68.87 .144.41] 4 11 ms 10 ms 11 ms 12.118.88.9 5 14 ms 11 ms 11 ms 12.123.40.214 6 34 ms 38 ms 35 ms tbr2-cl5.cgcil.ip.att.net [12.122.10.106] 7 38 ms 34 ms 36 ms gar1-p390.chail.ip.att.net [12.123.216.217] 8 36 ms 37 ms 35 ms 12.119.137.50 9 36 ms 36 ms 41 ms so-1-0-0.cr1.ord2.us.above.net [64.125.30.146] 10 87 ms 87 ms 87 ms so-4-0-0.mpr3.sjc2.us.above.net [64.125.30.213] 11 140 ms 87 ms 161 ms so-2-0-0.er10a.sjc2.us.above.net [64.125.30.90] 12 86 ms 87 ms 88 ms 64.124.229.117.o1.com [64.124.229.117] 13 * * * Request timed out. 14 * * * Request timed out. 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. C:Documents and SettingsAndrew>ping -n 100 12.119.136.14 Pinging 12.119.136.14 with 32 bytes of data: Request timed out. Reply from 12.119.136.14: bytes=32 time=54ms TTL=244 Reply from 12.119.136.14: bytes=32 time=54ms TTL=244 Request timed out. Request timed out. Reply from 12.119.136.14: bytes=32 time=55ms TTL=244 Request timed out. Reply from 12.119.136.14: bytes=32 time=55ms TTL=244 Reply from 12.119.136.14: bytes=32 time=55ms TTL=244 Request timed out. Request timed out. Reply from 12.119.136.14: bytes=32 time=53ms TTL=244 Reply from 12.119.136.14: bytes=32 time=57ms TTL=244 Request timed out. Reply from 12.119.136.14: bytes=32 time=56ms TTL=244 Reply from 12.119.136.14: bytes=32 time=55ms TTL=244 Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Reply from 12.119.136.14: bytes=32 time=58ms TTL=244 Request timed out. Reply from 12.119.136.14: bytes=32 time=54ms TTL=244 Request timed out. Request timed out. Reply from 12.119.136.14: bytes=32 time=58ms TTL=244 Request timed out. Reply from 12.119.136.14: bytes=32 time=53ms TTL=244 Reply from 12.119.136.14: bytes=32 time=54ms TTL=244 Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Reply from 12.119.136.14: bytes=32 time=53ms TTL=244 Request timed out. Request timed out. Reply from 12.119.136.14: bytes=32 time=54ms TTL=244 Reply from 12.119.136.14: bytes=32 time=53ms TTL=244 Reply from 12.119.136.14: bytes=32 time=54ms TTL=244 Request timed out. Request timed out. Request timed out. Reply from 12.119.136.14: bytes=32 time=55ms TTL=244 Request timed out. Request timed out. Request timed out. Reply from 12.119.136.14: bytes=32 time=54ms TTL=244 Request timed out. Reply from 12.119.136.14: bytes=32 time=56ms TTL=244 Request timed out. Request timed out. Reply from 12.119.136.14: bytes=32 time=54ms TTL=244 Request timed out. Reply from 12.119.136.14: bytes=32 time=54ms TTL=244 Request timed out. Request timed out. Request timed out. Reply from 12.119.136.14: bytes=32 time=55ms TTL=244 Reply from 12.119.136.14: bytes=32 time=53ms TTL=244 Request timed out. Request timed out. Reply from 12.119.136.14: bytes=32 time=55ms TTL=244 Request timed out. Reply from 12.119.136.14: bytes=32 time=55ms TTL=244 Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Reply from 12.119.136.14: bytes=32 time=53ms TTL=244 Reply from 12.119.136.14: bytes=32 time=54ms TTL=244 Request timed out. Reply from 12.119.136.14: bytes=32 time=54ms TTL=244 Request timed out. Request timed out. Reply from 12.119.136.14: bytes=32 time=54ms TTL=244 Request timed out. Request timed out. Reply from 12.119.136.14: bytes=32 time=54ms TTL=244 Reply from 12.119.136.14: bytes=32 time=53ms TTL=244 Request timed out. Reply from 12.119.136.14: bytes=32 time=54ms TTL=244 Request timed out. Request timed out. Request timed out. Reply from 12.119.136.14: bytes=32 time=55ms TTL=244 Request timed out. Reply from 12.119.136.14: bytes=32 time=57ms TTL=244 Request timed out. Request timed out. Request timed out. Request timed out. Reply from 12.119.136.14: bytes=32 time=54ms TTL=244 Reply from 12.119.136.14: bytes=32 time=53ms TTL=244 Request timed out. Ping statistics for 12.119.136.14: Packets: Sent = 100, Received = 38, Lost = 62 (62% loss), Approximate round trip times in milli-seconds: Minimum = 53ms, Maximum = 58ms, Average = 54ms Quote Link to comment Share on other sites More sharing options...
Xobile Posted April 3, 2005 Author CID Share Posted April 3, 2005 Van buren, i need some help, i called my cable company and they are getting teh same problem but have no idea what to do. they are sending a tech out to check the wires but if they are getting the same thing what am i gonna do? Quote Link to comment Share on other sites More sharing options...
VanBuren Posted April 4, 2005 CID Share Posted April 4, 2005 im running out of ideas, wait and see what they find VanBuren Quote Link to comment Share on other sites More sharing options...
Xobile Posted April 4, 2005 Author CID Share Posted April 4, 2005 they came said everything is alright and left before i could get home to talk to him, and im still getting the same results, they have a block on my tv cable because i don't have all the channels, you think that might be the problem? Quote Link to comment Share on other sites More sharing options...
VanBuren Posted April 4, 2005 CID Share Posted April 4, 2005 that block wont matter, but you could try using windows default settings and see if lag dissapear some videogames might not like tweaks to delete tweaks, just open cablenut and click delete cablenut tweaks and click save to registry+ reboot VanBuren Quote Link to comment Share on other sites More sharing options...
Xobile Posted April 5, 2005 Author CID Share Posted April 5, 2005 its even worse without the tweaks, i just recently started getting into tweaks now, before i just had normal settings. Quote Link to comment Share on other sites More sharing options...
VanBuren Posted April 5, 2005 CID Share Posted April 5, 2005 run this test http://www.dslreports.com/tweaks copy and paste result URL adress in your post VanBuren Quote Link to comment Share on other sites More sharing options...
Xobile Posted April 10, 2005 Author CID Share Posted April 10, 2005 http://ttester.broadbandreports.com/tweak/block:5c666cd?service=cable&speed=6000&os=winXP&via=enternet here, been really busy and all sorry i took so long Quote Link to comment Share on other sites More sharing options...
VanBuren Posted April 10, 2005 CID Share Posted April 10, 2005 http://ttester.broadbandreports.com/tweak/block:5c666cd?service=cable&speed=6000&os=winXP&via=enternet here, been really busy and all sorry i took so long thats not default settings make a screenshot of your cablenut settings VanBuren Quote Link to comment Share on other sites More sharing options...
Xobile Posted April 13, 2005 Author CID Share Posted April 13, 2005 i still get choke when i remove the settings and put default settings on. Quote Link to comment Share on other sites More sharing options...
VanBuren Posted April 13, 2005 CID Share Posted April 13, 2005 open cablenut, click delete cablenut tweaks and click save to registry open Dr.Tcp make sure all fields is blank, if you see a value then use delete key and erase it, and all settings is on default, like this attached picture, now click save and exit reboot your PC, also reboot your modem and router, leave it off for 30 full seconds run this test http://www.dslreports.com/tweaks copy and paste result URL adress in your post VanBuren 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.