Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

TRACERT = request time out

Status
Not open for further replies.

pbxphoneman

Technical User
Oct 4, 2002
104
when I do a tracert to the internet from a remote LAN PC,(across a t1 to the main LAN then out to the internet Via a DSL router) I get "request time out" I see about 30 hops of this.If I tracert to the DSL router I "see" how it gets to the router with no problem.If I do a tracert to another PC even if it's unplugged,I at least see on where it fails along the way.
I have my default gateway for this remote PC pointing at the T1 router,so the data should be moved off it's subnet.I have no problem with talking to the main LAN from this computer...it's just to the DSL router.
question..I think my routing is correct other wise I won't get a ping response back fron the DSL router..but why am I getting "request time out" from it when I TRACERT? (to the DSL router)...it looks like it's not even trying to get off it's subnet.It sure knows how to TRACERT across the T1 to the other machines with no problem.I don't get to see where the tracert fails.The ROUTE PRINT command tells me 0.0.0.0 / 0.0.0.0 / 192.168.1.100 (the T1 router gateway) that should send the internet request at least to it's T1 router,right?I would think have thought TRACERT would show me where the data journey failed when I tryed to trace into the internet. maybe a default route missing somewhere? here's a snap of my small network, thanks for the help
T
 
look for a router setting in the DSL router to allow you to be pingable. that may let ICMP packets get back in your network from the internet

I tried to remain child-like, all I acheived was childish.
 
You have a statement in your question saying you get ping responses back from the DSL router, is this the 192.168.254.254 router in your drawing?? If ping works, there should be no reason that tracert doesn't. Anyway, I am not sure what the problem is from your description but remember that routing needs to be configured in both directions, you may be able to get to the DSL router but that doesn't mean the router knows how to get back to you. I would make sure that the DSL router knows that the 192.168.1 network exist through gateway 192.168.254.100. Hope this helps

Brian
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top