Web Service calls Blocked in Flash Player 9/10

Question

This is a common issue, so if someone knows of a thread that would help, please point me in the right direction. I was unable to find an exact match on my own.
The project:
I've created a video player which contacts a web service on a remote machine. It retreives a user's viewing progress, reports it back to the player, and advances them to their last location. Testing this locally from within the Flash IDE works fine, as do other web services (such as the ones found on webservicex.net). I'm using the as3webservice package from wellconsidered (http://code.google.com/p/as3webservice/) which has worked flawlessly in testing so far.
The issue:
When finally uploading the swf to a remote server (which is NOT the same as the one that hosts the web service) the web service hangs; not generating a fault, but basically not connecting at all (appears to be hanging/timing out). Research led me to create a crossdomain.xml policy file, which I uploaded to the root and subdirecctories of the machine hosting the webservice:
<cross-domain-policy>
<allow-access-from domain="*"/>
</cross-domain-policy>
This is the one used by most services, including public ones like webservicex.net. Creating this file (named crossdomain.xml) and uploading it did not help at all. I also noticed that when testing the public web service for contrast, they didn't connect either.
I found another article which led me to believe that the cross domain xml file needs to be modified for new security rules in Flash Player 9/10 - This article applies to Flex, but i'm assuming Flash Player is Flash Player:
http://blog.flexmonkeypatches.com/2008/09/29/flex-waylaid-by-webservices-and-flash-player- security-changes/
can anyone confirm this is the case, or share an experience/solution with me that falls within the same ballpark? I'm hung up on this and don't know what to tell the server admins/devs that are working with me on this project. They don't know what to do.
Thanks, fred

Answer 1

I don't know that this is a CS4 issue, but in my experience  it's been a for as long as I've used Flash issue...  If you have the same symbol as diffferent instances in adjacent frames but give it a different name in those frames, the latter instance will adapt the name of the preceding one.  Your best bet may be to assign the same name in both frames, though an alternative would be to shift one to a differ layer than the other.
There's still something of the error or your description that makes me wonder, but it's worth seeing if making a change as suggested takes care of things.