TimPawlak

C:Documents and SettingsTim>tracert testmy.net Tracing route to testmy.net [67.18.179.85] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms DD-WRT [192.168.1.1] 2 16 ms 15 ms 12 ms 74-132-48-1.dhcp.insightbb.com [74.132.48.1] 3 13 ms 15 ms 8 ms 74-132-0-189.dhcp.insightbb.com [74.132.0.189] 4 28 ms 12 ms 11 ms 74.128.8.201 5 29 ms 25 ms 30 ms so-3-1-0.gar2.Atlanta1.Level3.net [4.78.214.21] 6 40 ms 35 ms 53 ms ae-32-52.ebr2.Atlanta2.Level3.net [4.68.103.62] 7 35 ms 61 ms 42 ms ae-1-100.ebr1.Atlanta2.Level3.net [4.69.132.33] 8 48 ms 50 ms 64 ms ae-3.ebr1.Dallas1.Level3.net [4.69.132.81] 9 54 ms 46 ms 52 ms THE-PLANET.car4.Dallas1.Level3.net [4.71.122.2] 10 64 ms 46 ms 55 ms THE-PLANET.car4.Dallas1.Level3.net [4.71.122.2] 11 52 ms 49 ms 53 ms te9-2.dsr01.dllstx3.theplanet.com [70.87.253.14] 12 49 ms 77 ms 53 ms vl41.dsr01.dllstx4.theplanet.com [70.85.127.83] 13 47 ms 58 ms 53 ms gi1-0-2.car17.dllstx4.theplanet.com [67.18.116.8 5] 14 50 ms 49 ms 60 ms 55.b3.1243.static.theplanet.com [67.18.179.85] what did i tell you coknuck?

1970-01-01 00:00:12 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response. 2007-01-09 01:57:56 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2007-01-09 01:57:44 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing 2007-01-09 01:57:43 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2007-01-09 01:57:37 3-Critical R001.0 No Maintenance Broadcasts for Ranging opportunities received - T2 time-out 2007-01-09 01:57:27 3-Critical R002.0 No Ranging Response received - T3 time-out 2007-01-09 01:57:06 3-Critical R001.0 No Maintenance Broadcasts for Ranging opportunities received - T2 time-out 2007-01-09 01:56:56 3-Critical R002.0 No Ranging Response received - T3 time-out 2007-01-09 01:56:30 3-Critical R001.0 No Maintenance Broadcasts for Ranging opportunities received - T2 time-out 2007-01-09 01:56:20 3-Critical R002.0 No Ranging Response received - T3 time-out 2007-01-09 01:55:46 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout 2007-01-09 01:55:46 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing 2007-01-09 01:51:24 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response. 2007-01-09 01:51:16 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2007-01-09 01:51:12 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing 2007-01-09 01:51:11 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2007-01-09 01:50:47 3-Critical R002.0 No Ranging Response received - T3 time-out 2007-01-09 01:50:45 3-Critical R001.0 No Maintenance Broadcasts for Ranging opportunities received - T2 time-out 2007-01-09 01:50:35 3-Critical R002.0 No Ranging Response received - T3 time-out 2007-01-09 01:50:20 3-Critical R001.0 No Maintenance Broadcasts for Ranging opportunities received - T2 time-out 2007-01-09 01:50:10 3-Critical R002.0 No Ranging Response received - T3 time-out 2007-01-09 01:49:42 3-Critical R001.0 No Maintenance Broadcasts for Ranging opportunities received - T2 time-out 2007-01-09 01:49:32 3-Critical R002.0 No Ranging Response received - T3 time-out 2007-01-09 01:49:16 3-Critical R001.0 No Maintenance Broadcasts for Ranging opportunities received - T2 time-out 2007-01-09 01:49:06 3-Critical R002.0 No Ranging Response received - T3 time-out 2007-01-09 01:48:41 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout 2007-01-09 01:48:08 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out 2007-01-06 21:59:33 5-Warning D103.0 DHCP RENEW WARNING - Field invalid in response 1970-01-01 00:00:10 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response. 1970-01-01 00:03:46 3-Critical R002.0 No Ranging Response received - T3 time-out 1970-01-01 00:03:39 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 1970-01-01 00:03:30 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing 1970-01-01 00:03:30 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 1970-01-01 00:03:28 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing 1970-01-01 00:03:27 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 1970-01-01 00:03:26 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing 1970-01-01 00:03:26 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 1970-01-01 00:03:26 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing 1970-01-01 00:03:22 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 1970-01-01 00:03:22 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing 1970-01-01 00:03:16 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 1970-01-01 00:03:16 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing 1970-01-01 00:03:15 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 1970-01-01 00:03:02 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing 1970-01-01 00:03:02 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 1970-01-01 00:02:44 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing 1970-01-01 00:02:43 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 1970-01-01 00:02:43 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing 1970-01-01 00:02:43 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 1970-01-01 00:02:43 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing 1970-01-01 00:02:37 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 1970-01-01 00:02:37 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing 1970-01-01 00:02:34 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 1970-01-01 00:02:33 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing 1970-01-01 00:02:28 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 1970-01-01 00:02:28 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing 1970-01-01 00:02:22 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 1970-01-01 00:01:52 3-Critical R001.0 No Maintenance Broadcasts for Ranging opportunities received - T2 time-out 1970-01-01 00:01:42 3-Critical R002.0 No Ranging Response received - T3 time-out 1970-01-01 00:01:28 3-Critical R001.0 No Maintenance Broadcasts for Ranging opportunities received - T2 time-out 1970-01-01 00:01:18 3-Critical R002.0 No Ranging Response received - T3 time-out 1970-01-01 00:01:09 3-Critical R001.0 No Maintenance Broadcasts for Ranging opportunities received - T2 time-out 1970-01-01 00:00:59 3-Critical R002.0 No Ranging Response received - T3 time-out 1970-01-01 00:00:55 3-Critical R001.0 No Maintenance Broadcasts for Ranging opportunities received - T2 time-out 1970-01-01 00:00:45 3-Critical R002.0 No Ranging Response received - T3 time-out 1970-01-01 00:00:29 3-Critical R001.0 No Maintenance Broadcasts for Ranging opportunities received - T2 time-out 1970-01-01 00:00:19 3-Critical R002.0 No Ranging Response received - T3 time-out 1970-01-01 00:00:03 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 1970-01-01 00:02:36 3-Critical R001.0 No Maintenance Broadcasts for Ranging opportunities received - T2 time-out 1970-01-01 00:02:26 3-Critical R002.0 No Ranging Response received - T3 time-out 1970-01-01 00:02:03 3-Critical R001.0 No Maintenance Broadcasts for Ranging opportunities received - T2 time-out 1970-01-01 00:01:53 3-Critical R002.0 No Ranging Response received - T3 time-out 1970-01-01 00:01:38 3-Critical R001.0 No Maintenance Broadcasts for Ranging opportunities received - T2 time-out 1970-01-01 00:01:28 3-Critical R002.0 No Ranging Response received - T3 time-out 1970-01-01 00:01:14 3-Critical R001.0 No Maintenance Broadcasts for Ranging opportunities received - T2 time-out 1970-01-01 00:01:04 3-Critical R002.0 No Ranging Response received - T3 time-out 1970-01-01 00:00:45 3-Critical R001.0 No Maintenance Broadcasts for Ranging opportunities received - T2 time-out 1970-01-01 00:00:35 3-Critical R002.0 No Ranging Response received - T3 time-out 1970-01-01 00:00:30 3-Critical R001.0 No Maintenance Broadcasts for Ranging opportunities received - T2 time-out 1970-01-01 00:00:20 3-Critical R002.0 No Ranging Response received - T3 time-out 1970-01-01 00:00:03 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 1970-01-01 01:26:11 3-Critical R001.0 No Maintenance Broadcasts for Ranging opportunities received - T2 time-out 1970-01-01 01:26:01 3-Critical R002.0 No Ranging Response received - T3 time-out 1970-01-01 01:25:50 3-Critical R001.0 No Maintenance Broadcasts for Ranging opportunities received - T2 time-out 1970-01-01 01:25:40 3-Critical R002.0 No Ranging Response received - T3 time-out 1970-01-01 01:25:28 3-Critical R001.0 No Maintenance Broadcasts for Ranging opportunities received - T2 time-out 1970-01-01 01:25:18 3-Critical R002.0 No Ranging Response received - T3 time-out 1970-01-01 01:25:08 3-Critical R001.0 No Maintenance Broadcasts for Ranging opportunities received - T2 time-out 1970-01-01 01:24:58 3-Critical R002.0 No Ranging Response received - T3 time-out 1970-01-01 01:24:46 3-Critical R001.0 No Maintenance Broadcasts for Ranging opportunities received - T2 time-out 1970-01-01 01:24:36 3-Critical R002.0 No Ranging Response received - T3 time-out 1970-01-01 01:24:22 3-Critical R001.0 No Maintenance Broadcasts for Ranging opportunities received - T2 time-out 1970-01-01 01:24:12 3-Critical R002.0 No Ranging Response received - T3 time-out 1970-01-01 01:23:48 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 1970-01-01 01:23:45 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing 1970-01-01 01:23:45 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 1970-01-01 01:23:42 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing 1970-01-01 01:23:42 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 1970-01-01 01:23:41 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing 1970-01-01 01:23:41 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing means nothing

hey, thats good dlewis...

prolly here?

C:Documents and SettingsTim>tracert 217.74.222.1 Tracing route to 217.74.222.1.DK-HTS-I.customers.dansketelecom.com [217.74.222.1 ] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms DD-WRT [192.168.1.1] 2 7 ms 9 ms 13 ms 74-132-48-1.dhcp.insightbb.com [74.132.48.1] 3 8 ms 6 ms 7 ms 74-132-0-189.dhcp.insightbb.com [74.132.0.189] 4 8 ms 12 ms 10 ms 74.128.8.201 5 24 ms 27 ms 25 ms so-3-1-0.gar2.Atlanta1.Level3.net [4.78.214.21] 6 27 ms 26 ms 25 ms ae-1-53.bbr1.Atlanta1.Level3.net [4.68.103.65] 7 137 ms 130 ms 129 ms as-0-0.bbr1.Dusseldorf1.Level3.net [212.187.128. 98] 8 142 ms 143 ms 141 ms as-0-0.mp2.Copenhagen1.Level3.net [212.187.130.7 4] 9 143 ms 143 ms 147 ms ge-1-1.car2.Copenhagen1.Level3.net [4.68.125.198 ] 10 143 ms 143 ms 143 ms 213.242.108.130 11 147 ms 154 ms 143 ms DT-vlan.gsr1-sc.net.webpartner.dk [195.184.107.4 2] 12 144 ms 144 ms 143 ms 217.74.222.1.DK-HTS-I.customers.dansketelecom.co m [217.74.222.1] Trace complete.

I just noticed something... are you in a different country? because i tracert you IP and get 300+ pings..

post a tracert, and who is your ISP?

158.00 per month?!!! we pay around 95 dollars per month for 10/1 cable internet, phone (unl longdistance, and Digital/hdtv)

does he have a static? if not, then he'll have problems

have you tried calling bellsouth yet? maybe they are upgrading their servers?

post a tracert. my friend in concord is experiencing slow speeds on 6.0 too..

:::.. Download Stats ..::: Download Connection is:: 10119 Kbps about 10.1 Mbps (tested with 12160 kB) Download Speed is:: 1235 kB/s Tested From:: https://testmy.net/ (Server 1) Test Time:: 2007/01/13 - 8:00am Bottom Line:: 176X faster than 56K 1MB Download in 0.83 sec Tested from a 12160 kB file and took 9.844 seconds to complete Download Diagnosis:: Awesome! 20% + : 118.08 % faster than the average for host (insightbb.com) D-Validation Link:: https://testmy.net/stats/id-ZSIPJC2D4 User Agent:: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.2; .NET CLR 1.1.4322; .NET CLR 2.0.50727) [!] :::.. Upload Stats ..::: Upload Connection is:: 938 Kbps about 0.9 Mbps (tested with 2992 kB) Upload Speed is:: 115 kB/s Tested From:: https://testmy.net/ (Server 1) Test Time:: 2007/01/13 - 8:06am Bottom Line:: 16X faster than 56K 1MB Upload in 8.9 sec Tested from a 2992 kB file and took 26.117 seconds to complete Upload Diagnosis:: Awesome! 20% + : 65.72 % faster than the average for host (insightbb.com) U-Validation Link:: https://testmy.net/stats/id-Q6JMB3NOI User Agent:: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.2; .NET CLR 1.1.4322; .NET CLR 2.0.50727) [!] i cant get any higher... except when i'm on wireless-- close to 11 mbps

u wish :::.. Download Stats ..::: Download Connection is:: 56823 Kbps about 56.8 Mbps (tested with 12160 kB) Download Speed is:: 6936 kB/s Tested From:: https://testmy.net/ (Server 1) Test Time:: 2007/01/12 - 10:56pm Bottom Line:: 991X faster than 56K 1MB Download in 0.15 sec Tested from a 12160 kB file and took 1.753 seconds to complete Download Diagnosis:: Awesome! 20% + : 1128.61 % faster than the average for host (insightbb.com) D-Validation Link:: https://testmy.net/stats/id-OXG3R10ZC User Agent:: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.2; Maxthon; .NET CLR 1.1.4322; .NET CLR 2.0.50727) [!] haha..... i know, its cached... wait.. actually, its TURBOOO!!!

is mine better?

who is your ISP?

welcome to the forums! go to command prompt, type tracert testmy.net

yeah, it could have something to do with te setting on your router... push the reset button on your router and see what happens

i'd like to see coknucks signal =)

lol, its quite easy to tell.. i have had the same problem before... i get a great signal to my modem because we have 1 line for TV and 1 for internet/cablemodem.. my signal ATM is..

8:39:43 PM Chris H Thank you for contacting Insight Help Chat. How may I help you? 8:40:13 PM You I have heard that Insight is using something called Sandvine? Is that why my P2P programs like limewire and bittorrent has been so slow? 8:40:50 PM You getting like a max 27 kb/s on everything.. even high quality torrent files 8:43:11 PM Chris H Insight does use a program called Sandvine to throttle the amount of upstream bandwith that can be used for uploading files for file sharing programs. 8:43:52 PM You oh, i do not upload, i just have it set to download... but i cant get good download speeds worth crap on limewire.. etc 8:44:44 PM Chris H We do not do anything that would effect download of file sharing, only uploading. 8:45:18 PM You ok, thank you they only use sandvine for uploading speeds =)

money isnt really an issue, but i wouldnt even touch a mac i hate them so much lol

well, i never have likes macs.. i havent been able to get spyware like you think.. i can manage it.. and like the "ease of access" and user friendly.. stick my grandma on a mac and see what she says... "she has no clue about pcs in the first place" she will be like... WTF!! GIMME MY EMACHINE BACK!

yeha, that would be best bet

BTW, Welcome to the forums! BLUEDOG314

yeah go to comcast.. they havent been the best latly, but its good. yes, they will deffinitly charge to run a cable upstairs.... insight wanted to charge us 50 dollar to run it from one room to another