tracert not working

Posted on 2007-09-28
Last Modified: 2012-05-05
From my home PC (Windows XP), I tried 'tracert' to outbound.

It is goes through fine.  Of course, I can get onto Internet.


Tracing route to []
over a maximum of 30 hops:

  1    10 ms     6 ms     7 ms
  2     9 ms     7 ms     7 ms
 17    35 ms    40 ms    46 ms
 18    34 ms    73 ms    34 ms []

Trace complete.

But, when I tried 'tracert' from outside to my home PC,


Tracing route to []
over a maximum of 30 hops:


 21    19 ms    13 ms    13 ms  []
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.

As you can see, 'request timed out' occurs right after
That is the IP
What is the the IP (  Is there a way to ping from outside to my home PC?
My guess is Remote Desktop is not working because of the block at
Any ideas, please?

Please see for more details.

On my home pc:
- no firewall in place
- symantec virus software installed
- Remote Desktop Connection 6.0 client update applied
- NVIDIA service not running

thx much
Question by:ethanjohnsons
    LVL 9

    Expert Comment

    First off your breaking rules by double posting.

    Second you are getting replies on the other post and they are all good replies and suggestions.

    You need the port forwarding setup.  Are you using a static ip address from comcast?  if so you need to apply that address to the wan side of your router and then apply a private ip to the lan side of router and a private in the same subnet to your pc.  then you need to forward from the public address on the wan interface to the private on the lan interface and off to your pc.
    LVL 9

    Accepted Solution

    all that means that the router at doesnt allow ICMP to pass thru. If you have access to it you can enable ICMP and that will let you ping your PC
    LVL 2

    Assisted Solution

    From outside, are you behind a firewall ? if so for example a fire will not allow a ping through. so the forward ping packet is OK and reply is not allowed. also remember tracert consist of echo echo reply and time exceed. so say if ech reply is not allowed then you will have an issue.

    so in short just because you can't ping an ip dose not mean that it is down.

    Featured Post

    Scale it in WD Gold

    With up to ten times the workload capacity of desktop drives, WD Gold hard drives employ advanced technology to deliver among the best in reliability, capacity, power efficiency and performance.

    Join & Write a Comment

    Quality of Service (QoS) options are nearly endless when it comes to networks today. This article is merely one example of how it can be handled in a hub-n-spoke design using a 3-tier configuration.
    Is your computer hacked? learn how to detect and delete malware in your PC
    After creating this article (, I decided to make a video (no audio) to show you how to configure the routers and run some trace routes and pings between the 7 sites…
    Here's a very brief overview of the methods PRTG Network Monitor ( offers for monitoring bandwidth, to help you decide which methods you´d like to investigate in more detail.  The methods are covered in more detail in o…

    732 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    17 Experts available now in Live!

    Get 1:1 Help Now