Results 1 to 5 of 5
Thread: PathPing
-
09-27-2009, 08:08 AM #1WHT Addict
- Join Date
- Mar 2006
- Posts
- 160
PathPing
Hey,
I was wondering if someone could take a look at the following pathping as I am in need to some independent advice to if it indicates any problems and if so, where?
N.B the traceroute does not ever get to the actual final IP (I am guessing it gets blocked when it enters their internal net) although connection is still possible with VERY high latency (Last time I checked)
Reason I am asking is I keep getting pinged around saying it is someone else's fault, etc.
Code:Tracing route to --removed for privacy-- [--removed for privacy--] over a maximum of 30 hops: 0 TOM-WORKSTATION.HOME.NET [192.168.2.30] 1 efw.home.net [192.168.2.15] 2 router01.dsl.home.net [192.168.1.254] 3 92.20.32.1 4 92.31.253.96 5 xe-11-2-0-scr001.log.as13285.net [78.144.2.3] 6 Opal-ge-2.2.0.mpr1.lhr3.above.net [213.161.78.213] 7 ldn-b3-link.telia.net [213.248.101.105] 8 ldn-bb2-link.telia.net [80.91.249.177] 9 prs-bb2-pos6-0-0.telia.net [213.248.65.114] 10 prs-b1-link.telia.net [80.91.250.249] 11 prs-tc-i1-link-telia.net [80.91.250.30] 12 * * * Computing statistics for 275 seconds... Source to Here This Node/Link Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address 0 TOM-WORKSTATION.HOME.NET [192.168.2.30] 0/ 100 = 0% | 1 0ms 0/ 100 = 0% 0/ 100 = 0% efw.home.net [192.168.2.15] 0/ 100 = 0% | 2 1ms 0/ 100 = 0% 0/ 100 = 0% router01.dsl.home.net [192.168.1.254] 0/ 100 = 0% | 3 43ms 0/ 100 = 0% 0/ 100 = 0% 92.20.32.1 0/ 100 = 0% | 4 44ms 0/ 100 = 0% 0/ 100 = 0% 92.31.253.96 0/ 100 = 0% | 5 --- 100/ 100 =100% 100/ 100 =100% xe-11-2-0-scr001.log.as13285.net [78.144.2.3] 0/ 100 = 0% | 6 49ms 0/ 100 = 0% 0/ 100 = 0% Opal-ge-2.2.0.mpr1.lhr3.above.net [213.161.78.213] 0/ 100 = 0% | 7 48ms 0/ 100 = 0% 0/ 100 = 0% ldn-b3-link.telia.net [213.248.101.105] 0/ 100 = 0% | 8 48ms 0/ 100 = 0% 0/ 100 = 0% ldn-bb2-link.telia.net [80.91.249.177] 0/ 100 = 0% | 9 54ms 0/ 100 = 0% 0/ 100 = 0% prs-bb2-pos6-0-0.telia.net [213.248.65.114] 0/ 100 = 0% | 10 51ms 0/ 100 = 0% 0/ 100 = 0% prs-b1-link.telia.net [80.91.250.249] 100/ 100 =100% | 11 --- 100/ 100 =100% 0/ 100 = 0% prs-tc-i1-link-telia.net [80.91.250.30] Trace complete.
TomLast edited by Tomdarkness; 09-27-2009 at 08:12 AM.
-
09-27-2009, 08:12 AM #2Web Hosting Master
- Join Date
- Jun 2004
- Posts
- 1,961
Are you having any issues?
I'm guessing everything is fine but their routers will block ICMP traffic or treat it as a very low priority.It's Scott!
-
09-27-2009, 08:16 AM #3WHT Addict
- Join Date
- Mar 2006
- Posts
- 160
High latency (i.e 1000/2000ms) + connections being dropped under higher than normal traffic (TCP traffic).
I've contacted the people who operate the server I am trying to connect to and they say its my ISP (refering to part 5 of my pathping as it drops all the packets there) but my ISP say they don't have any problems.
-
09-28-2009, 04:46 PM #4Newbie
- Join Date
- Jan 2008
- Location
- Montreal, Canada
- Posts
- 8
Give it a try from a different ISP and see what happens. You can always try sites that provide you the ability to traceroute a host from the web.
-
09-28-2009, 06:56 PM #5******* Unleaded
- Join Date
- Feb 2004
- Posts
- 3,849
"under higher than normal tcp traffic"
have them check the cpu load on all networking equipment in front of your server.
dropping at the adsl interface on a home connection is perfectly normal as it transitions from ppoe is perfectly normal and expectededgedirector.com
managed dns global failover and load balance (gslb)
exactstate.com
uptime report for webhostingtalk.com