Welcome to the MacNN Forums.

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

You are here: MacNN Forums > Enthusiast Zone > Networking > What would cause all traceroutes to fail after the first hop?

What would cause all traceroutes to fail after the first hop?
Thread Tools
Clinically Insane
Join Date: Oct 2000
Location: Los Angeles
Status: Offline
Reply With Quote
Jan 31, 2009, 10:02 PM
 
Can anyone tell me what would cause all traceroutes on my connection to fail after the first hop, which is to my router? Everything else, such as pings, browsing and torrents, work properly. Is my router misconfigured in some way, or is it an ISP issue?

"The natural progress of things is for liberty to yield and government to gain ground." TJ
     
Administrator
Join Date: Apr 2001
Location: San Antonio TX USA
Status: Offline
Reply With Quote
Feb 1, 2009, 10:00 AM
 
I'm assuming you're still connecting, even though traceroute doesn't show you how?
Glenn -----
OTR/L, MOT, Tx
     
Big Mac  (op)
Clinically Insane
Join Date: Oct 2000
Location: Los Angeles
Status: Offline
Reply With Quote
Feb 2, 2009, 12:30 AM
 
Yeah, all Internet services work fine, but traceroutes fail.

"The natural progress of things is for liberty to yield and government to gain ground." TJ
     
Clinically Insane
Join Date: Mar 2001
Location: yes
Status: Offline
Reply With Quote
Feb 2, 2009, 07:29 AM
 
Are you permitting ICMP traffic? Are you using an IP address or FQDN?
     
Big Mac  (op)
Clinically Insane
Join Date: Oct 2000
Location: Los Angeles
Status: Offline
Reply With Quote
Feb 3, 2009, 03:26 AM
 
ICMP traffic seems to be functioning because pings work fine. It's just the traceroutes that fail after my Netgear router receives them. I'm trying to traceroute IP addresses.

"The natural progress of things is for liberty to yield and government to gain ground." TJ
     
Clinically Insane
Join Date: Mar 2001
Location: yes
Status: Offline
Reply With Quote
Feb 3, 2009, 07:16 AM
 
If the traceroute is to an IP outside of your LAN, perhaps this IP is blocking ICMP traffic? Traceroutes aren't really definitive diagnostic tools for this reason.
     
Big Mac  (op)
Clinically Insane
Join Date: Oct 2000
Location: Los Angeles
Status: Offline
Reply With Quote
Feb 3, 2009, 04:17 PM
 
Interesting. The thing is, I can't get a single traceroute to complete, no matter which IP address I choose. I guess I should direct connect to my modem and try to see if it's my ISP or router (most likely the latter, obviously).

"The natural progress of things is for liberty to yield and government to gain ground." TJ
     
Big Mac  (op)
Clinically Insane
Join Date: Oct 2000
Location: Los Angeles
Status: Offline
Reply With Quote
Mar 10, 2009, 05:15 PM
 
Eureka! I found the answer. My router's old firmware was to blame.

"The natural progress of things is for liberty to yield and government to gain ground." TJ
     
   
Thread Tools
Forum Links
Forum Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On
Top
Privacy Policy
All times are GMT -5. The time now is 09:54 PM.
All contents of these forums © 1995-2011 MacNN. All rights reserved.
Branding + Design: www.gesamtbild.com
vBulletin v.3.8.7 © 2000-2011, Jelsoft Enterprises Ltd., Content Relevant URLs by vBSEO 3.3.2