Routing Issues - Trouble trace/pinging

Ok, just added a mlppp circuit into our existing inet router.  We've got three different carriers going into this router now, each exchanging full bgp tables.  I'm running into issues where SOME machines outside of my network can't ping or trace to my new multilink interface.  I can get to the next hop router, but can't seem to get to mine.  Some places it works, though.  It's my belief that there's no route back, as when I add a static route to the pinger's network, I get a response everytime.

Is there something I'm missing?  Packets making it to my router are possibly routing out a different interface?  Checked static routes and acls and there's no problem there (we have 1 static route and 3 acls, so pretty simple).

Any help for a BGP noob?

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.

Did you bind your BGP to a loopback or the physical interfaces?
cory_spenceAuthor Commented:
Not sure.  I'm not utilizing loopback interfaces, so I assume it binds to the physical by default?  Any way to check?

Post your BGP config
Your Guide to Achieving IT Business Success

The IT Service Excellence Tool Kit has best practices to keep your clients happy and business booming. Inside, you’ll find everything you need to increase client satisfaction and retention, become more competitive, and increase your overall success.

cory_spenceAuthor Commented:
Just spoke to Cisco.  The guy sounded like a noob just like me, but he said my config is ok - for whatever that is worth.  

router bgp (my as)
 no synchronization
 bgp log-neighbor-changes
 network 192.x.x.x
 network 199.x.x.x
 neighbor att_ip remote-as (att as)
 neighbor att_ip route-map ADVERTISE out
 neighbor qwest_ip remote-as (qwest as)
 neighbor qwest_ip route-map ADVERTISE out
 neighbor broadwing_ip remote-as (broadwing as)
 neighbor broadwing_ip route-map ADVERTISE out
no auto-summary

access-list 99 permit 192.x.x.x
access-list 99 permit 199.x.x.x

route-map ADVERTISE permit 10
 match ip address 99
cory_spenceAuthor Commented:

Naser GabajE&P Senior Software SpecialistCommented:
No comment has been added to this question in more than 21 days, so it is now classified as abandoned.

I will leave the following recommendation for this question in the Cleanup topic area:
   PAQ with points refunded

Any objections should be posted here in the next 4 days. After that time, the question will be closed.

EE Cleanup Volunteer
PAQed with points (500) refunded

Community Support Moderator

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
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
Network Analysis

From novice to tech pro — start learning today.