Stuart McLachlan
stuart at lexacorp.com.pg
Sun May 1 21:47:20 CDT 2005
On 1 May 2005 at 18:47, Jim Lawrence wrote: > Third: Both of your sets of packets try to resolve through the same > backbone server, described as 38.136.211.66.inaddr.G4.NET in a vain attempt > to get to [66.211.136.38] Looks like it's back up now. Here's my tracert where you can see the incredibly fast internet access we have here in PNG thanks to the huge 8Gb pipe that the governemt monopoly PANGTEL allows everyone in PNG to share. :-( Tracing route to www.databaseadvisors.com [66.211.140.127] over a maximum of 30 hops: 1 78 ms 78 ms 78 ms wireless-pmc.global.net.pg [202.1.52.252] 2 63 ms * 47 ms gateway.global.net.pg [202.165.194.11] 3 172 ms 140 ms 172 ms 202.165.192.1 4 453 ms 422 ms 468 ms 134.159.127.13 5 438 ms * 391 ms i-7-0.syd-core01.net.reach.com [202.84.219.249] 6 469 ms 500 ms 422 ms i-5-0.syd-core02.net.reach.com [202.84.144.249] 7 672 ms 578 ms 531 ms i-0-0.wil-core02.net.reach.com [202.84.144.101] 8 641 ms 578 ms 656 ms i-3-2.wil03.net.reach.com [202.84.251.170] 9 1031 ms 1156 ms 1063 ms so-6-1.LosAngeles1.Level3.net [4.68.127.237] 10 1234 ms 1375 ms * so-3-0-0.bbr1.LosAngeles1.Level3.net [4.68.96.6 ] 11 891 ms 1046 ms 1079 ms so-2-0-0.mp2.Boston1.Level3.net [64.159.4.181] 12 * 1531 ms 860 ms ge-11-2.hsa2.Boston1.Level3.net [4.68.100.165] 13 1156 ms 1594 ms * h0.gfourcom.bbnplanet.net [4.24.92.26] 14 1031 ms 1125 ms 1250 ms gige-7-1.manchester0-5.nh.G4.net [216.177.5.26] 15 1266 ms 1141 ms 1312 ms 38.136.211.66.inaddr.G4.NET [66.211.136.38] 16 1593 ms * 1359 ms www2.korksoft.com [66.211.140.127] Trace complete.-- Stuart