Fatty September 2, 2004 Share Fatty GC Founder September 2, 2004 Thanks for your time! We're getting closer on a deal that may involve moving everything but Cuffo. Thanks for giving us a moment and reporting your pings and traces. GC Link to comment Share on other sites More sharing options...
Fatty September 2, 2004 Author Share Fatty GC Founder September 2, 2004 BTW, can someone give tips on how to get the text out of a command window for guys like me that forget every time? Link to comment Share on other sites More sharing options...
Guest zerodamage September 2, 2004 Share Guest zerodamage Guests September 2, 2004 It is timing out for me. No responses at all. Link to comment Share on other sites More sharing options...
All Kill3r September 2, 2004 Share All Kill3r Member September 2, 2004 after i ping from command prompt i select all, then copy, than paste into a post. Microsoft Windows XP [Version 5.1.2600] © Copyright 1985-2001 Microsoft Corp. C:\Documents and Settings\joe>ping 66.150.107.32 Pinging 66.150.107.32 with 32 bytes of data: Reply from 66.150.107.32: bytes=32 time=40ms TTL=115 Reply from 66.150.107.32: bytes=32 time=44ms TTL=115 Reply from 66.150.107.32: bytes=32 time=40ms TTL=115 Reply from 66.150.107.32: bytes=32 time=45ms TTL=115 Ping statistics for 66.150.107.32: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 40ms, Maximum = 45ms, Average = 42ms C:\Documents and Settings\joe> Link to comment Share on other sites More sharing options...
Guest Arcturus September 2, 2004 Share Guest Arcturus Guests September 2, 2004 09/02/04 18:00:15 Fast traceroute 66.150.107.32 Trace 66.150.107.32 ... 1 64.21.236.1 10ms 9ms 10ms TTL: 0 2 66.163.135.161 * 10ms 24ms TTL: 0 3 65.207.235.213 16ms 18ms 17ms TTL: 0 4 152.63.69.30 18ms 18ms 19ms TTL: 0 5 152.63.70.105 26ms 26ms 25ms TTL: 0 6 152.63.69.181 27ms 27ms 27ms TTL: 0 7 65.207.239.22 36ms 37ms 36ms TTL: 0 8 64.94.32.10 36ms 34ms 34ms TTL: 0 9 64.94.34.202 36ms 34ms 33ms TTL: 0 10 66.150.107.32 36ms 35ms 35ms TTL:117 Link to comment Share on other sites More sharing options...
X-Razer September 2, 2004 Share X-Razer Member September 2, 2004 Here you go Fatty: Pinging 66.150.107.32 with 32 bytes of data: Reply from 66.150.107.32: bytes=32 time=78ms TTL=107 Reply from 66.150.107.32: bytes=32 time=62ms TTL=107 Reply from 66.150.107.32: bytes=32 time=63ms TTL=107 Reply from 66.150.107.32: bytes=32 time=78ms TTL=107 Ping statistics for 66.150.107.32: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss Approximate round trip times in milli-seconds: Minimum = 62ms, Maximum = 78ms, Average = 70ms Link to comment Share on other sites More sharing options...
Guest Arcturus September 2, 2004 Share Guest Arcturus Guests September 2, 2004 (edited) / "BTW, can someone give tips on how to get the text out of a command /window for guys like me that forget every time?" Right click the border and choose MARK. Then select your text. Then, right click the border again and choose copy. /"Without the Bread of Life, you're toast." "No man can come to me, except the Father which hath sent me draw him: and I will raise him up at the last day." Truth Lives. Preach it brother. Edited September 2, 2004 by Arcturus Link to comment Share on other sites More sharing options...
Hitman September 2, 2004 Share Hitman Member September 2, 2004 C:\>ping 66.150.107.32 Pinging 66.150.107.32 with 32 bytes of data: Reply from 66.150.107.32: bytes=32 time=68ms TTL=117 Reply from 66.150.107.32: bytes=32 time=53ms TTL=117 Reply from 66.150.107.32: bytes=32 time=52ms TTL=117 Reply from 66.150.107.32: bytes=32 time=52ms TTL=117 Ping statistics for 66.150.107.32: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 52ms, Maximum = 68ms, Average = 56ms C:\> Link to comment Share on other sites More sharing options...
Dingy September 2, 2004 Share Dingy Member September 2, 2004 Ping response is 22mS. Pretty Cool! Any way you can get the server closer to me? 22mS isn't good enough! Here's teh trace: Tracing route to 66.150.107.32 over a maximum of 30 hops 1 <1 ms <1 ms <1 ms 192.168.1.1 2 1 ms 1 ms 1 ms 192.168.0.1 3 12 ms 11 ms 12 ms 69.209.159.254 4 12 ms 12 ms 13 ms 67.38.70.242 5 12 ms 12 ms 11 ms 67.38.70.116 6 20 ms 19 ms 20 ms 151.164.242.37 7 21 ms 20 ms 20 ms 151.164.188.42 8 20 ms 21 ms 21 ms 151.164.242.205 9 20 ms 21 ms 21 ms 151.164.191.182 10 21 ms 21 ms 21 ms 151.164.188.162 11 21 ms 21 ms 21 ms 151.164.248.134 12 21 ms 22 ms 21 ms 208.174.226.98 13 21 ms 20 ms 22 ms 64.94.32.74 14 22 ms 22 ms 21 ms 64.94.34.202 15 22 ms 22 ms 22 ms 66.150.107.32 Trace complete. Link to comment Share on other sites More sharing options...
Guest PDO September 3, 2004 Share Guest PDO Guests September 3, 2004 45, looks good. Link to comment Share on other sites More sharing options...
Liltard September 3, 2004 Share Liltard Member September 3, 2004 Tracing route to 66.150.107.32 over a maximum of 30 hops 1 12 ms 11 ms 12 ms 10.230.0.1 2 12 ms 14 ms 12 ms ubr02-p2-0.whithe1.mn.attbb.net [24.31.1.158] 3 11 ms 14 ms 13 ms bic03-p2-3.rosehe1.mn.attbb.net [24.31.1.190] 4 13 ms 13 ms 14 ms 24.31.1.166 5 14 ms 13 ms 12 ms 24.31.2.81 6 26 ms 23 ms 25 ms 12.118.239.169 7 25 ms 25 ms 23 ms tbr2-p012301.cgcil.ip.att.net [12.123.6.13] 8 24 ms 25 ms 24 ms ggr2-p390.cgcil.ip.att.net [12.123.6.37] 9 104 ms 22 ms 24 ms dcr1-so-3-3-0.Chicago.savvis.net [208.175.10.93] 10 22 ms 23 ms 24 ms dcr2-loopback.Chicago.savvis.net [208.172.2.100] 11 23 ms 24 ms 22 ms bpr1-ae0.ChicagoEquinix.savvis.net [208.174.226. 85] 12 26 ms 23 ms 24 ms 208.174.226.98 13 23 ms 24 ms 23 ms border5.ge4-1-bbnet2.chg.pnap.net [64.94.32.74] 14 22 ms 24 ms 24 ms prohosting-2.border5.chg.pnap.net [64.94.34.202] 15 22 ms 24 ms 23 ms 66.150.107.32 Trace complete. LT Link to comment Share on other sites More sharing options...
jessica_alba September 3, 2004 Share jessica_alba Member September 3, 2004 Tracing route to 66.150.107.32 over a maximum of 30 hops 1 2 ms 2 ms 2 ms 192.168.102.1 2 13 ms 16 ms 19 ms 10.229.0.1 3 17 ms 88 ms 39 ms bic04-p0-1.rosehe1.mn.attbb.net [24.31.1.17] 4 12 ms 13 ms 13 ms 24.31.2.21 5 109 ms 55 ms 30 ms 12.118.239.169 6 27 ms 25 ms 23 ms tbr1-p012301.cgcil.ip.att.net [12.123.6.9] 7 27 ms 21 ms 21 ms ggr2-p310.cgcil.ip.att.net [12.123.6.65] 8 21 ms 22 ms 21 ms dcr1-so-3-3-0.Chicago.savvis.net [208.175.10.93] 9 27 ms 45 ms 22 ms dcr2-loopback.Chicago.savvis.net [208.172.2.100] 10 45 ms 33 ms 21 ms bpr1-ae0.ChicagoEquinix.savvis.net [208.174.226. 85] 11 62 ms 214 ms 87 ms 208.174.226.98 12 81 ms 65 ms 29 ms border5.ge4-1-bbnet2.chg.pnap.net [64.94.32.74] 13 31 ms 23 ms 21 ms prohosting-2.border5.chg.pnap.net [64.94.34.202] 14 26 ms 23 ms 28 ms 66.150.107.32 Trace complete. Link to comment Share on other sites More sharing options...
Guest Stinger September 3, 2004 Share Guest Stinger Guests September 3, 2004 Microsoft Windows XP [Version 5.1.2600] © Copyright 1985-2001 Microsoft Corp. C:\Documents and Settings\Owner>ping 66.150.107.32 Pinging 66.150.107.32 with 32 bytes of data: Reply from 66.150.107.32: bytes=32 time=20ms TTL=112 Reply from 66.150.107.32: bytes=32 time=19ms TTL=112 Reply from 66.150.107.32: bytes=32 time=19ms TTL=112 Reply from 66.150.107.32: bytes=32 time=20ms TTL=112 Ping statistics for 66.150.107.32: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 19ms, Maximum = 20ms, Average = 19ms C:\Documents and Settings\Owner>tracert 66.150.107.32 Tracing route to 66.150.107.32 over a maximum of 30 hops 1 <1 ms <1 ms <1 ms 192.168.0.1 2 9 ms 7 ms 9 ms 10.63.160.1 3 9 ms 8 ms 9 ms fas2-5.kscymovivi-rtr1.kc.rr.com [24.94.161.165] 4 8 ms 7 ms 8 ms srp14-0.kscymordc-rtr1.kc.rr.com [24.31.239.1] 5 15 ms 8 ms 7 ms srp14-0.kscymordc-rtr3.kc.rr.com [24.94.160.193] 6 19 ms 19 ms 20 ms so0-0-0.chcgilL3-rtr1.kc.rr.com [24.94.160.5] 7 20 ms 19 ms 18 ms so-2-0-0-0.gar2.Chicago1.Level3.net [67.72.124.1 7] 8 19 ms 20 ms 20 ms so-7-0-0.gar1.Chicago1.Level3.net [209.247.11.33 ] 9 19 ms 19 ms 20 ms so-0-3-0.bbr1.Chicago1.Level3.net [209.247.11.25 ] 10 20 ms 19 ms 20 ms so-5-0.ipcolo1.Chicago1.Level3.net [4.68.112.202 ] 11 19 ms 19 ms 19 ms unknown.Level3.net [209.247.34.166] 12 27 ms 19 ms 19 ms border5.ge4-1-bbnet2.chg.pnap.net [64.94.32.74] 13 19 ms 28 ms 19 ms prohosting-2.border5.chg.pnap.net [64.94.34.202] 14 22 ms 27 ms 20 ms 66.150.107.32 Trace complete. C:\Documents and Settings\Owner> Link to comment Share on other sites More sharing options...
Brillow_Head September 3, 2004 Share Brillow_Head Member September 3, 2004 Microsoft Windows XP [Version 5.1.2600] © Copyright 1985-2001 Microsoft Corp. C:\Documents and Settings\Jason Cose>ping 66.150.107.32 Pinging 66.150.107.32 with 32 bytes of data: Reply from 66.150.107.32: bytes=32 time=34ms TTL=118 Reply from 66.150.107.32: bytes=32 time=33ms TTL=118 Reply from 66.150.107.32: bytes=32 time=28ms TTL=118 Reply from 66.150.107.32: bytes=32 time=33ms TTL=118 Ping statistics for 66.150.107.32: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 28ms, Maximum = 34ms, Average = 32ms -------------------------------------------------------------------- C:\Documents and Settings\Jason Cose>tracert 66.150.107.32 Tracing route to 66.150.107.32 over a maximum of 30 hops 1 10 ms 20 ms 12 ms 10.18.168.1 2 12 ms 12 ms 12 ms 12-215-17-193.client.mchsi.com [12.215.17.193] 3 21 ms 21 ms 21 ms 12-215-2-130.client.mchsi.com [12.215.2.130] 4 32 ms 30 ms 31 ms tbr1-p012701.cgcil.ip.att.net [12.122.2.222] 5 29 ms 28 ms 27 ms ggr2-p310.cgcil.ip.att.net [12.123.6.65] 6 29 ms 30 ms 29 ms dcr1-so-3-3-0.Chicago.savvis.net [208.175.10.93] 7 30 ms 37 ms 31 ms dcr2-loopback.Chicago.savvis.net [208.172.2.100] 8 29 ms 31 ms 32 ms bpr1-so-0-0-0.ChicagoEquinix.savvis.net [208.175 .10.238] 9 29 ms 123 ms 50 ms 208.174.226.98 10 274 ms 68 ms 45 ms border5.ge4-1-bbnet2.chg.pnap.net [64.94.32.74] 11 29 ms 39 ms 30 ms prohosting-2.border5.chg.pnap.net [64.94.34.202] 12 49 ms 30 ms 29 ms 66.150.107.32 Trace complete. Link to comment Share on other sites More sharing options...
Jiffy September 3, 2004 Share Jiffy Member September 3, 2004 im a noob and cant do trace. i ping 13ms Link to comment Share on other sites More sharing options...
hyperactiveChipmunk September 3, 2004 Share hyperactiveChipmunk Member September 3, 2004 >8D -hC Link to comment Share on other sites More sharing options...
dwEEziL September 3, 2004 Share dwEEziL Member September 3, 2004 BTW, can someone give tips on how to get the text out of a command window for guys like me that forget every time? You can also just type at either the Run field or the Dos prompt the following: tracert 66.150.107.32 > c:\Iron_Rocket_tracert.txt <enter> Or whatever you want to name the text file. This directs the output to the text file instead of the screen. Then just go to your C drive (you can change the path to whatever you want...if you just put the text file name instead of the path, then it creates the text file in the same directory as your cmd executable (c:\Windows\System32\)) If you use 2 right-pointing carots (>>) instead, and the file name already exists, it will append the out put to the given text file allowing you to keep all your tracert/ping tests in one text file. If the file name doesn't exist, >> will create it for you as well. Here are my results (from work) for this server (which I also posted in the other xgaming thread). Link to comment Share on other sites More sharing options...
Fatty September 3, 2004 Author Share Fatty GC Founder September 3, 2004 I think we have more pings in our private forum! Link to comment Share on other sites More sharing options...
Guest zerodamage September 3, 2004 Share Guest zerodamage Guests September 3, 2004 This is from my work. Unable to do tracert but can do ping. Will do another from home (My dsl here is free and the worst you could ever have) Microsoft Windows 2000 [Version 5.00.2195] © Copyright 1985-2000 Microsoft Corp. D:\Documents and Settings\Administrator>ping 66.150.107.32 Pinging 66.150.107.32 with 32 bytes of data: Reply from 66.150.107.32: bytes=32 time=47ms TTL=113 Reply from 66.150.107.32: bytes=32 time=47ms TTL=113 Reply from 66.150.107.32: bytes=32 time=47ms TTL=113 Reply from 66.150.107.32: bytes=32 time=78ms TTL=113 Ping statistics for 66.150.107.32: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 47ms, Maximum = 78ms, Average = 54ms Link to comment Share on other sites More sharing options...
Guest zerodamage September 3, 2004 Share Guest zerodamage Guests September 3, 2004 Microsoft Windows XP [Version 5.1.2600] © Copyright 1985-2001 Microsoft Corp. C:\Documents and Settings\Administrator>ping 66.150.107.32 Pinging 66.150.107.32 with 32 bytes of data: Reply from 66.150.107.32: bytes=32 time=36ms TTL=113 Reply from 66.150.107.32: bytes=32 time=36ms TTL=113 Reply from 66.150.107.32: bytes=32 time=36ms TTL=113 Reply from 66.150.107.32: bytes=32 time=37ms TTL=113 Ping statistics for 66.150.107.32: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 36ms, Maximum = 37ms, Average = 36ms C:\Documents and Settings\Administrator> 37ms, Average = 36ms From my home Link to comment Share on other sites More sharing options...
Silver-Bullet September 3, 2004 Share Silver-Bullet Member September 3, 2004 im not all fancy like that...but 20-35 average Link to comment Share on other sites More sharing options...
appalachian_fox September 7, 2004 Share appalachian_fox Member September 7, 2004 Pinging 66.150.107.32 with 32 bytes of data: Reply from 66.150.107.32: bytes=32 time=52ms TTL=113 Reply from 66.150.107.32: bytes=32 time=47ms TTL=113 Reply from 66.150.107.32: bytes=32 time=53ms TTL=113 Reply from 66.150.107.32: bytes=32 time=46ms TTL=113 Ping statistics for 66.150.107.32: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 46ms, Maximum = 53ms, Average = 49ms Tracing route to 66.150.107.32 over a maximum of 30 hops 1 1 ms <1 ms <1 ms x.x.x.x 2 <1 ms <1 ms <1 ms x.x.x.x 3 <1 ms <1 ms <1 ms x.x.x.x 4 8 ms 7 ms * x.x.x.x 5 7 ms 7 ms 7 ms x.x.x.x 6 8 ms * 3 ms x.x.x.x 7 23 ms 22 ms 20 ms x.x.x.x 8 16 ms 17 ms 16 ms g9-7.core01.atl01.atlas.cogentco.com [66.250.15.81] 9 27 ms 27 ms 27 ms p5-0.core02.dca01.atlas.cogentco.com [66.28.4.162] 10 43 ms 40 ms 37 ms p6-0.core01.jfk02.atlas.cogentco.com [66.28.4.82] 11 41 ms 37 ms 35 ms p15-0.core02.jfk02.atlas.cogentco.com [66.28.4.14] 12 51 ms 49 ms 48 ms p14-0.core02.ord01.atlas.cogentco.com [66.28.4.86] 13 59 ms 58 ms 60 ms p15-0.core01.ord03.atlas.cogentco.com [154.54.2.242] 14 49 ms 47 ms 50 ms core101.cogent-212.chg.pnap.net [64.74.106.97] 15 41 ms 41 ms 43 ms border5.ge3-1-bbnet1.chg.pnap.net [64.94.32.10] 16 48 ms 46 ms 44 ms prohosting-2.border5.chg.pnap.net [64.94.34.202] 17 39 ms 40 ms 42 ms 66.150.107.32 Trace complete. Did this from work so I had to hash out everything under Atlanta, but the picture is still clear. And on an unrelated note (OK, it's related): http://visualroute.visualware.com/ Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now