Posted May 29, 200915 yr I have been having problems with teamspeak the last few days. I hear other people but they cut out. Others hear me alright though. When I right click to get info on me it shows I have a large packet loss of between 23-34%. Now that is huge when everone else is generally 0%. I have also while playing PR the last couple of times been getting bad lag and problems with ingame coms. The ping seems fine but the lag is still bad. This is in brief what I have been doing to fix this problem. All with no success. 1. I have done a speed test and the download and upload speeds are normal. 2. I have reinstalled teamspeak. 3. I have run full virus and spyware scans. 4. I have uninstalled programs that may be trouble. 5. I have used a different cable from the ADSL modem. 6. I have now reinstalled windows (vista) 7. Updated windows and drivers 8. Downloaded new version of teamspeak. 9. STILL DOING THE SAME THING!!!!! What more can I do? I guess I could try someone elses connection to isolate wether it is my computer or the connection?? Oh and I also selected teamspeak as allowed with Norton and tried with firewall on and off. I have been using Teamspeak for a long time now and this has just happened from out of nowhere. Edited May 29, 200915 yr by YourHumbleNarrator
May 29, 200915 yr Tried using revo uninstaller to get rid of all the excess registry files and stuff?? that might work.. http://i.imgur.com/zoL1k.png
May 29, 200915 yr Remove old teamspeak codecs and reinstall (uninstalling teamspeak doesnt remove the codec's) http://i.imgur.com/rfTYp.png
May 29, 200915 yr Author Thanks for the replys guys. I have done a complete new install of windows and new install of Teamspeak. So I don't think codecs would be a problem on a new install.
May 30, 200915 yr Firstly, remove Norton. Most computer issues can be traced back to it. Use the Windows Firewall. Get a decent third-party free antivirus. Antivir is one of the better ones (as per the FreewareGenius). Don't run the antivirus all the time, just do weekly scans or targeted scans of downloaded files before execution. Try Mumble, does it happen there? Did you reboot your router? Did you check if an upgraded firmware for your modem may help anything? http://imgur.com/e5y6e.gif You've already ruined these forums for me, I have no desire to read your rhetoric or the pathetic arguments you get yourself in to, or the personal vendetta you have against me, so please, do not talk to me. Ever. About anything.
May 30, 200915 yr Firstly, remove Norton. Most computer issues can be traced back to it. Use the Windows Firewall. Get a decent third-party free antivirus. Antivir is one of the better ones (as per the FreewareGenius). Don't run the antivirus all the time, just do weekly scans or targeted scans of downloaded files before execution. Try Mumble, does it happen there? Did you reboot your router? Did you check if an upgraded firmware for your modem may help anything? This. When we used Norton it was more of a virus then an anti virus. Slows the computer down tenfold and was one of the hardest things to uninstall (wouldn't go away without editing the registry). Windows Firewall + AVG is another good combination. Had my computer for over 2 years now and havn't got 1 bit of spyware/virus on my computer. As for TS I am fairly sure this happened to me as well a looooong time ago. From memory I had to play around with changing the Sound Devices under Settings -> Options. In here I either changed it from Wave to Direct Sound or the other way around. If you have the choice you can also try changing the Input (or maybe outbox? Confuses me >.<) box to the other options you may have. Also check under the Bandwidth tab in the same Options box, make sure they aren't set way down low which would restrict you getting the message. http://www.deadlycombinationclan.com/anaraith/sig/rotate.php FEAR ME I AM PITA BREAD
May 30, 200915 yr oooo god i hate Norton, worst program ever built, i had to get rid of my version of it cause it would always stuff up any game i tried to paly. If you want to use a anti-virus program you pay for get Trend Micro best ever! http://i574.photobucket.com/albums/ss187/Chanvlan/new_kit.jpg yeah but this is the internet' date=' you have to expect the unexpected or else you'll get caught out by things you should've expected but didn't. Its exactly like knowing about the stuff you dont know about, that way you know theres stuff you dont know so when you know what you dont know you can say "ah i knew that!"[/quote']
May 31, 200915 yr Author I have removed norton and re-installed windows again, updated driver and have nothing else installed that could be a problem. I have tried every setting recomended and then some. No joy.
June 1, 200915 yr Author Line quality test results. Any ideas ? http://www.dslreports.com/linequality/nil/2526787
June 1, 200915 yr Line quality test results. Any ideas ? http://www.dslreports.com/linequality/nil/2526787 Hmm so I take it you're with Dodo? 10 & 12% packet loss on the first and last hops @ your place are not exactly numbers you want to see... Have you tried swapping modems over with someone else just as a last resort sort of thing? http://i235.photobucket.com/albums/ee94/psyrus_uraya/awards-1.png QFT: Your computer is smart man. It tells you not to play the second worst PR map [burning Sands] (first is Wanda Shan). QFT: if you dont get pissed off when you lose you dont care enough
June 1, 200915 yr Author Your Psychic powers are legendary Psyrus. Yes Dodo. Have not had a problem before and I have been with them for over two years. I will try to get another modem and test it. Who would you use other than dodo? Thanks
June 1, 200915 yr Your Psychic powers are legendary Psyrus. Yes Dodo. Have not had a problem before and I have been with them for over two years. I will try to get another modem and test it. Who would you use other than dodo? Thanks Not psychic, just reading the trace dodomel-lns001-ge3-4-2.core.dodo.com.au To be honest? Pretty much anyone else except Telstra or TPG [but my first choices would be iiNet or Internode]. :sweat: But nah, maybe it's an isolated problem and not part of the larger extinction process happening to dodo Edited June 1, 200915 yr by Husker http://i235.photobucket.com/albums/ee94/psyrus_uraya/awards-1.png QFT: Your computer is smart man. It tells you not to play the second worst PR map [burning Sands] (first is Wanda Shan). QFT: if you dont get pissed off when you lose you dont care enough
June 1, 200915 yr Author Just done a test and these are the results. I still have problems with ingame voip and Teamspeak. What the?? TS gives me a packet loss of 18% at the same time. Edit.This was done with a downloaded program VisualRoute. I think the result is bull****. ie. not correct. VoIP test statistics -------------------- Jitter: you --> server: 5.6 ms Jitter: server --> you: off Packet loss: you --> server: 0.0 % Packet loss: server --> you: off Packet discards: 0.0 % Packets out of order: 0.0 % Estimated MOS score: 4.0 Edited June 1, 200915 yr by YourHumbleNarrator
June 2, 200915 yr Author Ok, I have used a different router and computer and I still get a packet loss on TS. 1. If it is my service provider what can I get them to do about it? They have already said that my download and upload speeds are alright and thats, that. End of story. 2. On download of TS the Codec downloaded is CLEP. Can I download and install other CODECs? I have read that it should be run in Speex 16.3. How is that done?
June 3, 200915 yr Author Does anyone know what to make of these line trace results? C:\Windows\system32>tracert http://www.teamspeak.com Tracing route to http://www.teamspeak.com [80.190.225.233] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms mygateway1.ar7 [10.1.1.1] 2 30 ms 29 ms 29 ms 123-2-27-1.static.dsl.dodo.com.au [123.2.27.1] 3 29 ms 29 ms 29 ms dodomel-core002-vlan102.core.dodo.com.au [123.2. 0.34] 4 30 ms 30 ms 30 ms GigabitEthernet2-7.lon55.Melbourne.telstra.net [ 139.130.205.17] 5 30 ms 31 ms 29 ms TenGigabitEthernet0-12-0-2.exi-core1.Melbourne.t elstra.net [203.50.80.1] 6 45 ms 44 ms 45 ms Bundle-POS1.chw-core2.Sydney.telstra.net [203.50 .6.13] 7 44 ms 44 ms 45 ms Bundle-Ether1.oxf-gw2.Sydney.telstra.net [203.50 .6.90] 8 45 ms 44 ms 44 ms TenGigabitEthernet14-0.sydo-core01.Sydney.reach. com [203.50.13.42] 9 45 ms 45 ms 45 ms i-3-1-0.sydp-core02.bi.reach.com [202.84.144.249 ] 10 193 ms 194 ms 194 ms i-14-0-0.wil-core02.bx.reach.com [202.84.140.237 ] 11 194 ms 194 ms 198 ms i-1-1.tlot03.bi.reach.com [202.84.251.234] 12 196 ms 195 ms 195 ms ge-6-21.car3.LosAngeles1.Level3.net [4.68.111.13 7] 13 201 ms 196 ms 196 ms ae-73-70.ebr3.LosAngeles1.Level3.net [4.69.144.1 16] 14 229 ms 233 ms 235 ms ae-2.ebr3.SanJose1.Level3.net [4.69.132.9] 15 228 ms 230 ms 234 ms ae-93-93.csw4.SanJose1.Level3.net [4.69.134.238] 16 239 ms 232 ms 234 ms ae-94-94.ebr4.SanJose1.Level3.net [4.69.134.253] 17 298 ms 304 ms 307 ms ae-2.ebr4.NewYork1.Level3.net [4.69.135.186] 18 308 ms 305 ms 306 ms ae-84-84.csw3.NewYork1.Level3.net [4.69.134.122] 19 295 ms 295 ms 294 ms ae-81-81.ebr1.NewYork1.Level3.net [4.69.134.73] 20 363 ms 367 ms 370 ms ae-42-42.ebr2.London1.Level3.net [4.69.137.69] 21 377 ms 372 ms 375 ms ae-2-2.ebr2.Amsterdam1.Level3.net [4.69.132.134] 22 372 ms * 370 ms ae-1-100.ebr1.Amsterdam1.Level3.net [4.69.141.16 9] 23 386 ms 386 ms 383 ms ae-2-2.ebr2.Dusseldorf1.Level3.net [4.69.133.90] 24 375 ms 374 ms 375 ms ae-1-100.ebr1.Dusseldorf1.Level3.net [4.69.141.1 49] 25 379 ms 378 ms 377 ms ae-2-2.ebr2.Frankfurt1.Level3.net [4.69.132.138] 26 379 ms 378 ms 378 ms ae-92-92.csw4.Frankfurt1.Level3.net [4.69.140.30 ] 27 378 ms 379 ms 378 ms ae-4-99.edge3.Frankfurt1.Level3.net [4.68.23.203 ] 28 387 ms 386 ms 387 ms tenge-1-3.cr2.NBG1.content-core.net [212.162.19. 34] 29 386 ms 386 ms 385 ms p1-94.rtr3.colo1.NBG1.content-colo.net [212.123. 127.36] 30 387 ms 386 ms 387 ms teamspeak.com [80.190.225.233] Trace complete. C:\Windows\system32>
June 3, 200915 yr There's nothing extraordinary about it Dog Bro, pinging teamspeak.com isn't really useful, since we use the GSA TS server [202.136.100.200]... Since you've ascertained that it is not your setup (PC & Router), the only other thing is Dodo, which is perhaps deprioritizing the TS packets and since it's UDP your dropped packets simply get lost. http://i235.photobucket.com/albums/ee94/psyrus_uraya/awards-1.png QFT: Your computer is smart man. It tells you not to play the second worst PR map [burning Sands] (first is Wanda Shan). QFT: if you dont get pissed off when you lose you dont care enough
June 3, 200915 yr Author Ok, thanks. The test was requested by dodo and emailed to them. Do you think there is anything that they can do? Because if it comes down to changing providers do you think I will have the same problem with whoever I connect with? Thanks for the input as well mate. I hope this sage is coming to a close as I just want to get online and play PR. I have only played twice in the last three weeks. :-0
June 3, 200915 yr Author Two more Tracing route to gamesrv12.gamingsa.com [202.136.100.200] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms mygateway1.ar7 [10.1.1.1] 2 30 ms 30 ms 29 ms 123-2-27-1.static.dsl.dodo.com.au [123.2.27.1] 3 29 ms 29 ms 30 ms dodomel-core002-vlan102.core.dodo.com.au [123.2. 0.34] 4 * * * Request timed out. 5 30 ms 30 ms 30 ms TenGigabitEthernet0-12-0-2.exi- core1.Melbourne.t elstra.net [203.50.80.1] 6 50 ms 44 ms 44 ms POS0-0-0-0.way-core4.Adelaide.telstra.net [203.5 0.6.190] 7 45 ms * 44 ms TenGigabitEthernet7- 1.way21.Adelaide.telstra.net [203.50.120.31] 8 46 ms 45 ms 46 ms optusn1.lnk.telstra.net [139.130.33.214] 9 * * * Request timed out. 10 45 ms 44 ms 44 ms 61.88.243.255 11 46 ms 45 ms * adaminternetptyltd.o5rxc76f000.optus.net.au [59. 154.56.2] 12 46 ms 47 ms 47 ms g0-1.busco1.adl1.adnap.net.au [219.90.143.166] 13 47 ms 45 ms 44 ms gamesrv12.gamingsa.com [202.136.100.200] Trace complete. C:\Windows\system32> Microsoft Windows [Version 6.0.6001] Copyright © 2006 Microsoft Corporation. All rights reserved. C:\Windows\system32>tracert 203.46.105.38:20050 Unable to resolve target system name 203.46.105.38:20050. C:\Windows\system32>tracert 203.46.105.38 Tracing route to ga0208.gamearena.com.au [203.46.105.38] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms mygateway1.ar7 [10.1.1.1] 2 30 ms 29 ms 29 ms 123-2-27-1.static.dsl.dodo.com.au [123.2.27.1] 3 29 ms 30 ms 29 ms dodomel-core002-vlan102.core.dodo.com.au [123.2. 0.34] 4 30 ms 29 ms 29 ms GigabitEthernet2-7.lon55.Melbourne.telstra.net [ 139.130.205.17] 5 30 ms 31 ms 30 ms TenGigabitEthernet0-12-0-2.exi-core1.Melbourne.t elstra.net [203.50.80.1] 6 45 ms 45 ms 45 ms Bundle-POS1.chw-core2.Sydney.telstra.net [203.50 .6.13] 7 46 ms 44 ms * TenGigabitEthernet7-1.ult1.Sydney.telstra.net [2 03.50.20.188] 8 45 ms 45 ms 46 ms TenGigabitEthernet7-2.ult2.Sydney.telstra.net [2 03.50.12.66] 9 * * * Request timed out. 10 * * * Request timed out. 11 * * * Request timed out. 12 * * * Request timed out. 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. Edited June 3, 200915 yr by YourHumbleNarrator
June 3, 200915 yr Try an extended ping. ping 202.136.100.200 -t -l 2400 [then push ctrl+c to end when ~10 mins has passed] Ping statistics for 202.136.100.200: Packets: Sent = 48, Received = 48, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 126ms, Maximum = 386ms, Average = 211ms You're looking at the "% Loss" stat, which should be <1% if not 0%. I'm guessing over the course of 10 minutes you should see 5-10%. http://i235.photobucket.com/albums/ee94/psyrus_uraya/awards-1.png QFT: Your computer is smart man. It tells you not to play the second worst PR map [burning Sands] (first is Wanda Shan). QFT: if you dont get pissed off when you lose you dont care enough
June 3, 200915 yr Author Extended ping test each test 10 minutes Test 1 Ping statistics for 202.136.100.200: Packets: Sent = 488, Received = 472, Lost = 16 (3% loss), Approximate round trip times in milli-seconds: Minimum = 75ms, Maximum = 84ms, Average = 77ms Test2 Ping statistics for 203.46.105.38: Packets: Sent = 108, Received = 0, Lost = 108 (100% loss), Edited June 3, 200915 yr by YourHumbleNarrator
June 4, 200915 yr Author Ok it all looks like it is incoming and nothing I can do about it on my end. Dam frustrating as it is causing me to get kicked from PR in every game for losing packets by punkbuster. Latest tests... Microsoft Windows [Version 6.0.6001] Copyright © 2006 Microsoft Corporation. All rights reserved. C:\Windows\system32>netstat -a Active Connections Proto Local Address Foreign Address State TCP 0.0.0.0:135 Trent-PC:0 LISTENING TCP 0.0.0.0:445 Trent-PC:0 LISTENING TCP 0.0.0.0:5357 Trent-PC:0 LISTENING TCP 0.0.0.0:49152 Trent-PC:0 LISTENING TCP 0.0.0.0:49153 Trent-PC:0 LISTENING TCP 0.0.0.0:49154 Trent-PC:0 LISTENING TCP 0.0.0.0:49155 Trent-PC:0 LISTENING TCP 0.0.0.0:49156 Trent-PC:0 LISTENING TCP 0.0.0.0:49157 Trent-PC:0 LISTENING TCP 10.1.1.3:139 Trent-PC:0 LISTENING TCP 127.0.0.1:49158 Trent-PC:0 LISTENING TCP [::]:135 Trent-PC:0 LISTENING TCP [::]:445 Trent-PC:0 LISTENING TCP [::]:5357 Trent-PC:0 LISTENING TCP [::]:49152 Trent-PC:0 LISTENING TCP [::]:49153 Trent-PC:0 LISTENING TCP [::]:49154 Trent-PC:0 LISTENING TCP [::]:49155 Trent-PC:0 LISTENING TCP [::]:49156 Trent-PC:0 LISTENING TCP [::]:49157 Trent-PC:0 LISTENING TCP [::1]:49159 Trent-PC:0 LISTENING UDP 0.0.0.0:123 *:* UDP 0.0.0.0:500 *:* UDP 0.0.0.0:3702 *:* UDP 0.0.0.0:3702 *:* UDP 0.0.0.0:4500 *:* UDP 0.0.0.0:5355 *:* UDP 0.0.0.0:50730 *:* UDP 10.1.1.3:137 *:* UDP 10.1.1.3:138 *:* UDP 10.1.1.3:1900 *:* UDP 10.1.1.3:64139 *:* UDP 127.0.0.1:1900 *:* UDP 127.0.0.1:44301 *:* UDP 127.0.0.1:51486 *:* UDP 127.0.0.1:52632 *:* UDP 127.0.0.1:52633 *:* UDP 127.0.0.1:64140 *:* UDP [::]:123 *:* UDP [::]:500 *:* UDP [::]:3702 *:* UDP [::]:3702 *:* UDP [::]:5355 *:* UDP [::]:50731 *:* UDP [::1]:1900 *:* UDP [::1]:64137 *:* UDP [fe80::100:7f:fffe%16]:1900 *:* UDP [fe80::100:7f:fffe%16]:64138 *:* UDP [fe80::962:936f:bfb6:2ef1%10]:1900 *:* UDP [fe80::962:936f:bfb6:2ef1%10]:64136 *:* UDP [fe80::1925:9b44:6215:6d7%12]:1900 *:* UDP [fe80::1925:9b44:6215:6d7%12]:64135 *:* UDP [fe80::8051:60c0:1a3a:433b%14]:1900 *:* UDP [fe80::8051:60c0:1a3a:433b%14]:64134 *:* C:\Windows\system32>netstat Active Connections Proto Local Address Foreign Address State C:\Windows\system32>ping -n 100 www.google.com Pinging www.l.google.com [72.14.203.104] with 32 bytes of data: Reply from 72.14.203.104: bytes=32 time=288ms TTL=237 Reply from 72.14.203.104: bytes=32 time=288ms TTL=237 Reply from 72.14.203.104: bytes=32 time=289ms TTL=237 Request timed out. Reply from 72.14.203.104: bytes=32 time=288ms TTL=237 Reply from 72.14.203.104: bytes=32 time=288ms TTL=237 Request timed out. Reply from 72.14.203.104: bytes=32 time=291ms TTL=237 Reply from 72.14.203.104: bytes=32 time=288ms TTL=237 Reply from 72.14.203.104: bytes=32 time=288ms TTL=237 Reply from 72.14.203.104: bytes=32 time=289ms TTL=237 Reply from 72.14.203.104: bytes=32 time=288ms TTL=237 Reply from 72.14.203.104: bytes=32 time=288ms TTL=237 Reply from 72.14.203.104: bytes=32 time=290ms TTL=237 Reply from 72.14.203.104: bytes=32 time=289ms TTL=237 Request timed out. Reply from 72.14.203.104: bytes=32 time=288ms TTL=237 Reply from 72.14.203.104: bytes=32 time=288ms TTL=237 Reply from 72.14.203.104: bytes=32 time=289ms TTL=237 Reply from 72.14.203.104: bytes=32 time=288ms TTL=237 Request timed out. Reply from 72.14.203.104: bytes=32 time=288ms TTL=237 Reply from 72.14.203.104: bytes=32 time=287ms TTL=237 Reply from 72.14.203.104: bytes=32 time=300ms TTL=237 Reply from 72.14.203.104: bytes=32 time=291ms TTL=237 Reply from 72.14.203.104: bytes=32 time=290ms TTL=237 Reply from 72.14.203.104: bytes=32 time=289ms TTL=237 Reply from 72.14.203.104: bytes=32 time=287ms TTL=237 Reply from 72.14.203.104: bytes=32 time=287ms TTL=237 Request timed out. Reply from 72.14.203.104: bytes=32 time=287ms TTL=237 Reply from 72.14.203.104: bytes=32 time=290ms TTL=237 Request timed out. Reply from 72.14.203.104: bytes=32 time=289ms TTL=237 Reply from 72.14.203.104: bytes=32 time=290ms TTL=237 Reply from 72.14.203.104: bytes=32 time=289ms TTL=237 Request timed out. Reply from 72.14.203.104: bytes=32 time=289ms TTL=237 Reply from 72.14.203.104: bytes=32 time=288ms TTL=237 Reply from 72.14.203.104: bytes=32 time=288ms TTL=237 Reply from 72.14.203.104: bytes=32 time=291ms TTL=237 Request timed out. Reply from 72.14.203.104: bytes=32 time=288ms TTL=237 Reply from 72.14.203.104: bytes=32 time=288ms TTL=237 Reply from 72.14.203.104: bytes=32 time=288ms TTL=237 Reply from 72.14.203.104: bytes=32 time=288ms TTL=237 Request timed out. Reply from 72.14.203.104: bytes=32 time=289ms TTL=237 Reply from 72.14.203.104: bytes=32 time=288ms TTL=237 Reply from 72.14.203.104: bytes=32 time=291ms TTL=237 Reply from 72.14.203.104: bytes=32 time=289ms TTL=237 Reply from 72.14.203.104: bytes=32 time=291ms TTL=237 Reply from 72.14.203.104: bytes=32 time=290ms TTL=237 Reply from 72.14.203.104: bytes=32 time=289ms TTL=237 Reply from 72.14.203.104: bytes=32 time=290ms TTL=237 Reply from 72.14.203.104: bytes=32 time=288ms TTL=237 Request timed out. Reply from 72.14.203.104: bytes=32 time=288ms TTL=237 Reply from 72.14.203.104: bytes=32 time=287ms TTL=237 Reply from 72.14.203.104: bytes=32 time=288ms TTL=237 Reply from 72.14.203.104: bytes=32 time=288ms TTL=237 Reply from 72.14.203.104: bytes=32 time=287ms TTL=237 Reply from 72.14.203.104: bytes=32 time=288ms TTL=237 Reply from 72.14.203.104: bytes=32 time=290ms TTL=237 Reply from 72.14.203.104: bytes=32 time=290ms TTL=237 Reply from 72.14.203.104: bytes=32 time=290ms TTL=237 Reply from 72.14.203.104: bytes=32 time=290ms TTL=237 Reply from 72.14.203.104: bytes=32 time=288ms TTL=237 Reply from 72.14.203.104: bytes=32 time=288ms TTL=237 Reply from 72.14.203.104: bytes=32 time=288ms TTL=237 Reply from 72.14.203.104: bytes=32 time=290ms TTL=237 Reply from 72.14.203.104: bytes=32 time=288ms TTL=237 Reply from 72.14.203.104: bytes=32 time=288ms TTL=237 Reply from 72.14.203.104: bytes=32 time=288ms TTL=237 Reply from 72.14.203.104: bytes=32 time=288ms TTL=237 Reply from 72.14.203.104: bytes=32 time=294ms TTL=237 Reply from 72.14.203.104: bytes=32 time=289ms TTL=237 Reply from 72.14.203.104: bytes=32 time=289ms TTL=237 Reply from 72.14.203.104: bytes=32 time=288ms TTL=237 Reply from 72.14.203.104: bytes=32 time=288ms TTL=237 Reply from 72.14.203.104: bytes=32 time=291ms TTL=237 Reply from 72.14.203.104: bytes=32 time=288ms TTL=237 Reply from 72.14.203.104: bytes=32 time=288ms TTL=237 Reply from 72.14.203.104: bytes=32 time=289ms TTL=237 Reply from 72.14.203.104: bytes=32 time=289ms TTL=237 Reply from 72.14.203.104: bytes=32 time=290ms TTL=237 Reply from 72.14.203.104: bytes=32 time=290ms TTL=237 Reply from 72.14.203.104: bytes=32 time=288ms TTL=237 Reply from 72.14.203.104: bytes=32 time=287ms TTL=237 Request timed out. Reply from 72.14.203.104: bytes=32 time=288ms TTL=237 Reply from 72.14.203.104: bytes=32 time=288ms TTL=237 Reply from 72.14.203.104: bytes=32 time=289ms TTL=237 Reply from 72.14.203.104: bytes=32 time=288ms TTL=237 Reply from 72.14.203.104: bytes=32 time=288ms TTL=237 Reply from 72.14.203.104: bytes=32 time=288ms TTL=237 Reply from 72.14.203.104: bytes=32 time=288ms TTL=237 Reply from 72.14.203.104: bytes=32 time=291ms TTL=237 Reply from 72.14.203.104: bytes=32 time=289ms TTL=237 Request timed out. Ping statistics for 72.14.203.104: Packets: Sent = 100, Received = 88, Lost = 12 (12% loss), Approximate round trip times in milli-seconds: Minimum = 287ms, Maximum = 300ms, Average = 288ms C:\Windows\system32>tracert www.google.com Tracing route to www.google.com [72.14.203.104] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms mygateway1.ar7 [10.1.1.1] 2 28 ms 27 ms 28 ms 123-2-27-1.static.dsl.dodo.com.au [123.2.27.1] 3 28 ms 28 ms 28 ms dodomel-core001-vlan101.core.dodo.com.au [123.2. 0.1] 4 29 ms 28 ms 28 ms 123-2-0-70.core.dodo.com.au [123.2.0.70] 5 29 ms * 29 ms GigabitEthernet2-7.lon55.Melbourne.telstra.net [ 139.130.205.17] 6 29 ms 29 ms 28 ms TenGigabitEthernet0-12-0-2.exi-core1.Melbourne.t elstra.net [203.50.80.1] 7 43 ms 43 ms 43 ms POS0-0-0-0.way-core4.Adelaide.telstra.net [203.5 0.6.190] 8 * 74 ms 74 ms POS0-0-0-0.pie-core1.Perth.telstra.net [203.50.6 .214] 9 74 ms 74 ms * GigabitEthernet1-1.pthp-core01.Perth.net.reach.c om [203.50.13.242] 10 169 ms * 169 ms i-9-3-7.tmh-core04.bx.reach.com [202.84.140.189] 11 * 189 ms 186 ms i-1-0-5.hkth01.bi.reach.com [202.84.153.234] 12 290 ms 300 ms 289 ms 72.14.196.109 13 289 ms 289 ms 289 ms 209.85.241.56 14 286 ms * 287 ms 209.85.250.122 15 299 ms 288 ms * 209.85.250.103 16 285 ms 290 ms 288 ms 209.85.241.166 17 287 ms 288 ms 289 ms www.google.com [72.14.203.104] Trace complete. C:\Windows\system32> Broadband Speed Test Results Test run on 04/06/2009 @ 12:54 PM Mirror: OptusNet Data: 3 MB Test Time: 5.62 secs Your line speed is 4.36 Mbps (4362 kbps). Your download speed is 545 KB/s (0.53 MB/s). Broadband Speed Test Results Test run on 04/06/2009 @ 12:53 PM Mirror: Telstra Bigpond Data: 3 MB Test Time: 5.02 secs Your line speed is 4.88 Mbps (4877 kbps). Your download speed is 610 KB/s (0.6 MB/s).
June 4, 200915 yr Churn from Dodo. Or you on a plan? http://imgur.com/e5y6e.gif You've already ruined these forums for me, I have no desire to read your rhetoric or the pathetic arguments you get yourself in to, or the personal vendetta you have against me, so please, do not talk to me. Ever. About anything.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.