General discussion

Locked

cisco routing question

By dgbaum ·
I have two locations remote and main. At both locations we have a cisco 2500 router, they are connected with a Point-to-Point T1 running HDLC. Both locations have public ip address. The main location has a connection to the Internet through a T1 that is running PPP. I have setup routes in both routers to let the remote location gain access to the internet through the main location. From the outside(Internet) I am able to get all the way to the remote network through telnet sessions and ping and traceroute's. From the remote's network and router I am unable to get past the main locations router, I am unable to get out to the internet. Any Suggestions.

This conversation is currently closed to new comments.

8 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

cisco routing question

by beecee In reply to cisco routing question

can you post your routes in a way that I would be able to understand which goes where?
ex;
internet
|
Firewall (what type, access list statements, ip address)
|
Router 1 (routes, ip address, mask)
|
Router 2 (routes, ip address, mask)

Please do not use your real ip address, just please stick to class)

Collapse -

cisco routing question

by dgbaum In reply to cisco routing question

I would like to think everyone for their responses, but it turns out that it was a private ip address on one of the interfaces that was causing the problem.

Again thanks for all the responses.

Collapse -

cisco routing question

by McKayTech In reply to cisco routing question

It's hard to offer a specific answer without the specific detail of the router configurations. If you wanted to share that information with me off-the-list, I would be glad to take a look at it.

That having been said, what you are seeing sounds like an access-list problem rather than a routing problem. Since the traffic from the remote site is getting to the main site and the main site knows the way to the Internet, it doesn't sound like a routing issue to me. That could also explain why you can get to the remote site from the Internet and not vice versa.

So I think I would start with the access-lists and go from there.

paul

Collapse -

cisco routing question

by dgbaum In reply to cisco routing question

I would like to think everyone for their responses, but it turns out that it was a private ip address on one of the interfaces that was causing the problem.

Again thanks for all the responses.

Collapse -

cisco routing question

by McKayTech In reply to cisco routing question

It also just occurred to me that one really piece of useful information would be how the pings fail when you ping from the remote site towards the Internet. Do they fail with "Destination net unavailable" or do they fail in some other way? That may be an even faster way to tell whether it's a routing problem or access-list problem.

paul

Collapse -

cisco routing question

by dgbaum In reply to cisco routing question

I would like to think everyone for their responses, but it turns out that it was a private ip address on one of the interfaces that was causing the problem.

Again thanks for all the responses.

Collapse -

cisco routing question

by dgbaum In reply to cisco routing question

I would like to think everyone for their responses, but it turns out that it was a private ip address on one of the interfaces that was causing the problem.

Again thanks for all the responses.

Collapse -

cisco routing question

by dgbaum In reply to cisco routing question

This question was closed by the author

Back to Networks Forum
8 total posts (Page 1 of 1)  

Related Discussions

Related Forums