Forum Home
Press F1
Thread ID: 81127	2007-07-17 11:43:00	Trouble with pinging but IE is fine..	slyme (12560)	Press F1

Post ID	Timestamp	Content	User
569728	2007-07-17 11:43:00	Hey guys, first time on this forum! :) Maybe you could help me out: My problem arose when I was trying to play Dark Reign, a '97 RTS game, via the internet . For some reason, the game servers wouldn't show up, even though I had the most up to date servers file for the game . So, someone suggested that I try pinging the server, which I did, and to my surprise I received 4x Request timed out . I thought that was weird, as my internet was working fine . So I decided to try pinging a common site, www . google . com, and even more to my surprise, 4x Request timed out again! So in conclusion, I can't ping anything outside of my LAN, and I don't know why . However I can open up any site in IE, just like normal . I am running XP service pack 2, have the windows firewall fully disabled, have no 3rd party firewall of any kind installed . My LAN uses the dick smith XH1173 router, updated to the latest firmware, allowing me to totally shutdown the router's firewall, which I have done, and still no ping! Does anybody have any idea why I can't ping? Thanks in advance!	slyme (12560)
569729	2007-07-17 14:59:00	Did you try "tracert" to identify exactly where the ping is being timed out? Could really help narrow down the source of the obstruction.	beeswax34 (63)
569730	2007-07-17 17:34:00	Okay ran tracert from the command prompt (targeting car . gr, the game server) and got this: 1 * * * Request timed out . 2 70ms 73ms 68ms ubs-ppp . qsi . net . nz [202 . 89 . 129 . 66] 3 73ms 73ms 71ms fe2-3-0 . gw1 . skyt . qsi . net . nz [202 . 89 . 128 . 86] 4 * * * Request timed out . 5 * * * Request timed out . 6 * * * Request timed out . 7 * * * Request timed out . 8 * * * Request timed out . 9 * * * Request timed out . 10 . . . and so on to 30 Any idea what that means? My ISP is Quicksilver/Woosh if that helps?	slyme (12560)
569731	2007-07-19 04:27:00	Here's an update . When I ping google . com (or any other site) I get this: Pinging google . com [64 . 233 . 167 . 99] with 32 bytes of data: Request timed out . Request timed out . Request timed out . Request timed out . Ping statistics for 64 . 233 . 167 . 99: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), And when I tracert google . com (or any other site) I get this: Tracing route to google . com [64 . 233 . 187 . 99] over a maximum of 30 hops: 1 63 ms 67 ms 65 ms 192 . 168 . 1 . 2 2 72 ms 67 ms 69 ms ubs-ppp . qsi . net . nz [202 . 89 . 129 . 66] 3 70 ms 75 ms 73 ms fe2-3-0 . gw1 . skyt . qsi . net . nz [202 . 89 . 128 . 86] 4 * * * Request timed out . 5 * * * Request timed out . 6 * * * Request timed out . 7 * * * Request timed out . 8 * * * Request timed out . 9 * * * Request timed out . 10 * * * Request timed out . . . . etc up to 30 My ISP is Quicksilver/Woosh . I rang them to ask why the tracert is cutting out and they say it has nothing to do with them, must be a firewall of mine . I have turned off my router's firewall, windows firewall and don't have 3rd party firewall installed . Can somebody help?! PLEASE!	slyme (12560)
569732	2007-07-19 04:43:00	The fact that you're getting a response from Quicksilver but no further suggests that they've got something that doesn't pass on the requests. It may be on Intl routes, have you tried a local NZ site?	PaulD (232)
569733	2007-07-19 05:47:00	Yeah I've tried trademe . co . nz, pcworld . co . nz, google . co . nz with the same result: Request timed out . I would have thought that the tracert cutting off at their server would mean a problem their side? But they insist the problem has nothing to do with them .	slyme (12560)
1