|
|
|
|
|||||
|
|
|
|
|
|
|||
| Welcome
to Tech Support Forum home to more then 136,000 problems solved. Issues
have included: Spyware, Malware, Virus Issues, Windows, Microsoft,
Linux, Networking, Security, Hardware, and Gaming Getting your
problem solved is as easy as: 1. Registering for a free account 2. Asking your question 3. Receiving an answer Registered members: * See fewer ads. * And much more..
|
| Want to know how to post a question? click here | Having problems with spyware and pop-ups? First Steps |
|
|||||||
| Networking Support General Networking Support Forum |
 |
|
|
LinkBack | Thread Tools |
04-18-2007, 01:45 PM
|
#1 (permalink) |
|
Registered User
Join Date: Sep 2003
Posts: 15
OS: win2k pro
|
tracert problem
I'm running an XP Pro (SP2) system and am connected via cable dsl.
I'm using a network enhancer application (cfos speed), which relies on icmp information. Whenever I try tracert, I get a report like the following: 1 13 ms 17 ms 19 ms 212.143.17.34 2 * * * Request timed out. 3 * * * Request timed out. 4 * * * Request timed out. I've suspected that the blocking stems from my MS firewall, stopped it, and the situation sustains. How can I solve this problem? What else may block my communication? Ran |
|
     
|
| Important Information |
|
Join the #1 Tech Support Forum Today - It's Totally Free!
TechSupportForum.com is a leading support website for your computer needs. We offer free, friendly and personalized computer support. Why pay to have your computer fixed when you can do it for free. Join TechSupportforum.com Today - Click Here |
|
04-19-2007, 11:53 AM
|
#2 (permalink) |
|
Manager, Networking Forums
Join Date: Sep 2002
Location: S.E. Pennsylvania, US
Posts: 40,965
OS: Windows 7, XP-Pro, Vista, Linux
Blog Entries: 1
|
Re: tracert problem
Your ISP can block them.
Try PATHPING 212.143.17.34 >c:\result.txt Open C:\RESULT.TXT and copy/paste the results here. I'll give it a try here and post my results.
__________________
If TSF has helped you, Tell us about it! or Donate to help keep the site up! Microsoft MVP - Windows Desktop Experience |
|
|
|
|
04-19-2007, 12:01 PM
|
#3 (permalink) |
|
Manager, Networking Forums
Join Date: Sep 2002
Location: S.E. Pennsylvania, US
Posts: 40,965
OS: Windows 7, XP-Pro, Vista, Linux
Blog Entries: 1
|
Re: tracert problem
Here's what I get tracing to that site:
Tracing route to 212.143.17.34 over a maximum of 30 hops 0 MAIN.home [192.168.1.2] 1 ActionTec [192.168.1.1] 2 72.78.224.1 3 P5-2.LCR-01.PHLAPA.verizon-gni.net [130.81.39.6] 4 so-1-3-0-0.BB-RTR1.PHIL.verizon-gni.net [130.81.28.41] 5 0.so-6-0-0.XL1.PHL6.ALTER.NET [152.63.3.77] 6 0.so-7-0-0.XL3.NYC4.ALTER.NET [152.63.10.21] 7 POS6-0.IG5.NYC4.ALTER.NET [152.63.35.29] 8 netvision2-gw.customer.alter.net [157.130.25.38] 9 pos4-4.core1.hfa.nv.net.il [212.143.12.34] 10 vl200.coresw1.hfa.nv.net.il [212.143.8.195] 11 fe0-1.edge04.hfa.nv.net.il [212.143.8.6] 12 212.143.157.214 13 * * * Computing statistics for 325 seconds... Source to Here This Node/Link Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address 0 MAIN.home [192.168.1.2] 0/ 100 = 0% | 1 0ms 0/ 100 = 0% 0/ 100 = 0% ActionTec [192.168.1.1] 0/ 100 = 0% | 2 4ms 0/ 100 = 0% 0/ 100 = 0% 72.78.224.1 0/ 100 = 0% | 3 4ms 0/ 100 = 0% 0/ 100 = 0% P5-2.LCR-01.PHLAPA.verizon-gni.net [130.81.39.6] 0/ 100 = 0% | 4 7ms 0/ 100 = 0% 0/ 100 = 0% so-1-3-0-0.BB-RTR1.PHIL.verizon-gni.net [130.81.28.41] 0/ 100 = 0% | 5 6ms 0/ 100 = 0% 0/ 100 = 0% 0.so-6-0-0.XL1.PHL6.ALTER.NET [152.63.3.77] 0/ 100 = 0% | 6 12ms 0/ 100 = 0% 0/ 100 = 0% 0.so-7-0-0.XL3.NYC4.ALTER.NET [152.63.10.21] 0/ 100 = 0% | 7 8ms 0/ 100 = 0% 0/ 100 = 0% POS6-0.IG5.NYC4.ALTER.NET [152.63.35.29] 0/ 100 = 0% | 8 12ms 0/ 100 = 0% 0/ 100 = 0% netvision2-gw.customer.alter.net [157.130.25.38] 0/ 100 = 0% | 9 --- 100/ 100 =100% 100/ 100 =100% pos4-4.core1.hfa.nv.net.il [212.143.12.34] 0/ 100 = 0% | 10 --- 100/ 100 =100% 100/ 100 =100% vl200.coresw1.hfa.nv.net.il [212.143.8.195] 0/ 100 = 0% | 11 --- 100/ 100 =100% 100/ 100 =100% fe0-1.edge04.hfa.nv.net.il [212.143.8.6] 0/ 100 = 0% | 12 156ms 0/ 100 = 0% 0/ 100 = 0% 212.143.157.214 100/ 100 =100% | 13 --- 100/ 100 =100% 0/ 100 = 0% MAIN [0.0.0.0] Trace complete.
__________________
If TSF has helped you, Tell us about it! or Donate to help keep the site up! Microsoft MVP - Windows Desktop Experience |
|
|
|
|
04-19-2007, 01:28 PM
|
#4 (permalink) |
|
Registered User
Join Date: Sep 2003
Posts: 15
OS: win2k pro
|
Re: tracert problem
Thanks for your suggestions.
I would appreciate receiving a pathping report from any site (meaning starting from any of your systems) to my ip, which is currently 194.90.167.19 (Since this is a dynamic ip, and since I may have to reboot, getting a new address, please do it asap). This way I'll be able to where incoming icmp signals get trapped. Ran |
|
|
|
|
04-20-2007, 02:47 PM
|
#5 (permalink) |
|
Manager, Networking Forums
Join Date: Sep 2002
Location: S.E. Pennsylvania, US
Posts: 40,965
OS: Windows 7, XP-Pro, Vista, Linux
Blog Entries: 1
|
Re: tracert problem
I'm doing that now, but note that this is going to be PINGS in the other direction.
 I'll post when it completes.
__________________
If TSF has helped you, Tell us about it! or Donate to help keep the site up! Microsoft MVP - Windows Desktop Experience |
|
|
|
|
04-20-2007, 02:52 PM
|
#6 (permalink) |
|
Manager, Networking Forums
Join Date: Sep 2002
Location: S.E. Pennsylvania, US
Posts: 40,965
OS: Windows 7, XP-Pro, Vista, Linux
Blog Entries: 1
|
Re: tracert problem
C:\>pathping 194.90.167.19
Tracing route to 194.90.167.19 over a maximum of 30 hops 0 MAIN.home [192.168.1.2] 1 ActionTec [192.168.1.1] 2 72.78.224.1 3 P5-2.LCR-02.PHLAPA.verizon-gni.net [130.81.39.40] 4 so-7-0-0-0.ASH-PEER-RTR2.verizon-gni.net [130.81.17.179] 5 ge11-9.br02.ash01.pccwbtn.net [63.218.94.169] 6 netvision.ge4-4.br01.nyc01.pccwbtn.net [63.218.9.2] 7 pos4-2.core1.hfa.nv.net.il [212.143.12.21] 8 vl200.coresw1.hfa.nv.net.il [212.143.8.195] 9 fe0-1.edge04.hfa.nv.net.il [212.143.8.6] 10 212.143.157.214 11 * * * Computing statistics for 275 seconds... Source to Here This Node/Link Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address 0 MAIN.home [192.168.1.2] 0/ 100 = 0% | 1 0ms 0/ 100 = 0% 0/ 100 = 0% ActionTec [192.168.1.1] 0/ 100 = 0% | 2 4ms 0/ 100 = 0% 0/ 100 = 0% 72.78.224.1 0/ 100 = 0% | 3 4ms 0/ 100 = 0% 0/ 100 = 0% P5-2.LCR-02.PHLAPA.verizon-gni.net [130.81.39.40] 0/ 100 = 0% | 4 13ms 0/ 100 = 0% 0/ 100 = 0% so-7-0-0-0.ASH-PEER-RTR2.verizon-g ni.net [130.81.17.179] 0/ 100 = 0% | 5 16ms 0/ 100 = 0% 0/ 100 = 0% ge11-9.br02.ash01.pccwbtn.net [63. 218.94.169] 0/ 100 = 0% | 6 14ms 0/ 100 = 0% 0/ 100 = 0% netvision.ge4-4.br01.nyc01.pccwbtn .net [63.218.9.2] 100/ 100 =100% | 7 --- 100/ 100 =100% 0/ 100 = 0% pos4-2.core1.hfa.nv.net.il [212.14 3.12.21] 0/ 100 = 0% | 8 --- 100/ 100 =100% 0/ 100 = 0% vl200.coresw1.hfa.nv.net.il [212.1 43.8.195] 0/ 100 = 0% | 9 --- 100/ 100 =100% 0/ 100 = 0% fe0-1.edge04.hfa.nv.net.il [212.14 3.8.6] 0/ 100 = 0% | 10 --- 100/ 100 =100% 0/ 100 = 0% 212.143.157.214 0/ 100 = 0% | 11 --- 100/ 100 =100% 0/ 100 = 0% MAIN [0.0.0.0] Trace complete.
__________________
If TSF has helped you, Tell us about it! or Donate to help keep the site up! Microsoft MVP - Windows Desktop Experience |
|
|
|
|
04-21-2007, 02:42 AM
|
#7 (permalink) |
|
Registered User
Join Date: Sep 2003
Posts: 15
OS: win2k pro
|
Re: tracert problem
Thank you Johnwill.
The picture now looks quite clear. Your pings reach my isp in address 212.143.157.214. The route to my own computer is blocked! Too bad. I'll check with my isp (Unfortunately, it's not even MY isp. I'm a staff member in a university and my institution subcontract a partial service plan from this national isp). Thanks again. Ran |
|
|
|
|
04-21-2007, 11:26 AM
|
#8 (permalink) |
|
Manager, Networking Forums
Join Date: Sep 2002
Location: S.E. Pennsylvania, US
Posts: 40,965
OS: Windows 7, XP-Pro, Vista, Linux
Blog Entries: 1
|
Re: tracert problem
I suspect it may be the university's firewall that's the issue.
__________________
If TSF has helped you, Tell us about it! or Donate to help keep the site up! Microsoft MVP - Windows Desktop Experience |
|
|
|
|
| Thread Tools | |
|
|
