I have a Point-to- point T1 router on my LAN that goes to a remote computer LAN (2 computers) about 1500ft away.On my LAN I have a bunch of computers and DSL access on it.everything works fine and I can reach my remote LAN and it can reach me for file access and what not...BUT
  It can't access my DSL router,so it can have internet access too.There are no filters turned on denying it anything.The remote computer LAN can ping and tracert just fine to every machine on my LAN...except the DSL router,ping replys are "request timed out".Is this normal for a router not to show it's self unless a route or gateway is "pointed" at it?I have a feeling I need to define something else in my remote T1 router.
 any suggestions will be great!!!

I think the suggestion you got in the other forum was probably your best lead.  Did you enter a static route on your DSL router pointing towards your remote network?  If not, you need to.  If you can't, you have problems.    

I think the suggestion you got in the other forum was probably your best lead.  Did you enter a static route on your DSL router pointing towards your remote network?  If not, you need to.  If you can't, you have problems.    

there are a ton of adjustments on the router,but I did not define a route to the remote network.I kind of figured that since this dsl router has a LAN address on the same subnet as all the other machines that it would be "pingable" thus be accessable to the remote LAN...I will play with the setting in the DSL router...thank you for your input!!

Not sure I understood that.  Your setup:?

ISP -> DSL Router -> LAN -> local router -> remote router -> remote LAN

If so, the subnet of the remote network can't be the same as the local network.  So there must be something I'm not understanding.  If I do have it right, your DSL router either needs a static route to the remote subnet or it needs a routing protocol peered with the remote router (almost an impossibility -- ISPs don't usually let you run routing protocols on DSL routers).

Maybe we're just looking at this differently.  Your remote hosts can hit the DSL router with ICMP Echo Requests (presumably you have a default route or a static route defined on your remote router).  The problem is one of ICMP Echo Replies.  Without a route entry, the DSL router can't respond.  Just because the Echo Request shows up on an interface doesn't mean that the router knows to respond correctly.  It has to do a route lookup.