Forum Home
PC World Chat
Thread ID: 71561	2006-08-09 05:37:00	Squirrel Die!?........Again?	SurferJoe46 (51)	PC World Chat

Post ID	Timestamp	Content	User
477363	2006-08-09 05:37:00	I think the squirrel fell off the treadmill again...it's taking 'way too long to get the little lights to blink when I hit "Enter". Will somebody go over to Meta's and see if the critter is OK? It IS Metla's turn to feed and run the little guy...no?	SurferJoe46 (51)
477364	2006-08-09 05:50:00	:confused: You talking about TradeF1 or PressF1? If you are talking about PressF1 it seem to be fine here on Xtra.	stu161204 (123)
477365	2006-08-09 06:39:00	F! seems to be the problem tonight (again)... Must be the Southern Lights acting up...or sun spots...or solar flares...or somebody with a powerful digeridoo.	SurferJoe46 (51)
477366	2006-08-09 06:45:00	You ought to run a tracert and see what route your packets are taking. Something along the route must be causing the problem. Using tracert (www.wurd.com)	Jen (38)
477367	2006-08-09 11:09:00	Hi Joe. Re the kind of arboreal rodent you mentioned, the one with the long bushy tail - we don't have them in NZ.	Scouse (83)
477368	2006-08-10 18:58:00	You ought to run a tracert and see what route your packets are taking . Something along the route must be causing the problem . Using tracert ( . wurd . com/misc_tracert . php" target="_blank">www . wurd . com) Ran tracert outta C: prompt and just got a blinking cursor as a result . I tried various permutations of the address: tracert pressf1 . com >tracert . txt tracert pressf1 . com>tracert . txt tracert PressF1 . com >tracert . txt tracert pcworld . com >tracert . txt tracert PCWorld . com>tracert . txt tracert PCWorld . com >tracert . txt nothing worked . . . :mad:	SurferJoe46 (51)
477369	2006-08-10 19:26:00	Ran tracert outta C: prompt and just got a blinking cursor as a result . I tried various permutations of the address: tracert pressf1 . com >tracert . txtRighty, first thing . That is not the NZ PC World website address - it uses . co . nz . Also that command sent the output of tracert to a text file called tracert . txt, so that is where you will find the output results . The file will be in the directory that the command window shows as the current path - probably found under C: . You don't have to send the output to a text file, just run the command without the >tracert . txt . tracert pressf1 . pcworld . co . nz You can copy the command output by clicking on the wee icon in the top left-hand of the command window title bar and using Select All . Then go back and pick Copy .	Jen (38)
477370	2006-08-11 01:52:00	SurferJoe46 this is the sort of result Tracing route to pressf1.co.nz [210.48.100.45] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 192.168.1.1 2 51 ms 47 ms 48 ms 222-152-0-1.jetstream.xtra.co.nz [222.152.0.1] 3 118 ms 91 ms 77 ms 210.55.205.59 4 70 ms 63 ms 47 ms fid-dom.aksw7.global-gateway.net.nz [202.50.245. 194] 5 46 ms 47 ms 62 ms v282.aksw7.global-gateway.net.nz [202.50.245.193 ] 6 101 ms 45 ms 47 ms g0-1-0-4.akcr8.global-gateway.net.nz [210.55.202 .49] 7 46 ms 47 ms 48 ms g1-0-0-4.akpr1.global-gateway.net.nz [210.55.202 .52] 8 47 ms 47 ms 46 ms iconz1.ape.net.nz [192.203.154.44] 9 48 ms 47 ms 47 ms fe-0-0-0.sky01-jcore.iconz.net [210.48.9.254] 10 48 ms 50 ms 47 ms fe-0-0-1.air02-jcore.iconz.net [210.48.5.10] 11 53 ms 50 ms 50 ms e0-0.core3.akl.iconz.net.nz [202.14.100.220] 12 48 ms 47 ms 51 ms ip-210-48-113-34.iconz.net.nz [210.48.113.34] 13 50 ms 49 ms 49 ms ip-210-48-100-45.iconz.net.nz [210.48.100.45] Trace complete. You should get. I won’t be surprised if the bottleneck for you is either when you hit global-gateway.net.nz (Telecom / Xtra) or the iconz network or the sprintlink.net network.	stu161204 (123)
477371	2006-08-11 05:16:00	This is what I got: Does anyone see the roadblock? Microsoft Windows XP [Version 5 . 1 . 2600] (C) Copyright 1985-2001 Microsoft Corp . C:\Documents and Settings\Joe Administrator>tracert pressf1 . pcworld . co . nz Tracing route to forums . pcworld . co . nz [210 . 48 . 100 . 45] over a maximum of 30 hops: 1 23 ms 23 ms 22 ms L100 . DSL-29 . LSANCA . verizon-gni . net [71 . 110 . 0 . 1] 2 23 ms 25 ms 23 ms P5-0 . LCR-04 . LSANCA . verizon-gni . net [130 . 81 . 35 . 70 ] 3 26 ms 26 ms 26 ms so-7-0-0-0 . PEER-RTR2 . LAX80 . verizon-gni . net [130 . 81 . 17 . 151] 4 28 ms 29 ms 28 ms POS5-0 . GW2 . LAX15 . ALTER . NET [152 . 63 . 114 . 201] 5 29 ms 28 ms 29 ms 0 . so-3-0-0 . CL1 . LAX15 . ALTER . NET [152 . 63 . 117 . 90] 6 39 ms 28 ms 28 ms 0 . so-4-1-0 . XL1 . LAX7 . ALTER . NET [152 . 63 . 117 . 118] 7 28 ms * 29 ms 0 . so-6-0-0 . BR1 . LAX7 . ALTER . NET [152 . 63 . 112 . 41] 8 29 ms 28 ms 28 ms 204 . 255 . 169 . 38 9 30 ms 31 ms 31 ms sl-bb24-ana-9-0 . sprintlink . net [144 . 232 . 20 . 68] 10 31 ms 31 ms 31 ms sl-bb20-ana-11-0 . sprintlink . net [144 . 232 . 1 . 137] 11 43 ms 42 ms 42 ms sl-bb24-sj-4-0 . sprintlink . net [144 . 232 . 9 . 93] 12 42 ms 43 ms 42 ms sl-bb22-sj-13-0 . sprintlink . net [144 . 232 . 3 . 213] 13 192 ms 192 ms 192 ms sl-bb20-syd-14-3 . sprintlink . net [144 . 232 . 8 . 129] 14 192 ms 192 ms 192 ms sl-bb20-syd-15-1 . sprintlink . net [203 . 222 . 32 . 33] 15 217 ms 217 ms 217 ms sl-gw1-auk-5-0-0 . sprintlink . net [203 . 222 . 33 . 23] 16 218 ms 217 ms 218 ms sla-iconz-2-0 . sprintlink . net [203 . 222 . 35 . 198] 17 218 ms 218 ms 218 ms fe-3-47 . cat01-air . iconz . net [210 . 48 . 5 . 42] 18 219 ms 220 ms 218 ms fe-0-0-0 . air01-jcore . iconz . net [210 . 48 . 5 . 25] 19 218 ms 218 ms 218 ms fe-0-0-2 . air02-jcore . iconz . net [210 . 48 . 5 . 6] 20 222 ms 222 ms 223 ms e0-0 . core3 . akl . iconz . net . nz [202 . 14 . 100 . 220] 21 227 ms 220 ms 223 ms ip-210-48-113-34 . iconz . net . nz [210 . 48 . 113 . 34] 22 223 ms 221 ms 222 ms ip-210-48-100-45 . iconz . net . nz [210 . 48 . 100 . 45] Trace complete . C:\Documents and Settings\Joe Administrator>	SurferJoe46 (51)
477372	2006-08-11 05:31:00	Joe, Is PressF1 always slow for you or only some times?, if it is only some times, maybe run a tracert when its slow then we might get a better idea?	stu161204 (123)
1 2