Allow External Access From Multiple Internal Subnets Cisco ASA

We have a Cisco ASA 5505 at our main site. We have a remote site that connectes back to the main site via a carrier router. The carrier router at the main site is connected to the internal interface of our ASA. The local subnet is 192.168.10.x and the remote subnet is 192.168.31.x. We can access the outside interface and gain Internet access from the local subnet, 192.168.10.x. However, the remote site, 192.168.31.x is unable to access the internet. We can ping a workstation at the remote site and the workstation at the remote site can ping the internal interface of the ASA but the workstation at the remote site cannot ping any devices beyond that. I can post the config of the ASA or answer any questions to clarify the issue.
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Fred MarshallPrincipalCommented:
I'm not sure what a "carrier router" is but the main site "carrier router" would need a route to that points to the internet gateway which appears to be the ASA.
And, the internet gateway (the ASA) needs a route: to (the "carrier router" on the main LAN)

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
abacustechnologyAuthor Commented:
Ill Clarify. The "carrier router" is the router provided by the ISP. I have checked with them and they have told me the route you reference above is correct. I also have the second route referenced above configured on the ASA.
Henk van AchterbergSr. Technical ConsultantCommented:
did you put the route on the same interface as the lan (inside)?
abacustechnologyAuthor Commented:
We went back to the ISP for a second time. We got the right tech this time that was able to correct the default route on their equipment. Problem solved.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Hardware Firewalls

From novice to tech pro — start learning today.