Ok, what would cause this?

From my main location (where the firewall is and all our T-1's get
routed to each other, etc), if I trace a route to www.yugma.com, it
goes some 17 hops before timing out & I figure that's due to some
routers out on the 'net having ping blocked.

If I trace a route from a remote network (part of my WAN, behind same
firewall, etc), it goes like this:

x.x.x.x (remote network default gateway)
y.y.y.y (WAN side of my main router)
z.z.z.z (main route out to the net)

Remote sites time out as soon as they leave our network out the

What gives?