Tracert not working

S

S.Penttila

My problem is, that tracert command doesn't work correctly. Here is
what i get:

Tracing route to host google.fi [66.102.9.104]

1 * * * Connection timeout
2 * * * Connection timeout
3 * * * Connection timeout
4 * * * Connection timeout
5 * * * Connection timeout
and so on...

Works fine on my friends computers. I really need that feature
sometimes. If no one here know ho to fix that, please direct me to
other newsgroupt / forum where i might get an answer.
 
Y

Yves Leclerc

Check firewall(s), either the XP one or other. Change or create an exception
rule to the firewall. You also need to check to see if your ISP is also
adding a firewall, or service block, to your access. Several ISPs now only
allow "standard" IP services (web, smtp, imap etc..) thru.



My problem is, that tracert command doesn't work correctly. Here is
what i get:

Tracing route to host google.fi [66.102.9.104]

1 * * * Connection timeout
2 * * * Connection timeout
3 * * * Connection timeout
4 * * * Connection timeout
5 * * * Connection timeout
and so on...

Works fine on my friends computers. I really need that feature
sometimes. If no one here know ho to fix that, please direct me to
other newsgroupt / forum where i might get an answer.
 
S

S.Penttila

Yves said:
Check firewall(s), either the XP one or other. Change or create an exception
rule to the firewall. You also need to check to see if your ISP is also
adding a firewall, or service block, to your access. Several ISPs now only
allow "standard" IP services (web, smtp, imap etc..) thru.

Firewalls aren't causing this. Also my friends use same ISP without any
problems.
 
L

LittleMoo

Firewalls aren't causing this. Also my friends use same ISP without any
problems.

Is your firewall set to allow ICMP traffic?
Have you tried completely disabling your firewall and use tracert just to
make sure. If so...

Then can you tracert your loopback (127.0.0.1) successfully?
Does ping work?

The only reason I ask is because tracert is not even to get to the next node
after your computer. So this leads me to believe that there is something on
your computer that is preventing it from accessing anything outside of your
computer. So the first step here is to make sure that the firewall isn't the
issue, and the only way to truely know if the firewall isn't the problem is
to completely disable your firewall (either exit it or allow all traffic)
and then try tracert.

-Dan
 
S

S.Penttila

Is your firewall set to allow ICMP traffic?
Have you tried completely disabling your firewall and use tracert just to
make sure. If so...

Then can you tracert your loopback (127.0.0.1) successfully?
Does ping work?

The only reason I ask is because tracert is not even to get to the next node
after your computer. So this leads me to believe that there is something on
your computer that is preventing it from accessing anything outside of your
computer. So the first step here is to make sure that the firewall isn't the
issue, and the only way to truely know if the firewall isn't the problem is
to completely disable your firewall (either exit it or allow all traffic)
and then try tracert.

-Dan

I've tried it without firewall, didn't help. Ping works fine to any
address. Also tracerto to 127.0.0.1 gives
1 <1 ms <1 ms <1 ms localhost [127.0.0.1]
So it works.
 
S

S.Penttila

Is your firewall set to allow ICMP traffic?
Have you tried completely disabling your firewall and use tracert just to
make sure. If so...

Then can you tracert your loopback (127.0.0.1) successfully?
Does ping work?

The only reason I ask is because tracert is not even to get to the next node
after your computer. So this leads me to believe that there is something on
your computer that is preventing it from accessing anything outside of your
computer. So the first step here is to make sure that the firewall isn't the
issue, and the only way to truely know if the firewall isn't the problem is
to completely disable your firewall (either exit it or allow all traffic)
and then try tracert.

-Dan

I've tried it without firewall, didn't help. Ping works fine to any
address. Also tracerto to 127.0.0.1 gives
1 <1 ms <1 ms <1 ms localhost [127.0.0.1]
So it works.
 
L

LittleMoo

Is your firewall set to allow ICMP traffic?
Have you tried completely disabling your firewall and use tracert just to
make sure. If so...

Then can you tracert your loopback (127.0.0.1) successfully?
Does ping work?

The only reason I ask is because tracert is not even to get to the next
node
after your computer. So this leads me to believe that there is something
on
your computer that is preventing it from accessing anything outside of
your
computer. So the first step here is to make sure that the firewall isn't
the
issue, and the only way to truely know if the firewall isn't the problem
is
to completely disable your firewall (either exit it or allow all traffic)
and then try tracert.

-Dan

I've tried it without firewall, didn't help. Ping works fine to any
address. Also tracerto to 127.0.0.1 gives
1 <1 ms <1 ms <1 ms localhost [127.0.0.1]
So it works.

Well we know that tracert at least works to some extent, seeing as you can
get a response from running it successfully on your loopback.
But since you can't tracert anywhere outside of that it makes me think that
either:
A) If you are behind a router then maybe your router isn't set up to allow
ICMP traffic, in which case you would need to read the manual for your
router to see how to enable it.
B) If you are behind a router and it has a built in firewall then maybe
somehow it is blocking tracert, in which case you would need to disable your
routers firewall, or set it to allow all internet traffic. Also it would be
good to try directly connecting your modem to your computer and completely
remove your router from the equation to rule it out.
C) It is possible that your ISP blocks tracert or ICMP traffic in general,
and for this you would need to contact your ISP and find out if they block
it. If they do block it then you might have to resort to using some other
tatic.

Other tatics:
Web traceroute: http://www.traceroute.org/#USA - the only downside to this
is that it performs the traceroute from the server that is used and the
endpoint (but this would be a handy tool to find out if your ISP blocks ICMP
traffic or tracert as you could traceroute to your IP address and if it
times out then you know that this is the case).

Other traceroute programs: you can try 3d Traceroute - http://www.d3tr.de/ -
the only downside is that the graph is kind of messy, but if this works then
you'll at least be able to look at the hops. There are other traceroute
programs out there, but probably not too many of them are free so you'll
have to do a little digging. And if this works without changing anything
else then something is either wrong with tracert in XP or somehow it's still
being blocked on your computer.

-Dan
 
S

S.Penttila

Well we know that tracert at least works to some extent, seeing as you can
get a response from running it successfully on your loopback.
But since you can't tracert anywhere outside of that it makes me think that
either:
A) If you are behind a router then maybe your router isn't set up to allow
ICMP traffic, in which case you would need to read the manual for your
router to see how to enable it.
B) If you are behind a router and it has a built in firewall then maybe
somehow it is blocking tracert, in which case you would need to disable your
routers firewall, or set it to allow all internet traffic. Also it would be
good to try directly connecting your modem to your computer and completely
remove your router from the equation to rule it out.
C) It is possible that your ISP blocks tracert or ICMP traffic in general,
and for this you would need to contact your ISP and find out if they block
it. If they do block it then you might have to resort to using some other
tatic.

-Dan

I disabled my router firewall, did not help. I couldn't find any
settings concerning ICMP traffic, but i'll try connectin directly to
computer as you suggested so that we can eliminate router from possible
reasons.
As I said before, my friends use same ISP and have no problem
tracerting, so they're not blocking anything.
I used first page you mentioned to tracert myself, and after 5
succesfull hops connection started to timeout. So i guess my computer
didn't answer to that tracert for some reason. Also i can't even ping
myself. Gonna get that router out of the way later.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top